Communication method, device and system

Abstract

A communication method, device and system are applied to a satellite communication system. The method comprises the following steps: the terminal equipment determines whether to store state information of the terminal equipment, the terminal equipment sends the state information to network equipment under the condition of determining to store the state information, and the state information is used for accessing a non-ground network. According to the technical scheme, simplified access and communication are realized based on the state information stored by the terminal equipment, and signaling overhead and access / communication time delay can be reduced.

Description

Technical Field

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

[0002] Non-terrestrial networks (NTNs) include nodes such as satellite networks, high-altitude platforms, and drones. They have significant advantages such as global coverage, long-distance transmission, flexible networking, convenient deployment, and no geographical limitations. They have been widely used in fields such as maritime communication, positioning and navigation, disaster relief, scientific experiments, video broadcasting, and Earth observation.

[0003] In an NTN system, satellite base stations (which can be understood as satellites carrying some or all of the base station functions) can communicate with core network elements through ground stations. Satellite base stations can also communicate with terminal devices via air interfaces. During the initial access process of terminal devices, the status information of the terminal devices, configured and maintained by the network side (e.g., including satellite base stations and core network elements), needs to be exchanged multiple times, resulting in excessive signaling overhead and long access latency. Therefore, simplifying the access process for terminal devices is a crucial issue that needs to be addressed. Summary of the Invention

[0004] This application provides a communication method, apparatus, and system that can simplify the access process for terminal devices.

[0005] Firstly, a communication method is provided. This method can be executed by a terminal device. Unless otherwise specified, "terminal device" in this application can refer to the terminal device itself, or a component in the terminal device (e.g., a processor, chip, or chip system, such as a circuit or chip in the terminal device responsible for communication functions (e.g., a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip containing a modem core or a system-in-package (SIP) chip)), or it can be a logic module or software that can implement all or part of the functions of the terminal device.

[0006] In this method, it is determined whether the terminal device's status information is stored; if it is determined that the status information is stored, the status information is sent to the network device, and the status information is used to access the non-terrestrial network.

[0007] In this application, a satellite with access network functionality is referred to as a satellite access network device, or a base station deployed on a satellite is referred to as a satellite base station. For example, network equipment refers to network-side equipment mounted on a satellite; network equipment can be called a satellite or a satellite base station, and the satellite can carry some or all of the functions of a base station.

[0008] In this application, whether or not valid status information of the terminal device is stored can be replaced with whether or not the terminal device has valid status information, or whether or not the terminal device itself carries valid status information, etc., without limiting its specific name. Here, the status information of the terminal device refers to valid status information; therefore, status information can be replaced with valid status information. It is understood that the status information of the terminal device is valid. For example, the status information of the terminal device may have an effective area and / or an effective time. For example, the effective area of ​​the status information is cell 1, and the effective time of the status information is 10:00-12:00. That is to say, if the terminal device is in the effective area, and / or the effective time of the status information is in progress, then the status information of the terminal device can be considered valid. That is, the status information of the terminal device is valid within the effective time and / or effective area, meaning that simplified access and communication can be achieved based on the status information carried by the terminal device itself, thereby reducing signaling overhead and access / communication latency. Conversely, if the terminal device is not in the effective area, and / or the effective time of the status information has not started or has ended, then the status information of the terminal device can be considered invalid, or the status information of the terminal device can be updated. This means that the status information of the terminal device is not valid outside the effective time and / or effective area. In this case, simplified access and communication based on the status information carried by the terminal device itself may not be supported.

[0009] Using the above method, the terminal device requests access to a non-terrestrial network, such as an NTN network, based on its own carried state information. This implementation avoids frequent state information exchange between different network devices during network device movement, simplifying the terminal device's access process and reducing signaling overhead and access latency. Especially in the scenario of regenerating satellites, where the satellite is constantly moving while the mobility of the terminal device is generally negligible, the design concept of shifting from the network side carrying the terminal device's state information to the terminal device itself can be adopted. This enables rapid access and communication based on the state information stored on the terminal device itself, eliminating the need for the network side (such as the access network) to store the terminal's state information, thus reducing processing complexity.

[0010] In some implementations of the first aspect, the terminal device can determine whether to store its own state information based on whether it has such information stored locally. Alternatively, the terminal device can determine whether it has stored valid state information based on the effective region and / or effective time of its state information.

[0011] In some implementations of the first aspect, the method further includes: sending a first registration request message to a network device when it is determined that state information is not stored, the first registration request message being used to request access to a non-terrestrial network.

[0012] Based on the above solution, for cases where the terminal device does not store the terminal device's status information, the terminal device can execute a registration process to request access to a non-terrestrial network. The specific process for accessing a non-terrestrial network includes, but is not limited to, non-access stratum (NAS) authentication, security authentication, subscription data acquisition, and context establishment, to ensure that the terminal device accesses the network.

[0013] In some implementations of the first aspect, before sending status information to the network device, the method further includes: receiving first information from the network device, the first information indicating that the network device supports access based on status information.

[0014] Based on the above scheme, by receiving the first information, it can be determined that the network device supports fast access with the terminal device carrying status information. Then, if it is determined that the terminal device's status information is stored, it can request access to the non-terrestrial network based on the status information from the network device. This method can adapt to the access of different types of terminal devices and provide an effective access path.

[0015] In some implementations of the first aspect, the method further includes: sending status indication information to a network device, the status indication information indicating that the terminal device stores status information.

[0016] Based on the above scheme, the terminal device can send a status information indication to the network device to indicate that it carries its own status information. This allows the network device to perform a fast access process based on the status information stored on the terminal device, reducing access complexity, signaling overhead, and access / communication latency.

[0017] In some implementations of the first aspect, the status indication information includes a first preamble, which is used for access when the terminal device stores status information.

[0018] In some implementations of the first aspect, the multiple preamble groups include a first preamble group and a second preamble group. The first preamble group is used for access when the terminal device stores state information, and the second preamble group is used for access when the terminal device does not store state information. The first preamble belongs to the first preamble group.

[0019] Based on the above scheme, since the first preamble is used for access when the terminal device stores state information, the terminal device can indicate that it stores state information by sending the first preamble, or by sending the first preamble in the first preamble group. Correspondingly, the network device can determine that the terminal device stores state information based on the received first preamble, and then can perform a fast access process based on the state information stored by the terminal device itself, thereby reducing access complexity, signaling overhead and access / communication latency.

[0020] In some implementations of the first aspect, the status indication information is carried in media access control control element (MAC CE) signaling or radio resource control (RRC) signaling.

[0021] Based on the above scheme, the terminal device indicates that it stores status information by adding a field to the MAC CE or RRC signaling. For example, the terminal device can set the value of the added field to 1 to indicate that it stores status information; conversely, it can set the value of the added field to 0 to indicate that it does not store status information. Alternatively, the terminal device can indicate that it stores status information by including the added field in the MAC CE or RRC signaling; conversely, it can indicate that it does not store status information by not including the added field in the MAC CE or RRC signaling.

[0022] In some implementations of the first aspect, the method further includes: sending capability information to a network device, the capability information indicating that the terminal device stores status information, the capability information including status indication information.

[0023] Based on the above scheme, the terminal device can report its own capability information, indicating that it stores state information, or in other words, instructing the terminal device to report its state information to the network device. Based on this reported capability information, the network device can determine that the terminal device stores state information, thereby triggering a fast access process based on the terminal device's stored state information, reducing signaling overhead and access / communication latency.

[0024] In some implementations of the first aspect, the method further includes: receiving second information from a network device, the second information indicating that the status information verification failed; and sending a second registration request message to the network device, the second registration request message being used to request access to a non-terrestrial network.

[0025] In some implementations of the first aspect, the method further includes: receiving third information from a network device, the third information indicating that the status information verification has passed; and accessing a non-terrestrial network based on the status information.

[0026] For example, the status information from the terminal device includes first security information, and the core network element itself stores the status information of the terminal device, including second security information. By comparing whether the first security information and the second security information are the same, it is determined whether the status information reported by the terminal device has been verified.

[0027] Based on the above scheme, after receiving the second information, the terminal device can determine that the status information verification has failed. In this case, the terminal device can re-initiate the registration process and request access to the non-terrestrial network. This access process cannot be simplified. Alternatively, after receiving the third information, the terminal device can determine that the status information verification has passed or succeeded. In this case, the terminal device does not need to re-initiate the registration process and can request access to the non-terrestrial network based on the status information stored in the terminal device itself. This implementation method simplifies the access process and reduces signaling overhead and access / communication latency. Furthermore, verifying the status information can prevent malicious tampering of the status information on the terminal device side, improving the security and reliability of the status information and ensuring secure access and communication for the terminal device.

