A communication method and apparatus

By sending a message indicating the architecture type in store-and-forward mode to the terminal device via satellite, the problem of invalid signaling interaction caused by the terminal device's inability to determine the satellite architecture is solved, thus achieving efficient resource utilization and optimized signaling interaction.

CN123074549APending Publication Date: 2026-11-10HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202510585421.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-05-07
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

In the store-and-forward mode of IoT NTN networks, terminal devices cannot determine the satellite architecture type, leading to invalid signaling interactions and wasted resources.

Method used

The first message, containing indication information, is sent from the satellite to the terminal device, indicating the satellite's architecture type in store-and-forward mode. The terminal device then performs corresponding operations based on this information, avoiding invalid signaling interactions.

Benefits of technology

This reduces resource waste, improves the efficiency of signaling interaction, and ensures that NAS processes are handled reasonably under different architecture types.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074549A_ABST
    Figure CN123074549A_ABST
Patent Text Reader

Abstract

The application provides a communication method, in which a terminal device receives a first message including first indication information sent by a satellite, the first indication information indicating a corresponding architecture type of the satellite in a store-and-forward mode, the architecture type referring to a network element architecture of a core network deployed on the satellite, and a feeder link between the satellite and a ground network being in a disconnected state in the store-and-forward mode. In this way, after receiving the first message, the terminal device obtains the first indication information by analyzing the first message, thereby learning the architecture type of the satellite in the store-and-forward mode, so as to perform corresponding operations according to the architecture type, thereby avoiding an invalid signaling interaction process caused by unknown architecture type.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

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

[0002] With the increasing global demand for communication, traditional terrestrial networks often struggle to cover remote or underserved areas. To address this, a satellite-to-ground communication technology based on the 5G standard, known as non-terrestrial networks (NTN), has been proposed. This technology aims to provide secure and reliable communication services to areas without terrestrial network coverage via satellite communication. 5G NTN can be further divided into two branches: Internet of Things (IoT) NTN and New Radio (NR) NTN. NR NTN aims to provide high-speed mobile broadband services, while IoT NTN focuses on narrowband, low-speed IoT services, further expanding the connectivity of the IoT through satellite networks.

[0003] In IoT NTN networks, there are two operating modes: store & forward (S&F) and normal. In store & forward mode, when a satellite covers an area, the user equipment (UE) sends data to the satellite. Upon receiving the data, the satellite stores it locally because the connection between the satellite and the ground network (usually the feeder link) is currently disconnected. When the satellite establishes a connection with the ground network, it relays / forwards the previously stored data to the ground network, which then transmits the data to its destination according to the established connection configuration and routing. In normal mode, when a satellite covers an area, the UE directly sends data to the satellite. Upon receiving the data, the satellite transmits it directly to the ground network via its downlink (usually the feeder link). The ground network receives and processes the data before transmitting it to its destination.

[0004] Currently, two architectures have been proposed for store-and-forward mode in NTN networks: Full Core Network (FullCN) and Split Mobility Management Entity (Split MME). In the FullCN architecture, all core network elements are deployed on satellites; in the Split MME architecture, only a portion of the MME's functionality is deployed on satellites, while other core network elements are deployed on terrestrial networks. When the satellite is in store-and-forward mode, these two architectures have different impacts on the UE. Summary of the Invention

[0005] To address the aforementioned issues, this application provides a communication method that enables a terminal device to learn the architecture type of a satellite in store-and-forward mode, allowing the terminal device to perform corresponding operations based on the specific architecture type, thereby reducing the impact on the terminal device.

[0006] Firstly, this application provides a communication method, which can be executed by a terminal device, a component configured in the terminal device (such as a circuit, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. In this communication method, the terminal device receives a first message from a satellite, including first indication information. This first indication information indicates the satellite's architecture type in store-and-forward mode. The architecture type refers to the network element architecture of the core network deployed on the satellite. In store-and-forward mode, the feeder link between the satellite and the ground network is disconnected. Thus, after receiving the first message, the terminal device parses the first message to obtain the first indication information, thereby determining the satellite's architecture type in store-and-forward mode. This allows the terminal device to perform corresponding operations based on the architecture type, avoiding invalid signaling interactions due to a lack of knowledge of the architecture type.

[0007] In one possible implementation, the first message is either a message corresponding to the non-access stratum (NAS) or a message corresponding to the access stratum (AS). That is, the satellite can inform the terminal device of the satellite-side architecture type through NAS layer signaling; it can also inform the terminal device of the satellite-side architecture type through AS layer signaling.

[0008] Specifically, when the first message corresponds to a NAS, it can be a registration acceptance message or a location update acceptance message; when the first message corresponds to an AS, it can be a system information block (SIB) message. The satellite broadcasts the satellite-side architecture type to the terminal device via SIB messages.

[0009] In one possible implementation, if the first message is a registration acceptance message, the terminal device sends a second message to the satellite to request registration before receiving the first message from the satellite. This second message includes second indication information requesting the satellite to inform it of the corresponding architecture type in store-and-forward mode. Upon receiving the second message, the satellite obtains the architecture type of its deployed core network, generates the first message, and sends it to the terminal device.

[0010] In one possible implementation, if the first message is a location update acceptance message, the terminal device sends a third message to the satellite requesting a location update before receiving the first message from the satellite. This third message includes third indication information requesting the satellite to inform it of the corresponding architecture type in store-and-forward mode. After receiving the third message, the satellite obtains the architecture type of its deployed core network, generates the first message, and sends the first message to the terminal device.

[0011] In one possible implementation, after the terminal device learns the architecture type of the satellite, if the satellite is in store-and-forward mode, the terminal device determines whether the NAS process to be executed needs to distinguish the architecture type. If it does not need to distinguish the architecture type, the terminal device directly executes the NAS process. In this implementation, if the NAS process to be executed does not need to distinguish the architecture type, it indicates that in store-and-forward mode, the entire NAS process can be quickly completed through interaction between the terminal device and the satellite.

[0012] If the NAS process to be executed requires differentiation based on the architecture type, the terminal device will determine the processing strategy for the NAS process based on the known architecture type. That is, when the satellite is in store-and-forward mode, due to the disconnection of the feeder link, if the NAS process to be executed requires differentiation based on the architecture type, it indicates that the NAS process requires the participation of network elements of other core networks besides the core network elements deployed on the satellite. Based on this, it is necessary to execute the NAS process using a processing strategy that matches the architecture type for different architecture types to avoid wasting resources.

[0013] Specifically, if the architecture type is the first architecture, indicating that all core network elements are deployed on the satellite, the terminal device can directly execute the NAS procedure. If the architecture type is the second architecture, indicating that only some core network elements are deployed on the satellite, since the NAS procedure needs to interact with other network elements in the core network, the terminal device delays processing the NAS procedure to avoid invalid signaling interaction when the feeder link is disconnected. That is, the terminal device delays processing the NAS procedure until the satellite enters normal mode. Other network elements are deployed on the terrestrial network, and the feeder link is connected in normal mode.

[0014] In one possible implementation, the terminal device delays the NAS process until the satellite enters normal mode, including: the terminal device determining the time corresponding to the satellite entering normal mode based on time information; and the terminal device processing the NAS process in response to the satellite's arrival at the normal mode entry time. That is, the terminal device can determine when the satellite enters normal mode based on the acquired time information, so as to initiate the NAS process after entering normal mode. The time information is transmitted by the satellite and indicates the time when the satellite transitions from store-and-forward mode to normal mode.

[0015] Secondly, a communication method is provided, which can be executed by a satellite, or by a component configured in the satellite (such as a circuit, chip, or chip system), or by a logic module or software that can realize all or part of the satellite's functions.

[0016] The method includes: the satellite acquiring the architecture type corresponding to the store-and-forward mode, which refers to the network element architecture of the core network deployed on the satellite, and the feeder link between the satellite and the ground network is disconnected in the store-and-forward mode; the satellite sending a first message to the terminal device, the first message including first indication information, which indicates the architecture type of the satellite in the store-and-forward mode.

[0017] In one possible implementation, the first message is either the message corresponding to the NAS layer or the message corresponding to the AS layer.

[0018] In one possible implementation, if the first message is a message corresponding to the NAS layer, the first message is a registration acceptance message, or the first message is a location update acceptance message; if the first message is a message corresponding to the AS layer, the first message is an SIB message.

[0019] In one possible implementation, if the first message is a registration acceptance message, the method further includes: the satellite receiving a second message sent by the terminal device to request registration, the second message including second indication information, the second indication information requesting the satellite to inform the corresponding architecture type in store-and-forward mode; if the satellite allows the terminal device to register, the satellite generates the registration acceptance message.

[0020] In one possible implementation, if the first message is a location update acceptance message, the method further includes: a satellite receiving a third message sent by the terminal device to request a location update, the third message including third indication information, the third indication information requesting the satellite to inform the corresponding architecture type in store-and-forward mode; if the satellite accepts the location update from the terminal device, the satellite generates a location update acceptance message.

[0021] Thirdly, a communication device includes a transceiver module and a processing module. The transceiver module is used to receive a first message transmitted by a satellite, the first message including first indication information, the first indication information indicating the architecture type corresponding to the satellite in store-and-forward mode, the architecture type referring to the network element architecture of the core network deployed on the satellite, the feeder link between the satellite and the ground network being disconnected in store-and-forward mode; the processing module is used to determine the architecture type corresponding to the satellite in store-and-forward mode based on the first indication information.

[0022] In one possible implementation, the first message is a message corresponding to the non-access stratum NAS, or the first message is a message corresponding to the access stratum AS.

[0023] In one possible implementation, if the first message is a message corresponding to the NAS, the first message is a registration acceptance message, or the first message is a location update acceptance message;

[0024] If the first message is the message corresponding to the AS, then the first message is a System Information Block (SIB) message.

[0025] In one possible implementation, if the first message is the registration acceptance message, the transceiver module is further configured to send a second message to the satellite, the second message including second indication information, the second indication information requesting the satellite to inform the corresponding architecture type in the store-and-forward mode.

[0026] In one possible implementation, the first message is the location update acceptance message, and the transceiver module is further configured to send a third message to the satellite to request a location update. The third message includes third indication information, which requests the satellite to inform it of the corresponding architecture type under the store-and-forward mode.

[0027] In one possible implementation, the processing module is further configured to determine the processing strategy of the NAS process based on the architecture type if the satellite is in the store-and-forward mode and the NAS process to be executed needs to distinguish the architecture type.

[0028] In one possible implementation, the processing module is specifically used to directly execute the NAS process if the architecture type is a first architecture, where the first architecture refers to all network elements of the core network being deployed on the satellite; if the architecture type is a second architecture, the NAS process is delayed until the satellite enters normal mode, where the second architecture refers to some network elements of the core network being deployed on the satellite, and in the normal mode the feeder link is in a connected state, and the NAS process needs to interact with other network elements in the core network, which are deployed on the terrestrial network.

[0029] In one possible implementation, the processing module is specifically configured to determine the time corresponding to the satellite entering the normal mode based on time information sent by the satellite to indicate the time when the satellite transitions from the store-and-forward mode to the normal mode; and to process the NAS process in response to the time when the satellite enters the normal mode.

[0030] In one possible implementation, the processing module is further configured to determine whether the NAS process needs to distinguish the architecture type when the satellite is in the store-and-forward mode; if the architecture type does not need to be distinguished, the NAS process is executed directly.

[0031] Fourthly, a communication device is provided, comprising a processing module and a transceiver module. The processing module is used to obtain the architecture type corresponding to the store-and-forward mode, which refers to the network element architecture of the core network deployed on the satellite, wherein the feeder link between the satellite and the ground network is disconnected in the store-and-forward mode; the transceiver module is used to send a first message to a terminal device, the first message including first indication information, the first indication information indicating the architecture type corresponding to the satellite in the store-and-forward mode.

[0032] In one possible implementation, the first message is a message corresponding to the non-access stratum NAS, or the first message is a message corresponding to the access stratum AS.

[0033] In one possible implementation, if the first message is a message corresponding to the NAS, the first message is a registration acceptance message, or the first message is a location update acceptance message; if the first message is a message corresponding to the AS, the first message is a System Information Block (SIB) message.

[0034] In one possible implementation, if the first message is the registration acceptance message, the transceiver module is further configured to receive a second message sent by the terminal device for requesting registration, the second message including second indication information, the second indication information requesting the satellite to inform the corresponding architecture type in the store-and-forward mode; if the satellite allows the terminal device to register, the processing module is further configured to generate the registration acceptance message.

[0035] In one possible implementation, if the first message is the location update acceptance message, the transceiver module is further configured to receive a third message sent by the terminal device for requesting a location update, the third message including third indication information, the third indication information requesting the satellite to inform the corresponding architecture type in the store-and-forward mode; if the satellite accepts the location update from the terminal device, the processing module is further configured to generate the location update acceptance message.

[0036] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method of the first aspect described above. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface, to which the processor is coupled.

[0037] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0038] In another implementation, the device is a chip configured in a terminal device. When the device is a chip configured in a terminal device, the communication interface can be an input / output interface.