[0028] In some implementations of the first aspect, the state information is verified through at least one of the following protocol layers: Packet Data Convergence Protocol (PDCP) layer, Non-Access NAS layer, Service Data Adaptation Protocol (SDAP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, Radio Resource Control (RRC) layer, or Physical Layer (PHY) layer.

[0029] In some implementations of the first aspect, the status information is associated with the first effective region, and the method further includes updating the status information when the terminal device is not located in the first effective region.

[0030] In some implementations of the first aspect, before updating the status information, the method further includes: determining that the terminal device is not located in the first effective area if the distance between the location of the terminal device and the reference location is greater than or equal to a first threshold; and / or determining that the terminal device is not located in the first effective area if the geographic grid number, geographic region number, beam position number and beam number corresponding to the location of the terminal device are not in a pre-configured number list.

[0031] In some implementations of the first aspect, before updating the status information, the method further includes: determining that the terminal device is located in a first effective area if the distance between the location of the terminal device and the reference location is less than a first threshold; and / or determining that the terminal device is located in a first effective area if the geographic grid number, geographic region number, beam position number and beam number corresponding to the location of the terminal device belong to a pre-configured number list.

[0032] Based on the above scheme, the terminal device determines whether to update its status information by judging whether its current location is within the first effective area. That is, the terminal device's status information stores the effective time and / or effective area. If the terminal device moves, for example, out of the effective area, or if the effective time of the status information expires, it means that the status information is invalid, and subsequent fast network access based on this status information is no longer possible. Therefore, the terminal device can update its status information.

[0033] In some implementations of the first aspect, the status information includes at least one of the following: first security information, identification information associated with the terminal device, location information associated with the terminal device, quality of service (QoS) information, billing information, or capability information of the terminal device.

[0034] Secondly, a communication method is provided. This method can be executed by a network device. Unless otherwise specified, "network device" in this application can refer to the network device itself, or a component in the network device (e.g., a processor, chip, or chip system, such as a circuit or chip in the network device responsible for communication functions (e.g., a modem chip, also known as a baseband chip, or a SoC chip or SIP chip containing a modem core), or a logic module or software that can implement all or part of the functions of a terminal device.

[0035] In this method, status information from the terminal device is received, and the status information is used to access the non-terrestrial network; the process of accessing the non-terrestrial network is triggered based on the status information.

[0036] In some implementations of the second aspect, before receiving status information from the terminal device, the method further includes: sending first information to the terminal device, the first information indicating that the network device supports access based on status information.

[0037] In some implementations of the second aspect, the method further includes: receiving status indication information from a terminal device, the status indication information indicating that the terminal device stores status information.

[0038] In some implementations of the second aspect, the status indication information includes a first preamble, which is used for access when the terminal device stores status information.

[0039] In some implementations of the second aspect, the multiple preamble groups include a first preamble group and a second preamble group. The first preamble group is used for access when the terminal device stores state information, and the second preamble group is used for access when the terminal device does not store state information. The first preamble belongs to the first preamble group.

[0040] In some implementations of the second aspect, the status indication information is carried in the Media Access Control and Controller (MACCE) signaling or the Radio Resource Control (RRC) signaling.

[0041] In some implementations of the second aspect, the method further includes: receiving capability information from a terminal device, the capability information indicating that the terminal device stores state information, the capability information including state indication information.

[0042] In some implementations of the second aspect, the process of accessing the non-terrestrial network is triggered based on state information, including: if the state information verification is successful, the process of accessing the non-terrestrial network is triggered based on the state information.

[0043] In some implementations of the second aspect, the status information from the terminal device includes first security information, and the method further includes: obtaining fourth information from the core network element, wherein the status information of the terminal device carried in the fourth information includes second security information; and determining that the status information verification is successful if the first security information and the second security information are the same.

[0044] In some implementations of the second aspect, the status information from the terminal device includes first security information, and the method further includes: obtaining fourth information from the core network element, wherein the status information of the terminal device carried in the fourth information includes second security information; and determining that the status information verification fails or fails if the first security information and the second security information are different.

[0045] In some implementations of the second aspect, a second message is sent to the terminal device, indicating that the status information verification has failed; a second registration request message is received from the terminal device, the second registration request message being used to request access to the non-terrestrial network.

[0046] In some implementations of the second aspect, the method further includes: sending third information to the terminal device, the third information indicating that the status information verification is successful; and accessing the non-terrestrial network based on the status information.

[0047] In some implementations of the second aspect, the state information is verified through at least one of the following protocol layers: Packet Data Convergence Protocol (PDCP), Non-Access NAS, Service Data Adaptation Protocol (SDAP), Radio Link Control (RLC), Media Access Control (MAC), Radio Resource Control (RRC), or Physical PHY.

[0048] In some implementations of the second aspect, the process of accessing the non-terrestrial network is triggered based on status information, including: sending registration and activation information to the core network element, wherein the registration and activation information indicates the status information of the activated terminal device.

[0049] In some implementations of the second aspect, the method further includes: sending first configuration information, the first configuration information including the first effective time and / or the first effective region of status information.

[0050] In some implementations of the second aspect, the method further includes: when the network device moves, activating second configuration information, the second configuration information being associated with a second effective area, and the network device supporting the provision of services to terminal devices within the second effective area.

[0051] In some implementations of the second aspect, the status information includes at least one of the following: first security information, identification information associated with the terminal device, location information associated with the terminal device, quality of service (QoS) information, billing information, or capability information of the terminal device.

[0052] The beneficial effects of the second aspect and some implementations thereof can be referred to the relevant descriptions in the first aspect, and will not be repeated here.

[0053] Thirdly, a communication device is provided. This communication device has the functions described in the first aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the first aspect. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0054] In one possible design, the communication device includes: a processing unit for determining whether to store status information of the terminal device; and a communication unit for sending the status information to a network device if it is determined that status information is stored, the status information being used to access a non-terrestrial network.

[0055] The communication unit can perform the receiving and transmitting processes described in the first aspect above, and the processing unit can perform other processes described in the first aspect above besides receiving and transmitting.

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

[0057] Fourthly, a communication device is provided. This communication device has the functions described in the second aspect above. For example, the communication device includes modules, units, or means corresponding to the operations involved in the second aspect above. These modules, units, or means can be implemented through software, hardware, or a combination of software and hardware.

[0058] In one possible design, the communication device includes: a communication unit for receiving status information from a terminal device, the status information being used to access a non-terrestrial network; and a processing unit for triggering the execution of a process to access the non-terrestrial network based on the status information.

[0059] The communication unit can perform the receiving and transmitting processes described in the second aspect above, and the processing unit can perform other processes described in the second aspect above besides receiving and transmitting.

[0060] The aforementioned communication device may be a network device, or a module (such as a circuit, chip, or chip system) within a network device, or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0061] Fifthly, a communication device is provided. The communication device includes at least one interface circuit and at least one processor. The at least one processor is coupled to a memory. The memory is used to store part or all of a computer program or instructions necessary for implementing the functions involved in either the first or second aspect described above. The at least one processor is capable of executing the computer program or instructions, such that when the computer program or instructions are executed, the communication device implements the methods in any possible design or implementation of the first or second aspect described above. The interface circuit is used to implement communication functions within the communication device and / or communication functions between the communication device and other devices or components.

[0062] In one possible design, the at least one processor is used to communicate with other devices or components through the interface circuit.

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

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

[0065] The aforementioned communication device may be a network device, or a module (such as a circuit, chip, or chip system) within a network device, or a logical node, logical module, or software capable of implementing all or part of the functions of a network device.

[0066] Sixthly, a communication system is provided. This communication system includes at least one of the communication devices described in the third or fourth aspect.

[0067] In a seventh aspect, a chip or chip system is provided. It includes at least one processing circuit for running a computer program, causing the chip or chip system to perform the methods described in the first or second aspect and any possible implementation thereof.

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

[0069] Eighthly, a computer-readable storage medium is provided. This computer-readable storage medium stores computer program code or instructions, which, when read and executed by a computer, cause the method in any of the possible implementations of the first or second aspect to be implemented.

[0070] Ninthly, a computer program product is provided. The computer program product includes computer program code or instructions that, when read and executed by a computer, cause the method in any of the possible implementations of the first or second aspect to be implemented.

[0071] In a tenth aspect, a computer program is provided. When the computer program is run, it causes the method in any of the possible implementations of the first or second aspect to be implemented.

[0072] It should be understood that the beneficial effects of the third to tenth aspects mentioned above can be referred to the first or second aspects mentioned above and any possible implementation thereof, which will not be elaborated here. Attached Figure Description

[0073] Figure 1 This is a schematic diagram of a communication system applicable to an embodiment of this application;

[0074] Figure 2 This is a schematic diagram of a satellite communication system beam operating mode applicable to embodiments of this application.

[0075] Figure 3 This is a schematic diagram of a transparent satellite architecture applicable to embodiments of this application;

[0076] Figure 4 This is a schematic diagram of a non-transparent satellite architecture applicable to embodiments of this application;

[0077] Figure 5 This is a schematic diagram of another non-transparent satellite architecture applicable to the embodiments of this application;

[0078] Figure 6 This is a schematic diagram of another communication system applicable to embodiments of this application;

[0079] Figure 7 This is a flowchart illustrating an initial access method;

[0080] Figure 8 This is a flowchart illustrating a method for establishing status information during the initial access process;

[0081] Figure 9 This is a flowchart illustrating a communication method provided in an embodiment of this application;

[0082] Figure 10 This is a schematic diagram of a preamble set grouping provided in an embodiment of this application;

[0083] Figure 11 This is a schematic diagram of a protocol stack for verifying status information provided in this embodiment;

[0084] Figure 12 This is a schematic flowchart illustrating the initial access based on the state information stored in the terminal device itself, provided in an embodiment of this application.

[0085] Figure 13 This is a schematic diagram illustrating the scenario of initial access by the terminal device provided in this application embodiment;

[0086] Figure 14 This is a schematic diagram of the method for configuring and updating the status information of a terminal device provided in an embodiment of this application;

[0087] Figure 15 This is a schematic diagram of an open wireless access network architecture applicable to this application;

[0088] Figure 16This is a possible exemplary block diagram of the communication device involved in the embodiments of this application;

[0089] Figure 17 This is a schematic diagram of the terminal structure provided in the embodiments of this application;

[0090] Figure 18 This is a schematic diagram of the structure of the baseband processor in the terminal provided in the embodiments of this application. Detailed Implementation

[0091] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0092] Before introducing the scheme of this application, the following points should be noted.

[0093] First, in this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0094] Second, in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. In the textual description of this application, the character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a, b, and c. Here, a, b, and c can each be single or multiple.

[0095] Third, in this application, the terms "first," "second," "#1," and "#2," as well as various numerical designations, are used for ease of description and are not intended to limit the scope of the embodiments of this application. For example, they are used to distinguish different messages, rather than to describe a specific order or sequence. It should be understood that such descriptions can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0096] Fourth, in this application, "instruction" or "for instruction" can include both direct and indirect instruction. When describing instruction information as being used to instruct A, it can include whether the instruction information directly or indirectly instructs A, but does not necessarily mean that the instruction information carries A.

[0097] The indication methods involved in the embodiments of this application should be understood to cover various methods that enable the party to be indicated to obtain the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. Moreover, the sending period and / or sending time of these sub-information can be the same or different. This application does not limit the sending method, for example.

[0098] The "instruction information" in the embodiments of this application can be an explicit instruction, that is, a direct instruction through signaling, or an instruction obtained by combining other rules or parameters with the parameters indicated by the signaling, or by deduction. It can also be an implicit instruction, that is, an instruction obtained based on rules or relationships, or based on other parameters, or by deduction. This application does not specifically limit it in this regard.

[0099] Fifth, in this application, "protocol" can refer to a standard protocol in the field of communications, such as fifth-generation (5G) protocols. th This application does not limit the scope of network protocols such as generation (5G), New Radio (NR) protocols, and related protocols applied in future communication systems. "Predefined" may include predefined terms, such as protocol definitions. "Preconfiguration" can be achieved by pre-storing corresponding codes, tables, or other means of indicating relevant information in the device; this application does not limit the implementation method.

[0100] Sixth, in this application, terms such as "message," "information," "signal," or "information element (IE)" can be used interchangeably. There are no restrictions on the name of the message or information, as long as it can achieve the corresponding function.

[0101] "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information to that device directly or indirectly. "Receiving information from XX (device), or receiving information from XX (device)" can be understood as the source of the information being that device. This can include receiving information from that device directly or indirectly. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0102] "Communication" can also be described as data transmission, information transmission, data processing, etc. "Transmission" includes sending and / or receiving. "Transmission" can be described as output. "Sending" can also be understood as the output of a chip interface, and "receiving" can be understood as the input of a chip interface. In other words, "sending" or "receiving" can occur between devices, for example, between network devices and terminal devices via an air interface. "Sending" or "receiving" can also occur within a device, for example, between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0103] For example, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For instance, "a network device sending information" can be understood as a network device sending information to another device (such as a terminal), or it can be understood as logical module 1 within the network device sending information to logical module 2 within the network device. Similarly, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as one logical module within a device receiving information from another logical module. For instance, "a network device receiving information" can be understood as a network device receiving information from another device (such as a terminal), or it can be understood as logical module 1 within the network device receiving information from logical module 2 within the network device.