[0039] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in the second aspect described above. Optionally, the device further includes a memory. Optionally, the device further includes a communication interface, to which the processor is coupled.

[0040] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0041] In another implementation, the device is a chip configured in a satellite. When the device is a chip configured in a satellite, the communication interface can be an input / output interface.

[0042] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method in any of the aspects.

[0043] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0044] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the methods in any of the preceding aspects.

[0045] Optionally, the processor may be one or more, and the memory may be one or more.

[0046] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when run, causes a computer to perform the methods of any of the preceding aspects.

[0047] In a tenth aspect, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods of any of the preceding aspects.

[0048] Eleventhly, embodiments of this application provide a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods described in the foregoing aspects to be performed. The chip system may be composed of a chip or may include chips and other discrete devices. The chip system may include input circuitry or interfaces for transmitting information or data, and output circuitry or interfaces for receiving information or data.

[0049] In a twelfth aspect, a communication system is provided, including the aforementioned terminal equipment and satellite. Optionally, the system may further include other equipment for communicating with the terminal equipment and / or the satellite. Attached Figure Description

[0050] Figure 1 This is a diagram of a satellite communication system architecture;

[0051] Figure 2 A flowchart illustrating the interaction of a communication method provided in this application embodiment;

[0052] Figure 3 This application provides an example of an interactive scenario.

[0053] Figure 4 This application provides a schematic diagram of a NAS process flow.

[0054] Figure 5 A structural diagram of a communication device provided in an embodiment of this application;

[0055] Figure 6 This is a structural diagram of a communication device provided in an embodiment of this application. Detailed Implementation

[0056] To enable those skilled in the art to better understand the solution of this application, the application scenario of the technical solution of this application will be described first below.

[0057] In an NTN network, there are user segments, space segments, and ground segments. The link between the user segment and the space segment is called a service link, the link between the ground segment and the space segment is called a feeder link, and the link between different satellites is called an inter-satellite link. For example... Figure 1 The example shown is a communication system that may include network devices, such as... Figure 1 The satellite 20, gateway station 30, and data network server 40 are shown. The communication system may also include terminal equipment, such as… Figure 1 The terminal device 10 is shown. The terminal device 10 communicates with the satellite 20 via a service link, and the satellite 20 communicates with the gateway station 30 via a feeder link.