[0104] Seventh, in this application, the words "exemplarily," "for example," etc., are used to indicate examples, illustrations, or descriptions. Any embodiment or design scheme described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the word "example" is intended to present concepts in a concrete manner. In the embodiments of this application, "of," "corresponding, relevant," "corresponding," and "associate" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.

[0105] Eighth, in this application, the configuration can be signaling configuration, such as Radio Resource Control (RRC) messages, downlink control information (DCI), or system information blocks (SIBs). Optionally, the signaling configuration can be provided to the terminal device by pre-configured signaling configuration, or configured to the terminal device through pre-configuration. Here, pre-configuration refers to defining or configuring the values ​​of corresponding parameters in advance using a protocol, and storing them in the terminal device during communication. The pre-configured messages can be modified or updated when the terminal device is connected to a network.

[0106] Ninth, in this application, when comparing A and B, the description "when A is greater than or equal to B, execute method A; when A is less than or equal to B, execute method B" can be implemented in a way that is "when A is greater than or equal to B, execute method A; when A is less than B, execute method B"; or it can be "when A is greater than B, execute method A; or when A is less than or equal to B, execute method B". This application does not limit this. For ease of description, the implementation methods provided in this application are all illustrated using "when A is greater than or equal to B, execute method A; or when A is less than B, execute method B" as an example. In other words, "<" means less than, "≤" means less than or equal to, and "<" and "≤" can be interchanged without limitation. Similarly, ">" means greater than, "≥" means greater than or equal to, and ">" and "≥" can be interchanged without limitation. The examples provided in this application are merely illustrative and do not constitute a limitation on this application.

[0107] The following describes the communication system to which this application applies.

[0108] The technical solution of this application can be applied to non-terrestrial network NTN systems such as satellite communication systems and high altitude platform station (HAPS) communication, including integrated communication and navigation (ICaN) systems and global navigation satellite systems (GNSS). Satellite communication systems can be integrated with traditional mobile communication systems. These mobile communication systems can be 5G or NR systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunication systems (UMTS), etc. The technical solution provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), Internet of Things (IoT) communication systems, or other communication systems.

[0109] For example, a satellite communication system may include terminal equipment and network equipment.

[0110] The terminal device in this application embodiment can be referred to as user equipment (UE). The terminal device in this application is a device with wireless transceiver capabilities, capable of communicating with one or more core networks via a satellite base station. The terminal device can also be referred to as an access terminal, terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, user agent, or user device, etc. The terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (e.g., on ships); and it can also be deployed in the air (e.g., on airplanes, balloons, and satellites). The terminal device can be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, smartphone, mobile phone, wireless local loop (WLL) station, personal digital assistant (PDA), etc.; or, the terminal device can also be a handheld device with wireless communication capabilities, a computing device or other device connected to a wireless modem, in-vehicle device, wearable device, drone device, or a terminal in the Internet of Things (IoT), vehicle network, 5G network, or any form of terminal in future networks, relay user equipment, or terminal in future networks, etc. This application does not limit the type or category of the terminal device.

[0111] 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.