[0058] exist Figure 1 In the communication scenario shown, the satellite operates in on-board regeneration mode. In this mode, the satellite integrates base station functions, including data processing, forwarding, and routing. Ground user equipment can communicate directly with the satellite, and the processing unit on the satellite processes and forwards the data.

[0059] Figure 1 An exemplary terminal device 10 and a satellite 20 are shown. Optionally, the communication system 100 may also include multiple terminal devices and / or multiple satellite devices, with the satellites communicating with each other via inter-satellite links.

[0060] Typically, satellites are in motion, and their feeder links to the ground network may be connected or disconnected. To ensure reliable data transmission, a store-and-forward mode and a normal mode are proposed for IoT NTN networks. In store-and-forward mode, the feeder link is disconnected, and data sent by user equipment cannot be quickly transmitted to the ground network. This mode is suitable for non-real-time or high-latency-tolerance service scenarios. In normal mode, the feeder link is connected, and user-sent data can be quickly transmitted to the ground network via satellite. This mode is suitable for services with high latency requirements, such as voice calls and video conferencing. Currently, a store-and-forward identifier is introduced for the operating modes of IoT NTN networks to inform user equipment that the satellite is operating in store-and-forward mode.

[0061] Currently, in store-and-forward mode, Full CN and Split MME architectures have been proposed. These two different architectures affect the operation of user equipment and lead to resource waste. For example, in the Full CN architecture, since all core network elements are deployed on satellites, even if the feeder link port is interrupted, it does not affect the execution of NAS processes. However, in the Split MME architecture, only some MME functions are deployed on satellites, while other core network elements are deployed on the ground. When certain NAS processes involve interaction with other network elements outside of the MME, the feeder link being disconnected prevents the NAS process from being completed quickly, resulting in wasted signaling resources. The impact of these two architectures on whether users need to delay NAS processes when the satellite is in store-and-forward mode differs. NAS processes mainly refer to processes that do not involve the data plane but only the control plane, such as registration, location updates, and the establishment of a public data network (PDN).

[0062] Based on this, this application provides a communication method in which a satellite sends a first message to a terminal device. This first message includes first indication information indicating the satellite's architecture type in store-and-forward mode. Upon receiving the first message, the terminal device can parse it to determine the satellite's architecture type in store-and-forward mode, and then perform operations matching that architecture type, thus avoiding resource waste.

[0063] The terminal devices in this application include various devices with wireless communication capabilities, which can be used to connect people, objects, machines, etc. These terminal devices can be widely applied in various scenarios, such as: cellular communication, D2D, V2X, peer-to-peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, and other scenarios.

[0064] The terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc. Terminal equipment can be user equipment (UE), terminal, fixed equipment, mobile station equipment or mobile equipment, subscriber unit, handheld device, vehicle-mounted equipment, wearable device, cellular phone, smartphone, session initialization protocol (SIP) phone, wireless data card, personal digital assistant (PDA), computer, tablet computer, laptop computer, wireless modem, handset, laptop computer, computer with wireless transceiver capability, smart book, vehicle, satellite, global positioning system (GPS) device, target tracking device, aircraft (e.g., drone, helicopter, multi-helicopter, quad-helicopter, or airplane), boat, remote control device, smart home device, industrial equipment, or devices built into the above devices (e.g., communication modules, modems, or chips in the above devices), or other processing devices connected to a wireless modem. For ease of description, the terminal equipment will be described below using terminals or UEs as examples.

[0065] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be a device that supports the terminal device in implementing the functions, such as a chip system or a chip. This device can be installed in the terminal device. In this embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0066] Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the terminal device is located. Furthermore, a terminal device can be a hardware device, or a software function running on dedicated hardware, or a software function running on general-purpose hardware, such as a virtualization function instantiated on a platform (e.g., a cloud platform), or an entity that includes dedicated or general-purpose hardware and software functions. This application does not limit the specific form of the terminal device.

[0067] See Figure 2This figure is a flowchart of a communication method provided in an embodiment of this application, such as... Figure 2 As shown, the method includes:

[0068] S201: The architecture type corresponding to the satellite acquisition store-and-forward mode.

[0069] In this embodiment, the satellite may include an access network module and a core network module. The access network module obtains the specific architecture type from the core network module. This architecture type refers to the network element architecture of the core network deployed on the satellite. This architecture type may include a first architecture and a second architecture. Under different architectures, the network elements of the core network deployed on the satellite are different. For example, the first architecture indicates that all core network elements are deployed on the satellite; the second architecture indicates that some core network elements are deployed on the satellite, such as only some functions of the MME network element being deployed on the satellite, while other core network elements are deployed on the ground.

[0070] S202: The satellite sends a first message to the terminal device, the first message including first indication information, the first indication information indicating the architecture type of the satellite in store-and-forward mode.

[0071] After obtaining the architecture type, the satellite sends a first message to the terminal device. This first message can include a field that carries first indication information to specify the architecture type. Alternatively, the satellite can use a reserved field in the first message to carry the first indication information.