[0112] The network device in this application embodiment may include one or more satellite and ground station devices. The network device can be any device with wireless transceiver capabilities used to communicate with terminal devices; it can also be called an access network device or a wireless access network device, such as a base station. In this application embodiment, the network device can refer to a radio access network (RAN) node (or RAN device, or RAN entity) that connects the terminal device to the wireless network. The RAN can be viewed as a sub-network of the operator's network, serving as the implementation system between service nodes and terminal devices within the operator's network. For example, for a terminal device to access the operator's network, it first goes through the network device, and then connects to the service nodes of the operator's network via the network device. The aforementioned RAN can be the 3rd Generation Partnership Project (3GPP). rdCellular systems related to the Generation Partnership Project (3GPP), such as 5G mobile communication systems or future-oriented evolved systems. RAN can also be an open radio access network (O-RAN or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (WiFi) system. RAN can also be a communication system that integrates two or more of the above systems. Network equipment includes, but is not limited to: generation node base stations (gNBs) in 5G systems, evolved node Bs (eNBs) in LTE, radio network controllers (RNCs), node Bs (NBs), base station controllers (BSCs), base transceiver stations (BTSs), home evolved node Bs (HNBs), base band units (BBUs), transmitting and receiving points (TRPs), transmitting points (TPs), small cell equipment, mobile switching centers, or network equipment in future networks. In systems employing different wireless access technologies, the names of devices with access network equipment functions may differ. For ease of description, in the embodiments of this application, the aforementioned devices providing wireless communication functions for terminal devices are collectively referred to as access network equipment or simply RAN or AN. It should be understood that this document does not limit the specific type of access network equipment.

[0113] In some deployments, multiple RAN nodes collaborate to assist terminals in achieving wireless access, with different RAN nodes each implementing some of the base station's functions. For example, a RAN node can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0114] In different systems, CU (including open CU-CP (O-CU-CP) and open CU-UP (O-CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called an open central unit (O-CU), DU can also be called an open distributed unit (O-DU), and RU can also be called an open radio unit (O-RU). For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0115] Network equipment can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of that mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0116] In this embodiment, the apparatus for implementing the functions of the access network device can be a network device or an apparatus capable of supporting the access network device in implementing the functions, such as a chip system or a chip. This apparatus can be installed in the access network device. In this embodiment, the chip system can be composed of chips or can include chips and other discrete components.

[0117] For example, a satellite communication system may also include a core network (CN). The core network may include, but is not limited to, the following network functions (NFs): user plane function (UPF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management function (UDM), unified data repository function (UDR), application function (AF), authentication server function (AUSF), access and mobility management function (AMF), and session management function (SMF).

[0118] It is understandable that the aforementioned network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualization functions instantiated on a shared platform (e.g., a cloud platform). Simply put, an NF can be implemented in hardware or software.

[0119] It should be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in future networks, some or all of the above-mentioned network elements may use the terminology from 5G, or they may use other names, etc.

[0120] Figure 1 This is a schematic diagram of a communication system applicable to an embodiment of this application. For example... Figure 1As shown, the system architecture 100 may include terminal equipment, satellite base stations (e.g., satellite base station 101 and satellite base station 102), a core network, and a data network (DN). The data network, also known as a packet data network (PDN), is typically a network located outside the operator's network, such as a third-party network. In some implementations, the DN may also be deployed by the operator, meaning the DN is part of the public land mobile network (PLMN). This application does not restrict whether the DN belongs to the PLMN. Various services can be deployed on the DN, providing data and / or voice services to the terminal equipment.

[0121] Each satellite can provide communication, navigation, and positioning services to terminal devices via multiple beams. In this scenario, the satellites include low Earth orbit (LEO), medium Earth orbit (MEO), high elliptical orbit (HEO), and geostationary Earth orbit (GEO) satellites. Satellite base station 102 connects to a ground gateway station (such as NTN Gateway), which can also be called a gateway station, signaling station, or ground station equipment. The satellite uses multiple beams to cover the service area, and different beams can communicate via one or more of time-division, frequency-division, and space-division multiplexing. The satellite communicates wirelessly with terminal devices through broadcast communication signals and navigation signals, and can also communicate wirelessly with ground station equipment. The satellite mentioned in this embodiment can be a satellite base station, an integrated access backhaul device, an orbital receiver or repeater for relaying information, or network-side equipment mounted on the satellite. For ease of description, in the embodiments of this application, a satellite with access network functionality is referred to as a satellite access network device, or a base station deployed on a satellite is referred to as a satellite base station.

[0122] Taking 5G networks as an example, ground-based terminal devices can communicate with satellite base stations using the 5G New Radio (NR). For instance, satellite base stations can wirelessly communicate with terminal devices via broadcast communication signals and navigation signals. The connection between the terminal device and the satellite base station can be called a service link. Satellite base stations can wirelessly communicate with ground stations (also known as gateway stations, ground access points, or signaling gateways) via the NG interface (e.g., for exchanging signaling such as NAS in the core network and user service data). Satellite base stations can also communicate with the core network via ground access points. Ground stations are primarily responsible for forwarding signaling and service data between satellite base stations and the core network; the connection between satellite base stations and ground stations can be called a feeder link. Simultaneously, inter-satellite links (ISL) exist between satellites to facilitate signaling interaction and user data transmission between 5G access network devices. For example, satellite base station 101 can wirelessly communicate with satellite base station 102 via the Xn interface (e.g., for handover signaling interaction). Normally, the service link between the terminal device and the satellite base station, as well as the feeder link between the satellite base station and the ground station, are connected. That is, uplink and downlink messages between the terminal device and the core network can be transmitted through the satellite base station and the ground station.

[0123] Figure 2 This is a schematic diagram of a satellite communication system beam operating mode applicable to embodiments of this application. For example... Figure 2 As shown, taking satellite communication as an example, based on the operating mode of the payload (such as a beam), satellite communication systems can generally be divided into staring (earth-fixed or quasi-earth fixed) and non-staring (earth-moving) systems. For example, for non-staring systems, such as... Figure 2 As shown in (a), over a period of time (e.g., times T1, T2, and T3), the satellite beam coverage area moves along with the satellite; for staring systems, as... Figure 2 As shown in (b), over a period of time (e.g., times T1, T2, and T3), the satellite dynamically adjusts the beam direction to make the beam approximately cover the same area of ​​the ground.

[0124] Depending on the payload type, satellite communication systems include transparent satellite architecture and non-transparent satellite architecture. Transparent transmission, also known as bend-tube relay transmission, means that the signal only undergoes frequency conversion and amplification on the satellite; the satellite is transparent to the signal, as if it doesn't exist. Non-transparent transmission, also known as regenerative (on-board access / processing) transmission, means that the satellite has some or all of the base station functions.

[0125] Figure 3This is a schematic diagram of a transparent satellite architecture applicable to embodiments of this application. For example... Figure 3 As shown, in the transparent satellite-based NG-RAN architecture, the base station is deployed on the ground, and the satellite acts as a relay node. Link transmission between the satellite and the UE, as well as between the satellite and the NTN gateway, uses the Uu interface (the interface between the terminal and the access network, also known as the air interface). The NTN gateway then forwards the signals from the satellite to the gNB via the Uu interface. The gNB then accesses the 5G core network through the terrestrial network.

[0126] Figure 4 and Figure 5 This is a schematic diagram of a non-transparent satellite architecture applicable to embodiments of this application. For example... Figure 4 As shown, all base station entities are deployed on NTN equipment, such as... Figure 5 As shown, the base station entity (e.g., gNB-DU) is deployed on NTN equipment. NTN equipment can be satellite or other non-terrestrial equipment. That is, in the NG-RAN architecture based on regenerated satellites, the satellite can either perform the functions of the entire gNB or only the functions of the DU within the gNB. When the satellite performs the functions of the entire gNB, the service link between the satellite and the UE uses the Uu interface, while the satellite radio interface (SRI) between the satellite and the NTN gateway uses the NG interface (the logical interface between NG-RAN and the 5G core network). The NTN gateway connects the NTN and the 5G core network through the NG interface. For multi-satellite NTNs, different satellites can also communicate through inter-satellite links (ISL) while serving their respective UEs, thus connecting to the same 5G core network on the ground. In this case, the ISL uses the Xn interface (the logical interface between gNBs). When the gNB is divided into DU and CU, the DU is deployed on a satellite, while the CU is deployed on the ground. In this case, the SRI between the satellite and the NTN gateway uses the F1 interface, and the NTN gateway then connects to the CU of the gNB through the F1 interface.

[0127] It is worth noting that, in addition to carrying the functions of the RAN side, satellites can also carry some or all of the core network functions, such as access and mobility management network elements (AMF), session management network elements (SMF), authentication server network elements (AUSF), policy control nodes (PCF), or user plane function network elements (UPF).

[0128] Figure 6 This is a schematic diagram of another satellite communication system applicable to embodiments of this application. For example... Figure 6As shown, the satellite communication system includes satellites 401, 402, and 403. Each satellite can provide communication, navigation, and positioning services to terminal devices via multi-beam communication. In this scenario, the satellites can be LEO or MEO satellites, etc. Satellite 403 connects to ground station equipment (such as…). Figure 6 (The core network equipment shown).

[0129] For example, a satellite can use multiple beams to cover the service area (e.g. Figure 6 The satellite, as shown, covers a service area with multiple beams. Different beams can communicate via one or more of time-division, frequency-division, or space-division methods. The satellite communicates wirelessly with terminal equipment through broadcast communication signals and navigation signals, and can also communicate wirelessly with ground station equipment.

[0130] Satellite communication systems include transparent satellite architecture and non-transparent satellite architecture. For example, Figure 6 Satellites 401 and 402 are non-transparent satellite architectures, while satellite 403 is a transparent satellite architecture. Furthermore, the satellites can operate in either staring (e.g., earth-fixed or quasi-earth fixed) or non-staring (e.g., earth-moving) mode.

[0131] It should be understood that the above Figures 1 to 6 The communication system illustrated uses a satellite communication system combined with a 5G system as an example. This is a simplified diagram for ease of understanding; the satellite communication system may also include other devices, which are not shown in the diagram. Furthermore, when the satellite communication system is combined with other terrestrial communication systems, the network elements and interfaces involved may have other names, and this application does not specifically limit them.

[0132] The following is combined Figure 7 and Figure 8 This document explains the initial access process for NR / NTN.

[0133] Figure 7 This is a flowchart illustrating an NR / NTN initial access method. Taking a 5G UE access in a standalone network as an example, the initial access process includes cell search and selection, access, RRC connection establishment, initial context establishment, and protocol data unit (PDU) session establishment, among which PDU session establishment is an optional step. Figure 7 As shown, the method includes the following steps; for details not covered, please refer to the relevant descriptions in existing solutions.

[0134] S710, UE performs cell search and selection: the process of UE and NR cell achieving downlink synchronization and selecting the NR cell with the best signal to camp on.

[0135] S720, the UE and gNB perform an access procedure: a necessary process for the UE and the network to establish a radio link. The UE establishes uplink synchronization with the NR cell and obtains uplink resources through the access procedure.

[0136] S730, UE and gNB perform RRC connection establishment: the process of establishing radio signaling bearer 1 (SRB1) between UE and gNB.

[0137] S740, Initial Context Establishment is Performed Between UE, gNB, and 5GC: When making various event decisions or executing various algorithms, the gNB needs to know the UE's context information (or UE's state information) in order to make the most appropriate decision. After the initial context establishment is completed, the gNB can obtain all the UE context it needs.

[0138] Understandably, during the initial UE access process, the UE and the network side need to exchange UE state information (also known as UE context information). For example, the UE state information includes at least one of the following: PDU session context, security key, mobility constraint list, UE radio capabilities, and UE security capabilities.

[0139] S750, PDU session establishment is performed between UE, gNB and 5GC: PDU session is used to provide PDU connectivity service between UE and data network DN, that is, to support PDU session exchange between UE and DN. Therefore, when UE initiates data service, PDU session establishment process is involved.

[0140] Figure 8 This is a method for establishing state information during the initial access process of NR / NTN. This is understandable. Figure 8 It can be seen as Figure 7 The specific implementation of the initial context establishment in step S740. For example... Figure 8 As shown, the method includes the following steps; for details not covered, please refer to the relevant descriptions in existing solutions.

[0141] S801, the UE sends an RRC setup complete (e.g., RRCSetupComplete) message to the gNB, and the gNB receives the RRC setup complete message from the UE. The RRC setup complete message may carry at least one of the following: selectedPLMN-Identity, registeredAMF, s-nssai-list, and NAS.

[0142] In S802, the gNB sends an initialization (e.g., INITIAL UE MESSAGE) message to the 5GC, and correspondingly, the 5GC receives the initialization message from the gNB. For example, the gNB assigns a dedicated RAN-UE-NGAP-ID to the UE, selects the 5GC (e.g., the AMF node) based on the selectedPLMN-Identity, registeredAMF, and s-nssai-list, and then sends the NAS carried in the RRCSetupComplete message to the AMF via the INITIAL UE MESSAGE, triggering the NG-C connection establishment.

[0143] S803 and gNB transmit NAS messages between UE and 5GC to complete IDENTITY query, authentication, NAS security mode and registration process.

[0144] In step S804, the 5GC sends an Initial Context Establishment Request (e.g., INITIAL CONTEXT SETUPREQUEST) message to the gNB, and the gNB receives the Initial Context Establishment Request message from the 5GC. This Initial Context Establishment Request message is used to request the initiation of initial context establishment.

[0145] In step S805, the gNB sends a security mode command (e.g., SecurityModeCommand) message to the UE, and the UE receives the security mode command message from the gNB. The security mode command message is used to notify the UE to initiate the integrity protection and encryption process. Afterwards, downlink encryption is initiated.

[0146] In step S806, the UE sends a Security Mode Complete (e.g., SecurityModeComplete) message to the gNB, and the gNB receives the Security Mode Complete message from the UE. For example, the UE derives a key based on the integrity protection and encryption algorithm indicated in the SecurityModeCommand message, and then replies with a SecurityModeComplete message to the gNB. Afterward, uplink encryption is initiated.

[0147] S807, the gNB sends a UE capability inquiry (e.g., UECapabilityEnquiry) message to the UE. Correspondingly, the UE receives the UE capability inquiry message from the gNB, that is, the gNB initiates the UE capability query process.

[0148] S808, the UE sends UE capability information (e.g., UECapabilityInformation) to the gNB, and the gNB receives the UE capability information from the UE.

[0149] In step S809, the gNB sends UE capability information (e.g., UE RADIO CAPABILITY INFOINDICATION) to the 5GC, and correspondingly, the 5GC receives the UE capability information from the gNB. It is understood that the above steps S808 and S809 are transmitted transparently by the gNB.

[0150] S810, the gNB sends an RRC reconfiguration (e.g., RRCReconfiguration) message to the UE, and the UE receives the corresponding RRC reconfiguration message from the gNB. This RRC reconfiguration message indicates the establishment of SRB2 and the data radiobearer (DRB). After encryption and integrity protection are completed during the dedicated NG-C connection establishment process, the gNB sends an RRCReconfiguration message carrying srb-ToAddModList and drb-ToAddModList information cells to the UE, instructing the UE to establish SRB2 and the DRB.

[0151] S811, the UE sends an RRC reconfiguration complete (e.g., RRCReconfigurationComplete) message to the gNB, and the gNB receives the RRC reconfiguration complete message from the UE. For example, after receiving the RRCReconfiguration message, the UE begins establishing SRB2 and DRB. Specifically, the UE establishes the corresponding PDCP entity and configures relevant security parameters, establishes and configures the RLC entity, establishes and configures the DCCH logical channel, and establishes and configures the DTCH logical channel. After the SRB2 and DRB are successfully established, the UE replies with an RRCReconfigurationComplete message to the gNB.

[0152] S812, gNB sends an initial context establishment response (e.g., INITIAL CONTEXT SETUPRESPONSE) message to 5GC, and 5GC receives the initial context establishment response message from gNB.

[0153] Based on the above scheme, during the initial access process for NTN, the UE's state information (or UE's context information) is configured and maintained by the network side. When a satellite node moves, the UE's state information needs to be transmitted to the next satellite node, resulting in significant signaling overhead. Furthermore, due to the large propagation delay of satellites, the complete initial access process involves multiple exchanges of UE state information, leading to significant end-to-end latency (up to 10 seconds or even higher).

[0154] Considering that satellites are constantly moving, the mobility of the UE itself is generally negligible. Therefore, the UE's state information can be shifted from being carried by the network side to being stored and carried by the UE itself. In view of this, this application provides a communication method and apparatus that simplifies the access process by having the UE carry its own state information, avoiding frequent state information exchanges between network nodes during satellite movement, thereby reducing signaling overhead and access latency.

[0155] The following detailed description, in conjunction with the accompanying drawings, will further illustrate the communication method and communication device provided in the embodiments of this application, which can be applied to the above-mentioned... Figures 1 to 6 The communication system shown. It should be understood that the embodiments of this application can be applied to scenarios where the sending end and the receiving end communicate.

[0156] It is understood that this application uses network devices and terminal devices as examples to illustrate the execution of the interaction, but this application does not limit the execution subject of the interaction. For example, the method executed by the network device in this application can also be implemented by a module (e.g., circuit, chip, or chip system) in the network device, or a logical node, logical module, or software that can implement all or part of the network functions; as another example, the method executed by the terminal device in this application can also be implemented by a communication module in the terminal device or a circuit or chip (such as a modem chip (also known as a baseband chip), or a SoC chip containing a modem core, or a SIP chip) in the terminal device that is responsible for communication functions.

[0157] It should be noted that, in this application, a satellite with access network functionality is referred to as a satellite access network device, or a base station deployed on a satellite is referred to as a satellite base station. For example, network equipment refers to network-side equipment mounted on a satellite; network equipment can be called a satellite or a satellite base station, and the satellite can carry some or all of the functions of a base station.

[0158] Figure 9 This is a schematic flowchart of a communication method provided in this application. Figure 9 As shown, the method includes the following steps; for details not covered, please refer to existing related descriptions.

[0159] S910, the terminal device determines whether to store the terminal device's state information (state replica).

[0160] In this application, whether or not the terminal device's valid status information is stored can be replaced with whether or not the terminal device has valid status information, or whether or not the terminal device's valid status information is carried by itself, etc., without limiting its specific name.

[0161] Here, the status information of the terminal device refers to valid status information. Therefore, "status information" can be replaced with "valid status information." It is understood that the status information of the terminal device is valid. For example, the status information of the terminal device may have an effective area and / or an effective time. For instance, the effective area of ​​the status information is cell 1, and the effective time of the status information is 10:00-12:00. That is to say, if the terminal device is within the effective area, and / or the effective time of the status information is in progress, then the status information of the terminal device can be considered valid. In other words, the status information of the terminal device is valid within the effective time and / or effective area, meaning that simplified access and communication can be achieved based on the status information carried by the terminal device itself, thereby reducing signaling overhead and access / communication latency. Conversely, if the terminal device is not within the effective area, and / or the effective time of the status information has not started or has ended, then the status information of the terminal device can be considered invalid, or the status information of the terminal device can be updated. In other words, the status information of the terminal device is not valid outside the effective time and / or effective area, meaning that simplified access and communication based on the status information carried by the terminal device itself may not be supported.

[0162] In one implementation, the terminal device can determine whether to store its own status information based on whether it has such information stored locally. Alternatively, the terminal device can determine whether it has stored valid status information based on the effective region and / or effective time of the status information.

[0163] For example, the status information includes at least one of the following: first security information, identification information associated with the terminal device, location information associated with the terminal device, quality of service (QoS) information, billing information, or capability information of the terminal device, as specifically defined below.

[0164] (1) First security information, such as key information, authentication vector, check code, or access policy, at least one of the following.

[0165] (2) Identification information associated with the terminal device, such as at least one of the following: terminal device identifier, session identifier, interface identifier, or tunnel identifier.

[0166] (3) Location information associated with the terminal device, such as cell identifier, tracking area identifier, wave position identifier, area identifier, Internet protocol address (IP), or other identifiers containing geographical location.

[0167] (4) Quality of Service (QoS) information, such as QoS level, priority, forwarding rules, and mapping rules between QoS and DRB.

[0168] (5) Billing information, such as network usage reports or contracted packages.

[0169] (6) Terminal equipment capability information, such as terminal type, power level, supported handover type, number of supported hybrid automatic repeat request (HARQ) processes, supported carrier aggregation (CA) or dual-connectivity (DC), or frequency / polarization capability, discontinuous reception (DRX) configuration information, etc.

[0170] In the embodiments of this application, the status information of the terminal device may also be referred to as the context information of the terminal device, or other information used for accessing the network. This application does not limit its name. For example, the status information of the terminal device may include context information of other access stratum (AS) and / or other non-access stratum (NAS), such as the UE's service status, allocated radio resources, relevant configuration information of the RRC layer, or relevant configuration information of the PDCP layer, etc.

[0171] In S920, if it is determined that state information is stored, the terminal device sends the state information to the network device, and the network device receives the state information from the terminal device. This state information is used to access non-terrestrial networks, such as NTN networks.

[0172] In other words, when a terminal device stores state information, it can request access to a non-terrestrial network based on the state information stored in the terminal device itself by sending the state information. This simplifies the access process and reduces signaling overhead and access / communication latency.

[0173] In steps S910-S920 above, the terminal device reports status information. Furthermore, the terminal device can explicitly or implicitly indicate to the network device whether it needs to store status information.

[0174] In one implementation, the method may further include: the terminal device sending status indication information to the network device, and correspondingly, the network device receiving the status indication information from the terminal device, wherein the status indication information indicates that the terminal device stores status information.

[0175] For example, the size of the status indication information is 1 bit. For instance, bit "1" indicates that the terminal device stores status information, and bit "0" indicates that the terminal device does not store status information. The terminal device can send bit "1" to the network device to indicate that the terminal device stores status information, and at the same time report the specific content of the status information.

[0176] In this embodiment, the timing of sending the status indication information is not limited. For example, the terminal device may send the status indication information to the network device before sending the status information; or, the terminal device may send the status indication information to the network device at the same time as sending the status information, i.e., the time of sending the status indication information is no later than the time of sending the status information. Optionally, the status indication information and the status information may be sent independently, or they may be carried in the same information (e.g., the sixth information). Based on this, the network device can determine that the terminal device stores status information.

[0177] The following provides examples illustrating the presentation of status indication information.

[0178] Example 1: The status indication information includes a first preamble, which is used for access when the terminal device has stored status information. The preamble is a specific bit sequence used in communication to synchronize signals between the transmitting and receiving ends, primarily for synchronization, frequency offset estimation, or automatic gain control.

[0179] For example, multiple preamble groups include a first preamble group and a second preamble group. The first preamble group is used for access when the terminal device stores state information, and the second preamble group is used for access when the terminal device does not store state information. The first preamble belongs to the first preamble group.

[0180] Figure 10 This is a schematic diagram of a preamble set grouping provided in an embodiment of this application. For example... Figure 10As shown, suppose there exists a preamble set containing multiple preambles. This preamble set is grouped into Group A (i.e., the first preamble group), Group B, and Group C, etc. Each Group includes one or more preambles. For example, Group A is dedicated to simplified access when the terminal device stores state information, Group B is dedicated to access when the network side configures state information, and Group C is dedicated to other uses. Therefore, when the terminal device selects a preamble from Group A (i.e., the first preamble) to send to the network device, it can instruct the terminal device to carry valid state information; when the terminal device selects a preamble from Group B or Group C (i.e., the second preamble group) to send to the network device, it instructs the UE not to carry valid state information.

[0181] Example 2: This status indication information is carried in the Media Access Control Unit (MAC) CE signaling or the Radio Resource Control (RRC) signaling.

[0182] For example, a new field can be added to the MAC CE to indicate whether the terminal device stores status information. For instance, this field is 1 bit in size, where bit "1" indicates that the terminal device stores status information and bit "0" indicates that the terminal device does not store status information. The terminal device can set the value of the new field in the MAC CE to "1" to indicate that the terminal device stores status information.

[0183] For example, in the EstablishmentCause scenario of a new RRC setup request, adding the mt-stateless-Access field indicates that the terminal device stores state information. Conversely, if the mt-stateless-Access field is not added to the RRC signaling to indicate that the terminal device does not store state information, the terminal device can indicate that it stores state information by including the mt-stateless-Access field in the RRC signaling.

[0184] Example 3: This status indication information is carried in the UE capability information. For example, the UE sends capability information to the network device, indicating that it stores status information, or in other words, that it supports reporting status information. The capability information includes the status indication information. Correspondingly, the network device receives the capability information from the UE and determines that the UE stores status information.

[0185] Before executing step S920, the network device can indicate whether it supports fast access and communication based on the status information carried by the terminal device itself by broadcasting a message.

[0186] In one implementation, before the terminal device sends status information to the network device, i.e. before executing step S920, the method further includes: the network device sending first information to the terminal device, and correspondingly, the terminal device receiving the first information from the network device, the first information indicating that the network device supports access based on status information.

[0187] For example, the first information can be a broadcast message, such as a master information block (MIB) message, a system information block (SIB) message, or other messages. For instance, the network device can carry indication information in the first information, indicating whether the network device supports access based on the state information stored by the terminal device itself, or in other words, whether it supports fast access based on the state information carried by the terminal device itself. For example, the size of this indication information is 1 bit, with bit "0" indicating no support and bit "1" indicating support; or, the network device can add a field `access_type` to the first information, with corresponding values ​​of {state, stateless} or {network, UE}, where stateless / UE indicates that the network device supports fast access with the terminal device carrying state information, and state / network indicates that access is supported by configuring state information on the network side; there is no limitation on this.

[0188] S930: Network devices trigger the process of accessing non-terrestrial networks based on status information.

[0189] For example, if the status information verification is successful, the network device triggers the execution of the access to the non-terrestrial network based on the status information.

[0190] Before executing step S930, the network device can perform security verification on the status information received from the terminal device to improve the reliability and security of the terminal device's status information and ensure the terminal device's secure access to the network.

[0191] Optionally, the network device sends registration activation information to the core network element, which instructs the core network element to activate the status information of the terminal device.

[0192] In one implementation, the network device can obtain fourth information from the core network element. This fourth information carries the terminal device's status information, including second security information. If the first and second security information are identical, the network device determines that the status information verification is successful. That is, by comparing the first security information in the status information reported by the terminal device with the second security information provided by the core network element, the network device determines that the status information verification is successful. Based on this, the network device can determine that the status information reported by the terminal device has not been tampered with, and can then execute step S930.

[0193] Furthermore, the network device can send a third piece of information to the terminal device, indicating that the status information verification has passed. Correspondingly, the terminal device receives the third piece of information from the network device, confirms that the status information verification has passed, and can then access the non-terrestrial network based on the status information, achieving a simplified access process and reducing signaling overhead and access latency.

[0194] In another implementation, the network device can obtain fourth information from the core network element. This fourth information carries the terminal device's status information, including second security information. If the first and second security information differ, the network device determines that the status information verification has failed. In other words, by comparing the first security information reported by the terminal device with the second security information provided by the core network element, a discrepancy is determined, thus indicating that the status information verification has failed. Based on this, the network device can determine that the status information reported by the terminal device has been tampered with, and therefore can refuse to execute step S930.

[0195] Furthermore, the network device can send a second message to the terminal device, indicating that the status information verification failed. Optionally, the second message may carry a reason value, indicating that the first security information in the status information failed verification. Correspondingly, the terminal device receives the second message from the network device and determines that the status information verification failed, thus preventing it from accessing the non-terrestrial network based on the status information. For example, the terminal device can send a second registration request message (e.g., a registration request) to the network device. The second registration request message is used to request access to the non-terrestrial network. Specific implementation methods can refer to the relevant descriptions of existing solutions, such as performing NAS authentication, security authentication, subscription data acquisition, and context establishment.

[0196] It should be noted that the second registration request message does not carry the status information of the terminal device, but it may carry the identifier of the terminal device.

[0197] For example, the second security information includes at least one of key information, authentication vector, checksum, or access policy.

[0198] Optionally, this application does not limit the security algorithm used to verify the first security information and the second security information.

[0199] Optionally, the second security information can be predefined or preconfigured, or it can be configured by the core network element through signaling; there is no limitation on this. The network device acquires the second security information no later than step S930.

[0200] In summary, step S930 is executed only if the terminal device's stored state information is successfully verified, thus ensuring secure network access for the terminal device. If the terminal device's state information verification fails, the network device can refuse the terminal device's access to the non-terrestrial network based on that state information.

[0201] The verification function for the status information of the aforementioned terminal devices can be deployed in at least one protocol layer of the network device.

[0202] In one implementation, the network device verifies the status information of the terminal device through at least one of the following protocol layers: Packet Data Convergence Protocol (PDCP), Non-Access NAS, Service Data Adaptation Protocol (SDAP), Radio Link Control (RLC), Media Access Control (MAC), Radio Resource Control (RRC), or Physical PHY. In other words, the terminal device's status information verification function can be deployed in at least one of the above protocol layers, without limitation.

[0203] Figure 11 This is a schematic diagram of a protocol stack for verifying status information provided in this embodiment. For example... Figure 11 As shown, the UE includes the NAS layer, RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, or PHY layer; the gNB includes the RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, or PHY layer; and the core network side (e.g., AMF) includes the NAS layer. For example, a status information verification function is added to the air interface PDCP layer to verify whether the status information carried by the terminal device is complete, or whether it has been tampered with.

[0204] Below is a brief explanation of the functions of the protocol layer that enables rapid authentication of terminal device status information.

[0205] (1) SDAP layer: mainly responsible for mapping QoS Flow to DRB.

[0206] (2) RRC layer: mainly responsible for the control plane processes related to the wireless access network.

[0207] (3) PDCP layer: mainly responsible for IP header compression, encryption and integrity protection.

[0208] (4) RLC layer: mainly responsible for data segmentation and reassembly.

[0209] (5) MAC layer: mainly responsible for logical channel multiplexing, HARQ retransmission, and scheduling-related functions.

[0210] (6) PHY layer: mainly responsible for functions such as encoding, decoding, modulation, demodulation, and multi-antenna mapping.

[0211] Based on the above scheme, malicious tampering of state information by the UE side is prevented, and the security performance and reliability of state information are improved. A new UE state verification function is added to the air interface protocol layer (such as the PDCP layer).

[0212] It should be noted that the protocol layer described above for implementing the fast authentication function of terminal device status information is only an example for ease of understanding. This application does not exclude other solutions, such as a newly defined air interface protocol layer.

[0213] Understandably, steps S920-S930 above are illustrative examples assuming the terminal device itself carries state information. Using the state information stored on the terminal device can simplify the access process and reduce signaling overhead and access / communication latency. Optionally, for cases where the terminal device does not store state information, the specific implementation method for the terminal device to access the network can refer to the relevant descriptions in existing solutions, i.e., the method also includes steps S940-S950.

[0214] S940, if it is determined that no state information will be stored, the terminal device sends a first registration request message (e.g., registration request) to the network device, and the network device receives the first registration request message from the terminal device. The first registration request message is used to request access to the non-terrestrial network.

[0215] S950, the network device triggers the process of accessing the non-terrestrial network based on the first registration request message.

[0216] It should be noted that the first registration request message does not carry the status information of the terminal device, but it may carry the identifier of the terminal device. The process by which a network device triggers the execution of access to a non-terrestrial network may include NAS authentication, subscription data acquisition, and context establishment. For specific implementation details, please refer to the relevant descriptions in existing solutions.

[0217] Below, in conjunction with Figure 12 and Figure 13 This paper provides an example illustrating the implementation method of initial access based on the state information stored in the terminal device itself.

[0218] Figure 12This is a schematic flowchart illustrating an initial access process based on the state information stored in the terminal device itself, provided in an embodiment of this application. Figure 12 As shown, firstly, when the UE turns on or enters the network device's coverage area, the UE can select the network PLMN it last registered (most recently) and perform cell selection. Further, the UE determines whether it has stored status information, or, based on the effective time and / or effective area, whether its status information is valid. If so, the UE reports this status information to the gNB, triggering a simplified access procedure for non-terrestrial networks; otherwise, if not, it sends a registration request message to the network device, requesting registration to the non-terrestrial network. Correspondingly, if the gNB receives the terminal device's status information, it instructs the core network element to execute the simplified access procedure; optionally, the gNB can verify the received status information and, if verification is successful, trigger the simplified access procedure to improve the security and reliability of network access. Conversely, if the gNB does not receive the terminal device's status information, or if status information verification fails, it rejects the UE's access request. Simultaneously, the gNB can instruct the UE to re-register and re-access the network.

[0219] Figure 13 This is a schematic diagram illustrating the initial access scenario of the terminal device provided in this application embodiment. For example... Figure 13 As shown, assuming UE-1 has no valid status information (such as first-time network access or invalid status information), UE-1 needs to trigger a regular access procedure. For example, UE-1 sends a registration request message to satellite 2 to request network access. UE-2 and UE-3 store valid status information locally. UE-2 and UE-3 can then request satellite 1 to trigger a simplified access procedure to reduce signaling overhead and access latency.

[0220] The following section provides examples illustrating the configuration and update methods for public configuration information on the network device side and private configuration information on the terminal device side.

[0221] For example, the public configuration information includes at least one of the following: mobility-related public configurations, such as LTM CSI Resource Config (including resource identifier, CSI resource set information corresponding to LTM candidate cells, or synchronization signal / physical broadcast channel block (SSB) resource set information), Radio Resource Config (signaling bearer, data bearer, bandwidth part (BWP) configuration, etc.), measurement configuration (SSB-based radio resource management measurement timing configuration (SMTC), measurement gap (GAP), measurement reporting method, and measurement reporting resource configuration), or RACH Config (access timing, preamble, etc. configuration), etc.

[0222] For example, the private configuration information includes at least one of the following: partial incremental configuration deltaconfig (the incremental configuration can be a differential configuration relative to LTM CSI Resource Config and Radio Resource Config), non-terrestrial communication network configuration NTN Config (such as ephemeris information, timing advance TA information, scheduling related information, effective service time t_service), and non-terrestrial communication network specific configuration NTN-specific measurement configuration information (such as smtc4 and associated measurement GAP information), UE's own capability information or security information, etc.

[0223] From the perspective of the terminal device, the terminal device can send configuration information #1 to the network device. This configuration information #1 includes the terminal device's status information #1, and the network device can trigger a simplified access process based on this status information #1.

[0224] Optionally, the network device may actively request to obtain the private configuration information of the terminal device (e.g., configuration information #1). When the service time or validity period of the network device expires, the network device may automatically release the private configuration information.

[0225] For example, suppose the status information of the terminal device is associated with a first effective area, which can be understood as the effective area of ​​the status information. In one implementation, the status information is effective when the terminal device is located in the first effective area; conversely, the status information is invalid when the terminal device is not located in the first effective area, and the terminal device can update its status information.

[0226] The method for determining whether a terminal device is located in the first effective region (or effective region, or effective geographical region, etc.) is as follows.

[0227] In one example, the terminal device can determine the relationship between the distance between its current location and a reference location and a first threshold. If the distance between the terminal device's current location and the reference location is greater than or equal to the first threshold, it can be determined that the terminal device is not located in the first effective area; conversely, if the distance between the terminal device's current location and the reference location is less than the first threshold, it can be determined that the terminal device is located in the first effective area.

[0228] Optionally, the first threshold can be predefined or preconfigured, or it can be configured by the network device through signaling; there is no limitation on this.

[0229] Optionally, the reference location can be set as the center point of the cell or the center point of the beam, without limitation.

[0230] In another example, the terminal device can determine whether the geographic grid number, geographic region number, wavelength number, and beam number corresponding to its current location belong to a pre-configured list of numbers. If none of these numbers belong to the pre-configured list, it can be determined that the terminal device is not located in the first effective area; conversely, if all of these numbers belong to the pre-configured list, it can be determined that the terminal device is located in the first effective area.

[0231] Optionally, the number list can also be predefined. Predefinition can include predefined rules, such as protocol definitions. Preconfiguration can be achieved by pre-storing the number list in network devices and / or terminal devices. The representation of the number list can also be replaced by: code, function, text, string, or other methods that can indicate relevant information (e.g., the correspondence between the current location of the terminal device and at least one of geographical grid number, geographical region number, beam number, or beam number). This application does not limit the specific implementation method.

[0232] It should be noted that when the terminal device is not located in the first effective area, or when the terminal device moves out of the effective area of ​​the status information, the terminal device needs to update the status information #1, such as re-initiating the registration process.

[0233] In one implementation, to ensure security, when the terminal device enters an idle or inactive state, a configuration update timer `timer_s` (e.g., `timer_s = 3h`) is triggered, indicating that the status information is valid for 3 hours. When the timer expires, a re-registration process needs to be triggered even if the terminal device is still within the effective geographical area. Optionally, if the terminal device enters a connected state before the timer expires, the timer is reset.

[0234] Optionally, the validity period (or effective time) of the terminal device's status information or the configuration information #1 reported by the terminal device can be constrained by Universal Time Coordinated (UTC) time, timers, system frame number (SFN) number, etc.

[0235] From the network device's perspective, the network device can send configuration information #2 to terminal devices within its service area. This configuration information #2 includes the effective time #1 of the status information and / or the effective area #1. At this time, the network device supports providing services to terminal devices within the effective area #1. In other words, the status information is valid within the effective time #1 and / or the effective area #1, and the terminal device can access the network based on this valid status information.

[0236] It should be noted that when a network device moves, it can activate configuration information #3, which is associated with the effective time #2 and / or the effective area #2. In this case, the network device supports providing services to terminal devices within the effective area #2. That is, after a network device moves, it may need to activate different public configuration information at different times and / or locations. For example, the network device activates configuration information #2 during time period T1, serving at least one terminal device in geographical area A1; after the move, the network device activates configuration information #3 during time period T2, serving at least one terminal device in geographical area A2. The terminal devices included in the serving geographical area A1 and the serving geographical area A2 can be different or partially the same, and this is not limited.

[0237] It is understandable that configuration information #2 and configuration information #3 are different. For example, the effective time #1 carried in configuration information #2 is different from the effective time #2 carried in configuration information #3, and / or the effective region #1 carried in configuration information #2 is different from the effective region #2 carried in configuration information #3.

[0238] Optionally, configuration information #1 can be sent as a candidate configuration, and configuration information #2 or configuration information #3 can be sent as a reference configuration. It is understood that a candidate configuration can be a partial configuration of configuration information (such as RRC configuration information) associated with a candidate cell or UE, a complete configuration, or an incremental configuration relative to the reference configuration. The reference configuration can be a general configuration provided by the network to a group of UEs within the same cell, providing a reference for incomplete candidate configurations. Optionally, configuration information #2 or configuration information #3 can be associated with different value tags. When the value tag does not change, even if the satellite changes, the terminal device does not need to update configuration information #2 or configuration information #3.

[0239] Figure 14 This is a schematic diagram illustrating the method for configuring and updating the status information of a terminal device provided in an embodiment of this application. For example... Figure 14 As shown, the terminal network collaboratively stores private and public configurations. For the network device side, for example, satellite 1 carries public configuration 1, and satellite 2 carries public configuration 2. Public configuration 1 and public configuration 2 can be considered as public RRC configuration information within the same effective area (e.g., within the same frequency band). Satellites 1 and 2 can communicate with UE-1, UE-2, and UE-3 within the effective area, and satellites 1 and 2 can communicate with the core network anchor point. Alternatively, UE-1, UE-2, and UE-3 can communicate with the core network anchor point through either satellite 1 or satellite 2. In one example, satellite 1 can configure public configuration 1 to UE-1, UE-2, and UE-3, and satellite 2 can configure public configuration 2 to UE-1, UE-2, and UE-3. It is understandable that the service area of ​​a satellite network can be divided into multiple geographical regions, each called a frequency band. Frequency bands can be represented in different shapes. For the terminal device side, for example, UE-1 carries UE-1 private configuration, UE-2 carries UE-2 private configuration, and UE-3 carries UE-3 private configuration. In one example, within the effective area, UE-1, UE-2 and UE-3 can report their respective private configurations to satellite 1 and / or satellite 2. Understandably, the private configurations of UE-1, UE-2 and UE-3 are different.

[0240] It should be noted that when any of UE-1, UE-2, or UE-3 moves out of the effective area, the private configuration of UE-1, UE-2, or UE-3 becomes invalid. UE-1, UE-2, or UE-3 can then update their own private configuration. Furthermore, due to satellite mobility, when satellite 1 or satellite 2 moves, different public configurations need to be activated at different times / locations. For example, satellite 1 can activate public configuration information P01 during time period T1, serving at least one terminal device in geographical area A1; after moving, satellite 1 can activate public configuration information P02 during time period T2, serving at least one terminal device in geographical area A2.

[0241] Based on the above scheme, by reporting the status information of the terminal device, a simplified access process can be executed based on this status information, reducing access latency and signaling overhead. Adding a status information verification function at the air interface protocol layer can prevent malicious tampering of the status information by the terminal device, improving the security and reliability of the status information. Reusing common configuration information further reduces signaling overhead. Furthermore, defining the effective area and / or validity period of the terminal device's status information can trigger timely updates of the terminal device's status information, ensuring its effectiveness.

[0242] As mentioned above, the network equipment involved in the technical solution of this application can be O-RAN. Under the O-RAN architecture, the RIC can directly control both the gNB-CU and the gNB-DU, requiring the above-mentioned... Figure 9 In the communication method steps shown, "network device" is extended to "CU" and "DU". Optionally, in various embodiments of this application, if the network device is a CU-DU separated architecture, after the CU receives information (e.g., fourth information) from a core network element (e.g., AMF), it can forward the information to the DU; or, after the DU receives information (e.g., status information) from the UE, it can forward the information to the CU.

[0243] Figure 15 This is a schematic diagram of the Open Radio Access Network (O-RAN) architecture applicable to this application. For example... Figure 15 As shown, the O-RAN architecture includes: a first network unit, a second network unit, a third network unit, an O-eNB, an O-CU-CP, an O-CU-UP, an O-DU, an O-RU, and an O-cloud.

[0244] The aforementioned network elements (also referred to as nodes) can be interconnected. For example, the first network unit connects to the O-cloud via the O2 interface; the first network unit connects to the third network unit, O-eNB, O-CU-CP, O-CU-UP, O-DU, and O-RU via the O1 interface; the first network unit connects to the O-RU via the open fronthaul M-Plane interface; the O-DU connects to the O-RU via the open fronthaul M-Plane interface and the open fronthaul C / U / S-Plane interface; the third network unit connects to the O-eNB, O-CU-CP, O-CU-UP, and O-DU via the E2 interface; the O-CU-CP connects to the O-DU via the F1-c interface; the O-CU-UP connects to the O-DU via the F1-u interface; and the O-CU-CP connects to the O-CU-UP via the E1 interface. Figure 15 For a detailed description of the interface shown, please refer to the existing standards; it will not be repeated here.

[0245] For example, the first network unit can be a service management and orchestration framework (SMO), or a network unit with similar functionality to an SMO; there is no limitation in this regard. The second network unit can be a Non-RT RIC, or a network unit with similar functionality to a Non-RT RIC; there is no limitation in this regard. The third network unit can be a Near-RT RIC, or a network unit with similar functionality to a Near-RT RIC; there is no limitation in this regard.

[0246] O-RAN aims to achieve an intelligent and open access network. A key feature of the O-RAN architecture is the separation of hardware and software, enabling the virtualization of network functions and the standardization of hardware. Furthermore, O-RAN incorporates artificial intelligence (AI).

[0247] The above text combined Figures 1 to 15 The communication method embodiments of this application have been described in detail below, and will be discussed in conjunction with... Figure 16 and Figure 17 The communication device embodiments of this application are described in detail below. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0248] Figure 16 This is a possible exemplary block diagram of the communication device involved in the embodiments of this application. For example... Figure 16As shown, the communication device 1000 may include modules or units for implementing the methods described in the embodiments above. In one possible design, the communication device 1000 includes a communication unit 1003 and a processing unit 1002. Optionally, the communication device 1000 may further include a storage unit 1001 for storing device program code and / or data. The communication unit 1003 may also be referred to as a communication interface, transceiver unit, or interface unit.

[0249] The communication device 1000 can be a terminal-side device as described in the above embodiments, such as a terminal device or a communication module in a terminal device, or a circuit or chip in a terminal device that is responsible for communication functions.

[0250] For example, in one embodiment, the processing unit 1002 is used to determine whether to store the status information of the terminal device; the communication unit 1003 is used to send the status information to the network device when it is determined that the status information is stored, and the status information is used to access the non-terrestrial network.

[0251] In one possible design, the communication unit 1003 is also used to send a first registration request message to the network device when it is determined that no state information is stored. The first registration request message is used to request access to the non-terrestrial network.

[0252] In one possible design, the communication unit 1003 is also used to receive first information from the network device, the first information indicating that the network device supports access based on status information.

[0253] In one possible design, the communication unit 1003 is also used to provide status indication information to the network device, indicating that the terminal device has stored status information.

[0254] In one possible design, the communication unit 1003 is also used to send capability information to the network device, the capability information indicating that the terminal device stores status information, and the capability information includes status indication information.

[0255] In one possible design, the communication unit 1003 is also used to receive second information from the network device, the second information indicating that the status information verification failed; the communication unit 1003 is also used to send a second registration request message to the network device, the second registration request message being used to request access to the non-terrestrial network.

[0256] In one possible design, the communication unit 1003 is also used to receive third information from the network device, the third information indicating that the status information verification is successful; the processing unit 1002 is also used to access the non-terrestrial network based on the status information.

[0257] In one possible design, the processing unit 1002 is also used to associate status information with the first effective area, and the method further includes: updating the status information when the terminal device is not located in the first effective area.

[0258] In one possible design, the processing unit 1002 is further configured to determine that the terminal device is not located in the first effective area if the distance between the location of the terminal device and the reference location is greater than or equal to a first threshold; and / or, determine that the terminal device is not located in the first effective area if the geographic grid number, geographic region number, beam position number and beam number corresponding to the location of the terminal device are not in a pre-configured number list.

[0259] In one possible design, when the communication device 1000 is a terminal device or a communication module within a terminal device, the function of the processing unit 1002 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the communication unit 1003 can be implemented by a transceiver circuit.

[0260] In one possible design, when the communication device 1000 is a circuit or chip responsible for communication functions in a terminal device, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 1002 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the communication unit 1003 can be implemented by an interface circuit or data transceiver circuit on the aforementioned chip.

[0261] The communication device 1000 can be a network-side device in the above embodiments, such as a network device, or a module (e.g., a circuit, chip, or chip system) in a network device, or a logical node or logical module that can implement all or part of the functions of the network device.

[0262] For example, in one embodiment, the communication unit 1003 is used to receive status information from the terminal device, the status information being used to access a non-terrestrial network; the processing unit 1002 is used to trigger the execution of the access to the non-terrestrial network process based on the status information.

[0263] In one possible design, the communication unit 1003 is also used to send first information to the terminal device, the first information indicating that the network device supports access based on status information.

[0264] In one possible design, the communication unit 1003 is also used to receive status indication information from the terminal device, the status indication information indicating that the terminal device stores status information.

[0265] In one possible design, the communication unit 1003 is also used to receive capability information from the terminal device, the capability information indicating that the terminal device stores status information, and the capability information including status indication information.

[0266] In one possible design, the processing unit 1002 is also used to trigger the execution of the access to the non-terrestrial network process based on the status information if the status information verification is successful.

[0267] In one possible design, the communication unit 1003 is further configured to obtain fourth information from the core network element, wherein the status information of the terminal device carried in the fourth information includes second security information; the processing unit 1002 is further configured to determine that the status information verification is successful if the first security information and the second security information are the same.

[0268] In one possible design, the communication unit 1003 is also used to send registration and activation information to the core network element, the registration and activation information indicating the status information of the activated terminal device.

[0269] In one possible design, the communication unit 1003 is also used to send first configuration information, which includes the first effective time and / or the first effective area of ​​status information.

[0270] In one possible design, the processing unit 1002 is further configured to activate second configuration information when the network device moves. The second configuration information is associated with a second effective area, and the network device supports providing services to terminal devices within the second effective area.

[0271] In one possible design, when the communication device 1000 is a network device or a communication module within a network device, the function of the processing unit 1002 can be implemented by one or more processors. Specifically, the processor may include a chip. The function of the communication unit 1003 can be implemented by a transceiver circuit.

[0272] In one possible design, when the communication device 1000 is a circuit or chip in a network device responsible for communication functions, the function of the processing unit 1002 can be implemented by a circuit system in the chip that includes one or more processors or processor cores. The function of the communication unit 1003 can be implemented by an interface circuit or data transceiver circuit on the chip.

[0273] It is understandable that the division of units in the above-mentioned device is merely a logical functional division. One function can correspond to one functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into one physical entity, or they can be distributed across different physical entities. Furthermore, the above-mentioned functional units can be implemented in hardware, software, or a combination of both.

[0274] In one example, the functional unit in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application-specific integrated circuits (ASICs), or one or more central processing units (CPUs), one or more microprocessor units (MPUs), one or more microcontroller units (MCUs), one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0275] In one example, storage unit 1001 may include random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory and / or registers, etc.