[0072] The first message can be an AS layer message, such as a System Information Block (SIB) message. Alternatively, the first message can be a NAS layer message, such as a registration acceptance message (e.g., an AttachAccept message) or a location update acceptance message (e.g., a Tracking Area Update (TAU) Accept message). In the protocol stack, the Radio Resource Control (RRC) layer, the Radio Access Network Application Part (RANAP) layer, and the protocol layers below them are called access layers. The Mobility Management (MM), Session Management (SM), Call Control (CC), and Short Messaging Service (SMS) layers above them are called non-access layers. The access layers establish connections between the UE, base station, and core network through RRC, while the non-access layers allow the UE to directly interact with the core network for mobility management and session management.

[0073] When the first message is a registration acceptance message or a location update acceptance message, the satellite receives a request message sent by the terminal device before sending the first message to the terminal device, and the satellite replies with a corresponding response message in response to the request message.

[0074] In one embodiment, if the first message is a registration acceptance message, the method further includes: the terminal device sending a second message to the satellite, the second message requesting registration, and the second message including second indication information, the second indication information requesting the satellite to inform it of the corresponding architecture type in store-and-forward mode; if the satellite allows the terminal device to register, the satellite generates a registration acceptance message and sends the registration acceptance message to the terminal device.

[0075] In other words, the terminal device adds a second indication information to its registration request (e.g., attach request) message, using this second indication information to request the satellite to inform it of the architecture type. When the satellite replies to the terminal device with a registration acceptance message (e.g., AttachAccept), it includes the first indication information in that message, using this first indication information to inform it of the architecture type. The Attach request is a signaling message sent by the terminal device when it first attempts to connect to the mobile network. This message includes the terminal device's identity information, attachment type, etc. After receiving the Attach Request, the network performs authentication and authorization checks. If authentication is successful, it allows the terminal device to access the network and sends an AttachAccept message to the terminal device.

[0076] Alternatively, if the first message is a location update acceptance message, the method further includes: the terminal device sending a third message to the satellite, the third message requesting a location update, the third message including third indication information, the third indication information requesting the satellite to inform it of the corresponding architecture type in store-and-forward mode; if the satellite accepts the location update from the terminal device, the satellite generates a location update acceptance message and sends the location update acceptance message to the terminal device.

[0077] In this implementation, because satellites are in motion, the satellites that the terminal device communicates with change. When the terminal device is within the service coverage of a new satellite, it needs to establish a connection with the new satellite to maintain communication. To achieve this, the terminal device needs to send a location update request to the new satellite, such as a TAU request message. This TAU request message contains the terminal device's identification information and location information. The new satellite determines the terminal device's location by receiving and processing the TAU request message and updates its tracking area. The tracking area is an area composed of multiple satellites used to manage the terminal device's location updates and communication processes.

[0078] If the new satellite accepts and acknowledges the terminal device's TAU request, it will send a TAU accept message to the terminal device, indicating that the terminal device has successfully completed the location update process and can continue to communicate within the service coverage area of ​​the new satellite.

[0079] It should be noted that carrying the second or third indication information in the above request message is only an optional solution. Even if the above request message does not carry the second or third indication information, the response message corresponding to the above request message can still carry the first indication information to proactively inform the terminal device of the satellite side architecture type.

[0080] For a better understanding of the above request interaction process, please refer to [link / reference]. Figure 3 The scene interaction diagram shown includes the following specific processes:

[0081] S301: The UE sends a registration request message or a location update request message to the satellite.

[0082] The registration request message is an Attach Request message, which may include second indication information; the location update request message is a TAU Request message, which may include third indication information.

[0083] S302: The UE completes the interaction process with the satellite, including identity authentication and security activation.

[0084] S303: The satellite sends a registration acceptance message or a location update acceptance message to the UE.

[0085] The registration acceptance message includes first indication information, or the location update acceptance message includes first indication information, wherein the first indication information indicates that the architecture type is Full CN architecture or Split MME architecture.

[0086] S304: The UE sends a registration completion message or a location update completion message to the satellite.

[0087] It should be noted that the registration process and location update process are relatively mature technologies, and will not be described in detail here.

[0088] S203: The terminal device determines the architecture type of the satellite in store-and-forward mode based on the first message.

[0089] After receiving the first message, the terminal device obtains the first indication information by parsing the first message, thereby knowing the architecture type of the satellite in store-and-forward mode.

[0090] When the satellite is in store-and-forward mode, the terminal device can determine whether the NAS process to be executed needs to distinguish the architecture type. If it does not need to distinguish the architecture type, the terminal device directly executes the NAS process. In other words, if the NAS process only needs to interact with the network elements of the core network deployed on the satellite, then regardless of whether it is the first architecture or the second architecture, the UE can quickly complete the entire NAS process in store-and-forward mode.

[0091] When the NAS process to be executed needs to differentiate between architecture types, the terminal device determines the processing strategy based on the architecture type. In other words, under the second architecture, if the NAS process needs to interact with other network elements deployed on the terrestrial network (core network elements), in store-and-forward mode, the disconnection of the feeder link between the satellite and the terrestrial network prevents the entire NAS process from being completed quickly, resulting in wasted signaling resources. Under the first architecture, since all core network elements are deployed on the satellite, even in store-and-forward mode, the completion of the NAS process is not affected. For example, for the initial registration process, since the registration process involves authentication and other procedures, requiring the participation of other network elements besides the MME network elements, it cannot be completed quickly under the Split-MME architecture, but can be completed quickly under the FullCN architecture. Therefore, different processing strategies need to be adopted for different architecture types.