[0276] Figure 17 This is a schematic diagram of the structure of the terminal 2000 provided in the embodiments of this application. The terminal 2000 can correspond to... Figure 1 The terminal device shown is used to implement the operations of the terminal in the above embodiments. Figure 17 As shown, the terminal 2000 includes: one or more antennas 2010, a radio frequency processing system 2020, and a processor system 2030.

[0277] In the downlink or sidelink direction, the RF processing system 2020 receives RF signals through the antenna 2010 and sends the RF-processed signals to the processor system 2030 for further processing. In the uplink or sidelink direction, the processor system 2030 processes the terminal-side information and sends it to the RF processing system 2020, which then processes the signal and transmits it through the antenna 2010.

[0278] In one example, the radio frequency (RF) processing system 2020 serves as the communication interface for external communication of the terminal and may include a radio frequency front end (RFFE) 2021 and an RF transceiver 2022. The RFFE 2021 is primarily used for one or more processing operations, such as shaping, passband selection, or gain adjustment, on the RF signals received by the antenna or those to be transmitted through the antenna. It may include one or more components such as RF switches, duplexers, filters, power amplifiers, antenna tuning, and low-noise amplifiers. The RFFE 2021 can be a circuit system composed of multiple discrete components or integrated into one or more chips. The RF transceiver 2022 processes the RF signals received by the RFFE into baseband / IF signals for further processing by the processor system 2030, and processes the baseband / IF signals provided by the processor system 2030 into RF signals for transmission to the RFFE 2021. The baseband / IF signals transmitted between the RF transceiver 2022 and the processor system 2030 can be digital or analog signals. An RF transceiver 2022 can be implemented by one or more chips, which are commonly referred to as RF chips.