[0092] Based on this, when the architecture type is the first architecture, the terminal device directly executes the NAS process. When the architecture type is the second architecture, the terminal device delays the NAS process until the satellite enters normal mode. This NAS process needs to interact with other network elements in the core network element, which are deployed on the terrestrial network.

[0093] In one possible implementation, the terminal device can also receive time information transmitted by the satellite, indicating the time when the satellite transitions from store-and-forward mode to normal mode. Based on this, the terminal device can determine the time corresponding to the satellite entering normal mode. In response to the satellite reaching the time to enter normal mode, the terminal device processes the NAS procedure. That is, when the satellite reaches the time to enter normal mode, the feeder link between the satellite and the ground network is connected, and the terminal device can execute the NAS procedure through this feeder link.

[0094] Specifically, the satellite can send time information to the terminal device via SIB messages, allowing the terminal device to delay the NAS process based on this time information. Specifically, the satellite can carry this time information via SIB31 messages.

[0095] After the UE learns the satellite's architecture type, to facilitate understanding of whether the UE delays initiating the NAS process, see [link to relevant documentation]. Figure 4 The aforementioned framework diagram illustrates that the technical framework includes:

[0096] S401: The satellite informs the UE that the satellite is in store-and-forward mode by sending an SIB message, and the SIB message includes the time information for the transition from store-and-forward mode to normal mode.

[0097] S402: If the UE needs to initiate a NAS procedure, determine whether the NAS procedure needs to distinguish the architecture type in the storage-forward mode. If yes, execute S403; otherwise, execute S404.

[0098] In other words, the UE determines whether the NAS process can be completed seamlessly under both the Split MME architecture and the Full CN architecture. For example, for periodic location area updates, since this process only involves the MME network elements of the core network, the UE can quickly and interactively complete the entire NAS process in store-and-forward mode, regardless of whether it is a Split-MME architecture or a Full CN architecture, so there is no need to distinguish between network architecture types.

[0099] For the initial registration process, because the registration process involves authentication and other procedures, requiring the participation of other network elements besides the MME, it cannot be completed quickly under the Split-MME architecture (where only some MME functions are satellite-mounted), but it can be completed quickly under the Full CN architecture. When no distinction is needed, redirect to 404; otherwise, redirect to 403.

[0100] S403: The UE determines whether the architecture type is Full CN architecture. If it is, then execute S404; otherwise, execute S405.

[0101] S404: UE directly initiates NAS process.

[0102] S405: The UE will delay initiating the NAS process until the satellite switches to normal mode.

[0103] In this embodiment, the terminal device can decide whether to delay initiating the NAS process based on the specific NAS process and architecture type, thereby avoiding invalid signaling interactions and reducing resource waste.

[0104] It should be understood that Figures 2 to 4 The flowcharts or scene diagrams shown are for illustrative purposes only and are not intended to limit the embodiments of this application to the examples illustrated. In fact, those skilled in the art can interpret the embodiments based on... Figures 2 to 4 The examples in the document can be transformed into equivalent ways to obtain more implementations.

[0105] The above text combined Figures 2 to 4 This document describes in detail the communication method provided in the embodiments of this application. The following will combine... Figure 5 and Figure 6The apparatus embodiments of this application are described in detail below. It should be understood that the apparatus of this application embodiments can perform the various methods of the foregoing embodiments of this application, that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0106] In the embodiments described above, the terminal device may execute some or all of the steps in each embodiment; the satellite may execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0107] Figure 5 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 5 As shown, the communication device 500 may include a communication module 520. The communication module 520 can implement corresponding communication and sensing functions. These communication functions can be internal communication functions of the communication device 500 or communication functions between the communication device 500 and other devices. Optionally, the communication module 520 may also be referred to as a communication interface or transceiver module. Optionally, the communication device 500 further includes a processing module 510. The processing module 510 can implement corresponding processing functions.

[0108] Optionally, the communication device 500 further includes a storage module, which can be used to store instructions and / or data; the processing module 510 can read the instructions and / or data in the storage module so that the communication device 500 can implement the aforementioned method embodiments.

[0109] In one possible design, the communication device 500 may correspond to the terminal device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 500 can be used to perform the steps or processes executed by the terminal device in any of the above method embodiments.

[0110] For example, the communication module 520 is used to receive a first message sent by the satellite. The first message includes first indication information, which indicates the architecture type of the satellite in store-and-forward mode. The architecture type refers to the network element architecture of the core network deployed on the satellite. In store-and-forward mode, the feeder link between the satellite and the ground network is disconnected.

[0111] The processing module 510 is used to determine the architecture type of the satellite in the store-and-forward mode based on the first indication information.

[0112] In one possible implementation, the first message is a message corresponding to the non-access stratum NAS, or the first message is a message corresponding to the access stratum AS.