[0279] In one example, processor system 2030 may include one or more processors for processing signals and executing one or more communication protocols. Optionally, processor system 2030 may also include memory 2036. In one example, the one or more processors include at least one baseband processor 2031 (also known as a modem processor). Memory 2036 is used to store data and / or computer program instructions. Optionally, processor system 2030 may also include one or more application processors 2032 for implementing processing of the terminal operating system and application layer. Optionally, processor system 2030 may also include one or more of a voice subsystem 2033, a multimedia subsystem 2034, or an interface circuit 2035. The voice subsystem 2033 is used to process voice signals, the multimedia subsystem 2034 is used to handle multimedia-related operations, such as video encoding / decoding, image processing, etc., and the interface circuit 2035 is used to implement communication with other terminal components, such as a display 2040, an input device 2050, memory 2060, etc. The above-mentioned components in processor system 2030 can communicate with each other via a bus or communication interface circuit.

[0280] In one example, the processor system 2030 can be packaged as a single processor chip, such as a SoC chip or a SIP chip. In another example, the processor system 2030 can be a system composed of multiple chips; for example, the baseband processor 2031 can be packaged as a single chip, or packaged with part or all of the circuitry of the radio frequency processing system into a single chip.

[0281] In one example, memory 2036 can be on-chip memory, i.e., located on the processor system 2030 chip. In another example, memory 2060 can be off-chip memory, i.e. located outside the processor system 2030 chip.