[0113] In one possible implementation, if the first message is a message corresponding to the NAS, the first message is a registration acceptance message, or the first message is a location update acceptance message; if the first message is a message corresponding to the AS, the first message is a System Information Block (SIB) message.

[0114] In one possible implementation, if the first message is the registration acceptance message, the communication module 520 is further configured to send a second message to the satellite for requesting registration. The second message includes second indication information, which requests the satellite to inform it of the corresponding architecture type under the store-and-forward mode.

[0115] In one possible implementation, the first message is the location update acceptance message, and the communication module 520 is further configured to send a third message to the satellite for requesting a location update. The third message includes third indication information, which requests the satellite to inform the satellite of the corresponding architecture type in the store-and-forward mode.

[0116] In one possible implementation, the processing module 510 is further configured to determine the processing strategy of the NAS process based on the architecture type if the satellite is in the store-and-forward mode and the NAS process to be executed needs to distinguish the architecture type.

[0117] In one possible implementation, the processing module 510 is specifically configured to directly execute the NAS process if the architecture type is a first architecture, where the first architecture refers to all network elements of the core network being deployed on the satellite; and if the architecture type is a second architecture, delay the NAS process until the satellite enters normal mode, where the second architecture refers to some network elements of the core network being deployed on the satellite, and in the normal mode the feeder link is in a connected state, and the NAS process needs to interact with other network elements in the core network, which are deployed on the terrestrial network.

[0118] In one possible implementation, the processing module 510 is specifically configured to determine the time corresponding to the satellite entering the normal mode based on time information, the time information indicating the time when the satellite transitions from the store-and-forward mode to the normal mode, the time information being sent by the satellite; and to process the NAS process in response to the time when the satellite arrives to enter the normal mode.

[0119] In one possible implementation, the processing module 510 is further configured to determine whether the NAS process needs to distinguish the architecture type when the satellite is in the store-and-forward mode; if the architecture type does not need to be distinguished, the NAS process is executed directly.

[0120] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0121] In one possible design, the communication device 500 may correspond to the satellite in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the satellite. The communication device 500 may be used to perform the steps or processes performed by the satellite in any of the above method embodiments.

[0122] For example, the processing module 510 is used to obtain the architecture type corresponding to the store-and-forward mode, wherein the architecture type refers to the network element architecture of the core network deployed on the satellite, and the feeder link between the satellite and the ground network is disconnected in the store-and-forward mode.

[0123] The communication module 520 is used to send a first message to the terminal device. The first message includes first indication information, which indicates the architecture type of the satellite in the store-and-forward mode.

[0124] In one possible implementation, the first message is a message corresponding to the non-access stratum NAS, or the first message is a message corresponding to the access stratum AS.

[0125] In one possible implementation, if the first message is a message corresponding to the NAS, the first message is a registration acceptance message, or the first message is a location update acceptance message; if the first message is a message corresponding to the AS, the first message is a System Information Block (SIB) message.

[0126] In one possible implementation, if the first message is the registration acceptance message, the communication module 520 is further configured to receive a second message sent by the terminal device for requesting registration, the second message including second indication information, the second indication information requesting the satellite to inform the corresponding architecture type in the store-and-forward mode; if the satellite allows the terminal device to register, the processing module 510 is further configured to generate the registration acceptance message.

[0127] In one possible implementation, if the first message is the location update acceptance message, the communication module 520 is further configured to receive a third message sent by the terminal device for requesting a location update, the third message including third indication information, the third indication information requesting the satellite to inform the corresponding architecture type in the store-and-forward mode; if the satellite accepts the location update from the terminal device, the processing module 510 is further configured to generate the location update acceptance message.

[0128] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0129] Figure 6 This is another schematic block diagram of the communication device 600 provided in the embodiments of this application. The communication device 600 may be a terminal device or a satellite implementing the above-described methods, including chips, chip systems, or processors. The communication device 600 can be used to implement the methods described in the above-described method embodiments; for details, please refer to the descriptions in the above-described method embodiments.

[0130] like Figure 6 As shown, the communication device 600 may include one or more processors 610, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 610 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 600 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0131] In an alternative design, the processor 610 may also store instructions and / or data that can be executed by the processor 610 to cause the communication device 600 to perform the methods described in the above method embodiments.

[0132] In another alternative design, the communication device 600 may include a communication interface 620 for implementing receiving and transmitting functions. For example, the communication interface 620 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0133] Optionally, the communication device 600 may include one or more memories 630, which may store instructions that can be executed on the processor 610, causing the communication device 600 to perform the methods described in the above method embodiments. Optionally, the memories 630 may also store data. Optionally, the processor 610 may also store instructions and / or data. The processor 610 and the memories 630 may be provided separately or integrated together.

[0134] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0135] In one implementation, the communication device 600 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0136] In another implementation, the communication device 600 may correspond to the satellite in the above method embodiments and may be used to execute the various steps and / or processes performed by the satellite in the above method embodiments. The processor 610 may be used to execute instructions stored in the memory 630, and when the processor 610 executes the instructions stored in the memory, the processor 610 is used to execute the various steps and / or processes of the above method embodiments corresponding to the satellite.

[0137] It should be understood that the aforementioned processing device can be one or more chips. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0138] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0139] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0140] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0141] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned terminal equipment and satellite.