[0282] Figure 18 This is a schematic diagram of the structure of the baseband processor 2031 in the terminal 2000 provided in this application embodiment, as shown below. Figure 18 As shown, the system may include one or more processor cores 20311 and interface circuitry 20314. The one or more processor cores 20311 are used to process signals and execute one or more communication protocols. Optionally, the baseband processor 2031 may also include a memory 20312 for storing at least a portion of the corresponding computer program instructions and / or data. In one example, the one or more processor cores 20311 implement the relevant operations in the above method embodiments by executing the computer program instructions stored in the memory 20312. In this application, the memory 20312 is used to store corresponding computer program instructions and / or data. This can mean that the memory 20312 stores all corresponding computer program instructions and / or data for execution by the processor core 20311; or it can mean that the memory 20312 stores a portion of the corresponding computer program instructions and / or data, including the computer program instructions and / or data currently required to be executed by the processor core 20311. The memory 20312 can store different portions of computer program instructions and / or data multiple times for execution by the processor core 20311 to implement the relevant operations in the above method embodiments. The interface circuit 20314 serves as a communication interface for communication with other components, such as transmitting signals with the radio frequency processing system 2020, communicating with other subsystems and related components of the processor system 2030 via a bus, such as transmitting data control signals with the application processor 2032, and transmitting data or computer program instructions with the memory 2036 or memory 2060. Optionally, in order to reduce the load on the processor core, a baseband signal processing circuit 20313 can be set to perform at least some baseband signal processing, including one or more of signal demodulation, modulation, encoding or decoding.