[0142] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes executed by the terminal device or satellite in any of the foregoing method embodiments.

[0143] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes performed by the terminal device or satellite in any of the foregoing method embodiments.

[0144] The computer-readable storage medium may be the aforementioned volatile memory or non-volatile memory, or it may include both volatile memory and non-volatile memory.

[0145] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0146] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

[0147] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0148] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0149] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, The method includes: The terminal device receives a first message sent by the satellite. The first message includes first indication information, which indicates the architecture type of the satellite in store-and-forward mode. The architecture type refers to the network element architecture of the core network deployed on the satellite. In store-and-forward mode, the feeder link between the satellite and the ground network is disconnected. The terminal device determines the architecture type of the satellite in the store-and-forward mode based on the first indication information.

2. The method according to claim 1, characterized in that, The first message is either a message corresponding to a non-access layer NAS or a message corresponding to an access layer AS.

3. The method according to claim 2, characterized in that, If the first message is the message corresponding to the NAS, the first message is a registration acceptance message, or the first message is a location update acceptance message; If the first message is the message corresponding to the AS, then the first message is a System Information Block (SIB) message.

4. The method according to claim 3, characterized in that, If the first message is the registration acceptance message, the method further includes: The terminal device sends a second message to the satellite to request registration. The second message includes second indication information, which requests the satellite to inform it of the corresponding architecture type under the store-and-forward mode.

5. The method according to claim 3, characterized in that, The first message is the location update acceptance message, and the method further includes: The terminal device sends a third message to the satellite to request a location update. The third message includes third indication information, which requests the satellite to inform it of the corresponding architecture type under the store-and-forward mode.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: If the satellite is in the store-and-forward mode and the NAS process to be executed needs to distinguish the architecture type, the terminal device determines the processing strategy of the NAS process according to the architecture type.

7. The method according to claim 6, characterized in that, The terminal device determines the processing strategy for the NAS process based on the architecture type, including: If the architecture type is the first architecture, the terminal device directly executes the NAS process. The first architecture refers to the deployment of all network elements of the core network on the satellite. If the architecture type is the second architecture, the terminal device delays processing the NAS process until the satellite enters normal mode. The second architecture refers to the deployment of some network elements in the core network on the satellite. In the normal mode, the feeder link is in a connected state, and the NAS process needs to interact with other network elements in the core network, which are deployed on the ground network.

8. The method according to claim 7, characterized in that, The terminal device delays the NAS process until the satellite enters the normal mode, including: The terminal device determines the time corresponding to the satellite entering the normal mode based on the time information, wherein the time information is sent by the satellite to indicate the time when the satellite switches from the store-and-forward mode to the normal mode; In response to the arrival time of the satellite entering the normal mode, the terminal device processes the NAS procedure.

9. The method according to any one of claims 6-8, characterized in that, The method further includes: When the satellite is in the store-and-forward mode, the terminal device determines whether the NAS process needs to distinguish between architecture types; If there is no need to distinguish the architecture type, the terminal device directly executes the NAS process.

10. A communication method, characterized in that, The method includes: The satellite acquires the corresponding architecture type in store-and-forward mode. The architecture type refers to the network element architecture of the core network deployed on the satellite. In store-and-forward mode, the feeder link between the satellite and the ground network is disconnected. The satellite sends a first message to the terminal device. The first message includes first indication information, which indicates the architecture type of the satellite in the store-and-forward mode.

11. The method according to claim 10, characterized in that, The first message is either a message corresponding to a non-access layer NAS or a message corresponding to an access layer AS.

12. The method according to claim 11, characterized in that, If the first message is the message corresponding to the NAS, the first message is a registration acceptance message, or the first message is a location update acceptance message; If the first message is the message corresponding to the AS, then the first message is a System Information Block (SIB) message.

13. The method according to claim 12, characterized in that, If the first message is the registration acceptance message, the method further includes: The satellite receives a second message from the terminal device requesting registration. The second message includes second indication information, which requests the satellite to inform it of the architecture type corresponding to the store-and-forward mode. If the satellite allows the terminal device to register, the satellite generates the registration acceptance message.

14. The method according to claim 12, characterized in that, If the first message is the location update acceptance message, the method further includes: The satellite receives a third message from the terminal device requesting a location update. The third message includes third indication information, which requests the satellite to inform it of the corresponding architecture type in the store-and-forward mode. If the satellite receives a location update from the terminal device, the satellite generates the location update acceptance message.

15. A communication device, characterized in that, The device includes at least one processor coupled to a memory storing a program or instructions, the processor executing the program or instructions to cause the device to perform the communication method as described in any one of claims 1 to 9, or to perform the communication method as described in any one of claims 10 to 14.

16. A computer-readable storage medium, characterized in that, It stores a computer program or instructions thereon, characterized in that, when the computer program or instructions are executed, they cause the computer to perform the method as described in any one of claims 1 to 14.

17. A communication system, characterized in that, Includes the communication device as described in claim 15.

18. A chip system, characterized in that, The chip system includes one or more processors, which are configured to retrieve and execute instructions stored in memory, such that the method as described in any one of claims 1 to 14 is performed.