[0283] In one example, the communication device provided in this application may be a terminal 2000, a communication module including a processor system 2030 and a radio frequency system 2020, the processor system 2030, or a baseband processor 2031.

[0284] The processor, processor system, application processor, baseband processor, processor circuit or processor core mentioned above can be collectively referred to as a processor. The processor may include one or more of the following: CPU, DSP, MPU, MCU, GPU, FPGA, ASIC, artificial intelligence (AI) processor or neural network processing unit (NPU).

[0285] The aforementioned memory may include one or more of the following storage media: random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), phase-change memory (PCM), resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), cache, register, read-only memory (ROM), flash memory, erasable programmable read-only memory (EPROM), hard disk, etc. In one example, computer program instructions for executing the above embodiments may be stored on non-volatile memory, such as at least a portion of the aforementioned memory 2060 (e.g., one or more of ROM, flash memory, EPROM, or hard disk). When the terminal is running, the corresponding computer program instructions may be partially or wholly loaded onto a memory with a faster transfer speed than the processor, such as at least a portion of memory 2036 and / or memory 20312 (e.g., one or more of RAM, SRAM, DRAM, PCM, RERAM, MRAM, FRAM, cache, or register), for the processor to execute in order to implement the steps in the above method embodiments.

[0286] In one example, the RF transceiver 2022 and the RF front-end 2021 can also be packaged in a single chip. In another example, the RF transceiver 2022, the RF front-end 2021, and the baseband processor 2031 can also be packaged in a single chip.

[0287] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by a communication device (e.g., a terminal-side device and / or a network-side device) in the above-described method embodiments.

[0288] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods described above as being performed by a communication device (e.g., a terminal-side device and / or a network-side device).

[0289] This application also provides a communication system, which includes the terminal-side device and / or network-side device described in the above embodiments.

[0290] Optionally, the communication system may also include the terminal-side device and / or network-side device described in the above embodiments.

[0291] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0292] In the various embodiments of this application, the order of the above-mentioned processes 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.

[0293] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0294] In this application, examples may reference each other without logical contradiction. For example, methods and / or terms between method embodiments may reference each other, functions and / or terms between device embodiments may reference each other, and functions and / or terms between device examples and method examples may reference each other.

[0295] It should be understood that the above embodiments are mainly illustrated using devices in existing network architectures as examples, and the specific form of the devices is not limited in the embodiments of this application. For example, any device that can achieve the same function in the future is applicable to the embodiments of this application.

[0296] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0297] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

[0298] 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.

[0299] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this implementation scheme according to actual needs.

[0300] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0301] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to existing solutions, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, external hard drives, ROM, RAM, magnetic disks, or optical disks.

[0302] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method is applied to a terminal device or a chip in a terminal device, including: Determine whether to store the terminal device's status information; If the status information is found to be stored, the status information is sent to the network device for accessing the non-terrestrial network.

2. The method according to claim 1, characterized in that, The method further includes: If it is determined that the status information is not stored, a first registration request message is sent to the network device, the first registration request message being used to request access to the non-terrestrial network.

3. The method according to claim 1 or 2, characterized in that, Before sending the status information to the network device, the method further includes: The network device receives first information indicating that it supports access based on the status information.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: The status indication information is sent to the network device, indicating that the terminal device has stored the status information.

5. The method according to claim 4, characterized in that, The status indication information includes a first preamble, which is used for access when the terminal device stores the status information.

6. The method according to claim 5, characterized in that, The multiple preamble groups include a first preamble group and a second preamble group. The first preamble group is used for access when the terminal device stores the status information, and the second preamble group is used for access when the terminal device does not store the status information. The first preamble belongs to the first preamble group.

7. The method according to claim 4, characterized in that, The status indication information is carried in the Media Access Control Unit (MAC CE) signaling or the Radio Resource Control (RRC) signaling.

8. The method according to any one of claims 4 to 7, characterized in that, The method further includes: The capability information is sent to the network device, the capability information indicating that the terminal device stores the status information, and the capability information includes the status indication information.

9. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Receive second information from the network device, the second information indicating that the status information verification failed; A second registration request message is sent to the network device, the second registration request message being used to request access to the non-terrestrial network.

10. The method according to any one of claims 1 to 8, characterized in that, The method further includes: Receive third information from the network device, the third information indicating that the status information verification has passed; Access to the non-terrestrial network is based on the aforementioned status information.

11. The method according to any one of claims 1 to 10, characterized in that, The status information is verified through at least one of the following protocol layers: Packet Data Convergence Protocol (PDCP) layer, Non-Access NAS layer, Service Data Adaptation Protocol (SDAP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, Radio Resource Control (RRC) layer, or Physical PHY layer.

12. The method according to any one of claims 1 to 11, characterized in that, The status information is associated with the first effective area, and the method further includes: If the terminal device is not located in the first effective area, update the status information.

13. The method according to claim 12, characterized in that, Before updating the status information, the method further includes: If the distance between the location of the terminal device and the reference location is greater than or equal to a first threshold, it is determined that the terminal device is not located in the first effective area; and / or, If the geographic grid number, geographic region number, wave position number, and beam number corresponding to the location of the terminal device are not in the pre-configured number list, it is determined that the terminal device is not located in the first effective area.

14. The method according to any one of claims 1 to 13, characterized in that, The status information includes at least one of the following: first security information, identification information associated with the terminal device, location information associated with the terminal device, Quality of Service (QoS) information, billing information, or capability information of the terminal device.

15. A communication method, characterized in that, The method is applied to a network device or a chip in a network device, including: Receive status information from the terminal device, the status information being used to access a non-terrestrial network; The process of accessing the non-terrestrial network is triggered based on the status information.

16. The method according to claim 15, characterized in that, Before receiving status information from the terminal device, the method further includes: Send first information to the terminal device, the first information indicating that the network device supports access based on the status information.

17. The method according to claim 15 or 16, characterized in that, The method further includes: The terminal device receives status indication information, which indicates that the terminal device stores the status information.

18. The method according to claim 17, characterized in that, The status indication information includes a first preamble, which is used for access when the terminal device stores status information.

19. The method according to claim 18, characterized in that, The multiple preamble groups include a first preamble group and a second preamble group. The first preamble group is used for access when the terminal device stores the status information, and the second preamble group is used for access when the terminal device does not store the status information. The first preamble belongs to the first preamble group.

20. The method according to claim 17, characterized in that, The status indication information is carried in the Media Access Control Unit (MAC CE) signaling or the Radio Resource Control (RRC) signaling.

21. The method according to any one of claims 17 to 20, characterized in that, The method further includes: The terminal device receives capability information, which indicates that the terminal device stores the status information, and the capability information includes the status indication information.

22. The method according to any one of claims 15 to 21, characterized in that, Based on the aforementioned status information, the process of accessing the non-terrestrial network is triggered, including: If the status information is verified successfully, the process of accessing the non-terrestrial network is triggered based on the status information.

23. The method according to claim 22, characterized in that, The status information from the terminal device includes first security information, and the method further includes: The fourth information is obtained from the core network element, and the status information of the terminal device carried in the fourth information includes the second security information; If the first security information and the second security information are the same, the status information verification is deemed successful.

24. The method according to any one of claims 15 to 23, characterized in that, The status information is verified through at least one of the following protocol layers: Packet Data Convergence Protocol (PDCP) layer, Non-Access NAS layer, Service Data Adaptation Protocol (SDAP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, Radio Resource Control (RRC) layer, or Physical PHY layer.

25. The method according to any one of claims 15 to 24, characterized in that, Based on the aforementioned status information, the process of accessing the non-terrestrial network is triggered, including: Send registration and activation information to the core network element, wherein the registration and activation information indicates the activation status information of the terminal device.

26. The method according to any one of claims 15 to 25, characterized in that, The method further includes: Send first configuration information, which includes the first effective time and / or the first effective area of ​​the status information.

27. The method according to any one of claims 15 to 26, characterized in that, The status information includes at least one of the following: first security information, identification information associated with the terminal device, location information associated with the terminal device, Quality of Service (QoS) information, billing information, or capability information of the terminal device.

28. A communication device, characterized in that, It includes at least one processor, said at least one processor being configured to execute a computer program or instructions to cause the method as described in any one of claims 1 to 14 to be performed, or to cause the method as described in any one of claims 15 to 27 to be performed.

29. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program or instructions that, when run on a computer, cause the method as described in any one of claims 1 to 27 to be performed.

30. A computer program product, characterized in that, Includes a computer program or instructions that, when executed by a processor, cause the method as described in any one of claims 1 to 27 to be performed.

Images