Communication method and apparatus

Abstract

The application relates to a communication method and device, belonging to the field of communication. The method is applied to an NTN scene. In the method, a node on an NTN device can sign path information and / or send data to a next-hop node at a position indicated by first position information. The above scheme can make data transmission have higher security through path signing and / or position limiting of a routing node. In addition, a terminal can trigger the node on the NTN device to perform path signing and / or position limiting of the routing node. Alternatively, the node on the NTN device can judge whether to perform path signing and / or whether to perform position limiting of the routing node based on first information. In addition, a first network element can be configured to configure the node on the NTN device with a complete routing path, so that the situation that data cannot be routed to a landing network element is avoided, and the packet loss rate of the data is reduced.

Description

Technical Field

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

[0002] In non-terrestrial network (NTN) scenarios, NTN equipment, such as satellites, is introduced into the communication system. NTN equipment can communicate with core network equipment through NTN gateways, and it can also communicate with terminal devices. Because the distance between NTN equipment and terminal devices is much greater, the signal coverage of network equipment deployed on NTN equipment is also much larger than that of current terrestrial networks. Taking uplink transmission as an example, data sent by a terminal device can pass through one or more NTN devices and ground-based gateways before reaching the serving network.

[0003] However, improving the security of data transmission in NTN scenarios is an urgent problem to be solved. Summary of the Invention

[0004] This application provides a communication method and apparatus that can improve the security of data transmission.

[0005] Firstly, a communication method is provided. The method provided in the first aspect can be executed by a first node deployed on a first NTN device. Unless otherwise specified, the first node in this application can be a communication device (e.g., an access network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the following description uses the first node as the executing entity.

[0006] For example, the method includes: receiving data from a previous hop node; signing first path information based on the key of the first node to obtain first signature information, wherein the first path information includes: information of the previous hop node, information of the first node, and information of a second node; and sending the data, the first path information, and the first signature information to the second node.

[0007] Based on the above scheme, the first node deployed on the NTN device can sign the path information, thereby improving the security of data transmission in NTN scenarios. For example, the path information and signature information sent by the first node eventually reach the network element used for verification (hereinafter referred to as the verification network element). This network element can verify the validity of the signature information based on the path information. In this way, if the verification network element can detect that the signature information is abnormal through the above verification process, it can be determined that the routing path of the data from the terminal to the landing network element has been tampered with, introducing an untrusted node. Therefore, the above scheme can protect the security of data transmission between the terminal and the landing network element.

[0008] In some implementations, the first path information also includes: the time information of when the first node processes the data.

[0009] Based on the above scheme, the first node can provide time information for data processing. In this way, the network element used for verification (hereinafter referred to as the verification network element) can verify whether the first node is located in a position that meets the secure routing requirements when processing data, based on the time information. If the first node does not meet the secure routing requirements, the verification network element can detect this problem, thereby improving the security of data transmission.

[0010] In some implementations, before signing the first path information based on the key of the first node to obtain the first signature information, the method further includes: determining to securely sign the first path information based on the first information, wherein the first information is at least one of first location information, first address information, or information of the terminal sending the data, wherein the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, the landing network element being a network element deployed on the ground for receiving the data, and the first address information is used to indicate the address of the terminal.

[0011] Based on the above scheme, the first node can determine whether to perform a secure signature on the path information based on the first information. Based on this determination, the first node can either choose to perform a secure signature to improve security, or choose not to perform a secure signature to save processing overhead and reduce data transmission latency.

[0012] In some implementations, the first node is configured with a mapping relationship between the first information and the first security policy; wherein, determining to perform a secure signature on the first path information based on the first information includes: determining the first security policy based on the mapping relationship and the first information, wherein the first security policy is used to instruct the first path information to be securely signed.

[0013] Based on the above scheme, the first node can determine which security policy to use based on the mapping relationship, thereby determining whether to perform a secure signature on the path information. This scheme is easy to implement and has low processing overhead.

[0014] In some implementations, before signing the first path information based on the key of the first node to obtain the first signature information, the method further includes: determining, based on the first information, to securely sign the first path information, and determining that the node processing the data is located at the location indicated by the first location information, wherein the first information is at least one of first location information, first address information, or information of the terminal sending the data, wherein the first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the landing network element, the landing network element being a terrestrial network element used to receive the data, and the first address information is used to indicate the address of the terminal.

[0015] Based on the above scheme, the first node can determine whether to perform a secure signature on the path information and whether to select a node at the location indicated by the first location information to process the data, based on the first information. Based on these determinations, the first node can either perform a secure signature and send data to a node at a specific location, thereby improving security; or it can decide not to perform a secure signature and have no special requirements for the location of the next-hop node, thereby reducing processing complexity.

[0016] In some implementations, the first node is configured with a mapping relationship between the first information and the second security policy; wherein, based on the first information, determining to perform a secure signature on the first path information and determining that the node processing the data is at the position indicated by the first location information includes: determining the second security policy based on the mapping relationship and the first information, wherein the second security policy is used to indicate to perform a secure signature on the first path information and to indicate that the node processing the data is at the position indicated by the first location information.

[0017] Based on the above scheme, the first node can determine which security policy to use based on the mapping relationship, thereby determining whether to securely sign the path information and whether there are special requirements for the location of the next-hop node. This scheme is easy to implement and has low processing overhead.

[0018] In some implementations, before signing the first path information based on the key of the first node to obtain the first signature information, the method further includes: receiving first indication information from the previous hop node, the first indication information being used to indicate that the first path information is securely signed.

[0019] Based on the above scheme, the first instruction information can trigger the first node to perform a secure signature on the path information, thereby enabling the first node to perform secure signatures on demand, effectively balancing security and processing overhead (or transmission latency).

[0020] In some implementations, the first indication information is also used to indicate that the node processing the data is at the location indicated by the first location information, wherein the first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the landing network element, the landing network element being a network element deployed on the ground for receiving the data, and the first address information is used to indicate the address of the terminal.

[0021] Based on the above scheme, the first instruction information can trigger the first node to select the node at the position indicated by the first position information to process the data, thereby enabling the first node to restrict the position of the node processing the data as needed, effectively balancing security and processing complexity.

[0022] In some implementations, the first node is configured with a third security policy, which is used to indicate that the node processing the data is at the location indicated by the first location information. The method further includes: determining the second node based on the third security policy, wherein the second node is at the location indicated by the first location information.

[0023] Based on the above scheme, the first node can determine whether to select a node at the location indicated by the first location information to process data based on the third security policy. This allows the first node to send data to nodes at specific locations, thereby improving security. If the first node uses other policies (e.g., the first security policy), it does not need to have special requirements regarding the location of the next-hop node, thus reducing processing complexity.

[0024] In some implementations, determining the second node based on the third security policy includes: determining the first routing path based on the third security policy, wherein the second node is the next-hop node of the first node on the first routing path, and the nodes on the first routing path are located at the positions indicated by the first location information.

[0025] In some implementations, determining the second node based on the third security policy includes: determining the second node at the location indicated by the first location information based on the third security policy and ephemeris information.

[0026] In some implementations, before sending the data, the first path information, and the first signature information to the second node, the method further includes: receiving first configuration information from a first network element, the first configuration information being used to configure a first routing path; determining the first routing path based on information of the landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data, the first routing path is a routing path with the destination network element being the landing network element, and wherein, on the first routing path, the second node is the next-hop node of the first node.

[0027] Based on the above scheme, the first node can be configured with a routing path, enabling it to send data to the next-hop node in the routing path. Compared to flooding (i.e., sending data to all next-hop nodes), the above implementation eliminates the need for the first node to send data to all next-hop nodes, thus saving overhead. Furthermore, in NTN scenarios, some NTN devices may not be able to communicate with each other. Therefore, the next-hop node temporarily determined by the first node may not be able to route data to the final network element through other NTN devices. The above implementation, by pre-planning a complete routing path, can avoid situations where data cannot be routed to the final network element, thereby reducing data packet loss.

[0028] In some implementations, the method further includes: sending second information to the first network element, the second information being used to instruct the sending of information about the first routing path to the verification network element; and / or sending the information about the first routing path to the second node.

[0029] Based on the above scheme, the first node can instruct the first network element to send the first routing path information to the verification network element; or it can pass the first routing path information to the next-hop node, eventually reaching the verification network element. In this way, the verification network element can obtain the complete routing path information determined by the first network element (i.e., the information of the first routing path), thereby enhancing the security strength of the verification path information. For example, if the verification network element concatenates multiple path information received on the routing path into complete routing path information, and multiple consecutive nodes (e.g., four consecutive nodes) jointly tamper with the path information, the verification network element may not be able to detect the tampering of the routing path. However, based on the above scheme, the verification network element can use the complete routing path information determined by the first network element to compare with the concatenated actual routing path information, thereby discovering whether the actually transmitted routing path has been tampered with.

[0030] In some implementations, the method further includes sending a second instruction message to the second node, the second instruction message being used to instruct the second node to perform a secure signature.

[0031] Secondly, a communication method is provided. The method provided in this application can be executed by a terminal. Unless otherwise specified, the terminal in this application can be a communication device (e.g., a terminal device), a component within a communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the following description uses a terminal as the executing entity.

[0032] For example, the method includes: sending third information to a first node deployed on a first NTN device, the third information being used to trigger the first node to perform a secure signature on first path information, wherein the first path information includes: information of the terminal, information of the first node, and information of the next-hop node of the first node; and sending data to the first node.

[0033] This application does not limit the execution order of the operations of sending third information and sending data. For example, the terminal may send the third information first and then send the data; or it may send the data first and then send the third information; or it may send the third information and the data simultaneously.

[0034] Based on the above scheme, the third information can trigger the first node to perform a secure signature on the path information, thereby enabling the first node to perform secure signatures on demand, effectively balancing security and processing overhead (or transmission latency).

[0035] In some implementations, the third information is also used to trigger the first node to send the data to the node at the location indicated by the first location information.

[0036] Based on the above scheme, the third information can trigger the first node to select the node at the position indicated by the first position information to process the data, thereby enabling the first node to restrict the position of the node processing the data as needed, effectively balancing security and processing complexity.

[0037] In some implementations, the third information is at least one of the following: indication information of the first location information; first address information; information of the terminal; or, first indication information used to indicate secure signing of the first path information, and / or, the first indication information used to indicate that the node processing the data is at the location indicated by the first location information.

[0038] The first address information is used to indicate the address of the terminal, and the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element. The landing network element is a network element deployed on the ground that is used to receive the data.

[0039] In some implementations, before sending the third information to the first node deployed on the first NTN device, the method further includes: receiving third indication information from a second network element, the third indication information being used to indicate secure signing of the first path information, and / or, the third indication information being used to indicate that the node processing the data is at the location indicated by the first location information.

[0040] For example, the terminal can obtain the aforementioned third indication information during the protocol data unit (PDU) session establishment process. For instance, the third indication information can be carried in the PDU session establishment acceptance message.

[0041] In some implementations, the method further includes: signing the information of the terminal and the information of the first node based on the key of the terminal to obtain second signature information; and sending the second signature information to the first node.

[0042] Thirdly, a communication method is provided. The execution subject of the method provided in this application can be a verification network element. Unless otherwise specified, the verification network element in this application can be a communication device (e.g., a core network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the following description uses the verification network element as the execution subject.

[0043] For example, the method includes: obtaining first signature information and first path information, wherein the first path information includes information of the previous hop node of the first node, information of the first node, and information of the next hop node of the first node, wherein the first node is deployed on a first NTN device; determining the public key of the first node based on the information of the first node; and verifying the validity of the first signature information based on the public key of the first node and the first path information.

[0044] In some examples, the verification network element can be implicitly instructed to verify the first signature information. For instance, the first signature information can implicitly instruct the verification network element to verify the first signature information. Based on the first signature information, the verification network element can determine the information of the first node from the first path information, thereby obtaining the public key of the first node to verify the first signature information.

[0045] In other examples, the verification network element can be explicitly instructed to verify the first signature information. In some possible implementations, the verification network element is a local network element, and the method further includes: the verification network element receiving indication information #1 from the second node. This indication information #1 can be used to instruct the verification network element to verify the first signature information.

[0046] In some possible implementations, the verification network element is a different network element from the landing network element, and the method further includes: the landing network element sending indication information #1 to the verification network element. This indication information #1 can be used to instruct the verification network element to verify the first signature information.

[0047] In other words, the aforementioned instruction information #1 can explicitly instruct the verification network element to verify the first signature information. In other words, instruction information #1 can be information that has the function of "instructing the verification network element to verify the first signature information." This application does not limit the specific form of instruction information #1. For example, instruction information #1 can be the first instruction information or the second instruction information in this application.

[0048] Based on the above scheme, the verification network element can verify the path information of the first node deployed on the NTN device, thereby preventing the routing path from being tampered with, and thus improving the security of data transmission in the NTN scenario.

[0049] In some implementations, the method further includes: receiving information about a first routing path from a first network element, wherein the first routing path is determined by the first network element, and the information about the first routing path includes information about each node used for data transmission; and verifying the validity of the first routing path information based on the information about the first routing path.

[0050] Based on the above scheme, the verification network element can obtain the complete routing path information determined by the first network element (i.e., the information of the first routing path), thereby enhancing the security strength of the verification path information. Specific examples are given in the relevant description in the first aspect and will not be repeated here.

[0051] In some implementations, the method further includes: determining information of a second routing path based on the path information of each node transmitting the data, the information of the second routing path including the information of each node transmitting the data, and the information of the second routing path including the first path information; wherein, based on the information of the first routing path, verifying the validity of the first path information includes: verifying the consistency between the second routing path and the first routing path.

[0052] In some implementations, the first path information further includes: time information of the first node processing the data; wherein, the method further includes: based on the time information, verifying whether the first node is located at the location indicated by the first location information when processing the data, wherein the first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the receiving network element.

[0053] Based on the above scheme, the verification network element can verify the location of the first node when it processes data based on time information. In this way, if the first node does not meet the location restriction requirements (i.e., it is not in a location that meets the security routing requirements), it can detect the above situation and take corresponding actions.

[0054] In some implementations, based on the time information, verifying whether the first node is located at the position indicated by the first location information when processing the data includes: obtaining second location information based on the time information, wherein the second location information is used to indicate the position of the first node at the time indicated by the time information; and determining whether the first node is located at the position indicated by the first location information when processing the data based on the second location information and the first location information.

[0055] In some implementations, obtaining the second location information based on the time information includes: sending a request message to a second network element, the request message requesting the location of the first node at the time indicated by the time information, the request message including the time information; and receiving a response message from the second network element, the response message including the second location information.

[0056] In some implementations, the request message also includes the identifier of the first node. Before sending the request message to the second network element, the method further includes: receiving second configuration information, which is used to configure the mapping relationship between the address information of the first node and the identifier of the first node; determining the identifier of the first node based on the mapping relationship and the address information of the first node, and the identifier of the first node is carried in the request message.

[0057] In some implementations, the method further includes receiving second configuration information, which is used to configure the public key of the first node.

[0058] Fourthly, a communication method is provided. The execution entity of the method provided in this application can be a third network element. Unless otherwise specified, the third network element in this application can be a communication device (e.g., core network equipment), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. As an example, the third network element can be a session management function (SMF) or other network element. For ease of description, the following description uses the example of an execution entity being a third network element.

[0059] For example, the method includes: determining third indication information, wherein the third indication information is used to indicate secure signing of the path information of the data, and / or, the third indication information is used to indicate that the routing node processing the data is located at the location indicated by first location information, wherein the path information of the data includes information of the routing node processing the data, information of the previous hop node of the routing node, and information of the next hop node of the routing node, the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data; and sending the third indication information to the terminal.

[0060] Based on the third instruction information in the above scheme, the terminal can be informed of the data security requirements. For example, the security requirement could be that the data path information needs to be securely signed. Another example is that the security requirement could be that the data path information needs to be securely signed, and that the data routing path needs to be location-restricted. In this way, the terminal can indicate the above security requirements to the first node, enabling the first node to protect the security of data transmission.

[0061] In some implementations, determining the third indication information includes any of the following: determining the third indication information based on the terminal's subscription data; determining the third indication information based on the service type of the data; determining the third indication information based on the location of the terminal, the location indicated by the terminal, or the location of the landing network element; or, in the case where the NTN device network has an inter-satellite link, determining the third indication information, wherein the NTN device network is used to transmit the terminal's data.

[0062] Based on the terminal's subscription data, the third instruction information can be determined, enabling terminal-level policy configuration to meet the security needs of different terminals.

[0063] Based on the business type of this data, the third indication information can be determined, enabling business-level policy configuration to meet the security requirements of different business types. For example, for businesses with high security requirements, location restrictions can be imposed on the nodes processing that business data. As examples, businesses with high security requirements could include factory operations or power grid operations, and so on.

[0064] The third indication information can be determined based on the location of the terminal, the location indicated by the terminal, or the location of the landing network element. This enables location-based configuration policies, meets data supervision requirements, and avoids redundant configuration.

[0065] When an NTN equipment network has inter-satellite links, third indication information is determined. Compared to schemes that restrict the location of any NTN equipment network, this scheme can make full use of the communication resources of NTN equipment.

[0066] Fifthly, a communication method is provided. The execution entity of the method provided in the fifth aspect can be a first network element. Unless otherwise specified, the first network element in this application can be a communication device (e.g., core network equipment or third-party equipment), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. As an example, the first network element can be called a path node controller or other names. For ease of description, the following description uses the example of the first network element as the execution entity.

[0067] For example, the method includes: determining a first routing path based on information of a landing network element, wherein the landing network element is the last hop node on the first routing path; and sending first configuration information to a first node on the first routing path, wherein the first configuration information is used to configure the first routing path or to configure the next hop node of the first node on the first routing path.

[0068] Based on the above scheme, the first network element can plan a complete routing path and configure a complete routing path for the first node, or the next-hop node of the first node on the planned routing path. In an NTN scenario, some NTN devices may not be able to communicate with each other. Therefore, without the above scheme, the first node may need to temporarily determine the next-hop node after receiving data. However, the temporarily determined next-hop node may not be able to route the data to the landing network element through other NTN devices. The above scheme, by planning a complete routing path in advance, can avoid the situation where data cannot be routed to the landing network element, thereby reducing the data packet loss rate.

[0069] In some implementations, determining the first planned route path includes: determining the first route path based on first location information, wherein the nodes on the first route path are located at the positions indicated by the first location information when processing data.

[0070] Based on the above scheme, the first routing path planned by the first network element can meet special location restrictions, that is, nodes on the first routing path can be located at the position indicated by the first location information when processing data. This location restriction provides higher security for data transmission on the first routing path.

[0071] In some implementations, the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, wherein the terminal is used to send the data transmitted on the first routing path.

[0072] In some implementations, before determining the first routing path, the method further includes: receiving first request information from the first node, the first request information being used to request the first network element to determine the routing path or to request the first network element to determine the next hop node of the first node on the routing path.

[0073] In some implementations, the first request information includes at least one of the following: information of the landing network element; first location information; or, fourth indication information, which is used to indicate that the node processing the data is at the location indicated by the first location information.

[0074] In some implementations, the method further includes: receiving second information from the first node; and in response to the second information, sending information about the first routing path to the verification network element.

[0075] Sixthly, a communication method is provided. The method provided in the sixth aspect can be executed by a first node deployed on a first NTN device. Unless otherwise specified, the first node in this application can be a communication device (e.g., an access network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the following description uses the first node as the executing entity.

[0076] For example, the method includes: receiving first configuration information from a first network element; and determining a first routing path or the next-hop node of the first node based on the first configuration information.

[0077] In some implementations, nodes on the first routing path are located at the position indicated by the first location information when processing data.

[0078] In some implementations, the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, wherein the terminal is used to send the data transmitted on the first routing path.

[0079] In some implementations, before receiving the first configuration information from the first network element, the method further includes: sending a first request message to the first network element, the first request message being used to request the first network element to determine a routing path or to request the first network element to determine the next-hop node of the first node.

[0080] In some implementations, the first request information includes at least one of the following: information about the landing network element, which is the last hop node on the first routing path; first location information; or, fourth indication information, which is used to indicate that the NTN device where the node processing the data is located is at the location indicated by the first location information.

[0081] In some implementations, the method further includes sending second information to the first network element, the second information being used to request the first network element to indicate the first routing path to the verification network element.

[0082] The beneficial effects of the sixth aspect and any implementation thereof are correspondingly described in the fifth aspect and certain implementations thereof.

[0083] In a seventh aspect, a communication method is provided. The method provided in the seventh aspect can be executed by a first node deployed on a first NTN device. Unless otherwise specified, the first node in this application can be a communication device (e.g., an access network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the following description uses the example of the first node as the executing entity.

[0084] The method includes: receiving data from a previous hop node; and sending the data to a second node, wherein the second node is located at a position indicated by first location information, the first location information being used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of a landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data.

[0085] Based on the above scheme, the first node can send data to the node located at the position indicated by the first location information. In other words, the next-hop node of the first node can satisfy a special location restriction: the next-hop node can be located at the position indicated by the first location information when processing data. This location restriction enhances the security of data transmission.

[0086] In some implementations, the method further includes: determining a second node at a location indicated by first location information based on first information, wherein at least one of the first location information, first address information, or information of the terminal is included, wherein the first address information is used to indicate the address of the terminal.

[0087] In some implementations, the first node is configured with a mapping relationship between first information and a third security policy; wherein, determining the second node at the location indicated by the first location information based on the first information includes: determining the third security policy based on the mapping relationship and the first information, wherein the third security policy is used to indicate that the node processing data is at the location indicated by the first location information.

[0088] In some implementations, before sending the data to the second node, the method further includes: receiving first indication information from the previous hop node, the first indication information being used to indicate that the node processing the data is at the position indicated by first location information.

[0089] Other implementations and beneficial effects of the seventh aspect can be found in the first aspect, the seventh aspect, or the specific implementation.

[0090] Eighthly, a communication device is provided, including processing circuitry (or a processor) and an input / output interface (also referred to as an interface circuit), the input / output interface being used for inputting and / or outputting signals, and the processing circuitry being used to execute any one of the first to seventh aspects, or any possible implementation of any one of the first to seventh aspects.

[0091] In some implementations, the processing circuitry is used to communicate with other devices via an interface circuitry and to execute any of the first to seventh aspects, or any possible implementation of any of the first to seventh aspects.

[0092] Ninthly, a communication device is provided. This communication device may include units, modules, or means for performing the functions of the communication device.

[0093] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the first aspect and any possible implementation of the first aspect. These modules, units, or means may be hardware circuits, software, or a combination of hardware circuits and software.

[0094] For example, the device includes a transceiver unit and a processing unit. The transceiver unit is used to receive data from the previous hop node; the processing unit is used to sign the first path information based on the key of the first node to obtain first signature information, wherein the first path information includes: information of the previous hop node, information of the first node, and information of the second node; the transceiver unit is also used to send the data, the first path information, and the first signature information to the second node.

[0095] In some implementations, the processing unit is further configured to: determine to securely sign the first path information based on the first information, wherein the first information is at least one of first location information, first address information, or information of the terminal sending the data, wherein the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, the landing network element being a network element deployed on the ground for receiving the data, and the first address information is used to indicate the address of the terminal.

[0096] In some implementations, the first node is configured with a mapping relationship between the first information and the first security policy; wherein, the processing unit is specifically used to: determine the first security policy based on the mapping relationship and the first information, the first security policy being used to instruct the first path information to be securely signed.

[0097] In some implementations, the processing unit is further configured to: based on the first information, determine to securely sign the first path information, and determine that the node processing the data is located at the position indicated by the first location information, wherein the first information is at least one of the first location information, the first address information, or the information of the terminal sending the data, wherein the first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the landing network element, the landing network element being a terrestrial network element used to receive the data, and the first address information is used to indicate the address of the terminal.

[0098] In some implementations, the first node is configured with a mapping relationship between the first information and the second security policy; wherein, the processing unit is specifically used to: determine the second security policy based on the mapping relationship and the first information, the second security policy being used to instruct the first path information to be securely signed, and to instruct the node processing the data to be located at the position indicated by the first location information.

[0099] In some implementations, the transceiver unit is also used to: receive first indication information from the previous hop node, the first indication information being used to instruct the first path information to be securely signed.

[0100] In some implementations, the first node is configured with a third security policy, which is used to indicate that the node processing the data is at the location indicated by the first location information. The processing unit is further configured to: determine the second node based on the third security policy, wherein the second node is at the location indicated by the first location information.

[0101] In some implementations, the processing unit is specifically used to: determine the first routing path based on the third security policy, wherein on the first routing path, the second node is the next-hop node of the first node, and the nodes on the first routing path are located at the positions indicated by the first location information.

[0102] In some implementations, the processing unit is specifically used to: determine the second node at the location indicated by the first location information based on the third security policy and ephemeris information.

[0103] In some implementations, the transceiver unit is further configured to receive first configuration information from the first network element, which is used to configure the first routing path; the processing unit is further configured to determine the first routing path based on the information of the landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data, and the first routing path is a routing path with the destination network element as the landing network element, wherein on the first routing path, the second node is the next-hop node of the first node.

[0104] In some implementations, the transceiver unit is further configured to: send second information to the first network element, the second information being used to instruct the sending of information about the first routing path to the verification network element; and / or, the transceiver unit is further configured to: send information about the first routing path to the second node.

[0105] In some implementations, the transceiver unit is also used to: send a second indication message to the second node, the second indication message being used to instruct the second node to perform a secure signature.

[0106] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the second aspect and any possible implementation of the second aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0107] For example, the device includes a transceiver unit. The transceiver unit is configured to send third information to a first node deployed on a first NTN device, the third information being used to trigger the first node to perform a secure signature on first path information, wherein the first path information includes: information of the terminal, information of the first node, and information of the next-hop node of the first node; the transceiver unit is also configured to send data to the first node.

[0108] In some implementations, the transceiver unit is further configured to: receive third indication information from the second network element, the third indication information being used to indicate secure signing of the first path information, and / or, the third indication information being used to indicate that the node processing the data is at the position indicated by the first location information.

[0109] In some implementations, the device further includes a processing unit. This processing unit is used to: sign the information of the terminal and the information of the first node based on the terminal's key to obtain second signature information; wherein the transceiver unit is also used to send the second signature information to the first node.

[0110] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the third aspect and any possible implementation of the third aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0111] For example, the device includes a transceiver unit and a processing unit. The transceiver unit is used to acquire first signature information and first path information, wherein the first path information includes information of the previous hop node of the first node, information of the first node, and information of the next hop node of the first node, wherein the first node is deployed on a first NTN device; the processing unit is used to determine the public key of the first node based on the information of the first node; the processing unit is also used to verify the validity of the first signature information based on the public key of the first node and the first path information.

[0112] In some implementations, the transceiver unit is further configured to receive information about a first routing path from the first network element, wherein the first routing path is determined by the first network element, and the information about the first routing path includes information about each node used for transmitting data; the processing unit is further configured to verify the validity of the first routing path information based on the information about the first routing path.

[0113] In some implementations, the processing unit is further configured to: determine information of a second routing path based on the path information of each node transmitting the data, the information of the second routing path including the information of each node transmitting the data, and the information of the second routing path including the first path information; wherein, the processing unit is specifically configured to: verify the consistency between the second routing path and the first routing path.

[0114] In some implementations, the first path information further includes: time information of the first node processing the data; wherein, the processing unit is further configured to: based on the time information, verify whether the first node is located at the location indicated by the first location information when processing the data, wherein the first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the receiving network element.

[0115] In some implementations, the processing unit is specifically used to: obtain second location information based on the time information, wherein the second location information is used to indicate the location of the first node at the time indicated by the time information; and determine, based on the second location information and the first location information, whether the first node is located at the location indicated by the first location information when processing the data.

[0116] In some implementations, the transceiver unit is further configured to: send a request message to a second network element, the request message being used to request the location of the first node at the time indicated by the time information, the request message including the time information; and receive a response message from the second network element, the response message including the second location information.

[0117] In some implementations, the request message also includes the identifier of the first node. The transceiver unit is further configured to: receive second configuration information, which is used to configure the mapping relationship between the address information of the first node and the identifier of the first node; the processing unit is further configured to determine the identifier of the first node based on the mapping relationship and the address information of the first node, and the identifier of the first node is carried in the request message.

[0118] In some implementations, the transceiver unit is also used to: receive second configuration information, which is used to configure the public key of the first node.

[0119] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the fourth aspect and any possible implementation of the fourth aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0120] For example, the device includes a transceiver unit and a processing unit. The processing unit is used to determine third indication information, wherein the third indication information is used to instruct the secure signing of the path information of the data, and / or, the third indication information is used to instruct the routing node processing the data to be located at the location indicated by first location information, wherein the path information of the data includes information of the routing node processing the data, information of the previous hop node of the routing node, and information of the next hop node of the routing node, and the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data; the transceiver unit is used to send the third indication information to the terminal.

[0121] In some implementations, the processing unit is specifically used for any of the following: determining the third indication information based on the terminal's subscription data; determining the third indication information based on the service type of the data; determining the third indication information based on the location of the terminal, the location indicated by the terminal, or the location of the landing network element; or, in the case where the NTN device network has an inter-satellite link, determining the third indication information, wherein the NTN device network is used to transmit the terminal's data.

[0122] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the fifth aspect and any possible implementation of the fifth aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0123] For example, the device includes a transceiver unit and a processing unit. The processing unit is used to determine a first routing path based on information of a landing network element, wherein the landing network element is the last hop node on the first routing path; the transceiver unit is used to send first configuration information to a first node on the first routing path, wherein the first configuration information is used to configure the first routing path or to configure the next hop node of the first node on the first routing path.

[0124] In some implementations, the processing unit is specifically used to: determine the first routing path based on the first location information, wherein the nodes on the first routing path are located at the positions indicated by the first location information when processing data.

[0125] In some implementations, the transceiver unit is also used to: receive a first request message from the first node, the first request message being used to request the first network element to determine a routing path or to request the first network element to determine the next hop node of the first node on the routing path.

[0126] In some implementations, the transceiver unit is also used to: receive second information from the first node; and in response to the second information, send information about the first routing path to the verification network element.

[0127] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the sixth aspect and any possible implementation of the sixth aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0128] For example, the device includes a transceiver unit and a processing unit. The transceiver unit is used to receive first configuration information from a first network element; the processing unit is used to determine a first routing path or the next-hop node of the first node based on the first configuration information.

[0129] In some implementations, the transceiver unit is also used to: send a first request message to the first network element, the first request message being used to request the first network element to determine a routing path or to request the first network element to determine the next-hop node of the first node.

[0130] In some implementations, the transceiver unit is also used to: send second information to the first network element, the second information being used to request the first network element to indicate the first routing path to the verification network element.

[0131] In some implementations, the communication device may include modules, units, or means for performing the methods / operations / steps / actions described in the seventh aspect and any possible implementation of the seventh aspect, which may be hardware circuits, software, or a combination of hardware circuits and software.

[0132] For example, the device includes a transceiver unit. The transceiver unit is used to receive data from the previous hop node; the transceiver unit is also used to send the data to a second node, wherein the second node is located at a location indicated by first location information, the first location information being used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of a landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data.

[0133] In some implementations, the device further includes a processing unit. This processing unit is used to determine a second node located at a position indicated by first location information, based on first information, wherein the first location information, first address information, or information of the terminal are at least one of these, and the first address information is used to indicate the address of the terminal.

[0134] In some implementations, the first node is configured with a mapping relationship between first information and a third security policy; wherein, the processing unit is specifically used to: determine the third security policy based on the mapping relationship and the first information, wherein the third security policy is used to indicate that the node processing the data is at the position indicated by the first location information.

[0135] In some implementations, the transceiver unit is also used to: receive first indication information from the previous hop node, the first indication information being used to indicate that the node processing the data is at the position indicated by the first position information.

[0136] In a tenth aspect, a computer-readable storage medium is provided, on which a computer program or instructions are stored, which, when executed, cause any one of the first to seventh aspects, or any possible implementation of any one of the first to seventh aspects, to be executed (or implemented).

[0137] Eleventhly, a computer program product is provided, comprising a computer program or instructions that, when executed, cause any one of the first to seventh aspects, or any possible implementation of any one of the first to seventh aspects, to be executed (or implemented).

[0138] In a twelfth aspect, a communication device is provided, comprising a processor for executing (or implementing) any of the first to seventh aspects, or any possible implementation of any of the first to seventh aspects, by executing a computer program (or computer-executable instructions) stored in a memory, and / or by logic circuitry.

[0139] In one possible implementation, the device also includes a memory. In another possible implementation, the processor and memory are integrated together. In yet another possible implementation, the memory is located outside the device. The processor may include one or more processors.

[0140] In some possible implementations, the memory may be used to store part or all of the necessary computer program or instructions for implementing any of the first to seventh aspects, or for any possible implementation of any of the first to seventh aspects.

[0141] In one possible implementation, the communication device further includes a communication interface for communicating with other devices, such as transmitting or receiving data and / or signals. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, input / output interface, or other types of communication interface.

[0142] In one implementation, the communication device of the eighth, ninth or twelfth aspect mentioned above can be a terminal device or a communication module in a terminal device, or a chip or chip system in a terminal device.

[0143] In one implementation, the communication device of the eighth, ninth or twelfth aspect mentioned above can be an access network device or a communication module in the access network device, or a chip or chip system in the access network device.

[0144] In one implementation, the communication device of the eighth, ninth or twelfth aspect mentioned above may be a core network device or a communication module in the core network device, or a chip or chip system in the core network device.

[0145] In one implementation, the communication device of the eighth, ninth or twelfth aspect mentioned above can be a third-party device or a communication module in a third-party device, or a chip or chip system in a third-party device.

[0146] In a thirteenth aspect, a chip is provided, including a processor for invoking a computer program or computer instructions in a memory to cause the processor to execute or implement any of the first to seventh aspects, or any possible implementation of any of the first to seventh aspects.

[0147] In some implementations, the processor is coupled to the memory via an interface.

[0148] In a fourteenth aspect, a communication system is provided, comprising at least one of the following: a first node, a terminal, a verification network element, a third network element, or a first network element. The first node is configured to execute the first aspect and any possible implementation thereof, or to execute the sixth aspect and any possible implementation thereof, or to execute the seventh aspect and any possible implementation thereof. The terminal is configured to execute the second aspect and any possible implementation thereof. The verification network element is configured to execute the third aspect and any possible implementation thereof. The third network element is configured to execute the fourth aspect and any possible implementation thereof. The first network element is configured to execute the fifth aspect and any possible implementation thereof.

[0149] The description of the beneficial effects of any of the eighth to fourteenth aspects can be referred to the description of the corresponding beneficial effects of the first to seventh aspects. Attached Figure Description

[0150] Figure 1 It is a schematic block diagram of a communication system.

[0151] Figure 2 This is a schematic diagram of another communication system.

[0152] Figure 3 This is a schematic flowchart of a communication method provided in an embodiment of this application.

[0153] Figure 4 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application.

[0154] Figure 5 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0155] Figure 6 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0156] Figure 7 This is a schematic flowchart of a communication method provided in an embodiment of this application.

[0157] Figure 8 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application.

[0158] Figure 9 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0159] Figure 10 This is a schematic flowchart illustrating another communication method provided in the embodiments of this application.

[0160] Figure 11 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0161] Figure 12 This is a schematic diagram of another communication device provided in an embodiment of this application.

[0162] Figure 13 This is a schematic diagram of a chip system provided in an embodiment of this application.

[0163] Figure 14 This is a schematic diagram of another chip system provided in an embodiment of this application. Detailed Implementation

[0164] In this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0165] I. 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.

[0166] II. In this application, the terms "first," "second," and various numerical designations (e.g., #1, #2, etc.) indicate distinctions made for ease of description and are not intended to limit the scope of the embodiments of this application. For example, first information and second information can distinguish different messages, rather than being used to describe a specific order or sequence. It should be understood that such described objects can be interchanged where appropriate to describe solutions other than those in the embodiments of this application.

[0167] Third, in this application, descriptions such as "when," "under the circumstances," and "if" all refer to the device taking corresponding actions or being in a corresponding position under certain objective circumstances. They are not time-limited, nor do they require the device to perform a judgment action when implementing it, nor do they imply any other limitations.

[0168] IV. In this application, "instruction" or "for instruction" can include both direct (or explicit) and indirect (or implicit) instruction. When describing instruction information as indicating A, it can include whether the instruction information directly or indirectly indicates A, but does not necessarily mean that the instruction information carries A. For example, in the case of indirect (or implicit) instruction, the receiving end of the instruction information can obtain A based on the parameters indicated by the instruction information, combined with other rules or parameters, or through deduction.

[0169] V. 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.

[0170] VI. In this application, "protocol" can refer to standard protocols in the field of communications, such as 5G protocols, new radio (NR) protocols, and related protocols applied to future communication systems; this application does not limit this term. "Predefined" can include predefined terms, such as protocol definitions. "Preconfiguration" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device; this application does not limit the implementation method.

[0171] VII. In this application, "communication" can also be described as "data transmission," "information transmission," "data processing," etc. "Transmission" includes "sending" and "receiving." For example, transmission can be uplink transmission, such as a terminal device sending a signal to a network device; transmission can also be downlink transmission, such as a network device sending a signal to a terminal device; transmission can also be sidelink transmission, such as a terminal device sending a signal to another terminal device. For example, "transmission" can be air interface level transmission, or it can be signal transmission from a chip input (I) / output (O) port, rather than air interface level transmission.

[0172] 8. 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.

[0173] 9. "Sending information to XX (device)" can be understood as the destination of the information being that device. This can include sending information directly or indirectly to that device. "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 directly or indirectly from that device. 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 understood in a similar way, and will not be repeated here. Furthermore, "sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the 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 the device via a bus, wiring, or interface.

[0174] 10. In this application, terms such as "exemplarily" and "for example" are used to indicate examples, illustrations, or descriptions to present concepts in a specific manner. Any embodiment or design described as an "example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. In the embodiments of this application, the terms "of," "corresponding (relevant)," "corresponding," and "associated" may sometimes be used interchangeably, and it should be noted that their intended meanings are consistent unless their distinctions are emphasized.

[0175] XI. In this application, configuration can be signaling configuration or can be described as configuring signaling. For example, signaling configuration includes configuration using signaling sent by network devices, which can be radio resource control (RRC) messages, downlink control information (DCI) messages, or system information blocks (SIBs), etc. Another example is signaling configuration between network devices. These network devices can include access network devices, core network devices, or management plane devices, etc. Optionally, signaling configuration can also be configured to terminal devices or network devices by pre-configured signaling, or configured to terminal devices or network devices through pre-configuration. Here, pre-configuration means defining or configuring the values ​​of corresponding parameters in advance using a protocol, and storing them in the terminal device or network device during communication. The pre-configured messages can be modified or updated when the terminal device or network device is connected to the network.

[0176] 12. This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. Each system may include devices, components, modules, etc., other than those illustrated, and / or may not include all and all of the devices, components, modules, etc. discussed in conjunction with the accompanying drawings.

[0177] Thirteen, the business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0178] XIV. In the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. The terms "comprising," "including," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0179] The technical solutions of this application embodiment can be applied to various communication systems, including but not limited to: Long Term Evolution (LTE) systems, NR systems, and other fifth-generation (5G) communication systems. thThis includes various mobile communication systems such as 5G, narrowband Internet of Things (NB-IoT), enhanced machine-type communication (eMTC), enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), satellite communication systems, LTE-machine-to-machine (LTE-M) systems, and other systems that evolve after 5G, such as future mobile communication systems.

[0180] As an example, satellite communication systems may include high altitude platform station (HAPS) communication or NTN systems such as unmanned aerial vehicles (UAVs). Alternatively, satellite communication systems may include integrated communication and navigation (ICAN) systems, global navigation satellite systems (GNSS), or ultra-dense low-Earth orbit (LEO) satellite communication systems.

[0181] The embodiments of this application are described below with reference to the accompanying drawings.

[0182] Figure 1 It is a schematic block diagram of a communication system. For example... Figure 1 As shown, this communication system uses the 5G system (5GS) as an example. As an example, this communication system consists of three parts: the terminal part, the data network (DN) part, the radio access network (RAN) part, and the core network (CN) part.

[0183] The following is a brief introduction to the network elements of each part.

[0184] 1. Terminal section:

[0185] The terminal portion may include one or more terminals. In the embodiments of this application, a terminal may be a device for implementing the functions of a terminal device, or a device capable of supporting the terminal device in implementing those functions, such as a chip or chip system, which may be installed in the terminal device. The chip system may consist of chips, or may include chips and other discrete components.

[0186] Terminal equipment can be any device that provides voice and / or data connectivity to users. Terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as on ships); and it can be deployed in the air (e.g., on NTN equipment such as airplanes, balloons, satellites, or high-altitude platforms). Terminal equipment can also be referred to as user equipment (UE), access terminal, terminal, subscriber unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, wireless network equipment, user agent, or user device. In this application embodiment, terminal devices include, but are not limited to: cellular phones, mobile phones, wireless data cards, wireless modems, tablets, laptop computers, notebook computers, handheld computers, mobile internet devices (MIDs), computers with wireless transceiver capabilities, cordless phones, session initiation protocol (SIP) phones, smartphones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handsets or handheld devices with wireless communication capabilities, computing devices or other devices connected to wireless modems, vehicle-mounted devices (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains, etc.), wearable devices (e.g., smartwatches, smart bracelets, pedometers, smart glasses, etc.), satellite terminals, terminal devices in the Internet of Things or the Internet of Vehicles, as well as any form of terminal in future networks, relay user equipment, or terminals in future evolved public land mobile networks (PLMNs), etc.Terminal devices can also be virtual reality (VR) devices, augmented reality (AR) devices, point-of-sale (POS) machines, customer-premises equipment (CPE), light UE, reduced capability UE (REDCAP UE), machine-type communication (MTC) terminals, terminal devices in industrial control, terminal devices in self-driving, terminal devices in telemedicine, terminal devices in smart grids, wireless terminals in transportation safety, terminal devices in smart cities, terminal devices in smart homes, tactile terminal devices, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters, etc.), intelligent robots, robotic arms, workshop equipment, wireless terminals in self-driving, or flying devices (e.g., intelligent robots, hot air balloons, drones, airplanes), etc. The terminal device can also be a vehicle device, such as a complete vehicle device, an in-vehicle module, an in-vehicle chip, an on-board unit (OBU), or a telematics box (T-BOX). The terminal device can also be other devices with terminal functions; for example, it can be a device that functions as a terminal in device-to-device (D2D) communication. This application does not limit the scope of the embodiments in this regard.

[0187] 2. Data Network Section:

[0188] The data network portion may include a Data Network (DN). A DN can be a network used to provide data transmission. For example, a DN may include networks used by carrier services (such as the Internet Protocol (IP) Multimedia Subsystem (IMS)), the Internet, or third-party service networks. A DN can also be called a Packet Data Network (PDN), and is typically a network located outside the carrier's network, such as a third-party network.

[0189] 3. The (R)AN portion may include one or more access network elements. In the embodiments of this application, an access network element may be a device for implementing the functions of an access network device, or a device capable of supporting the access network device in implementing those functions, such as a chip or chip system, which may be installed in the access network device. A chip system may consist of chips or may include chips and other discrete components. In the NTN scenario, Figure 1 The RAN in this context can be deployed on NTN devices. As an example, NTN devices can include satellites or high-altitude platforms.

[0190] Access network equipment can be any device with wireless transceiver capabilities. For example, access network equipment can be a base station used to connect terminal devices to a radio access network (RAN). Access network equipment is sometimes also referred to as access network element, access network node, RAN node, RAN, access network (AN) node, or AN. It is understood that the names of devices with access network functionality may differ in systems employing different wireless access technologies. For ease of description, devices providing wireless communication access functionality to terminal devices can be collectively referred to as base stations or RANs. Exemplarily, access network equipment includes, but is not limited to, various forms of macro base stations, micro base stations or indoor stations, pico base stations, small stations, balloon stations, relay stations, access points, etc. Access network equipment can include evolved node Bs (eNBs or eNodeBs) in LTE, access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TRPs or TPs), or transmission reception points (TRPs) in Wi-Fi systems. It can also include next-generation NodeBs (gNBs), next-generation RAN (NG-RAN) nodes or transmission points (TRPs or TPs) in 5G systems, one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, and network nodes constituting a gNB or transmission point, such as baseband units (BBUs) or distributed units (DUs). Furthermore, it can include access network equipment, servers, or vehicle-mounted equipment in networks evolving after 5G. Access network equipment can also be modules or units that perform some of the functions of a base station; for example, it can be a central unit (CU) or a DU.

[0191] Access network devices and terminal devices can communicate via wireless links. The transmission link from the access network device to the terminal device can be called a downlink (DL) or downlink channel, used for transmitting downlink signals. The transmission link from the terminal device to the access network device can be called an uplink (UL) or uplink channel, used for transmitting uplink signals. The transmission link from one terminal device to another can be called a sidelink (SL) or sidelink channel, used for transmitting sidelink signals.

[0192] 4. CN section:

[0193] The CN portion may include, but is not limited to, the following network functions (NFs): network slice selection function (NSSF), network slice specific authentication and authorization function (NSSAAF), authentication server function (AUSF), unified data management (UDM), network exposure function (NEF), network repository function (NRF), policy control function (PCF), application function (AF), access and mobility management function (AMF), session management function (SMF), user plane function (UPF), and signaling control point (SCP). Figure 1 Partial NF is shown below. Figure 1 A brief introduction to the part of NF shown is provided.

[0194] 1) UPF network element:

[0195] A UPF network element can be used to implement at least one of the following: packet routing of user plane data, forwarding of user plane data, processing user plane paths for Protocol Data Unit (PDU) sessions, or processing quality of service (QoS) for user plane data. User data can access the DN through this network element. In the embodiments of this application, the UPF network element can be used to implement user plane functions.

[0196] 2) SMF network elements:

[0197] SMF network elements can be used to implement at least one of the following: session management, UE IP address allocation and management, selection, control or management of user plane functions (e.g., UPF network elements), configuration of flow control on the UPF to route traffic to the correct destination, policy control, QoS-related control, or downlink data notification, etc.

[0198] PCF network elements can be used to implement at least one of the following: a unified policy framework to guide network behavior, providing policy rule information to network elements (e.g., SMF network elements, RAN, etc.) or terminal devices.

[0199] Figure 1 Npcf, Nsmf, N3, N4, and N6 are interface serial numbers. For example, the meaning of these interface serial numbers can be found in the Third Generation Partner Program (3...). rd The meaning of the interface sequence number as defined in the Generation Partnership Project (3GPP) standard protocol is not limited in this application. It should be noted that... Figure 1 The interface names between the various network functions in this document are merely examples. In specific implementations, the interface names of this system architecture may be other names, and this application does not limit them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0200] exist Figure 1 In the architecture shown, the interface between (R)AN and CN can also be called the NG interface (not shown in the figure). (R)AN and CN are connected through the NG interface. The NG interface can include the NG-C interface and the NG-U interface. The NG-C interface is the control plane interface, connecting (R)AN and AMF network elements, and is used to transmit control plane data. The NG-U interface is the user plane interface, connecting (R)AN and UPF, and is used to transmit user plane data.

[0201] Figure 1The network elements shown, such as SMF, UPF, or PCF, can be understood as network elements in the core network used to implement different functions, such as network slices that can be combined as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the aforementioned network elements. Furthermore, the aforementioned network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualized functions instantiated on a shared platform (e.g., a cloud platform). Simply put, an NF can be implemented by hardware or software.

[0202] Furthermore, the aforementioned 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 communication networks, some or all of the aforementioned network elements may retain the terminology used in 5G, or they may adopt other names, etc.

[0203] The various methods provided in the embodiments of this application can be applied to... Figure 1 The communication system shown. For example, the RAN node in the embodiments of this application can be... Figure 1 The (R)AN shown. Figure 1 The (R)AN in the middle can be deployed on NTN devices. Figure 1 The UPF in the system can be deployed on the ground.

[0204] In NTN scenarios, NTN devices such as satellites are introduced into communication systems. Because the distance between NTN devices and terminal devices is very long, the coverage area of ​​the signals transmitted by network devices deployed on NTN devices is much larger than that of current terrestrial networks. In some examples, NTN devices can provide access services to multiple countries. The following example uses a satellite as the NTN device. Figure 2 Detailed introduction.

[0205] Figure 2 This is a schematic diagram of another communication system. STA#1 to STA#4 belong to a satellite access network, and the satellites in this network can communicate with each other via inter-satellite links (ISL). This satellite access network can provide access services to countries D, E, and F.

[0206] Satellites providing access services to multiple countries can communicate with the terrestrial core network via gateway stations. Optionally, the gateway stations connect to core network elements through a terrestrial routing network. For example, gateway stations i and j can communicate with... Figure 2The diagram illustrates satellite access network communication. Gateway station i can connect to a core network element (e.g., UPF) via routers i1 and i2. Gateway station j can connect to a core network element (e.g., UPF) via routers j1 and j2. Thus, terminals in countries D, E, and F can communicate with the core network element (e.g., UPF) sequentially via the satellite access network, gateway stations (including gateway station i or j), and the terrestrial routing network (including routers i1, i2, j1, or j2).

[0207] As an example, terrestrial core network elements can belong to the serving network. Thus, Figure 2 This can also be understood as terminals located in countries D, E, and F connecting to the service network via satellite access networks and gateways.

[0208] In some examples, the gateway station and service network may be deployed in the same country or in different countries. For example, the gateway station and service network may both be deployed in country D, country E, country F, or another country. Alternatively, the gateway station and service network may each be deployed in two of the following countries: country D, country E, country F, or another country.

[0209] In this application, the gateway station and the service network can be deployed one-to-one, meaning one gateway station connects to one service network. Alternatively, the gateway station and service network can be deployed in a many-to-one, one-to-many, or many-to-many manner; this application does not impose any limitations on this. As an example, one service network can correspond to one PLMN identifier (ID). Different service networks correspond to different PLMN IDs. The service network can be a visited network, a home network, or a combination of both. Taking a service network that is a combination of a visited network and a home network as an example, terminal data can first pass through the visited network and then through the home network.

[0210] Taking uplink transmission as an example, data sent by a terminal can successively pass through one or more satellites in the satellite access network and ground-based gateway stations to reach the service network. The one or more satellites and gateway stations traversed by the data can constitute a routing path (or part of a routing path). However, the routing path may be tampered with, resulting in poor data transmission security.

[0211] Therefore, improving the security of data transmission in NTN scenarios is an urgent problem to be solved.

[0212] In view of this, embodiments of this application provide a communication method. In this method, the first node signs the path information, thereby improving the security of data transmission. A detailed description is provided below with reference to the accompanying drawings.

[0213] Figure 3This is a schematic flowchart of a communication method 300 provided in an embodiment of this application. Optional operations in method 300 are shown with dashed lines. Some nodes that may be involved in this application are described below.

[0214] Terminal: Unless otherwise specified, the terminal in this application can be a communication device (e.g., a terminal device), a component within a communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the following description uses a UE as an example of a terminal.

[0215] First Node: The first node can receive data from its upstream node and send data to its next-hop node. As an example, the first node can be deployed on a first NTN device, and its upstream node can be deployed on another NTN device different from the first NTN device. Alternatively, the upstream node of the first node can be a UE (User Equipment). The next-hop node of the first node can be referred to as the second node.

[0216] In some examples, the first node can sign to obtain the first signature information and send the first signature information to the second node.

[0217] Unless otherwise specified, the first node in this application can be a communication device (e.g., an access network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the first node will be denoted as RAN#1 below.

[0218] Second Node: The second node can be the next-hop node of RAN#1. As an example, the second node can be deployed on a second NTN device. The second NTN device and the first NTN device can be different NTN devices.

[0219] In some examples, the second node can receive data and the first signature information from RAN#1 and send the data and the first signature information to its next-hop node. The next-hop node can be a node deployed on an NTN device (e.g., another NTN device different from the first and second NTN devices) or a terrestrial network element. As an example, the terrestrial network element can be a UPF or a gateway station. Exemplarily, a gateway station can be used to receive and transmit signals from the NTN device and establish a power supply link with the NTN device. A gateway station can also be called a gate station or other names, which are not limited in this application.

[0220] Unless otherwise specified, the second node in this application can be a communication device (e.g., an access network device), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the second node will be referred to as RAN#2 below.

[0221] Verification of network elements: Verification of network elements can obtain at least one signature information and verify the validity of at least one signature information. See the description in S376 below for details.

[0222] In some examples, the verification network element can be a terminating network element (e.g., a gateway station or a UPF). This verification network element (i.e., the terminating network element) can receive at least one signature from the next-hop node of the verification network element.

[0223] In other examples, the verification network element can be a different network element from the landing network element. This verification network element can receive at least one signature information from the landing network element.

[0224] Unless otherwise specified, the verification network element in this application may be a communication device (e.g., a core network device), a component in the communication device (e.g., a processor, chip, or chip system), or a logic module or software that can implement some or all of the functions of the communication device.

[0225] As an example, the verification network element can be a UPF, gateway station, SMF, other network elements involved in the current 3GPP protocol, or network elements added in future 3GPP protocols. The verification network element can also be called a security function network element or other names, which are not limited in this application.

[0226] It is understood that this application may also involve other nodes. These will be described in detail when introducing the various operations of this application later.

[0227] Before introducing the various operations of method 300, some descriptions in method 300 will be explained.

[0228] Method 300 describes the process by which data sent by the UE (denoted as data #1) is forwarded sequentially through at least one RAN node and finally reaches the destination network element (denoted as destination network element #1). For ease of description, the RAN nodes traversed by data #1 and the destination network element #1 can be referred to as the routing path. Thus, the RAN nodes traversed by data #1 and the destination network element #1 can be considered as nodes on the routing path. That is, the nodes on the routing path can include at least one RAN node and the destination network element #1. Optionally, the nodes on the routing path also include the UE.

[0229] The direction of this routing path is from the UE's next-hop node to the landing network element #1. In other words, the destination network element of this routing path is the landing network element #1.

[0230] For ease of description, if node #1 on the routing path sends data #1 directly or indirectly to node #2, it can be described as: node #1 is before node #2; correspondingly, node #2 is after node #1.

[0231] In this context, Node #1 sending data #1 "directly" to Node #2 can be understood as data #1 sent by Node #1 to Node #2 without passing through other nodes on the routing path, reaching Node #2 directly from Node #1. Thus, Node #1 can be called the "previous hop node" of Node #2; correspondingly, Node #2 can be called the "next hop node" of Node #1. Node #1 and Node #2 can be called "adjacent nodes"; or, in other words, Node #1 and Node #2 are "adjacent".

[0232] In this context, node #1 "indirectly" sends data #1 to node #2. This can be understood as data #1 sent by node #1 reaching node #2 through at least one intermediary node. Thus, the aforementioned at least one node can be referred to as a "node between node #1 and node #2"; or, in other words, "there is at least one node" between node #1 and node #2. Furthermore, nodes #1 and #2 can be referred to as "non-adjacent nodes." Or, in other words, node #1 and node #2 are "not adjacent."

[0233] The following describes the various operations of method 300.

[0234] S320, the UE transmits data (denoted as data #1). Correspondingly, RAN #1 receives data #1. RAN #1 can be deployed in the first NTN device.

[0235] Here, data #1 can be understood as data sent by the UE and received by RAN #1. Specifically, RAN #1 can receive data #1 from the upstream node of RAN #1.

[0236] In some examples, RAN#1 and UE can be adjacent nodes. In other words, the upstream node of RAN#1 can be the UE. Thus, S320 can be understood as the UE directly sending data #1 to RAN#1, and RAN#1 directly receiving data #1 from the UE.

[0237] In other examples, RAN#1 and the UE can be non-adjacent nodes. In other words, the upstream node of RAN#1 can be a different node from the UE. In this way, data #1 sent by the UE can be relayed through at least one node before finally reaching RAN#1.

[0238] For example, the UE can directly send data #1 to the upstream node of RAN#1; the upstream node of RAN#1 can receive data #1 and send data #1 back to RAN#1. RAN#1 can receive data #1 from the UE from the upstream node of RAN#1.

[0239] For example, a UE can send data #1 to a node (e.g., a RAN). This node can send data #1 directly to the upstream node of RAN #1, or indirectly to the upstream node of RAN #1 through at least one node. Furthermore, the upstream node of RAN #1 can receive data #1 and send data #1 back to RAN #1. RAN #1 can receive data #1 from the UE's upstream node.

[0240] S340, RAN#1 signs the first path information (denoted as path information #1) based on the key of RAN#1 to obtain the first signature information (denoted as signature information #1).

[0241] For example, the key for RAN#1 can be RAN#1's private key. As an example, this private key can be used to prove or determine the identity of RAN#1. For instance, RAN#1's private key can correspond to a public key stored in the verification network element. In this way, RAN#1 uses this private key to sign, obtaining signature information #1. Subsequent verification network elements can verify the signature information #1 based on the public key corresponding to this private key, thereby verifying the identity of RAN#1.

[0242] For example, the path information #1 may include: information of the previous hop node of RAN#1, information of RAN#1, and information of RAN#2. RAN#2 is the next hop node of RAN#1. Optionally, if the UE is the previous hop node of RAN#1, the path information #1 may include information of RAN#1 and information of RAN#2.

[0243] As an example, the information of a node (e.g., the previous hop node of RAN#1, RAN#1, RAN#2, etc.) may include at least one of the following: the node's identifier (ID) or the node's address information (e.g., IP address).

[0244] In some cases, the node can be deployed on an NTN device. Optionally, the node's information may also include at least one of the following: the ID of the NTN device on which the node resides, or the address information (e.g., IP address) of the NTN device on which the node resides.

[0245] For example, the UE information may include the UE ID and / or the UE IP address. As another example, the RAN#1 information may include at least one of the following: RAN#1ID, RAN#1 IP address, first NTN device ID, or first NTN device IP address.

[0246] For example, the UE IP address mentioned above can be an IP address assigned during the PDU session establishment process. The UE IP address mentioned above can also be understood as, or replaced by, a UE IP prefix.

[0247] For example, signature information #1 can be information obtained by RAN#1 signing path information #1 based on RAN#1's key. For instance, signature information #1 can be represented as sign(path information #1). As an example, verifying the signature of path information can guarantee the security of the transmission path.

[0248] Based on the above scheme, RAN#1 deployed on NTN equipment can sign the path information, thereby preventing the routing path from being tampered with, and thus improving the security of data transmission in NTN scenarios.

[0249] S350, RAN#1 sends data #1, path information #1 and signature information #1 to RAN#2.

[0250] Optionally, the path information #1 also includes: the time information of RAN#1 processing data #1 (denoted as, time information #1). RAN#1 “processing” data #1 may include operations such as RAN#1 receiving, buffering, or sending data #1.

[0251] Time information #1 can be used to indicate the time when RAN #1 processes data #1. As an example, time information #1 may include one or more moments, such as the moment when RAN #1 receives and / or transmits data #1; time information #1 may also include one or more time periods, such as the time period during which RAN #1 receives and transmits data #1; time information #1 may also include one or more durations, such as the length of time RAN #1 processes data #1. This application does not limit the specific form of the time information.

[0252] As a concrete example, suppose RAN#1 receives data #1 at 15:30 (i.e., executes S320) and sends data #1 to RAN#2 at 15:31 (i.e., executes S350). The time information #1 can indicate 15:30 and 1 minute, indicating that the time period for RAN#1 to process data #1 is from 15:30 to 15:31. The above example is for illustrative purposes only and is not intended to limit this application.

[0253] S360, RAN#2 sends data#1, path information#1, and signature information#1 to the landing network element#1. Correspondingly, the landing network element#1 receives data#1, path information#1, and signature information#1 from RAN#2.

[0254] In some examples, RAN#2 and the landing network element #1 can be adjacent nodes. In other words, RAN#2 can be the upstream node of the landing network element #1. Thus, S360 can include: RAN#2 directly sending data #1, path information #1, and signature information #1 to the landing network element #1; and the landing network element #1 directly receiving data #1, path information #1, and signature information #1 from RAN#2.

[0255] In other examples, RAN#2 and the destination network element #1 may be non-adjacent nodes. In other words, RAN#2 is not the previous hop node of destination network element #1. Or, there is at least one node between RAN#2 and destination network element #1. Thus, S360 may include: RAN#2 sending data #1, path information #1, and signature information #1 to destination network element #1 through at least one node; destination network element #1 receiving data #1, path information #1, and signature information #1 from RAN#2 through at least one node.

[0256] In some possible implementations, each RAN node on the routing path of data #1 signs the path information of that RAN node based on its key, thus obtaining the signature information of that RAN node.

[0257] For example, the key of a RAN node can be its private key. As an example, this private key can be used to prove or determine the identity of the RAN node. For instance, the RAN node's private key can correspond to a public key stored in the verification network element. In this way, the RAN node uses the private key to sign, thereby obtaining the RAN node's signature information. Subsequent verification network elements can verify the RAN node's signature information based on the public key corresponding to the private key, thus determining the identity of the RAN node.

[0258] For example, the path information of a RAN node may include: information of the RAN node's previous hop node, information of the RAN node itself, and information of the RAN node's next hop node.

[0259] As an example, a node's information may include at least one of the following: the node's ID, or the node's address information (e.g., IP address).

[0260] In some cases, the node can be deployed on an NTN device. Optionally, the node's information may also include at least one of the following: the ID of the NTN device on which the node resides, or the address information (e.g., IP address) of the NTN device on which the node resides.

[0261] For example, the UE IP address mentioned above may be an IP address assigned during the PDU session establishment process.

[0262] For example, suppose there are i RAN nodes on the routing path, where i is an integer greater than 1. RAN#i can be the previous hop node of the landing network element #1. RAN#1 can sign the path information #1 based on RAN#1's key to obtain signature information #1. RAN#2 can sign the path information #2 based on RAN#2's key to obtain signature information #2. Path information #2 can include information from RAN#1, RAN#2, and the next-hop node of RAN#2. Similarly, RAN#i can sign the path information #i based on RAN#i's key to obtain signature information #i. Path information #i can include information from RAN#i-1 (i.e., the previous hop node of RAN#i), RAN#i, and the landing network element #1.

[0263] Furthermore, in some possible implementations, each RAN node on the routing path of data #1 can send its path information and signature information to its next-hop node. Additionally, the RAN node can send the path information and signature information of all nodes preceding it to its next-hop node.

[0264] For example, RAN#2 can directly or indirectly send its path information and signature information, as well as the path information and signature information of all RAN nodes preceding RAN#2, to the landing network element #1. RAN#2 can receive the path information and signature information of all RAN nodes preceding RAN#2 from the node preceding RAN#2.

[0265] For example, assuming there are i RAN nodes on the routing path, RAN#1 can send data #1, path information #1, and signature information #1 to RAN#2. RAN#2 can send data #1, path information #1 to path information #2, and signature information #1 to signature information #2 to the next-hop node of RAN#2. And so on, RAN#i can send data #1, path information #1 to path information #i, and signature information #1 to signature information #i to the landing network element #1.

[0266] To facilitate understanding, a specific example is provided below. Assume the routing path includes a UE, RAN#1, RAN#2, and a landing network element #1. The actions of each node can then include steps 1) through 5), as detailed below:

[0267] 1) The UE executes S320, that is, sends data #1 to RAN#1.

[0268] 2) RAN#1 executes S340, that is, based on the key of RAN#1, signs the path information of RAN#1 (i.e., path information #1) to obtain the signature information of RAN#1 (i.e. signature information #1).

[0269] 3) RAN#1 sends data #1, path information #1 and signature information #1 to RAN#2.

[0270] 4) Based on the key of RAN#2, RAN#2 signs the path information of RAN#2 (denoted as path information #2) to obtain the signature information of RAN#2 (denoted as signature information #2).

[0271] 5) RAN#2 sends data#1, path information#1, signature information#1, path information#2 and signature information#2 to the landing network element#1.

[0272] In some possible implementations, the UE can sign the path information #0 (including the UE's information and the RAN#1's information) based on the UE's key to obtain second signature information (denoted as signature information #0). The UE can then send the path information #0 and signature information #0 to RAN#1.

[0273] The following are two examples of triggering RAN#1 to execute S340, referred to as trigger example 1 and trigger example 2 respectively.

[0274] Trigger Example 1:

[0275] In some possible implementations, method 300 may also include S335 before S340.

[0276] S335, RAN#1 determines whether to perform a secure signature on path information #1 based on the first information.

[0277] The first information may include at least one of the following: first location information, first address information, or UE information. The meaning and acquisition method of the first location information are described below.

[0278] For example, the first location information can be used to indicate the location of the UE that sent data #1, the location indicated by the UE, or the location of the landing network element #1. As an example, the location indicated by the first location information can be one or more countries including the country where the UE is located, one or more regions including the area where the UE is located, one or more PLMNs including the PLMN that the UE accesses, or one or more networks including the UE's home network, etc.

[0279] The UE's location can be understood as its location when transmitting data #1. As a specific example, if the UE is in country D, region 1, or PLMN #1 when transmitting data #1, then the first location information can indicate country D, region 1, or PLMN #1.

[0280] The location indicated by the UE can be indicated by information in the UE's subscription data, information sent by the UE to RAN#1, or other means. The location indicated by the UE can also be understood as: the UE's preferred location, the UE's desired location, the UE's recommended location, or the UE's home network, etc.

[0281] The location of the landing network element #1 can be the country, region, or PLMN that the landing network element #1 is located in.

[0282] In some examples, the first location information may include a location identifier to indicate the aforementioned location. For example, the location identifier may include a country identifier, a region identifier, or a PLMN identifier. As an example, the country identifier may be a mobile country code (MCC). The region identifier may be a tracking area code (TAC). The PLMN identifier may include an identifier composed of an MCC and a mobile network code (MNC).

[0283] The following describes three possible examples of RAN#1 obtaining the first location information. They are referred to as location information acquisition examples 1 to 3.

[0284] Location information acquisition example 1: RAN#1 obtains the first location information from the UE.

[0285] The above example of obtaining location information can be applied to situations where the UE is located as indicated by the first location information, the location indicated by the UE, or the location of the landing network element #1.

[0286] In some possible implementations, prior to S335, method 300 further includes: the UE sending indication information of the first location information to RAN#1. This indication information of the first location information can be used to indicate the first location information itself. For example, the indication information of the first location information can be the first location information itself; or, for example, the indication information of the first location information can be used to indicate a location (denoted as location #1), which belongs to the location indicated by the first location information. In other words, the location indicated by the first location information can include the location indicated by the indication information of the first location information.

[0287] In some possible implementations, RAN#1 can determine the first location information based on the indication information of the first location information. For example, the indication information of the first location information reported by the UE to RAN#1 can indicate country D. Location information #1 configured by RAN#1 indicates countries D and F, and location information #2 indicates countries E and G. In this way, RAN#1 can determine that the location indicated by the first location information is countries D and F, that is, the location indicated by location information #1, based on the indication information of the first location information.

[0288] For example, if the UE and RAN#1 are adjacent nodes, the UE can directly send indication information of the first location information to RAN#1.

[0289] For example, if the UE and RAN#1 are not adjacent nodes, the UE can send a first location information indication to its next-hop node. The UE's next-hop node will send the first location information indication directly to RAN#1 or through at least one node. In the above example, the UE may not be aware that RAN#1 will receive the first location information indication, but objectively, the UE will send the first location information indication to RAN#1 through one or more nodes. Therefore, the above example can also be understood as a case of "the UE sending a first location information indication to RAN#1".

[0290] In some examples, the UE can send the indication information of the first location information together with data #1 to RAN#1. For example, the indication information of the first location information and data #1 can be carried in a single message, or separately in multiple messages sent simultaneously.

[0291] In other examples, the UE can send the indication information of the first location information and data #1 to RAN#1 respectively. For example, the UE can send the indication information of the first location information to RAN#1 during the PDU session establishment procedure, registration procedure, registration request, or other procedures. When there is uplink data to be transmitted, the UE can execute S320, that is, send data #1 to RAN#1.

[0292] Location information acquisition example 2: RAN#1 obtains indication information of the first location information from core network elements such as SMF.

[0293] The above example of obtaining location information can be applied to situations where the first location information indicates the location of the UE, the location indicated by the UE, or the location of the landing network element #1.

[0294] In some possible implementations, prior to S335, method 300 also includes: RAN#1 obtaining indication information of the first location information from network elements such as SMF.

[0295] For example, during session establishment, registration, or other procedures, the UE can send indication information of the first location information to network elements such as the SMF. Furthermore, the SMF, AMF, and location management function (LMF) can obtain the indication information of the first location information by locating the UE on the network side. Network elements such as the SMF can send the indication information of the first location information to RAN#1 before S335.

[0296] In some examples, network elements such as the SMF also indicate the correspondence between the UE and the indication information of the first location information to RAN#1. For example, when the SMF sends the indication information of the first location information to RAN#1, it can carry the UE's information (e.g., UE ID or UE IP address) or information corresponding to the UE (e.g., UE's PDU session ID, etc.). In this way, RAN#1 can determine that the indication information of the first location information corresponds to the UE. Further, in S320, the data #1 sent by the UE to RAN#1 can carry the UE's information or information corresponding to the UE. RAN#1 can determine the indication information of the first location information based on the correspondence between the UE and the indication information of the first location information, as well as the UE's information or the information corresponding to the UE. As an example, the SMF can send information to RAN#1 through the AMF. For example, the SMF can indicate the correspondence between the UE and the indication information of the first location information to the AMF, and the AMF can then indicate the correspondence between the UE and the indication information of the first location information to RAN#1.

[0297] Location information acquisition example 3: RAN#1 determines the first location information based on its own coverage area.

[0298] The above example of obtaining location information 3 can be applied to situations where the UE is located as indicated by the first location information.

[0299] In some possible implementations, prior to S335, method 300 further includes: RAN#1 determining indication information of the first location information based on the coverage of RAN#1, thereby determining the first location information; or, RAN#1 may directly determine the first location information based on the coverage of RAN#1.

[0300] For example, if the coverage area of ​​RAN#1 is entirely within a certain country or region, intersects with a certain country or region, or completely covers a certain country or region, then RAN#1 can determine that the indication information of the first location information points to that country or region. The location indicated by the first location information may include that country or region.

[0301] For example, RAN#1 can use multiple beams to communicate with the UE. As an example, if the coverage area of ​​a certain beam entirely belongs to a certain country or region, intersects with a certain country or region, or completely covers a certain country or region, then RAN#1 can determine that the indication information of the first location information points to that country or region. The location indicated by the first location information may include that country or region.

[0302] For example, if RAN#1's signal covers (or is understood as accessing) a certain PLMN, then RAN#1 can determine that the indication information of the first location information indicates that PLMN. The location indicated by the first location information may include the PLMN.

[0303] The above describes three possible examples of RAN#1 obtaining the first location information. In this application, RAN#1 may also obtain the first location information in other ways, which are not limited here.

[0304] The meaning and acquisition method of the first address information are explained below.

[0305] For example, the first address information can be used to indicate the address of the UE. For instance, the first address information may include the UE's IP address. The first address information may also have other forms, which are not limited herein.

[0306] In some examples, RAN#1 and UE are adjacent nodes. In S320, the data #1 sent by the UE to RAN#1 may carry first address information. For example, in S320, the UE may send a data packet to RAN#1, where data #1 may be the payload part of the data packet, and the first address information may be carried in the source address field (e.g., the source IP address field) of the data packet.

[0307] In other examples, RAN#1 and the UE are not adjacent nodes. In S320, data #1 sent by the UE to its next-hop node can carry first address information; data #1 sent by the UE's next-hop node to RAN#1 can also carry first address information. RAN#1 can receive data #1 and first address information.

[0308] For an example of how the UE obtains the first address information, please refer to the following text, for example, Figure 4 Method 400 is shown below. The meaning and acquisition method of UE information are described below.

[0309] For example, UE information may include UE ID, UE IP address, UE session ID, UE session core network (CN) tunnel information, or UE session access network (AN) tunnel information, etc. As an example, CN tunnel information may include the UE session's UPF IP address, or the UE session's tunnel endpoint identifier (TEID) on the UPF side, etc. As an example, AN tunnel information may include the UE session's RAN IP address (e.g., the IP address of the UE's next-hop RAN node), or the UE session's TEID on the RAN side, etc.

[0310] In some examples, the UE can report its information to RAN#1; that is, data #1 can carry the UE's information. In other examples, RAN#1, core network elements, or other network elements can configure specific communication resources for the UE. In this way, RAN#1 can determine that data #1 received from that specific communication resource originates from the UE, thereby obtaining the UE's information. For example, the aforementioned communication resources may include time-frequency resources, radio bearers, or other communication resources that can embody the UE's information.

[0311] The following example illustrates in detail how RAN#1 determines whether to perform a secure signature on path information #1 based on the first piece of information.

[0312] In some examples, RAN#1 may be configured with a mapping relationship (denoted as mapping relationship #1) between first information and a first security policy (denoted as policy #1). The first information may include at least one of first location information, first address information, or UE information. For example, the aforementioned mapping relationship #1 may be pre-configured in RAN#1.

[0313] For example, SMF, PCF, other core network elements, or other third-party network elements can configure the aforementioned mapping relationship #1 to RAN#1. Here, a third-party network element can be understood as a network element that does not belong to the core network. In some possible implementations, PCF, SMF, operations, administration and maintenance (OAM), or other core network elements can obtain the updated mapping relationship #1 and distribute it to RAN#1. Here, "updated mapping relationship #1" can be understood as the mapping relationship between the updated first information and policy #1. For example, the updated first information may include updated first location information, where the first location information before and after the update can be different. Another example is that the updated first information may include updated first address information, where the first address information before and after the update can be different. As an example, PCF, SMF, OAM, or other core network elements can obtain the updated mapping relationship #1 from third-party network elements. For example, the act of updating mapping relationship #1 can be triggered by changes in laws and regulations, or 3GPP standards. For example, updating mapping relationship #1 can be periodic or timed. In some possible implementations, the UE can subscribe to security policy services, so that PCF, SMF, OAM, or other core network elements can obtain the updated mapping relationship #1 and distribute it to RAN #1.

[0314] Here, policy #1 can be used to instruct the secure signing of path information. In some possible implementations, S335 includes: RAN #1 determines policy #1 based on mapping relationship #1 and first information. Thus, RAN #1 can determine the secure signing of path information (i.e., path information #1) based on policy #1, that is, execute S340.

[0315] In some possible implementations, RAN#1 can also determine, based on the first information, whether to impose location restrictions on the routing path of data #1.

[0316] The phrase "restricting the location of the routing path for data #1" can also be understood as: the routing path for data #1 meets security requirements; or, the node processing data #1 has location restriction requirements; or, the node processing data #1 meets security requirements; or, the node processing data #1 is located at the position indicated by the first location information.

[0317] In this application, unless otherwise specified, security requirements may also be replaced with: security requirements, secure routing requirements, secure routing requirements, location requirements, location requirements, data management requirements, data management requirements, data supervision requirements, or data supervision requirements.

[0318] For example, S335 may include: RAN#1 determining, based on the first information, whether the node processing data #1 has a location restriction; or, based on the first information, RAN#1 determining whether the node processing data #1 needs to meet security requirements; or, based on the first information, RAN#1 determining whether the node processing data #1 needs to be at the location indicated by the first location information.

[0319] As an example, if RAN#1 determines that the node processing data #1 has a location restriction, then it determines that the node processing data #1 is at the location indicated by the first location information; if RAN#1 determines that the node processing data #1 does not have a location restriction, then it determines that the node processing data #1 may or may not be at the location indicated by the first location information, and this application does not limit it.

[0320] The phrase "the node is located at the location indicated by the first location information" can be understood as follows: the node's coverage area falls entirely within the location indicated by the first location information (e.g., a country or region); or, the node's coverage area falls partially within the location indicated by the first location information; or, the node's coverage area completely covers the location indicated by the first location information. "The node is located at the location indicated by the first location information" can also be understood as the node being connected to the PLMN indicated by the first location information.

[0321] In some examples, RAN#1 can be configured with a mapping relationship (denoted as mapping relationship #2) between the first information and the second security policy (policy #2). For example, the mapping relationship #2 can be pre-configured in RAN#1. Alternatively, SMF, PCF, other core network elements, or other third-party network elements can configure the mapping relationship #2 for RAN#1.

[0322] Strategy #2 can be used to instruct the secure signing of path information and to instruct the node processing the data to be located at the location information corresponding to the data. The location information corresponding to the data can be understood as the location of the UE sending the data, the location indicated by the UE, or the location of the receiving network element #1.

[0323] In some examples, policy #2 can be a single policy that instructs: securely sign the path information, and that the node processing the data is located at the position indicated by the location information corresponding to the data. In other examples, policy #2 can include multiple policies. For instance, one of these policies could be the aforementioned policy #1, which instructs that the path information be securely signed. Another of these policies could instruct that the node processing the data is located at the position indicated by the location information corresponding to the data.

[0324] In some possible implementations, S335 includes: RAN#1 determining policy #2 based on mapping relationship #2 and first information. Thus, RAN#1 can determine, based on policy #2, to securely sign the path information (i.e., path information #1) of RAN#1, i.e., execute S340; and RAN#1 can determine, based on policy #2, to send data #1, path information #1, and signature information #1 to the RAN located at the position indicated by the first location information. Let's assume that the RAN determined by RAN#1 to be at the position indicated by the first location information is RAN#2. In this case, the above example can be understood as RAN#2 determining to execute S340 and S350 based on policy #2.

[0325] In some possible implementations, RAN#1 can be configured with at least one policy. Two examples are described below, denoted as Policy Example 1 and Policy Example 2, respectively.

[0326] Strategy Example 1:

[0327] In some examples, the policies configured for RAN#1 may contain some or all of the following information:

[0328] Policy #0 indicates that secure signing should not be performed.

[0329] Strategy #1 instructs that path information be securely signed.

[0330] Strategy #2 instructs that path information be securely signed, and that the node processing the data be located at the position indicated by the location information corresponding to the data.

[0331] Strategy #3 indicates that the node processing the data is located at the position indicated by the location information corresponding to the data.

[0332] In the above policy example 1, policies #0 to #3 can be two independent policies. As an example, SMF, PCF, other core network elements, or other third-party network elements can configure policies #0 to #3 for RAN#1.

[0333] For example, assume that strategy #1 has a mapping relationship with position #1 and position #2 (i.e., mapping relationship #1); strategy #2 has a mapping relationship with position #3 and position #4 (i.e., mapping relationship #2); and strategy #3 has a mapping relationship with position #5 and position #6 (denoted as mapping relationship #3).

[0334] For example, if the first location information indicates location #1 or location #2, S335 includes: RAN #1 determines the path information (i.e., path information #1) of RAN #1 based on the mapping relationship #1 and the first location information, i.e., performs S340.

[0335] For example, when the first location information indicates location #3 or location #4, S335 includes: RAN #1 determines to securely sign the path information (i.e., path information #1) of RAN #1 based on the mapping relationship #2 and the first location information, i.e., executes S340, and RAN #1 determines to send data #1, path information #1, and signature information #1 to the RAN located at location #3 (or location #4) indicated by the first location information.

[0336] For example, if the first location information indicates location #5 (or location #6), method 300 further includes: RAN #1 determines, based on mapping relationship #3 and the first location information, to send data #1 to the RAN located at location #5 (or location #6) indicated by the first location information.

[0337] For example, assume that strategy #1 has a mapping relationship with address #1 and address #2 (i.e., mapping relationship #1); strategy #2 has a mapping relationship with address #3 and address #4 (i.e., mapping relationship #2); and strategy #3 has a mapping relationship with address #5 and address #6 (denoted as mapping relationship #3).

[0338] For example, if the first address information indicates address #1 or address #2, S335 includes: RAN #1 determines the path information (i.e., path information #1) of RAN #1 based on the mapping relationship #1 and the first address information, i.e., performs S340.

[0339] For example, if the first address information indicates address #3 or address #4, S335 includes: RAN #1 determines to securely sign the path information (i.e., path information #1) of RAN #1 based on the mapping relationship #2 and the first address information, i.e., executes S340, and RAN #1 determines to send data #1, path information #1, and signature information #1 to the RAN at the location indicated by the first location information.

[0340] For example, if the first address information indicates address #5 or address #6, S335 includes: RAN #1 determines, based on mapping relationship #3 and the first address information, to send data #1 to the RAN located at the position indicated by the first location information. The method by which RAN #1 obtains the first location information can be found in Examples 1 to 3 of location information acquisition, and will not be repeated here.

[0341] For example, assume that there is a mapping relationship between policy #1 and UE information #1 and UE information #2 (i.e., mapping relationship #1); there is a mapping relationship between policy #2 and UE information #3 and UE information #4 (i.e., mapping relationship #2); and there is a mapping relationship between policy #3 and UE information #5 and UE information #6 (denoted as mapping relationship #3).

[0342] For example, if the UE information is UE information #1 or UE information #2, S335 includes: RAN #1 determines the path information (i.e., path information #1) of RAN #1 based on the mapping relationship #1 and the UE information, i.e., performs S340.

[0343] For example, if the UE information indicates UE information #3 or UE information #4, S335 includes: RAN #1 determines to securely sign the path information (i.e., path information #1) of RAN #1 based on the mapping relationship #2 and the UE information, i.e., executes S340, and RAN #1 determines to send data #1, path information #1, and signature information #1 to the RAN at the location indicated by the first location information.

[0344] For example, if the UE information indicates UE information #5 or UE information #6, S335 includes: RAN #1 determines, based on mapping relationship #3 and UE information, to send data #1 to the RAN at the location indicated by the first location information.

[0345] Strategy Example 2:

[0346] In some examples, the policies configured for RAN#1 may contain some or all of the following information:

[0347] Strategy #a, no requirements.

[0348] Policy #b instructs that path information be securely signed.

[0349] Strategy #c indicates the location of the node processing the data, as indicated by the location information corresponding to the data.

[0350] As an example, SMF, PCF, other core network elements, or other third-party network elements can configure the above policies #a to #c for RAN#1.

[0351] In this context, strategy #a can be understood as strategy #0 in strategy example 1. Strategy #b can be understood as strategy #1 in strategy example 1. Strategies #b and #c can be understood as strategy #2 in strategy example 1. In other words, strategy #2 can include strategy #b and strategy #c. Strategy #c can be understood as strategy #3.

[0352] For example, assume that strategy #b has a mapping relationship with position #1, position #2, position #3 and position #4 (i.e., mapping relationship #1); and strategy #c has a mapping relationship with position #3, position #4, position #5 and position #6 (i.e., mapping relationship #2).

[0353] For example, if the first location information indicates location #1 or location #2, S335 includes: RAN #1 determines the use strategy #b based on the mapping relationship #1 and the first location information, thereby performing a secure signature on the path information of RAN #1 (i.e., path information #1), that is, executing S340.

[0354] For example, if the first location information indicates location #3 (or location #4), method 300 further includes: RAN #1 determines, based on mapping relationship #2 and the first location information, to use policy #b and policy #c to perform secure signing, and sends data #1, path information #1, and signature information #1 to the RAN located at location #3 (or location #4) indicated by the first location information.

[0355] For example, if the first location information indicates location #5 (or location #6), method 300 further includes: RAN #1 determines, based on mapping relationship #2 and the first location information, to use strategy #c to send data #1 to the RAN at location #5 (or location #6) indicated by the first location information.

[0356] For example, assume that strategy #b has a mapping relationship with address #1, address #2, address #3 and address #4 (i.e., mapping relationship #1); and strategy #c has a mapping relationship with address #3, address #4, address #5 and address #6 (i.e., mapping relationship #2).

[0357] For example, if the first address information indicates address #1 or address #2, S335 includes: RAN #1 determines the use policy #b based on the mapping relationship #1 and the first address information, thereby performing a secure signature on the path information of RAN #1 (i.e., path information #1), that is, executing S340.

[0358] For example, if the first address information indicates address #3 or address #4, method 300 further includes: RAN #1 determines, based on mapping relationship #2 and the first address information, to use strategy #b and strategy #c to securely sign the path information of RAN #1 (i.e., path information #1), and to send data #1, path information #1, and signature information #1 to the RAN at the location indicated by the first location information.

[0359] For example, if the first address information indicates address #5 or address #6, method 300 further includes: RAN #1 determines the use strategy #c based on the mapping relationship #2 and the first address information, thereby sending data #1 to the RAN at the location indicated by the first location information.

[0360] For details on how RAN#1 obtains the first location information, please refer to Examples 1 to 3 for Location Information Acquisition, which will not be repeated here.

[0361] For example, assume that there is a mapping relationship between policy #b and UE information #1, UE information #2, UE information #3 and UE information #4 (i.e., mapping relationship #1); and that there is a mapping relationship between policy #c and UE information #3, UE information #4, UE information #5 and UE information #6 (i.e., mapping relationship #2).

[0362] For example, if the UE information is UE information #1 or UE information #2, S335 includes: RAN #1 determines the use policy #b based on the mapping relationship #1 and the UE information, thereby performing a security signature on the path information of RAN #1 (i.e., path information #1), that is, executing S340.

[0363] For example, if the UE information is UE information #3 or UE information #4, method 300 further includes: RAN #1 determines, based on mapping relationship #2 and UE information, to use policy #b and policy #c to securely sign the path information of RAN #1 (i.e., path information #1), and sends data #1, path information #1, and signature information #1 to the RAN at the location indicated by the first location information.

[0364] For example, if the UE information is UE information #5 or UE information #6, method 300 further includes: RAN #1 determines the use strategy #c based on the mapping relationship #2 and the first address information, thereby sending data #1 to the RAN at the location indicated by the first location information.

[0365] The above describes trigger example 1. As can be seen from the content of trigger example 1, the first information can be used to trigger RAN#1 to perform a secure signature on path information #1. For ease of description, information that has the function of "triggering RAN#1 to perform a secure signature on path information #1" can be referred to as "third information".

[0366] In some possible implementations, method 300 also includes: S330, the UE sends third information to RAN#1.

[0367] As can be seen from the content of Trigger Example 1, the third information can be at least one of the first location information, the first address information, or the UE's information. However, this application does not limit the specific content of the third information, and the third information may also be other information.

[0368] Optionally, the third information may also be used to trigger RAN#1 to send data #1 to the node located at the position indicated by the first location information. For example, referring to triggering example 1, the first location information, the first address information, or the UE's information may be used to trigger RAN#1 to send data #1 to the node located at the position indicated by the first location information.

[0369] Trigger Example 2:

[0370] In trigger example 2, the third information sent by the UE in S330 can be the first indication information. In some possible implementations, RAN#1 receives the first indication information from the previous hop node of RAN#1. The content of the first indication information will be described below.

[0371] Optionally, the first indication information is used to instruct the path information to be securely signed. Thus, S340 may include: RAN#1, in response to the first indication information, signing the path information #1 based on the key of RAN#1 to obtain signature information #1.

[0372] In some examples, the first indication information can be an optional field in a message. Whether or not the message carries the first indication information indicates whether the path information should be securely signed. For example, if the message carries the first indication information, i.e., RAN#1 receives the first indication information, then RAN#1 can execute S340; if the message does not carry the first indication information, i.e., RAN#1 does not receive the first indication information, then RAN#1 can choose not to execute S340.

[0373] In other examples, the first indication information can indicate whether the path information is securely signed. For example, the first indication information can be 1 bit. A value of "1" indicates that the path information is signed; a value of "0" indicates that the path information is not signed. Alternatively, a value of "0" indicates that the path information is signed; a value of "1" indicates that the path information is not signed. The first indication information can also be more bits, which is not limited in this application.

[0374] Optionally, the first indication information is used to indicate that the node processing data #1 is at the location indicated by the first location information. For example, the first indication information may indicate: location restriction on the routing path of data #1; or, that the node processing data #1 is at the location indicated by the location information corresponding to data #1.

[0375] The phrase "restricting the location of the routing path for data #1" can also be understood as: the routing path for data #1 meets security requirements; or, the location of the node processing data #1 is restricted; or, the node processing data #1 meets security requirements; or, the node processing data #1 is located at the position indicated by the first location information.

[0376] The location information corresponding to the data can be understood as the location of the UE that sent the data, the location indicated by the UE, or the location of the receiving network element #1.

[0377] In some examples, the first indication information can be used to indicate: securely signing the path information, and / or that the node processing data #1 is at the position indicated by the first location information.

[0378] In other examples, the information indicating the secure signing of the path information and the information indicating that the node processing data #1 is in the position indicated by the first location information may be different. For example, instruction information #5 may be used to indicate the secure signing of the path information. Instruction information #6 may be used to indicate that the node processing data #1 is in the position indicated by the first location information; these may be different information.

[0379] Thus, the first instruction information in S330 can be used to implement the functions of instruction information #5 and / or instruction information #6. Unless otherwise specified, the first instruction information in this application can be replaced with instruction information #5 and / or instruction information #6. Instruction information #5 and instruction information #6 are different pieces of information.

[0380] In some examples, the first indication information (or alternatively, indication information #5 and / or indication information #6) may be an optional field in a message. Whether or not the message carries the first indication information can indicate whether to securely sign the path information and whether to impose location restrictions on the routing path of data #1. For example, if the message carries the first indication information, i.e., RAN #1 receives the first indication information, then RAN #1 can execute S340 and determine to send data #1, path information #1, and signature information #1 to the RAN located at the position indicated by the first location information; if the message does not carry the first indication information, i.e., RAN #1 does not receive the first indication information, then RAN #1 may not execute S340, and the next-hop node of RAN #1 may or may not be located at the position indicated by the first location information, which is not limited in this application.

[0381] In other examples, the first indication information may indicate whether the path information is securely signed and whether the routing path of data #1 is subject to positional restrictions. For example, the first indication information may be 1 bit. A value of "1" indicates that the path information is signed and the routing path of data #1 is subject to positional restrictions; a value of "0" indicates that the path information is not signed and the routing path of data #1 is not subject to positional restrictions. Alternatively, a value of "0" indicates that the path information is signed and the routing path of data #1 is subject to positional restrictions; a value of "1" indicates that the path information is not signed and the routing path of data #1 is not subject to positional restrictions. The first indication information may also consist of more bits, which is not limited in this application.

[0382] In some further examples, the first indication information may indicate whether the path information is securely signed and whether the routing path for data #1 is subject to location restrictions. For example, the first indication information may be 1 bit. A value of "0" indicates that the path information is signed; a value of "1" indicates that the path information is signed and the routing path for data #1 is subject to location restrictions. As another example, the first indication information may be 1 bit. A value of "0" indicates that the path information is signed and the routing path for data #1 is not subject to location restrictions; a value of "1" indicates that the path information is signed and the routing path for data #1 is subject to location restrictions.

[0383] The following is an example of the previous hop node of RAN#1.

[0384] In some examples, the upstream node of RAN#1 can be the UE. In other words, RAN#1 and the UE can be adjacent nodes. Thus, S330 can be understood as the UE directly sending the first indication information to RAN#1, and RAN#1 directly receiving the first indication information from the UE.

[0385] As an example, the UE can send data #1 and the first indication information together to RAN #1, or it can send data #1 and the first indication information separately to RAN #1. In other words, S320 and S330 can be one step or two steps, and this application does not limit them.

[0386] In other examples, the upstream node of RAN#1 can be a different node from the UE. In other words, RAN#1 and the UE can be non-adjacent nodes.

[0387] For example, the UE can send a first indication message, which can be relayed through at least one node and eventually reach RAN#1. Exemplarily, the previous hop node of RAN#1 can be a RAN deployed on an NTN device.

[0388] It is understood that the first indication information refers to information with a certain function, without limiting the specific form of the first indication information. For example, the first indication information has the function of "instructing to perform a secure signature on the path information" and / or has the function of "instructing the node processing data #1 to be at the position indicated by the first location information".

[0389] The first indication information sent by the UE and the first indication information ultimately received by RAN#1 may be the same or different in form. As an example, the "form" of the first indication information can be understood as the content contained in the first indication information, the name of the first indication information, etc.

[0390] As can be seen from the content of triggering example 2, the third information can be the first instruction information. However, this application does not limit the specific content of the third information, and the third information may also be other information.

[0391] Optionally, the third information may also be used to trigger RAN#1 to send data #1 to the node at the location indicated by the first location information. For example, referring to triggering example 2, the first indication information may be used to trigger RAN#1 to send data #1 to the node at the location indicated by the first location information.

[0392] For an example of how to enable the UE to send the first indication information, see the following text, for example, Figure 5 Method 500 is shown.

[0393] The above details triggering example 1 and triggering example 2 for RAN#1 to execute S340. Below is an example of RAN#1 instructing RAN#2 to perform a security signature.

[0394] In some examples, RAN#1 can implicitly instruct RAN#2 to perform a secure signature. For example, signature information #1 can implicitly instruct RAN#2 to perform a secure signature. Based on signature information #1, RAN#2 can determine to perform a secure signature on its path information (denoted as path information #2).

[0395] In other examples, RAN#1 can explicitly instruct RAN#2 to perform a secure signature. In some possible implementations, method 300 further includes: S352, RAN#1 sends a second instruction message to RAN#2. This second instruction message can be used to instruct RAN#2 to perform a secure signature. That is, the second instruction message can explicitly instruct RAN#2 to perform a secure signature.

[0396] As an example, the second instruction information in S352 can be sent simultaneously with the data #1, path information #1, and signature information #1 in S350. In other words, S350 and S352 can be the same step. As another example, the second instruction information in S352, the data #1, path information #1, and signature information #1 in S350 can be sent separately. In other words, S350 and S352 can be different steps.

[0397] Optionally, the second indication information is also used to instruct RAN#2 to impose location restrictions on the routing path of data #1.

[0398] In some possible implementations, RAN#1 can determine the second indication information based on the first information or the first indication information.

[0399] For example, RAN#1 can determine a policy based on the first information. As an example, if RAN#1 determines policy #1, the second indication information determined by RAN#1 can be used to instruct RAN#2 to perform a secure signature. If RAN#1 determines policy #2, the second indication information determined by RAN#1 can be used to instruct RAN#2 to perform a secure signature and to instruct RAN#2 to impose location restrictions on the routing path of data #1.

[0400] For example, RAN#1 can determine second indication information based on the first indication information. If the first indication information instructs RAN#1 to perform a security signature, the second indication information determined by RAN#1 can be used to instruct RAN#2 to perform a security signature. If the first indication information instructs RAN#1 to perform a security signature and also instructs RAN#1 to restrict the location of the routing path for data #1, the second indication information determined by RAN#1 can be used to instruct RAN#2 to perform a security signature and to instruct RAN#2 to restrict the location of the routing path for data #1.

[0401] This application does not limit the specific name of the second instruction information. For example, the second instruction information may also be called a secure routing instruction, a secure signature instruction, a signature instruction, or other names.

[0402] As an example, the second indication information determined by RAN#1 can be two different indication information, such as indication information #7 and indication information #8. Indication information #7 can be used to instruct RAN#2 to perform a secure signature. Indication information #8 can be used to instruct RAN#2 to apply location restrictions to the routing path of data #1.

[0403] The following details how RAN#1 selects RAN#2 as its next-hop node. Examples 1 through 2 of node selection are described below.

[0404] Node selection example 1:

[0405] In Node Selection Example 1, RAN#1 can be configured with information on at least one routing path or at least one next-hop node. RAN#1 can select a suitable routing path from the at least one configured routing path, and then send data #1, path information #1, and signature information #1 to the next-hop node (denoted as RAN#2) on that routing path, i.e., execute S350. Alternatively, RAN#1 can select a suitable next-hop node from the at least one configured next-hop node, and then send data #1, path information #1, and signature information #1 to that next-hop node (denoted as RAN#2), i.e., execute S350.

[0406] To facilitate understanding, the following section provides a detailed explanation of node selection example 1, using specific examples.

[0407] In some possible implementations, method 300 also includes S310 before S350.

[0408] S310, RAN#1 receives the first configuration information from the first network element (or, the routing node controller). Correspondingly, the first network element sends the first configuration information to RAN#1. An example of the first network element is described below.

[0409] The first network element can be used to plan routing paths. For example, the first network element can determine the routing path from the UE to the landing network element #1, and determine the complete routing path information.

[0410] Unless otherwise specified, the first network element in this application may be a communication device (e.g., a core network device or a third-party device), a component in the communication device (e.g., a processor, a chip, or a chip system), or a logic module or software that can implement some or all of the functions of the communication device.

[0411] As an example, the first network element can be a RAN node, SMF, other network elements involved in the current 3GPP protocol, or a network element added by the future 3GPP protocol. In other examples, the first network element can also be RAN#1, in which case S310 can be understood as RAN#1 determining the first configuration information. In still other examples, the first network element can be a different network element from the SMF. The first network element can send the first configuration information to RAN#1 through the SMF.

[0412] The first network element can also be called a routing node controller, path planning network element, or other names. For ease of understanding, this application refers to the first network element as a routing node controller.

[0413] In some examples, the routing node controller can be deployed on NTN devices, such as low Earth orbit (LEO) satellites, medium Earth orbit (MEO) satellites, or geostationary orbit (GEO) satellites. In other examples, the routing node controller can be deployed on the ground; this application is not limited to this.

[0414] The following are examples of the two functions of the first configuration information, referred to as Configuration Example 1 and Configuration Example 2, respectively.

[0415] Configuration Example 1: The first configuration information can be used to configure the first route path.

[0416] As an example, the first routing path can be a routing path with the destination network element as the landing network element #1. Exemplarily, the first routing path can also be understood as a routing path planned (or determined) by the routing node controller that can route data #1 from the UE to the landing network element #1. The first routing path can also be called a planned routing path, a preset routing path, or other names.

[0417] In some examples, the first configuration information may include information about the first routing path. For example, the first routing path information may include information about RAN#1, RAN#2, ..., and the landing network element #1. Optionally, the first routing path information may also include UE information.

[0418] The first routing path can correspond to the information of the landing network element #1. For example, the information of the first routing path can include the information of the landing network element #1. In this way, after obtaining the information of the first routing path, RAN #1 can determine that there is a correspondence between the first routing path and the information of the landing network element #1. In some possible implementations, before S350, method 300 further includes: S342.

[0419] S342, RAN#1 determines the first routing path based on the information of the landing network element #1. For example, RAN#1 can determine the first routing path based on the correspondence between the first routing path and the information of the landing network element #1, as well as the information of the landing network element #1. Alternatively, RAN#1 can find the routing path (i.e., the first routing path) whose last hop node is the aforementioned landing network element #1, based on the information of the landing network element #1.

[0420] As an example, S342 can be executed if RAN#1 is the next-hop node of the UE.

[0421] In this first routing path, RAN#2 can be the next-hop node of RAN#1. Thus, after S342, RAN#1 can determine that RAN#2 is the next-hop node of RAN#1 based on the first routing path, and thus execute S350.

[0422] For example, the information of the landing network element #1 can be the ID of the landing network element #1, the IP address of the landing network element #1, or the TEID of the landing network element #1. The landing network element #1 can be a gateway station or a UPF. For ease of understanding, the following detailed explanation of how RAN#1 obtains the information of the landing network element #1 is provided with specific examples.

[0423] In some examples, prior to S342, RAN#1 can obtain data #1 by executing S320 and perform data radio resource (DRB) mapping based on data #1 to obtain the UPF IP address. For example, the UPF IP address can be the information of the aforementioned terminating network element #1. As another example, RAN#1 can determine the UPF ID based on the mapping relationship between the UPF IP address and the UPF ID; where the UPF ID can be the information of the aforementioned terminating network element #1. Yet another example, RAN#1 can determine the gateway station ID (or gateway station IP address) based on the mapping relationship between the UPF IP address and the gateway station ID (or gateway station IP address); where the gateway station ID (or gateway station IP address) can be the information of the aforementioned terminating network element #1.

[0424] As an example, RAN#1 can obtain the mapping relationship between UPF IP address and UPF ID during the PDU session establishment process.

[0425] In other examples, data #1 may carry UE information (e.g., UE identifier), or RAN #1 may obtain UE information based on data #1. RAN #1 stores a mapping between UE information and gateway IDs, so RAN #1 can determine the gateway ID based on the UE identifier.

[0426] As an example, RAN#1 can obtain the ID (or IP address) of the gateway station corresponding to the UE during the UE registration process and store the mapping relationship between the UE information and the gateway station ID.

[0427] As an example, RAN#1 can obtain the ID (or IP address) of the gateway station corresponding to the UE during the UE registration process. Furthermore, RAN#1 can obtain the UPF IP address corresponding to the UE during the UE's PDU session establishment process. In this way, RAN#1 can obtain the mapping relationship between the UPF IP address and the gateway station ID (or IP address).

[0428] In some examples, the first configuration information can be used to configure multiple routing paths. The first routing path can be one of the aforementioned multiple routing paths.

[0429] As an example, the destination network elements of multiple routing paths can be different landing network elements. In this way, RAN#1 can select the first routing path corresponding to the information of landing network element #1 from multiple routing paths by executing S342.

[0430] As another example, the destination network element for multiple routing paths can all be the landing network element #1. RAN #1 can determine which routing path to use based on security policies, UE indication information, or the load conditions of the multiple routing paths. See Example 1 and Example 2 for second node determination below for details.

[0431] Configuration Example 2: The first configuration information can be used to configure RAN#2.

[0432] In some examples, the first configuration information may include information about RAN#2. For instance, the routing node controller may determine a first routing path and configure the next-hop node for RAN#1 (i.e., RAN#2) for RAN#1, and the next-hop node for RAN#2 for RAN#2. In some possible implementations, the routing node controller may configure the next-hop node for each node on the first routing path, respectively.

[0433] In this implementation, the information in RAN#2 can correspond to the information in the destination network element #1. For example, the routing node controller can indicate the correspondence between the information in RAN#2 and the information in the destination network element #1 to RAN#1. As an example, the routing node controller can explicitly configure the correspondence between the information in RAN#2 and the information in the destination network element #1 for RAN#1. As another example, the routing node controller can send the information in RAN#2 and the information indicating the destination network element #1 to RAN#1 (e.g., the information in the destination network element #1 itself, or, implicitly, the information in the destination network element #1). In this way, RAN#1 can determine the correspondence between the information in RAN#2 and the information indicating the destination network element #1 based on the information in RAN#2 and the information indicating the destination network element #1. In some possible implementations, before S350, method 300 further includes: S344.

[0434] S344, RAN#1 determines RAN#2 based on the first configuration information and the information of the landing network element #1. For example, RAN#1 can determine RAN#2 based on the correspondence between the information of RAN#2 and the information of the landing network element #1, as well as the information of the landing network element #1.

[0435] As an example, S344 can be executed if RAN#1 is the next-hop node of the UE.

[0436] For example, the information of the landing network element #1 can be the ID of the landing network element #1 or the IP address of the landing network element #1. The landing network element #1 can be a gateway station or a UPF.

[0437] In some examples, before S344, RAN#1 can obtain data #1 by executing S320 and perform DRB mapping based on data #1 to obtain the UPF IP address. For example, the UPF IP address can be the information of the aforementioned landing network element #1. Alternatively, RAN#1 can obtain information about the landing network element #1 (such as the UPF ID, the gateway ID, or the gateway IP address) based on the UPF IP address. See Configuration Example 1 for details, which will not be elaborated further.

[0438] In some examples, the initial configuration information can be used to configure information for multiple RANs. These multiple RANs can all be the next-hop node of RAN#1. RAN#2 can be one of these multiple RANs.

[0439] As an example, information from multiple RANs corresponds to different destination network elements. Thus, RAN#1 can execute S344 to select RAN#2 from among the multiple RANs, corresponding to the information of destination network element #1.

[0440] As another example, the information from multiple RANs all corresponds to the landing network element #1. RAN #1 can determine which RAN among the multiple RANs to select based on security policies or UE indications. See Example 1 and Example 2 for second node determination below for details.

[0441] In some examples of configuration example 2, the first configuration information can also be used to indicate the identifier of the first routing path. For example, the routing node controller can configure the next-hop node and the identifier of the first routing path for each node on the first routing path. In this way, each node on the first routing path can determine the next-hop node corresponding to the identifier of the first routing path.

[0442] As a concrete example, the first configuration information can configure RAN#1 with RAN#2 information and path identifier #1. The routing node controller can configure RAN#2 with RAN#3 information and path identifier #1, and RAN#4 information and path identifier #2. RAN#1 can send path identifier #1 to RAN#2, so that RAN#2 can determine its next-hop node as RAN#3, instead of RAN#4, based on path identifier #1.

[0443] The above describes two functions of the first configuration information: Configuration Example 1 and Configuration Example 2. A description of how the routing node controller determines the first configuration information is provided later. Figure 6 Method 600 is shown.

[0444] Node selection example 2:

[0445] In node selection example 2, RAN#1 can determine at least one RAN based on ephemeris information and destination node information (e.g., information of landing network element #1), wherein the at least one RAN includes RAN#2.

[0446] Furthermore, RAN#1 can send data #1 to at least one of the aforementioned RANs. Specifically, S360 can be considered as the case where RAN#1 sends data to RAN#2.

[0447] As an example, assuming RAN#1, based on ephemeris information, determines that the RAN also includes RAN#a, then RAN#1 can send data #1, path information #a, and signature information #a to RAN#a. The path information #a includes information about the previous hop node of RAN#1, information about RAN#1, and information about RAN#5. The signature information #a can be a signature obtained by RAN#1 signing the aforementioned path information #a using RAN#1's key.

[0448] Optionally, the path information #a also includes the time information for RAN#1 processing data #1. See the relevant description in S350 for details, which will not be repeated here.

[0449] The above describes node selection examples 1 and 2. In short, in node selection example 1, the routing node controller can configure a complete routing path for RAN#1, or configure the next-hop node for RAN#1. In node selection example 2, RAN#1 can send data #1, the corresponding path information, and the corresponding signature information using a "flooding" method based on ephemeris information.

[0450] The following section describes how RAN#1 determines RAN#2 from another perspective, denoted as Second Node Determination Example 1 and Second Node Determination Example 2. In short, in Second Node Determination Example 1, RAN#1 can determine RAN#2 based on a security policy. In Second Node Determination Example 2, RAN#1 can determine RAN#2 based on first indication information.

[0451] Example 1 of determining the second node:

[0452] In some possible implementations, method 300 also includes S346 before S350.

[0453] S346, RAN#1 determines RAN#2 based on policy #0, policy #1, policy #2 or policy #3.

[0454] As an example, RAN#1 can determine RAN#2 based on strategy #0 or strategy #1. RAN#2 may or may not be located at the position indicated by the first location information. This application does not limit this.

[0455] As another example, RAN#1 can determine RAN#2 based on strategy #2 or strategy #3, and RAN#2 can be located at the position indicated by the first location information.

[0456] For an example of how RAN#1 determines whether to use policy #0, policy #1, policy #2, or policy #3, please refer to the corresponding content in trigger example 1, such as the section on "How RAN#1 determines whether to perform a secure signature on path information #1 based on the first information", which will not be repeated here.

[0457] In some examples, second node determination example 1 can be combined with node selection example 1. Thus, method 300 also includes S310, where RAN#1 receives first configuration information.

[0458] As an example, the first configuration information can be used to configure the first routing path (i.e., the content of configuration example 1). Thus, S346 and S342 can be considered as a single step, or as two steps with no fixed execution order. For example, S346 may include: RAN#1 determines the first routing path based on policy #2 or policy #3. Wherein, on the first routing path, RAN#2 is the next-hop node of RAN#1, and the nodes on the first routing path are located at the positions indicated by the first location information.

[0459] For example, S346 and S342 can be understood as follows: RAN#1 can determine whether to restrict the location of the node processing data #1 based on the security policy, and determine the next-hop node (denoted as RAN#2) based on the routing path configured by the routing node controller.

[0460] When multiple routing paths are configured in the first configuration information, this application denotes the routing path ultimately selected by RAN#1 as the first routing path. Thus, S346 and S342 above can be understood as follows: RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on the security policy, and finally determine the first routing path that satisfies the security policy among the multiple routing paths, and select the next-hop node of RAN#1 on the first routing path (denoted as RAN#2).

[0461] For example, on a first routing path satisfying both strategy #0 and strategy #1, each node may or may not be located at the position indicated by the first location information; this application does not limit this. As another example, on a first routing path satisfying either strategy #2 or strategy #3, each node may be located at the position indicated by the first location information.

[0462] As another example, the first configuration information can be used to configure RAN#2 (i.e., the content of configuration example 2). Thus, S346 and S344 can be regarded as a single step, or as two steps without a defined execution order. That is, RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on the security policy, and select a next-hop node (denoted as RAN#2) from the next-hop nodes configured in the routing node controller.

[0463] When multiple RANs are configured in the first configuration information, this application designates the RAN ultimately selected by RAN#1 as RAN#2. Thus, S346 and S344 above can be understood as follows: RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on the security policy, and ultimately select RAN#2 that satisfies the security policy from the multiple RANs configured in the first configuration information.

[0464] For example, RAN#2 satisfying both strategy #0 and strategy #1 may or may not be located at the position indicated by the first location information; this application does not limit this. As another example, RAN#2 satisfying either strategy #2 or strategy #3 may be located at the position indicated by the first location information.

[0465] In other examples, the second node determination example 1 can be combined with the node selection example 2. For instance, RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on a security policy, and ephemeris information can determine the next-hop node.

[0466] As an example, RAN#1 can determine, based on policy #0 or policy #1, that no location restrictions need to be imposed on the node processing data #1. Thus, RAN#1 can determine at least one next-hop node (including RAN#2) based on ephemeris information and destination node information (e.g., information from the landing network element #1).

[0467] As another example, RAN#1 can determine the location restriction for the node processing data #1 based on policy #2 or policy #3. Thus, RAN#1 can determine one or more RANs (including RAN#2) where the next-hop node is located, based on ephemeris information and destination node information (e.g., information of the landing network element #1). For example, S346 may include: RAN#1 determines RAN#2 located at the position indicated by the first location information based on policy #2 (or policy #3) and ephemeris information.

[0468] Example 2 of determining the second node:

[0469] In some possible implementations, method 300 also includes S348 before S350.

[0470] S348, RAN#1 determines RAN#2 based on the first indication information.

[0471] As an example, if the first indication information does not indicate that the node processing data #1 is at the position indicated by the first location information, or indicates that the node processing data #1 does not need to be at the position indicated by the first location information, then RAN #1 can determine RAN #2 based on the first indication information. RAN #2 may or may not be at the position indicated by the first location information, and this application does not limit this.

[0472] As another example, if the first indication information indicates that the node processing data #1 is at the position indicated by the first location information, then RAN#1 can determine RAN#2 based on the first indication information, and RAN#2 can be at the position indicated by the first location information.

[0473] For details regarding the first instruction message, please refer to Trigger Example 2; it will not be repeated here.

[0474] In some examples, the second node determination example 2 can be combined with the node selection example 1. Thus, method 300 also includes S310, whereby RAN#1 receives the first configuration information.

[0475] As an example, the first configuration information can be used to configure the first routing path (i.e., the content of configuration example 1). Thus, S348 and S342 can be considered as a single step, or as two steps with no fixed execution order. For example, S348 may include: RAN#1 determines the first routing path based on the first indication information. Wherein, on the first routing path, RAN#2 is the next-hop node of RAN#1, and the nodes on the first routing path are located at the positions indicated by the first location information.

[0476] For example, S348 and S342 can be understood as follows: RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on the first indication information, and determine the next-hop node (denoted as RAN#2) based on the routing path configured by the routing node controller.

[0477] When multiple routing paths are configured in the first configuration information, this application denotes the routing path finally selected by RAN#1 as the first routing path. Thus, the above S348 and S342 can be understood as follows: RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on the first indication information, and finally determine the first routing path that satisfies the first indication information among the multiple routing paths, and select the next-hop node of RAN#1 on the first routing path (denoted as RAN#2).

[0478] As another example, the first configuration information can be used to configure RAN#2 (i.e., the content of configuration example 2). Thus, S348 and S344 can be regarded as a single step, or as two steps without a defined execution order. That is, RAN#1 can determine whether to impose a location restriction on the node processing data #1 based on the first indication information, and select a next-hop node (denoted as RAN#2) from the next-hop nodes configured in the routing node controller.

[0479] When multiple RANs are configured in the first configuration information, this application designates the RAN ultimately selected by RAN#1 as RAN#2. Thus, S348 and S344 above can be understood as follows: RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on the first indication information, and ultimately select RAN#2 that satisfies the first indication information from the multiple RANs configured in the first configuration information.

[0480] In other examples, the second node determination example 2 can be combined with the node selection example 2. For example, RAN#1 can determine whether to impose location restrictions on the node processing data #1 based on the first indication information, and the ephemeris information determines the next-hop node.

[0481] As an example, if the first indication information does not indicate that the node processing data #1 is at the location indicated by the first location information, RAN #1 can determine, based on the first indication information, that there is no need to restrict the location of the node processing data #1. In this way, RAN #1 can determine at least one next-hop node (including RAN #2) based on ephemeris information and destination node information (e.g., information of the landing network element #1).

[0482] As another example, if the first indication information indicates that the node processing data #1 is at the location indicated by the first location information, RAN #1 can determine a location restriction on the node processing data #1 based on the first indication information. Thus, RAN #1 can determine one or more RANs (including RAN #2) at the location indicated by the first location information based on ephemeris information and destination node information (e.g., information of the landing network element #1). For example, S346 may include: RAN #1 determining RAN #2 at the location indicated by the first location information based on the first indication information and ephemeris information.

[0483] The above examples, combining node selection example 1, node selection example 2, second node determination example 1, and second node determination example 2, detail how RAN#1 selects RAN#2 as the next-hop node for RAN#1. The following example demonstrates how network elements verify the validity of signature information.

[0484] In some possible implementations, after S360, method 300 also includes: S372, S374, and S376. These are described below.

[0485] S372, verify the network element to obtain signature information #1 and path information #1.

[0486] In some examples, the verification network element can be the destination network element. In this case, S372 and S360 can be regarded as a single step. That is, S372 includes: the verification network element (i.e., the destination network element) receiving data #1, path information #1, and signature information #1 from RAN#2.

[0487] In other examples, the verification network element can be a different network element from the destination network element. Thus, S372 can include: the destination network element sending path information #1 and signature information #1 to the verification network element. Correspondingly, the verification network element receives path information #1 and signature information #1 from the destination network element.

[0488] S374, verify the network element based on the information of RAN#1 to determine the public key of RAN#1.

[0489] For example, path information #1 may include information about the previous hop node of RAN#1, information about RAN#1, and information about RAN#2 (i.e., the next hop node of RAN#1). Therefore, the verification network element can obtain the information about RAN#1 from path information #1.

[0490] In some examples, the verification network element can store the mapping between RAN#1 information and RAN#1's public key. In this way, the verification network element can determine RAN#1's public key based on the aforementioned mapping and RAN#1 information.

[0491] For example, the verification network element can be configured with certificate information for RAN#1. This certificate information may include RAN#1's information (e.g., RAN#1's IP address, RAN#1's ID, the ID of the first NTN device where RAN#1 resides, or the IP address of the first NTN device where RAN#1 resides) and RAN#1's public key. This certificate information can serve as an example of the correspondence between RAN#1's information and RAN#1's public key. The verification network element can determine RAN#1's public key based on this certificate information and RAN#1's information.

[0492] In some possible implementations, prior to S374, method 300 further includes: verifying that the network element receives second configuration information from the key management network element. This second configuration information is used to configure the public key of RAN#1. Optionally, the second configuration information is also used to configure the correspondence between the information of RAN#1 and the public key of RAN#1.

[0493] The aforementioned key management network element can be a core network element or a third-party network element; this application does not limit its scope. Furthermore, the key management network element can also be called a key repository, certificate repository, or other names; this application does not impose any limitations on these names.

[0494] S376, verify the validity of the network element based on the public key and path information #1 of RAN#1, and verify the validity of the signature information #1.

[0495] For example, the verification network element can process path information #1 based on the public key of RAN#1 to obtain signature information #1'. The verification network element can compare the difference between signature information #1' and signature information #1 to verify the validity of signature information #1. The verification network element can also verify the validity of signature information #1 in other ways, which are not limited in this application.

[0496] In some examples, the verification network element can be a terminating network element. If, based on S376 above, the verification network element determines that signature information #1 is valid, then the verification network element can forward data #1. For example, the verification network element can be a gateway station, which can forward data #1 to the terrestrial routing network. Another example is a UPF, which can forward data #1 to the DN.

[0497] In other examples, the verification network element can be a different network element from the destination network element. If, based on S376 above, the verification network element determines that signature information #1 is valid, then the verification network element can indicate to the destination network element that signature information #1 is valid. Further, the destination network element can forward the data #1.

[0498] In some examples, the verification network element can be implicitly instructed to verify signature information #1. For example, signature information #1 can implicitly instruct the verification network element to verify signature information #1. Based on signature information #1, the verification network element can determine how to obtain RAN#1 information from path information #1, thereby executing S376.

[0499] In other examples, the verification network element can be explicitly instructed to verify the signature information #1. In some possible implementations, the verification network element is a local network element, and method 300 further includes: RAN#2 sending indication information #1 to the verification network element. This indication information #1 can be used to instruct the verification network element to verify the signature information #1. For example, RAN#2 can send indication information #1 to the verification network element in S360.

[0500] In some other possible implementations, the verification network element is a different network element from the destination network element, and method 300 further includes: the destination network element sending indication information #1 to the verification network element. This indication information #1 can be used to instruct the verification network element to verify the signature information #1.

[0501] In other words, the aforementioned instruction information #1 can explicitly instruct the verification network element to verify the signature information #1. In other words, instruction information #1 can be information that has the function of "instructing the verification network element to verify the signature information #1". This application does not limit the specific form of instruction information #1. For example, instruction information #1 can be the aforementioned first instruction information or second instruction information.

[0502] The above, combining S372, S374, and S376, describes an example of the verification network element verifying the signature information #1 of RAN#1. In some possible implementations, each RAN node on the routing path of data #1 signs its path information based on its own key, thus obtaining the signature information of that RAN node.

[0503] Furthermore, in some possible implementations, each RAN node on the routing path of data #1 can send its path information and signature information to its next-hop node. In this way, the verification network element can obtain the path information and signature information of each RAN node on the routing path of data #1.

[0504] For example, the verification network element can be a local network element. In this way, the verification network element can obtain the path information and signature information of each RAN node on the routing path of data #1.

[0505] For example, the verification network element can be a different network element from the landing network element. The landing network element can obtain the path information and signature information of each RAN node on the routing path of data #1, and send the above path information and signature information to the verification network element.

[0506] In some possible implementations, the verification network element can be configured with a mapping between the information and public keys of each RAN node along the routing path. In this way, the verification network element can obtain the information of each RAN node from the path information of each RAN node along the routing path, and obtain the public key of each RAN node based on the aforementioned mapping. The verification network element can then verify the validity of the signature information of each RAN node based on the public key and the path information of each RAN node.

[0507] In some examples, the verification element can be a terminating element. If the verification element determines that the signature information of each RAN node on the routing path is valid, then the verification element can forward data #1. For example, the verification element can be a gateway station, which can forward data #1 to the terminating routing network. Another example is a UPF, which can forward data #1 to the DN.

[0508] In other examples, the verification network element can be a different network element from the destination network element. If the verification network element determines that the signature information of each RAN node on the routing path is valid, then the verification network element can indicate to the destination network element that the signature information of each RAN node is valid. Further, the destination network element can forward this data #1.

[0509] Based on the above scheme, the verification network element can verify the path information of RAN#1 deployed on the NTN device, thereby preventing the routing path from being tampered with, and thus improving the security of data transmission in the NTN scenario.

[0510] The following is an example of verifying the validity of network element verification path information.

[0511] In some possible implementations, after S360, method 300 also includes: S382.

[0512] S382, verify the information received by the network element from the first routing path.

[0513] The first routing path can be a routing path determined by the routing node controller. The information of this first routing path can include information about each node used to transmit data #1. See the description of the first routing path in Node Selection Example 1 for details; it will not be repeated here.

[0514] In some examples, the verification network element can receive information about the first routing path from the routing node controller.

[0515] In some possible implementations, method 300 may also include S380 before S382.

[0516] In step S380, RAN#1 sends a second message to the routing node controller. This second message instructs the routing node controller to send the first routing path information to the verification network element. Based on this second message, the routing node controller can then execute step S382, i.e., send the first routing path information to the verification network element.

[0517] Further, optionally, after receiving the information of the first routing path, the verification network element can send an acknowledgment (ACK) to the routing node controller. The routing node controller can then send an ACK to RAN#1. This ACK indicates that the verification network element has received the information of the first routing path.

[0518] Optionally, the routing node controller also sends the information of the destination network element #1 to the verification network element. This allows the verification network element to determine a correspondence between the information of the destination network element #1 and the information of the first routing path. After receiving the path information of each RAN node on the routing path of data #1, the verification network element can determine the information of the destination network element #1 based on the path information of each node, and determine that the routing path corresponding to the destination network element #1 is the first routing path. The path information of the last hop RAN node on the routing path of data #1 includes the information of the destination network element #1.

[0519] Optionally, the routing node controller also sends UE information to the verification network element, such as the TEID, session ID, or UE identifier from the UPF side. This allows the verification network element to determine a correspondence between the UE information and the information of the first routing path. After receiving the path information of each RAN node on the routing path of data #1, the verification network element can determine that the corresponding routing path is the first routing path based on the UE information (e.g., the path information carried in the UE's next-hop node).

[0520] As an example, RAN#1 can execute S380 after performing S342, i.e., determining the first routing path to use. In other words, after determining the first routing path configured by the routing node controller, RAN#1 can instruct the routing node controller to indicate the first routing path to the verification network element.

[0521] As another example, RAN#1 can execute S380 after executing S344, that is, determining that the next-hop node is RAN#2. In other words, after determining that the next-hop node is RAN#2 configured by the routing node controller, RAN#1 can instruct the routing node controller to indicate the complete routing path corresponding to RAN#2 to the verification network element.

[0522] Optionally, the second information sent by RAN#1 to the routing node controller in S380 includes the identifier of the first routing path. This identifier of the first routing path may be carried in the first configuration information sent by the routing node controller to RAN#1 in S310. Based on this identifier of the first routing path, the routing node controller can execute S382, that is, send the information of the first routing path to the verification network element.

[0523] Based on the above scheme, RAN#1 can instruct the routing node controller to send the first routing path information to the verification network element. In this way, the verification network element can obtain the complete routing path information determined by the routing node controller (i.e., the information of the first routing path), thereby enhancing the security strength of the verification path information. For example, if the verification network element concatenates multiple path information received on the routing path of data #1 into a complete routing path, it might fail to detect the tampering if multiple consecutive nodes (e.g., four consecutive nodes) jointly tamper with the path information. However, based on the above scheme, the verification network element can use the first routing path information sent by the routing node controller to compare with the concatenated complete routing path information, thereby detecting whether the routing path has been tampered with.

[0524] In other examples, the verification element can receive information about the first routing path from the routing path.

[0525] In some possible implementations, method 300 may also include S381 before S382.

[0526] In step S381, RAN#1 sends the first routing path information to RAN#2. As an example, RAN#1 can execute S381 after executing S342, i.e., determining the first routing path to use. In other words, after determining the first routing path configured by the routing node controller, RAN#1 can send this first routing path information to its next-hop node (i.e., RAN#2). Furthermore, RAN#2 can send the first routing path information to its next-hop node until it reaches the final network element.

[0527] For example, the verification network element is the same as the destination network element. In this way, through the above example, the verification network element (i.e., the destination network element) can receive information from the first routing path from the routing path.

[0528] For example, the verification network element and the destination network element are different network elements. In this way, through the above example, after the destination network element receives the information of the first routing path from the routing path, it can send the information of the first routing path to the verification network element.

[0529] Optionally, the information of the first routing path sent from RAN#1 to RAN#2 is securely protected. For example, the security protection may include encryption and / or integrity protection.

[0530] Based on the above scheme, RAN#1 can transmit the information of the first routing path to the next-hop node. In this way, the verification network element can obtain the complete routing path information determined by the routing node controller (i.e., the information of the first routing path), thereby enhancing the security strength of the verification path information. For example, if the verification network element concatenates multiple path information received on the routing path of data #1 into complete routing path information, it may be unable to detect the tampering if multiple consecutive nodes (e.g., four consecutive nodes) jointly tamper with the path information. However, based on the above scheme, the verification network element can use the information of the first routing path received from the routing path (i.e., through the second node) to compare with the concatenated complete routing path information, thereby detecting whether the routing path has been tampered with.

[0531] In some possible implementations, after S382, method 300 also includes: S386.

[0532] S386, the verification network element verifies the validity of path information #1 based on the information of the first routing path. For example, the verification network element can compare the information of the first routing path with path information #1. If the information of the previous hop node and the next hop node of RAN#1 in the information of the first routing path are the same as the information of the previous hop node and the next hop node of RAN#1 in path information #1, then the verification network element can determine that path information #1 is valid.

[0533] If the information of the previous hop node of RAN#1 in the first routing path information is different from the information of the previous hop node of RAN#1 in the path information #1, or if the information of the next hop node of RAN#1 in the first routing path information is different from the information of the next hop node of RAN#1 in the path information #1, then the verification network element can determine that the routing path has been tampered with.

[0534] Furthermore, the verification network element can report the nodes corresponding to the content in path information #1 that differs from the information in the first routing path to the routing node controller. The routing node controller can mark the reported nodes as untrusted nodes. The routing node controller can then avoid selecting these untrusted nodes when planning subsequent routing paths. In addition, the routing node controller can update the first routing path, thereby avoiding the presence of nodes on the first routing path that are easily tampered with.

[0535] In some possible implementations, method 300 may also include S384 prior to S386.

[0536] S384, the verification network element determines the information of the second routing path based on the path information of each node transmitting data #1.

[0537] The second routing path information includes information about each node involved in transmitting data #1. For example, the verification network element can receive the path information of each node. The path information of a node can include information about its previous hop, the node itself, and its next hop. Thus, the verification network element can construct the information of each node involved in transmitting data #1—that is, the second routing path information—based on the path information of each node.

[0538] For example, the second routing path can be understood as the actual routing path for data #1. Each node on the second routing path can transmit data #1 in a timely manner.

[0539] In some possible implementations, S386 includes: verifying the consistency between the second routing path and the first routing path using the verification network element.

[0540] In other words, the verification network element can verify the consistency between the actual routing path of data #1 and the planned routing path of data #1. For example, the verification network element can compare the information of the second routing path with the information of the first routing path. If the information of the second routing path is the same as that of the first routing path, the verification network element can determine that the information of the second routing path is valid.

[0541] If the information of the second routing path is different from that of the first routing path, the verification network element can determine that the routing path has been tampered with.

[0542] In some scenarios, the routing path for data #1 requires location restrictions; that is, the node processing data #1 needs to be located at the position indicated by the first location information. In the above scenario, the verification network element can verify whether the node processing data #1 is at the position indicated by the first location information. For ease of understanding, an example of the verification network element verifying time information is given below.

[0543] For example, path information #1 may also include: time information #1 for RAN #1 processing data #1. A detailed description of time information #1 is given in the relevant description of S350, and will not be repeated here. In some possible implementations, method 300 also includes: S394.

[0544] S394, based on time information #1, verify whether RAN#1 is located at the position indicated by the first position information when processing data #1.

[0545] If the verification network element determines that RAN#1 is located at the position indicated by the first location information when processing data #1, and if the verification network element is a terminating network element, it can forward data #1. For example, the verification network element can be a gateway station, which can forward data #1 to the terrestrial routing network. Another example is a UPF, which can forward data #1 to the DN. If the verification network element is a different network element from the terminating network element, it can indicate to the terminating network element that RAN#1 meets the location restrictions when processing data #1.

[0546] If the verification network element determines that RAN#1 is not located at the position indicated by the first location information when processing data #1, the verification network element can directly or indirectly send the information of RAN#1 to each node. When subsequently selecting a node to process the data, each node may choose not to select RAN#1.

[0547] In some possible implementations, each RAN node on the routing path of data #1 can send its path information to its next-hop node. In this way, the verification network element can obtain the path information of each RAN node on the routing path of data #1.

[0548] For example, the verification network element can be a local network element. In this way, the verification network element can obtain the path information of each RAN node on the routing path of data #1.

[0549] For example, the verification network element can be a different network element from the destination network element. The destination network element can obtain the path information of each RAN node on the routing path of data #1 and send the above path information to the verification network element.

[0550] As an example, the path information of each RAN node mentioned above may include the time information of when the RAN node processes data #1.

[0551] In some possible implementations, the verification network element can verify whether each RAN node is at the position indicated by the first position information when processing data #1, based on the time information of each RAN node processing data #1.

[0552] In some examples, the verification element can be a terrestrial element. If the verification element determines that each RAN node on the routing path is located at the position indicated by the first location information when processing data #1, then the verification element can forward data #1. For example, the verification element can be a gateway station, which can forward data #1 to the terrestrial routing network. Another example is a UPF, which can forward data #1 to the DN.

[0553] In other examples, the verification network element can be a different network element from the destination network element. If the verification network element determines that each RAN node on the routing path is located at the position indicated by the first location information when processing data #1, the verification network element can indicate to the destination network element that the time information of each RAN node is valid. Furthermore, the destination network element can forward the data #1.

[0554] If a RAN node on the routing path is processing data #1 at a location not indicated by the first location information, the verification network element can directly or indirectly send information about that RAN node to each node. When subsequently selecting a node to process the data, each node may choose not to select that RAN node.

[0555] Based on the above scheme, the verification network element can verify the position of RAN#1 when it processes data #1 based on time information #1. In this way, if RAN#1 does not meet the position restriction requirements, the above situation can be detected and corresponding actions can be taken.

[0556] In some possible implementations, S394 includes: S394a, the verification network element obtains second location information based on time information #1; S394b, the verification network element determines whether RAN#1 is located at the position indicated by the first location information when processing data #1 based on the second location information and the first location information.

[0557] As an example, the second location information can be used to indicate the location of RAN#1 at the time indicated by time information #1. For example, the location indicated by the first location information could be a country, region, or PLMN, etc.

[0558] In some possible implementations, S394a includes: S394a1, the verification network element sends a request message (denoted as request message #1) to the second network element, the request message #1 being used to request the location of RAN#1 at the time indicated by time information #1; S394a2, the verification network element receives a response message (denoted as response message #1) from the second network element, the response message #1 including second location information.

[0559] The second network element can be used to store or manage ephemeris information. Optionally, the second network element is used to predict the motion trajectory of the NTN device. Unless otherwise specified, the second network element in this application can be a communication device (e.g., a core network device or a third-party device), a component in the communication device (e.g., a processor, chip, or chip system), or a logic module or software that can implement some or all of the functions of the communication device.

[0560] The second network element can also be called an ephemeris information node or other names. For ease of understanding, this application refers to the second network element as an ephemeris information node.

[0561] As an example, request message #1 may include time information #1. The ephemeris information node can determine the second location information based on the time information #1 and the ephemeris information. For example, the ephemeris information node can query the location of RAN#1 under the time information #1 from the ephemeris information stored or retrieved by the ephemeris information node, thereby obtaining the second location information. The ephemeris information node can send response message #1 to the verification network element, and this response message #1 may carry the aforementioned second location information.

[0562] In some examples, the above request message #1 also includes the identifier of RAN#1. This identifier can be either the RAN#1 ID or the ID of the first NTN device. The first NTN device is the NTN device deployed on RAN#1. In this way, the ephemeris information node can query the ephemeris information of RAN#1 based on the identifier of RAN#1. The following describes how the verification network element obtains the identifier of RAN#1.

[0563] In some possible implementations, method 300 also includes S390 and S392 before S394a1.

[0564] S390, the network element receives the second configuration information. This second configuration information can be used to configure the mapping relationship between the address information and the identifier of RAN#1 (denoted as mapping relationship #3). For example, the address information of RAN#1 can be the RAN#1 IP address, and there is a mapping relationship #3 between the RAN#1 IP address and the RAN#1 ID. As another example, the address information of RAN#1 can be the IP address of the first NTN device, and there is a mapping relationship #3 between the first NTN device IP address and the first NTN device ID.

[0565] For example, in S390, the verification network element can receive the second configuration information from the core network element or the network element on the NTN device.

[0566] S392, the verification network element determines the identifier of RAN#1 based on the address information of mapping relationship #3 and RAN#1.

[0567] For example, the verification network element can obtain path information #1 in S372, and the information of RAN#1 in the path information #1 can be the address information of RAN#1.

[0568] In some other possible implementations, the verification network element can obtain path information #1 in S372, where the RAN#1 information in path information #1 can be the identifier of RAN#1. In this way, the verification network element can carry the identifier of RAN#1 in request message #1.

[0569] In other examples, the aforementioned request message #1 also includes the address information of RAN#1. Thus, the ephemeris information node can query the ephemeris information of RAN#1 based on the address information of RAN#1; or, the ephemeris information node can determine the identifier of RAN#1 based on the address information of RAN#1 and mapping relationship #3, and then query the ephemeris information of RAN#1 based on the identifier of RAN#1. As an example, the ephemeris information node can obtain mapping relationship #3 from core network elements or network elements on NTN devices.

[0570] In some possible implementations, the verification network element can obtain path information #1 in S372, and the information of RAN#1 in path information #1 can be the address information of RAN#1.

[0571] In some other possible implementations, the verification network element can obtain path information #1 in S372, where the RAN#1 information in path information #1 can be the identifier of RAN#1. The verification network element can obtain mapping relationship #3 in S390, and based on mapping relationship #3 and the identifier of RAN#1, determine the address information of RAN#1, thereby carrying the address information of RAN#1 in request message #1.

[0572] The above examples illustrate how a verification network element verifies signature information, path information, and time information. It's understood that a verification network element can perform at least one of these three verifications. For example, a verification network element can verify both signature and path information; if both are valid, the verification passes. Specifically, if the verification network element is a terminating network element, it can forward data #1. For instance, the verification network element could be a gateway station, which can forward data #1 to the terrestrial routing network. Another example is a UPF, which can forward data #1 to the DN. If the verification network element is different from the terminating network element, it can instruct the terminating network element that RAN #1 satisfies location restrictions when processing data #1.

[0573] If the verification network element is not the destination network element, the verification network element can indicate to the destination network element that the signature information and path information are valid.

[0574] Figure 4 This is a schematic flowchart of another communication method 400 provided in an embodiment of this application. Optional operations in method 400 are shown in dashed lines. Method 400 can be combined with method 300. The following describes the process in conjunction with... Figure 4 An example illustrating how a UE obtains its first address information.

[0575] S410, UE completes the authentication and registration process.

[0576] S420, the UE sends a PDU session establishment request to the SMF. Correspondingly, the SMF receives the PDU session establishment request from the UE.

[0577] S430, SMF determines that the path information of the UE's data needs to be securely signed, and / or that the routing path of the UE's data needs to be location-restricted.

[0578] The above S430 can also be understood as the SMF determining to use policy #1 to protect the data transmitted by the UE, or to use policy #2 to protect the data transmitted by the UE, or to use policy #3 to protect the data transmitted by the UE. Policy #1 may indicate that the path information of the data transmitted by the UE needs to be securely signed. Policy #2 may indicate that the path information of the data transmitted by the UE needs to be securely signed, and that the routing path of the data transmitted by the UE needs to be location-restricted.

[0579] Regarding how to trigger SMF to execute S430, several methods are introduced below, referred to as judgment method 1 to judgment method 4 respectively.

[0580] Judgment Method 1: SMF can determine policy #0, policy #1, policy #2 or policy #3 based on the location of the UE, the location indicated by the UE, or the location of the landing network element to which the data sent by the UE arrives.

[0581] For example, a PDU session establishment request may include the location of the UE.

[0582] For example, a UE can send a PDU session establishment request to the SMF through a RAN node. The RAN node can determine the location of the UE based on its coverage area and report the location of the UE to the SMF.

[0583] For example, if the network side locates the UE, the SMF can obtain the UE's location from core network elements such as the LMF.

[0584] For example, a PDU session establishment request may include the UE's identifier. The SMF can then obtain the UE's indicated location from the UDM based on this UE identifier.

[0585] For example, a landing network element can be a gateway station. SMF can obtain the location of the gateway station determined by the UE in S410.

[0586] For a detailed description of judgment method 1, please refer to the content of RAN#1 in trigger example 1, which determines the security policy (or policy) based on the first location information (i.e., the location of the UE, the location indicated by the UE, or the location of the landing network element). The difference is that in judgment method 1, the subject determining the UE's security policy is the SMF.

[0587] In other words, SMF can determine the security policy to use based on the above correspondence between location and security policy.

[0588] Method 1 can implement location-based configuration strategies, which can meet data supervision requirements and avoid redundant configuration.

[0589] Method 2: The SMF can obtain the UE's subscription data from the UDM. This subscription data can indicate the security policy. In other words, the SMF can determine whether to use policy #0, policy #1, policy #2, or policy #3 based on the content of the subscription data.

[0590] For example, SMF can retrieve or update subscription data through subscription retrieval or subscription for updates. The subscription data in this application may also be referred to as subscription data or other names.

[0591] For example, a PDU session establishment request may include the UE's identifier. The SMF can then retrieve the UE's subscription data from the UDM based on this UE identifier.

[0592] In some examples, the UE's subscription data can indicate the use of policy #1, policy #2, or policy #3 in an NTN scenario. Thus, the SMF can determine whether to use policy #1, policy #2, or policy #3 if it determines that the data transmitted by the UE needs to be forwarded by one or more on-board RAN nodes. Alternatively, the SMF can determine whether to use policy #1, policy #2, or policy #3 and determine indication information #3. This indication information #3 can be carried in a subsequent message sent to the UE (e.g., a PDU session establishment accept message). This indication information #3 can be used to instruct the UE to use the address information corresponding to policy #1, policy #2, or policy #3 in an NTN scenario.

[0593] Method 2 can enable UE-level policy configuration, thereby meeting the security requirements of different UEs.

[0594] Method 3: The SMF can obtain the service type of the UE's data, as well as the mapping relationship between the specific service type and policy #1 (or policy #2, or policy #3). In this way, the SMF can determine whether the UE's data service type belongs to the aforementioned specific service type, and the SMF can determine the service for that specific service type of the UE and allocate the address information corresponding to that policy.

[0595] For example, a PDU session establishment request may include a business type.

[0596] SMF can obtain the mapping relationship between service types and policies of UE data from UDM.

[0597] As an example, service type #1 corresponds to policy #1. The SMF can allocate address information #1 to the UE, and this address information #1 corresponds to policy #1. Thus, when the UE transmits data of service type #1, address information #1 can be used as the UE's address information. RAN #1 can determine the use of policy #1 based on address information #1, that is, to perform a secure signature on the path information of the data.

[0598] As another example, service type #2 corresponds to policy #2. The SMF can assign address information #2 to the UE, which corresponds to policy #2. Thus, when the UE transmits data of service type #2, address information #2 can be used as the UE's address information. RAN #2 can determine the use of policy #2 based on address information #2, that is, to securely sign the path information of the data and restrict the location of the nodes processing the data.

[0599] Method 3 allows for policy configuration at the business level, thus meeting the security requirements of different business types. For example, for businesses with high security requirements, location restrictions can be imposed on the nodes processing that business data. As an example, businesses with high security requirements could include factory operations or power grid operations, and so on.

[0600] Judgment Method 4: The SMF can determine whether the NTN equipment network transmitting UE data has an ISL. If the NTN equipment network has an ISL, the SMF can determine policy #2 or policy #3.

[0601] In some examples, after receiving a PDU session establishment request from the UE, the RAN node (e.g., RAN#1) can send indication information #4 to the SMF. This indication information #4 indicates that the data sent by the UE is routed through the NTN device network, or in other words, that the data sent by the UE is in an NTN scenario. In this way, the SMF can determine that the data sent by the UE needs to be transmitted through the NTN device network. Furthermore, the SMF can determine whether the NTN device network accessed by the UE has an ISL (Independent Service Level).

[0602] The instruction information #4 can be carried in a PDU session establishment request or in other messages; this application is not limited to this. This instruction information #4 can be called an NTN instruction, satellite instruction, NTN ISL instruction, or other names.

[0603] In other examples, the PDU session establishment request sent by the UE to the SMF may carry the PLMN ID of the NTN device network. This PLMN ID can be the identifier of the NTN device network (i.e., the PLMN) to which the UE is accessing. The SMF can be configured with the PLMN ID of the NTN device network that has an ISL. In this way, the SMF can determine whether the PLMN ID reported by the UE belongs to the PLMN ID configured by the SMF.

[0604] As an example, if the PLMN ID reported by the UE belongs to the PLMN ID configured in the SMF, it can be determined that the NTN device network transmitting the UE's data has an ISL.

[0605] As an example, if the PLMN ID reported by the UE does not belong to the PLMN ID configured in the SMF, it can be determined that the NTN device network transmitting the UE's data does not have an ISL.

[0606] SMF can also determine whether the NTN device network transmitting UE data has ISL in other ways, which is not limited in this application.

[0607] In decision method 4, if the NTN device network has an ISL (Independent Service Level), either strategy #2 or strategy #3 can be determined. Compared to the scheme that imposes location restrictions on all NTN device networks, decision method 4 can make full use of the communication resources of NTN devices.

[0608] For S440, select UPF#1 for SMF.

[0609] For example, UPF#1 can be a verification network element. If the SMF determines that the path information of the data transmitted by the UE needs to be securely signed, the SMF can select UPF#1 that supports verification of the signature information. Optionally, the UPF#1 selected by the SMF can also support verification of the path information.

[0610] For example, UPF#1 and the verification network element can be different network elements. If the SMF determines that the path information of the data sent by the UE needs to be securely signed, the SMF can select UPF#1 and instruct UPF#1 to send the path information and signature information to the verification network element.

[0611] For example, UPF#1 can be a verification network element. If the SMF determines that the path information of the data transmitted by the UE needs to be location-restricted, the SMF can select UPF#1 that supports time information verification. Optionally, the UPF#1 selected by the SMF is located at the position indicated by the first location information.

[0612] For example, UPF#1 and the verification network element can be different network elements. If the SMF determines that the path information of the data transmitted by the UE needs to be securely signed, the SMF can select UPF#1 and instruct UPF#1 to send the path information (including time information) to the verification network element. Optionally, the UPF#1 selected by the SMF is located at the position indicated by the first location information.

[0613] S450, the SMF sends indication information #2 to the UPF#1. This indication information #2 can be used to determine first address information. Correspondingly, the UPF#1 receives the indication information #2 from the SMF. This first address information can be related to a policy.

[0614] For example, the first address information corresponding to policy #1 can indicate policy #1, that is, the first address information can indicate the secure signing of the data path information. As another example, the first address information corresponding to policy #2 can indicate policy #2, that is, the first address information can indicate the secure signing of the data path information and the location restriction of the data routing path.

[0615] In some possible implementations, the SMF can allocate first address information to the UE and carry this first address information in the indication information #2. In this way, the UPF#1 can determine the first address information based on the indication information #2.

[0616] In some other possible implementations, the SMF can send indication information #2 to the UPF#1, which instructs the UPF#1 to allocate address information corresponding to the policy. In this way, the UPF#1 can determine the address information corresponding to the policy based on indication information #2.

[0617] In the case of UPF#1 address allocation information, method 400 also includes S455.

[0618] S455, UPF#1 can indicate first address information to SMF. This first address information is the address information corresponding to the policy, determined by UPF#1 based on the indication of indication information #2.

[0619] In some examples, SMF and / or UPF#1 may be configured with at least one address information mapping to policy #1, and / or at least one address information mapping to policy #2.

[0620] At least one of the aforementioned address information can also be understood as an address range. For example, the address information corresponding to policy #1 can belong to address range #1; the address information corresponding to policy #2 can also belong to address range #1. If the address information in a data packet belongs to address range #1, it means that the path information of that data packet requires a secure signature. If the address information in a data packet belongs to address range #2, it means that the path information of that data packet requires a secure signature, and the routing path of that data packet needs to be location-restricted.

[0621] S460, the SMF sends a PDU session establishment accept message to the UE. Correspondingly, the UE receives the PDU session establishment accept message from the SMF.

[0622] The PDU session establishment acceptance message may include first address information. The PDU session establishment acceptance message may also be called the PDU session establishment completion message or other names.

[0623] S470, the UE and UPF#1 complete the data channel establishment.

[0624] For example, the aforementioned data channel could be a user plane (UP) data channel.

[0625] In some possible implementations, after the above method 400 is executed, the third information that the UE can send in S330 may be the first address information or a combination of information including the first address information, so that RAN#1 can determine the policy to be used based on the first address information.

[0626] In some examples, the UE can be configured with multiple address information. For instance, when the RAN node needs to securely sign the data path information, the UE can use the address information corresponding to policy #1. As another example, when the RAN node needs to restrict the location of the data routing path, the UE can use the address information corresponding to policy #3. Yet another example is when secure signing of the data path information is not required, the UE can use the address information corresponding to policy #0.

[0627] The “UE uses address information” can be understood as the address information that the UE carries in the data packets it sends to the RAN node.

[0628] Figure 5 This is a schematic flowchart of another communication method 500 provided in an embodiment of this application. Optional operations in method 500 are shown with dashed lines. Method 500 can be combined with methods 300 and 400. The following describes the process in conjunction with... Figure 5 This section provides an example of how to enable the UE to send the first indication information.

[0629] S510, the third network element (e.g., SMF) determines the third indication information.

[0630] The third indication information can be used to indicate the secure signing of the path information of the data, and / or the third indication information can be used to indicate that the routing node (or node) that processes the data is at the position indicated by the first location information.

[0631] Unless otherwise specified, the third network element in this application can be a communication device (e.g., core network equipment), a component within the communication device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing some or all of the functions of the communication device. For ease of description, the following description uses an SMF as an example of the third network element.

[0632] As an example, the path information of the data may include information about the routing node that processes the data, information about the previous hop node of the routing node, and information about the next hop node of the routing node.

[0633] S520, the SMF sends the third indication information to the UE. Correspondingly, the UE receives the third indication information from the SMF.

[0634] In this way, the UE can determine the first indication information based on the third indication information, and then send the first indication information to RAN#1 in S330.

[0635] As an example, the content indicated by the third indication information can be the same as the content indicated by the first indication information. For example, if the third indication information is used to indicate the secure signing of the path information of the data, then the first indication information can indicate the secure signing of the path information of data #1 (i.e., path information #1). As another example, if the third indication information is used to indicate the secure signing of the path information of the data and that the routing node processing the data is at the position indicated by the first location information, then the first indication information can indicate the secure signing of the path information of data #1 (i.e., path information #1) and that the node processing data #1 is at the position indicated by the first location information.

[0636] In some examples, the third instruction information may have the same form as the first instruction information. In other examples, the third instruction information and the first instruction information may have different forms, which is not limited in this application.

[0637] For example, the UE can obtain the aforementioned third indication information during the PDU session establishment process. For instance, the third indication information can be carried in the PDU session establishment accept message.

[0638] Based on the third indication information in the above scheme, the UE can be informed of the data security requirements. For example, the security requirement could be that the data path information needs to be securely signed. Another example is that the security requirement could be that the data path information needs to be securely signed, and that the data routing path needs to be location-restricted. In this way, the UE can indicate the above security requirements to the RAN, enabling the RAN to protect the security of data transmission.

[0639] In some possible implementations, S510 may include any of the following:

[0640] The third indication information is determined based on the location of the UE, the location indicated by the UE, or the location of the network element to which the data sent by the UE arrives. See judgment method 1 in S430 for details. For example, if the SMF determines to use policy #1, the third indication information may indicate that the path information of the data is securely signed. If the SMF determines to use policy #2, the third indication information may indicate that the path information of the data is securely signed, and that the routing node (or node) processing the data is located at the location indicated by the first location information.

[0641] • Based on the UE's subscription data, determine the third indication information. See judgment method 2 in S430 for details. For example, in the case of subscription data indication policy #1, the third indication information may indicate the secure signing of the data path information. In the case of subscription data indication policy #2, the third indication information may indicate the secure signing of the data path information and the location indicated by the first location information for the routing node (or node) processing the data.

[0642] • Based on the business type of the data, determine the third indication information. See judgment method 3 in S430 for details. Examples will not be repeated here.

[0643] • When the NTN device network has an inter-satellite link, third indication information is determined. The NTN device network can be used to transmit UE data. For example, when the NTN device network has an ISL, the third indication information can indicate the secure signature of the data path information and the location indicated by the first location information for the routing node (or node) processing the data. See determination method 4 in S430 for further details.

[0644] In some possible implementations, method 500 may further include S410 and / or S420 before S510. In some possible implementations, method 500 may further include S440 before S520. The descriptions of S410, S420, and S440 above are given in method 400 and will not be repeated here.

[0645] In some possible implementations, method 500 also includes S515 before S520.

[0646] S515, SMF obtains the UE's address information.

[0647] In some possible implementations, the UE's address information may be assigned by the SMF. In other possible implementations, the UE's address information may be obtained by the SMF from UPF#1. The aforementioned UE address information may be address information specific to the PDU session established for the UE. For example, the UE's address information may be the UE IP address.

[0648] In some examples, the address information of the UE described above can be the first address information in method 400. That is, method 400 and method 500 can be combined, and the UE can receive specific first address information and third indication information. The UE can choose to implicitly instruct RAN#1 to perform a secure signature on the path information of the data sent by the UE using the first address information, and / or to restrict the location of the routing path for processing the data; the UE can also explicitly instruct RAN#1 to perform a secure signature on the path information of the data sent by the UE using the first indication information based on the third indication information, and / or to restrict the location of the routing path for processing the data.

[0649] The UE may also use the first address information and the first indication information mentioned above to instruct RAN#1 to perform a secure signature on the path information of the data sent by the UE, and / or to impose location restrictions on the routing path for processing the data, which is not limited in this application.

[0650] In some examples, the UE's address information can be carried in the PDU session establishment accept message. That is, the PDU session establishment accept message can carry third-party indication information as well as the UE's address information.

[0651] In some possible implementations, after S520, method 500 also includes S470. The description of S470 is the same as that in method 400 and will not be repeated here.

[0652] Figure 6 This is a schematic flowchart of another communication method 600 provided in an embodiment of this application. Optional operations in method 600 are shown in dashed lines. Method 600 can be combined with method 300, method 400, or method 500. The following describes the process in conjunction with... Figure 6 This section provides an example of how a routing node controller determines the initial configuration information.

[0653] S620: The routing node controller determines the first routing path based on the information of the landing network element #1. The landing network element #1 can be the last hop node on this first routing path. The following describes how the routing node controller obtains the information of the landing network element #1.

[0654] In some examples, the information for the landing network element #1 can be reported by a RAN node (e.g., RAN#1) or a node such as an SMF. Taking RAN#1 as an example, RAN#1 can obtain the information for the landing network element #1 during the UE registration process or the PDU session establishment process, and then RAN#1 can report the information for the landing network element #1 to the routing node controller. For example, the landing network element #1 can be a gateway station, and the gateway station's information can be obtained during the UE registration process. Another example is that the landing network element #1 can be UPF#1, and the UPF#1's information can be obtained during the PDU session establishment process.

[0655] In other examples, the routing node controller can be a RAN node or an SMF node. Taking the SMF as an example, the SMF can obtain information about the landing network element #1 during the UE registration process or PDU session establishment process.

[0656] In some examples, the routing node controller determines the first routing path based on the information from RAN#1 and the information from the landing network element #1. The information from RAN#1 can be reported by the RAN, obtained by the routing node controller during PDU session establishment, or obtained through other means.

[0657] The following is an example of how the routing node controller determines the first routing path.

[0658] In some examples, the routing node controller can construct a first routing path using RAN#1 as the destination network element. For example, the information of this first routing path may include: RAN#1 IP address, RAN#2 IP address, ..., RAN#1 IP address.

[0659] As an example, the routing node controller can construct a first routing path based on ephemeris information so that each on-board node on the first routing path can be connected via ISL.

[0660] In some possible implementations, S620 includes: a routing node controller determining a first routing path based on information about the landing network element #1 and first location information. Nodes on the first routing path are located at the positions indicated by the first location information when processing data.

[0661] Here, "data" can be understood as data transmitted on the first routing path. For example, when data transmitted on other routing paths happens to pass through a node on the first routing path, that node may or may not be at the location indicated by the first location information; this application does not impose any limitations on this.

[0662] S630, the routing node controller sends first configuration information to RAN#1 on the first routing path. This first configuration information is used to configure the first routing path or to configure the next-hop node of RAN#1 on the first routing path.

[0663] The relevant content of S630 above can be found in S310 of method 300, and will not be repeated here.

[0664] S640, RAN#1 determines the first routing path or the next-hop node of RAN#1 based on the first configuration information.

[0665] The relevant content of S630 above can be found in S342 or S344 of method 300, and will not be repeated here.

[0666] In some possible implementations, RAN#1 can determine the first routing path or the next-hop node of RAN#1 based on the security policy or the first indication information sent by the UE. See S346 or S348 in method 300 for details, which will not be elaborated further.

[0667] Based on the above scheme, the routing node controller can plan a complete routing path and configure either the complete routing path for RAN#1 or the next-hop node for RAN#1 on the planned routing path. In an NTN scenario, some NTN devices may not be able to communicate with each other. Therefore, without the above scheme, RAN#1 might need to temporarily determine the next-hop node after receiving data. However, the temporarily determined next-hop node for RAN#1 may not be able to route the data to the destination network element through other NTN devices. The above scheme, by planning a complete routing path in advance, can avoid the situation where data cannot be routed to the destination network element, thereby reducing the data packet loss rate.

[0668] In some possible implementations, prior to S630, method 600 also includes S610.

[0669] S610, RAN#1 sends a first request message to the routing node controller. This first request message can be used to request the routing node controller to determine a routing path, or to request the routing node controller to determine the next-hop node for RAN#1 on the routing path.

[0670] For example, the first request information is used to request the routing node controller to determine a routing path. S630 may include: in response to the first request information, the routing node controller sends first configuration information to RAN#1, which is used to configure the first routing path.

[0671] For example, the first request information is used to request the routing node controller to determine the next-hop node of RAN#1 on the routing path. S630 may include: in response to the first request information, the routing node controller sends first configuration information to RAN#1, which is used to configure the next-hop node of RAN#1 on the first routing path (denoted as RAN#2).

[0672] Understandably, S610 can be an optional operation. For example, after determining the first routing path, the routing node controller can proactively send the first configuration information to RAN#1 without requiring a request from RAN#1.

[0673] In some possible implementations, the first request information may include at least one of the following:

[0674] • Information about the landing network element #1;

[0675] Information for RAN#1;

[0676] • Security routing requirements / policy information;

[0677] • First location information;

[0678] • Fourth indication information. For example, this fourth indication information can be used to indicate that the node processing data #1 is at the position indicated by the first position information.

[0679] For example, policy information may indicate one or more of policies #0 to #4, or one or more of policies #a to #c. Secure routing requirements may include whether path information is signed, and / or whether location restrictions are imposed on the nodes processing the data.

[0680] As an example, RAN#1 can establish a PDU session and / or perform a registration procedure with other UEs (denoted as UE#2) before establishing a PDU session and / or performing a registration procedure with the UE (denoted as UE#1) in method 600. Here, the location information of both UE#1 and UE#2 is first location information, and the landing network element is landing network element #1. Thus, RAN#1 can obtain information about landing network element #1 during the process of establishing a PDU session and / or performing a registration procedure with UE#2. Unless otherwise specified, the UE in this application refers to the aforementioned UE#1, which will not be described again hereafter.

[0681] For example, if RAN#1 requests a routing path corresponding to policy #0 or policy #1, or if the routing path requested by RAN#1 has no location restrictions, then RAN#1 may omit the first location information and the fourth indication information from its first request information. In this way, the routing node controller can plan the routing path without considering the first location information.

[0682] For example, if RAN#1 requests the routing path corresponding to policy #2, or if the routing path requested by RAN#1 has location restrictions, then RAN#1 can carry the first location information and / or the fourth indication information in the first request information.

[0683] As an example, the first request information includes first location information, or the first request information includes first location information and fourth indication information. The routing node controller can determine a location-restricted routing path based on the first location information, or in response to the fourth indication information and thus based on the first location information. Nodes on this location-restricted routing path are located at the positions indicated by the first location information when processing data.

[0684] As another example, the first request information includes fourth indication information. In response to the fourth indication information, the routing node controller can obtain first location information from RAN#1, SMF, or other network elements, or obtain first location information cached by the routing node controller, and thus determine a location-restricted routing path based on the first location information.

[0685] In the example above, if the first request information carries the fourth indication information, it indicates that the node processing data #1 needs to be at the position indicated by the first location information. In other words, if the first request information does not carry the fourth indication information, it indicates that the node processing data #1 may or may not be at the position indicated by the first location information. That is to say, the first request information can indicate whether the node processing data #1 needs to be at the position indicated by the first location information by whether or not it carries the fourth indication information.

[0686] In other examples, the fourth indication information can indicate whether the node processing data #1 is located at the position indicated by the first location information. That is, the first request information can use the content of the fourth indication information to indicate whether the node processing data #1 needs to be at the position indicated by the first location information. For example, assuming the fourth indication information indicates that the node processing data #1 does not need to be at the position indicated by the first location information, then regardless of whether RAN #1 sends the first location information, or whether the routing node controller has the first location information, the routing node controller can plan the route without location restrictions. In other words, the routing node controller can disregard the first location information when determining the first route.

[0687] In other examples, the first request information carries a fourth indication, instructing the routing node controller to distribute path #1 (where the node does not need to be at the location indicated by the first location information) and path #2 (where the node is at the location indicated by the first location information). Thus, the routing node controller can distribute path #1 and path #2 to RAN #1 based on the fourth indication. The first routing path can be either path #1 or path #2.

[0688] In other examples, if the first request information does not carry the fourth indication information, then the routing node controller is instructed to issue path #1 where the node does not need to be at the location indicated by the first location information, and path #2 where the node is at the location indicated by the first location information. Here, the first routing path can be either path #1 or path #2. If the first request information carries the fourth indication information, and the fourth indication information indicates that the node processing data #1 does not need to be at the location indicated by the first location information, the routing node controller issues path #1 (considered the first routing path). If the first request information carries the fourth indication information, and the fourth indication information indicates that the node processing data #1 is at the location indicated by the first location information, the routing node controller issues path #2 (considered the first routing path).

[0689] In other possible implementations, the routing node controller may obtain the information of the aforementioned landing network element #1, RAN #1, first location information, or fourth indication information through other means. For example, the routing node controller may receive at least one of the following from the SMF: information of the landing network element #1, RAN #1, first location information, or fourth indication information.

[0690] For example, the first location information can indicate the location of the UE. The routing node controller can obtain the location of RAN#1 from the ephemeris information node based on the information of RAN#1 (e.g., the IP address of RAN#1). This location of RAN#1 can be understood as the location of the UE, and thus as the first location information. That is, in the example above, the routing node controller can obtain the first location information from the ephemeris information node. As an example, after receiving the first request information, the routing node controller can obtain the location of RAN#1 from the ephemeris information node. Thus, the location of RAN#1 can be understood as the location of RAN#1 when it sent the first request information, or, in other words, the location of RAN#1 a short period of time after it sent the first request information.

[0691] For example, the routing node controller can obtain the information of RAN#1 and the information of the landing network element #1 during the PDU session establishment process or UE registration process, and associate the information of RAN#1 with the information of the landing network element #1.

[0692] In some possible implementations, the routing node controller can interact with RAN#1 through a 3GPP network element (e.g., SMF). This 3GPP network element can then obtain information about RAN#1 and the destination network element #1 during the interaction between the routing node controller and RAN#1. The 3GPP network element can send a first request message to the routing node controller, requesting the routing node controller to issue a routing path to RAN#1, or requesting the routing node controller to issue the next-hop node of RAN#1 on the routing path. As an example, the first request message may include information about RAN#1 and the destination network element #1.

[0693] In some possible implementations, method 600 further includes: S380, the routing node controller receives second information from RAN#1; in response to the second information, the routing node controller sends information about the first routing path to the verification network element. See the description of S380 in method 300 for details, which will not be repeated here.

[0694] Figure 7 This is a schematic flowchart of a communication method 700 provided in an embodiment of this application. Method 700 can be considered as a specific example of a combination of method 600 and method 300. In method 700, RAN#1 can determine whether to perform a secure signature on the path information based on location information. Optionally, RAN#1 can also determine whether to select a routing path with location restrictions based on location information. The configuration of nodes involved in method 700 is described below.

[0695] As an example, RAN#1 can be configured with policy #0, policy #1, and policy #2. Furthermore, RAN#1 can also be configured with a mapping between security policies and locations. For ease of understanding, assume policy #0 corresponds to location #0, policy #1 corresponds to location #1, and policy #2 corresponds to location #2.

[0696] For example, the above information for RAN#1 can be configured by PCF, SMF or other network elements.

[0697] As an example, the routing node controller can be configured with a mapping relationship between node address information (e.g., IP address) and node ID. The nodes can include RAN nodes and / or the NTN devices where the RAN nodes reside. For example, the mapping relationship could be between the IP address of RAN#1 and the ID of the first NTN device deployed on RAN#1. Based on the mapping relationship and the node address information, the routing node controller can determine the node ID and obtain the node's location information from the ephemeris information node based on the node ID, thereby determining whether the node's location meets location restrictions or whether the node can communicate with other nodes (i.e., has an ISL).

[0698] For example, the above information of the routing node controller can be configured by core network elements or network elements on NTN devices.

[0699] As an example, the verification network element and the landing network element can be a UPF#1. This UPF#1 can be configured with a mapping relationship between the public key of the satellite node and the satellite node's information (e.g., address information). For instance, the UPF#1 can be configured with the satellite node's certificate information, which may include the RAN node's public key and the RAN node's address information (e.g., IP address), thereby indicating the mapping relationship between the public key and the address information.

[0700] For example, the above information for UPF#1 can be configured by core network elements, third-party certificate repositories, or other network elements.

[0701] Optionally, UPF#1 is also configured with a mapping relationship between the public key of the ground network element and the address information (e.g., IP address) of the ground network element.

[0702] Optionally, UPF#1 is also configured with a mapping relationship between node address information (e.g., IP address) and node ID. For details on the meaning and configuration method, please refer to the description of configuring the above information in the routing node controller above, which will not be repeated here.

[0703] The following is combined with Figure 7 This section introduces the various operations of method 700.

[0704] S710, the routing node controller configures the routing path for UPF#1.

[0705] The above configuration method can also be understood as the routing node controller configuring routing paths per UPF. As an example, the routing node controller can configure two types of routing paths, denoted as path #1 and path #2. Path #1 can be a routing path without location restrictions. Path #2 can be a routing path with location restrictions, meaning that the node on path #2 is located at the position indicated by the location information when processing data. Both path #1 and path #2 correspond to UPF #1. UPF #1 is the last hop of both path #1 and path #2.

[0706] In some examples, in S710, the routing node controller and RAN#1 can execute method 600 to configure the routing path. Here, path #1 can also be understood as the routing path corresponding to policy #1 or policy #0, and path #2 can also be understood as the routing path corresponding to policy #2. The first routing path in method 600 can be either path #1 or path #2. The first configuration information in method 600 can be understood as being used to configure path #1 and / or path #2.

[0707] S720, the UE and network elements such as UPF#1 complete the PDU session establishment process.

[0708] As an example, the above S710 can be executed before, during, or after the PDU session establishment process. In other words, the execution order of S710 and S720 is not limited, and they can also be executed as a single step.

[0709] S730, RAN#1 receives data #1 from UE.

[0710] As an example, the description of S730 can be found in S320 of method 300, and will not be repeated here.

[0711] S740, RAN#1 determines the security policy based on the first location information.

[0712] For example, if the first location information indicates location #0, then RAN#1 can determine strategy #0. If the first location information indicates location #1, then RAN#1 can determine strategy #1. If the first location information indicates location #2, then RAN#1 can determine strategy #2.

[0713] As an example, other details of S740 are described in S335 and will not be repeated here.

[0714] S750, RAN#1 sends data #1 to RAN#2.

[0715] As an example, RAN#1 can perform DRB mapping based on data #1 to obtain the UPF#1 IP address and TEID. RAN#1 can also send the TEID to RAN#2.

[0716] In some examples, if RAN#1 determines policy #0 in S740, then RAN#1 may not need to perform a security signature. In some possible implementations, RAN#1 may select path #1 from one or more paths configured for RAN#1 based on the UPF#1 IP address and policy #0. See, for example, S342 and S346.

[0717] In other examples, if RAN#1 determines policy #1 in S740, then RAN#1 can perform a secure signature. In this way, RAN#1 can also send path information #1 and signature information #1 to RAN#2, as detailed in S340 and S350. In some possible implementations, RAN#1 can select path #1 from one or more paths configured by RAN#1 based on the UPF#1 IP address and policy #1. See, for example, S342 and S346.

[0718] In some further examples, if RAN#1 determines policy #2 in S740, then RAN#1 can perform a secure signature. In this way, RAN#1 can also send path information #1 and signature information #1 to RAN#2, as detailed in S340 and S350. In some possible implementations, RAN#1 can select path #2 from one or more paths configured by RAN#1 based on the UPF#1 IP address and policy #2. See, for example, S342 and S346.

[0719] In some possible implementations, RAN#1 also sends information about the first routing path to RAN#2. For example, the routing node controller might configure the first routing path only for RAN#1 on the first routing path. In this way, RAN#2 can receive the information about the first routing path from RAN#1, thereby determining the next-hop node for RAN#2.

[0720] Other details of S750 can be found in S330 and S335, and will not be repeated here.

[0721] Taking the RAN node information as an example where the IP address is used, the above path information #1 can be represented as: (UE IP address, RAN#1 IP address, RAN#2 IP address). The above signature information #1 can be represented as: sign(UE IP address, RAN#1 IP address, RAN#2 IP address).

[0722] S760, RAN#2 sends data #1 to UPF#1.

[0723] In some examples, if RAN#1 determines policy #1 or policy #2 in S740, then RAN#2 and all subsequent RAN nodes also securely sign the path information of the corresponding RAN nodes. For example, the path information #i of RAN#i can be represented as: (IP address of the previous hop node of RAN#i, IP address of RAN#i, IP address of the next hop node of RAN#i). The signature information #i of RAN#i can be represented as: sign(IP address of the previous hop node of RAN#i, IP address of RAN#i, IP address of the next hop node of RAN#i).

[0724] Here, RAN#i is assumed to be the last-hop RAN node, and i is an integer greater than or equal to 2. This RAN#i can send data #1, path information #1 to path information #i, and signature information #1 to signature information #i to UPF#1.

[0725] Optionally, RAN#i also sends the first routing path to UPF#1. See S381 for details.

[0726] Optionally, RAN#i also sends indication information #1 to UPF#1. See the relevant description in S376 for details.

[0727] For further descriptions of S760 above, please refer to method 300 or method 400, which will not be repeated here.

[0728] S770, UPF#1 verifies signature information and / or path information.

[0729] For example, if RAN#i sends path information #1 to path information #i and signature information #1 to signature information #i to UPF#1, then UPF#1 can obtain the IP addresses of RAN#1 to RAN#i based on the path information of RAN#1 to RAN#i; obtain the public key of RAN#1 to RAN#i based on the IP addresses of RAN#1 to RAN#i and the aforementioned mapping relationship between IP addresses and public keys; and verify the validity of signature information #1 to signature information #i based on the public key of RAN#1 to RAN#i and the path information of RAN#1 to RAN#i.

[0730] For further details on the above examples, please refer to the descriptions in S372, S374, and S376, which will not be repeated here.

[0731] For example, if RAN#i sends path information #1 to path information #i to UPF#1, then UPF#1 can verify path information #1 to path information #i. As an example, UPF#1 can determine whether path information #1 to path information #i is consecutive.

[0732] For example, if RAN#1 executes S380 or S381 before S770, UPF#1 can obtain the first routing path based on the information of UPF#1, and verify the path information #1 to the path information #i based on the first routing path.

[0733] For further details on the above examples, please refer to the descriptions in S382, S384, and S386, which will not be repeated here.

[0734] Understandably, the IP address of each node in Method 700 can be replaced with the ID of each node or the ID of the NTN device where each node is located.

[0735] Furthermore, the verification network element in this application is not limited to UPF. For example, the verification network element in method 700 can be a network element different from UPF#1. After UPF#1 receives data #1, path information #1 to path information #i, and signature information #1 to signature information #i, it can send the path information #1 to path information #i and signature information #1 to signature information #i to the verification network element. The verification network element can perform the verification operation of UPF#1 in S770.

[0736] In some possible implementations, if another RAN (denoted as RAN#1') moves to the location of RAN#1, RAN#1' can determine the security policy to be used.

[0737] In some examples, RAN#1 can send the security policy determined by RAN#1 in S740 to RAN#1'. In other examples, RAN#1' can take the security policy determined by S740.

[0738] Figure 8 This is a schematic flowchart of another communication method 800 provided in this application embodiment. Method 800 can be regarded as a specific example of a combination of methods 600, 500 and 300. In method 800, RAN#1 can determine whether to perform a secure signature on the path information based on the first indication information sent by the UE. Optionally, RAN#1 also determines whether to select a routing path with location restrictions based on the first indication information. The configuration of the nodes involved in method 800 is described below.

[0739] As an example, RAN#1 can be configured with policy #0, policy #1, and policy #2. For instance, the above information for RAN#1 can be configured by PCF, SMF, or other network elements.

[0740] For the configuration of the routing node controller and the verification network element, please refer to method 700, which will not be repeated here.

[0741] Method 800 takes UPF#1 as an example when the verification network element and the landing network element are UPF#1. The following is combined with Figure 8 This section introduces the various operations of method 800.

[0742] S810, the routing node controller configures the routing path for UPF#1.

[0743] For details, please refer to S710, which will not be repeated here.

[0744] S820, the UE and network elements such as UPF#1 complete the PDU session establishment process.

[0745] For details, please refer to S720, which will not be elaborated further.

[0746] S830, the UE determines the first indication information.

[0747] For example, the UE can determine the first indication information based on method 500, which is detailed in method 500 and will not be repeated here.

[0748] S840, RAN#1 receives data #1 and first indication information from UE.

[0749] As an example, the description of S840 can be found in S320 and S330 of method 300, and will not be repeated here.

[0750] S850, RAN#1 sends data #1 and other information to RAN#2 based on the first instruction information.

[0751] As an example, RAN#1 can perform DRX mapping based on data #1 to obtain the UPF#1 IP address and TEID. RAN#1 can also send the TEID to RAN#2.

[0752] In some examples, if the first indication information indicates that a security signature is not required, then RAN#1 may not perform a security signature. In some possible implementations, RAN#1 may select path #1 from one or more paths configured for RAN#1 based on the UPF#1 IP address and the first indication information. See, for example, S342 and S348.

[0753] In other examples, if the first indication information indicates that secure signing is required and there are no location restrictions on the routing path for data #1, then RAN#1 can perform secure signing. In this case, RAN#1 can also send path information #1 and signature information #1 to RAN#2, as detailed in S340 and S350. In some possible implementations, RAN#1 can select path #1 from one or more paths configured in RAN#1 based on the UPF#1 IP address and the first indication information. See, for example, S342 and S348.

[0754] In some further examples, if the first indication information indicates that secure signing is required and there are location restrictions on the routing path of data #1, then RAN#1 can perform secure signing. In this way, RAN#1 can also send path information #1 and signature information #1 to RAN#2, as detailed in S340 and S350. In some possible implementations, RAN#1 can select path #2 from one or more paths configured in RAN#1 based on the UPF#1 IP address and the first indication information. For example, see S342 and S348.

[0755] In some possible implementations, RAN#1 also sends information about the first routing path to RAN#2. For example, the routing node controller might configure the first routing path only for RAN#1 on the first routing path. In this way, RAN#2 can receive the information about the first routing path from RAN#1, thereby determining the next-hop node for RAN#2.

[0756] Other details regarding S850 can be found in the corresponding description of trigger example 2, and will not be repeated here.

[0757] Taking the RAN node information as an example where the IP address is used, the above path information #1 can be represented as: (UE IP address, RAN#1 IP address, RAN#2 IP address). The above signature information #1 can be represented as: sign(UE IP address, RAN#1 IP address, RAN#2 IP address).

[0758] S860, RAN#2 sends data #1 to UPF#1.

[0759] The difference between S860 and S760 is that in S870, a secure signature is triggered by a first instruction message. The content of the signature can be found in S760.

[0760] For further descriptions of S860 above, please refer to method 300 or method 400, which will not be repeated here.

[0761] S870, UPF#1 verifies the signature information and / or path information.

[0762] For details, please refer to S770, which will not be repeated here.

[0763] Figure 9 This is a schematic flowchart of a communication method 900 provided in an embodiment of this application. Method 900 can be considered as a specific example of a combination of methods 600, 400, and 300. In method 900, RAN#1 can determine whether to perform a secure signature on the path information based on the UE's address information. Optionally, RAN#1 can also determine whether to select a routing path with location restrictions based on the UE's address information.

[0764] As an example, RAN#1 can be configured with a mapping relationship between address information and security policies. For example, policy #0 corresponds to address information #0; policy #1 corresponds to address information #1; and policy #2 corresponds to address information #2.

[0765] For other configurations of RAN#1, routing node controller, and verification network element, please refer to Method 800, which will not be repeated here.

[0766] Method 900 takes UPF#1 as an example when the verification network element and the landing network element are both UPF#1. The following section combines... Figure 9This section introduces the various operations of method 900.

[0767] S910, the routing node controller configures the routing path for UPF#1.

[0768] For details, please refer to S810, which will not be repeated here.

[0769] S920, the UE and network elements such as UPF#1 complete the PDU session establishment process.

[0770] For details, please refer to S820, which will not be repeated here.

[0771] S930, RAN#1 receives data #1 and first address information from UE.

[0772] The first address information can be the UE's address information. The process by which the UE obtains the first address information is described in method 400 and will not be repeated here. Further descriptions of S930 are available in S320 of method 300 and will not be repeated here.

[0773] S940, RAN#1 determines the security policy based on the first address information.

[0774] For example, if the first address information is address information #0, then RAN#1 can determine policy #0. If the first address information is address information #1, then RAN#1 can determine policy #1. If the first address information is address information #2, then RAN#1 can determine policy #2.

[0775] As an example, other details of S940 are described in S335 and will not be repeated here.

[0776] S950, RAN#1 sends data #1 to RAN#2.

[0777] For details, please refer to S750, which will not be elaborated further.

[0778] S960, RAN#2 sends data #1 to UPF#1.

[0779] For details, please refer to S760, which will not be elaborated further.

[0780] S970, UPF#1 verifies the signature information and / or path information.

[0781] For details, please refer to S770, which will not be repeated here.

[0782] Figure 10This is a schematic flowchart illustrating a communication method 1000 provided in an embodiment of this application. Method 1000 can be considered a specific example of method 300. In method 1000, the path information sent by RAN#1 can carry the time information of RAN#1 processing data #1. In this way, the verification network element can verify the time information.

[0783] S1010, the UE and network elements such as UPF#1 complete the PDU session establishment process.

[0784] S1020, the UE sends data #1 to RAN#1.

[0785] Optionally, the UE also sends its signature information #0 and path information #0 to RAN#1. The signature information #0 is obtained by the UE signing the path information #0 based on its key. The path information #0 may include information about the UE (e.g., the UE's IP address) and information about RAN#1 (e.g., the ID of the NTN device where RAN#1 is located).

[0786] S1030, RAN#1 determines whether to securely sign the path information and whether to select a next-hop node with location restrictions.

[0787] As an example, RAN#1 can determine the content to be determined in S1030 using the first location information, the first address information, or the first indication information. See S335 or S330 of method 300 for details. Furthermore, see methods 700, 800, and 900 respectively.

[0788] S1040, RAN#1 selects RAN#2 based on the UPF#1 IP address and ephemeris information.

[0789] As an example, RAN#1 can perform DRX mapping based on data #1 to obtain the UPF#1 IP address.

[0790] As an example, RAN#1 can obtain ephemeris information from the ephemeris information node. RAN#1 can also obtain ephemeris information stored within itself; this application does not limit this.

[0791] Understandably, in method 1000, RAN#1 may not have obtained a complete first routing path, or RAN#1 may have obtained a first routing path from the routing node controller but not used it. In such cases, RAN#1 may select RAN#2, which can communicate with RAN#1, based on ephemeris information.

[0792] In some examples, if RAN#1 determines in S1030 that the next-hop node has a location restriction, then RAN#1 can choose the RAN located at the position indicated by the first location information as RAN#2. If RAN#1 determines in S1030 that the next-hop node does not have a location restriction, then RAN#1 can choose the RAN located at the position indicated by the first location information as RAN#2, or it can choose the RAN not located at the position indicated by the first location information as RAN#2; this application does not limit this choice.

[0793] S1050, RAN#1 sends data #1 to RAN#2.

[0794] Optionally, if RAN#1 determines to securely sign the path information, RAN#1 also sends path information #1 and signature information #1 to RAN#2.

[0795] Optionally, if RAN#1 determines to select a next-hop node with location restrictions, the path information #1 sent by RAN#1 to RAN#2 also includes time information #1. Furthermore, the signature information #1 is obtained by RAN#1 through a secure signature of the path information #1, which includes the time information #1.

[0796] S1060, RAN#2 sends data #1 to UPF#1.

[0797] Optionally, if RAN#1 determines to securely sign the path information, RAN#2 and all subsequent RAN nodes also securely sign the path information of their respective RAN nodes. For example, the path information #i of RAN#i can be represented as: (IP address of the previous hop node of RAN#i, IP address of RAN#i, IP address of the next hop node of RAN#i). The signature information #i of RAN#i can be represented as: sign(IP address of the previous hop node of RAN#i, IP address of RAN#i, IP address of the next hop node of RAN#i).

[0798] Optionally, if RAN#1 determines to select a next-hop node with location restrictions, the path information of RAN#2 and all subsequent RAN nodes includes the time information of the corresponding RAN node processing data #1. For example, the path information #i of RAN#i can be represented as: (IP address of the previous hop node of RAN#i, IP address of RAN#i, IP address of the next hop node of RAN#i, time information #i). The signature information #i of RAN#i can be represented as: sign(IP address of the previous hop node of RAN#i, IP address of RAN#i, IP address of the next hop node of RAN#i, time information #i).

[0799] For further descriptions of S1060 above, please refer to method 300 or method 400, which will not be repeated here.

[0800] S1070, UPF#1 verifies the signature information and / or path information.

[0801] For details, please refer to S770, which will not be repeated here.

[0802] S1080, UPF#1 verifies the time information.

[0803] For example, if path information #1 to path information #i respectively carry time information #1 to time information #i, UPF#1 can extract time information #1 to time information #i from the path information #1 to path information #i respectively.

[0804] As an example, UPF#1 can extract (the IP address of RAN#1, time information #1) to (the IP address of RAN#i, time information #i). Furthermore, UPF#1 can obtain (the ID of the NTN device where RAN#1 is located, time information #1) to (the ID of the NTN device where RAN#i is located, time information #i) based on the mapping relationship between the IP address of the RAN node and the NTN device where the RAN node is located.

[0805] In some possible implementations, UPF#1 can send a request message #1 to the ephemeris information node. This request message #1 can carry the aforementioned (ID of the NTN device where RAN#1 is located, time information #1) to (ID of the NTN device where RAN#i is located, time information #i). Further, the ephemeris information node can determine (ID of the NTN device where RAN#1 is located, time information #1, location information #1) to (ID of the NTN device where RAN#i is located, time information #i, location information #i) based on (ID of the NTN device where RAN#1 is located, time information #1) to (ID of the NTN device where RAN#i is located, time information #i) and the ephemeris information. Here, location information #1 indicates the location of the NTN device where RAN#1 is located at the time indicated by time information #1, and so on, location information #i indicates the location of the NTN device where RAN#i is located at the time indicated by time information #i. The aforementioned location information #1 can also be understood as the second location information in method 300.

[0806] Furthermore, the ephemeris information node can send a response message #1 to UPF#1. This response message #1 can carry (the ID of the NTN device where RAN#1 is located, time information #1, and location information #1) to (the ID of the NTN device where RAN#i is located, time information #i, and location information #i). UPF#1 can verify whether the aforementioned location information #1 to location information #i is the location indicated by the first location information. If the aforementioned location information #1 to location information #i are all the locations indicated by the first location information, then UPF#1 can forward data #1 to the DN. For more details, please refer to the descriptions of S390, S392, and S394, which will not be repeated here.

[0807] This application does not limit the execution order of S1080 and S1070. Furthermore, S1080 and S1070 can both be executed, or only one of them can be executed; this application does not limit this.

[0808] In some possible implementations, method 1000 further includes: UPF#1 obtaining the location of the ground network element (e.g., a ground router) based on its IP address. UPF#1 can verify whether the location of the ground network element is the location indicated by the first location information. If the location of the ground network element is the location indicated by the first location information, then UPF#1 can forward data #1 to the DN. The above verification of the location of the ground network element and the location of the satellite node can both be performed, so that if the location information #1 to location information #i and the location of the ground network element are all the locations indicated by the first location information, UPF can forward data #1 to the DN.

[0809] The following, combined with Figures 11 to 14 This application provides a detailed description of the communication device provided in the embodiments. The descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, for content not described in detail, please refer to the above method embodiments. For the sake of brevity, some content will not be repeated.

[0810] This application embodiment can divide the communication device into functional modules according to the above method example. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing module. The integrated modules can be implemented in hardware, software, or a combination of both. The module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the division of functional modules according to each function as an example.

[0811] Figure 11 This is an exemplary block diagram of the communication device 10 provided in the embodiments of this application.

[0812] like Figure 11As shown, for example, the communication device 10 may include a chip system 110, a memory 120, a bus 130, a power management module 140, or a transceiver 150, etc.

[0813] The chip system 110 can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed through integrated logic circuits in the hardware of the chip system 110 or through software instructions.

[0814] By way of example and not limitation, chip system 110 may include circuitry or chips responsible for signal processing (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core).

[0815] Optionally, the chip system 110 may also include a memory (such as a cache) for storing instructions and data. In some embodiments, the memory in the chip system 110 is a cache memory. This memory can store instructions or data that the chip system 110 has just used or that are used repeatedly. If the chip system 110 needs to use the instruction or data again, it can retrieve it directly from this memory. This avoids repeated accesses, reduces the waiting time of the chip system 110, and thus improves the efficiency of the system.

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

[0817] The memory 120 may include random access memory (RAM) and read-only memory (ROM). The memory 120 may store computer-readable and computer-executable code, including instructions that, when executed, cause the processor to perform the various functions of this application.

[0818] Optionally, the code may include instructions for implementing various aspects of the embodiments of this application, such as instructions for performing secure signing. The code may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, the code may not be directly executable by the chip system 110, but may enable a computer (e.g., at compile and execution time) to perform the functions of this application. In some cases, memory 120 may contain a basic I / O system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0819] For example, the chip system 110 executes various functional applications and data processing of the communication device 10 by running instructions stored in the memory 120. For instance, when the communication device 10 transfers files with other devices (which may also be terminals or access network devices), the chip system 110 of the communication device 10 can call the computer-executable program code stored in the memory 120 to implement the communication method provided in the embodiments of this application.

[0820] In addition, the memory 120 can be integrated into the chip system 110 or independent of the chip system 110.

[0821] For example, bus 130 may be USB, used to support communication between various parts of communication device 10.

[0822] The power management module 140 is used to receive charging input from the charger. Optionally, the power management module 140 can also supply power to the communication device 10 while charging it (e.g., the battery module of the communication device 10). By way of example and not limitation, the power management module 140 can also supply power to other devices besides the communication device 10.

[0823] Transceiver 150 can communicate bidirectionally via one or more antennas, wired links, or wireless links. For example, transceiver 150 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 150 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and for demodulating packets received from the antenna. Transceiver 150 may include a receiver and a transmitter, the receiver performing the function of receiving information and the transmitter performing the function of transmitting information.

[0824] In some cases, a wireless device may include a single antenna. However, in other cases, a device may have more than one antenna, such as... Figure 11 Antennas 1 and 2 shown may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Exemplarily, antennas 1 and 2 are used to transmit and receive electromagnetic wave signals. Each antenna in communication device 10 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with a tuning switch. Communication device 10 can transfer files to other devices via wireless communication functionality.

[0825] In one design, the communication device 10 may correspond to the first node in the above method embodiment.

[0826] The device 10 can implement the steps or processes corresponding to the first node executed in the above method embodiments. The transceiver 150 can be used to execute transmission and reception related operations of the first node in the above method embodiments, such as executing step S350 in the above method embodiments. The chip system 110 can be used to execute processing related operations of the first node in the above method embodiments, such as S340.

[0827] In another design, the communication device 10 may correspond to the terminal in the above method embodiment.

[0828] The device 10 can implement the steps or processes executed by the terminal in the above method embodiments. The transceiver 150 can be used to perform operations related to the transmission and reception of the terminal in the above method embodiments, such as executing step S320 in the above method embodiments. The chip system 110 can be used to perform operations related to the processing of the terminal in the above method embodiments.

[0829] In another design, the communication device 10 may correspond to the verification network element in the above method embodiment.

[0830] The device 10 can implement the steps or processes corresponding to the verification network element in the above method embodiments. The transceiver 150 can be used to perform operations related to the transmission and reception of the verification network element in the above method embodiments, such as executing step S372 in the above method embodiments. The chip system 110 can be used to perform processing-related operations of the verification network element in the above method embodiments, such as S376.

[0831] In another design, the communication device 10 may correspond to the third network element in the above method embodiment.

[0832] The device 10 can implement the steps or processes corresponding to the third network element in the above method embodiments. The transceiver 150 can be used to perform operations related to the transmission and reception of the third network element in the above method embodiments, such as executing step S460 in the above method embodiments. The chip system 110 can be used to perform processing-related operations of the third network element in the above method embodiments, such as S430.

[0833] In another design, the communication device 10 may correspond to the first network element in the above method embodiment.

[0834] The device 10 can implement the steps or processes corresponding to the first network element in the above method embodiments. The transceiver 150 can be used to perform operations related to the transmission and reception of the first network element in the above method embodiments, such as executing step S630 in the above method embodiments. The chip system 110 can be used to perform processing-related operations of the first network element in the above method embodiments, such as S620.

[0835] In a design where the communication device 10 corresponds to a terminal (e.g., a terminal device), the communication device 10 may include, for example: Figure 11 The short-range communication module 164, sensor 161, display 162, or camera 163 shown are examples of such modules.

[0836] The short-range communication module 164 may include modules that support short-range communication, such as Wi-Fi and Bluetooth.

[0837] For example, sensor 161 may include pressure sensor, gyroscope sensor, barometric pressure sensor, magnetic sensor, accelerometer, distance sensor, proximity sensor, fingerprint sensor, temperature sensor, touch sensor, ambient light sensor, bone conduction sensor, etc.

[0838] For example, display 162 is used to display images, videos, etc. The display includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a mini light-emitting diode (LED), a microLED, a microOLED, a quantum dot light-emitting diode (QLED), etc. For example, in this embodiment, the display can be used to display the interface required by the communication device 10. For example, the communication device 10 implements display functions through a graphics processing unit (GPU), a display, and an application processor. The GPU is a microprocessor for image processing, connected to the display and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The chip system 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0839] For example, camera 163 is used to acquire images, videos, etc.

[0840] Understandable, Figure 11 The structure shown does not constitute a specific limitation on the communication device 10. The specific structure of the terminal equipment, access network equipment or core network equipment can be referred to Figure 11 As shown. In some embodiments, the communication device 10 may also include a... Figure 11 This could mean having more or fewer components, combining some components, separating some components, or having different component arrangements. Or, Figure 11 Some of the components shown can be implemented in hardware, software, or a combination of software and hardware. Terminal devices and / or access network devices can be implemented in… Figure 11 The components were added or removed based on the given structure.

[0841] Figure 12 This is a schematic block diagram of the communication device 20 provided in the embodiments of this application.

[0842] like Figure 12As shown, the communication device 20 may include a baseband unit 210, which can communicate with external devices via a cellular radio frequency (RF) transceiver 220 (e.g., if the communication device 20 is a terminal device, the baseband unit 210 can communicate with access network devices via the cellular RF transceiver 220; or, if the communication device 20 is an access network device, the baseband unit 210 can communicate with terminal devices and / or core network devices via the cellular RF transceiver 220).

[0843] Exemplarily, baseband unit 210 may include a computer-readable medium / memory. Baseband unit 210 may be responsible for general processing, including the execution of software stored on the computer-readable medium / memory. When executed by baseband unit 304, the software causes baseband unit 210 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by baseband unit 210 during software execution.

[0844] Optionally, the baseband unit 210 further includes a receiving unit 201, a management unit 202, and a transmitting unit 203. When the communication device 20 is used to implement the functions of the first node, the management unit 202 includes one or more of these components. Figure 12 The sub-units shown are, for example, a secure signature sub-unit, which can be used for secure signature operations in the above method embodiments. Units within management unit 201 can be stored in a computer-readable medium / memory and / or configured as hardware within baseband unit 210. Management unit 201 can also be referred to as a processing unit. The receiving unit 201 and the sending unit 203 can be referred to as transceiver units.

[0845] When the communication device 20 is used to implement the function of the first node in the above method embodiments, the receiving unit 201 is used to perform the receiving step of the first node, the sending unit 203 is used to perform the sending step of the first node, and the management unit 202 is used to perform the processing step of the first node.

[0846] For example, when the communication device 20 is used to implement the function of the first node in the above method embodiments, the receiving unit 201 is used to receive data from the previous hop node; the management unit 202 is used to sign the first path information based on the key of the first node to obtain the first signature information, wherein the first path information includes: the information of the previous hop node, the information of the first node, and the information of the second node; the sending unit 203 is used to send the data, the first path information, and the first signature information to the second node.

[0847] For example, when the device 20 is used to perform Figures 3 to 10When the method is in use, the receiving unit 201 can be used to execute the step of receiving information in the method; the management unit 202 can be used to execute the processing step in the method; and the sending unit 203 can be used to execute the step of sending information in the method.

[0848] When the communication device 20 is used to implement the functions of the terminal in the above method embodiments, the receiving unit 201 is used to perform the receiving step of the terminal, the sending unit 203 is used to perform the sending step of the terminal, and the management unit 202 is used to perform the processing step of the terminal.

[0849] For example, when the communication device 20 is used to implement the functions of the terminal in the above method embodiments, the sending unit 203 is used to send third information to the first node deployed on the first NTN device. The third information is used to trigger the first node to perform a secure signature on the first path information. The first path information includes: the terminal information, the first node information, and the next-hop node information of the first node. The sending unit 203 is also used to send data to the first node.

[0850] For example, when the device 20 is used to perform Figures 3 to 10 When the method is in use, the receiving unit 201 can be used to execute the step of receiving information in the method; the management unit 202 can be used to execute the processing step in the method; and the sending unit 203 can be used to execute the step of sending information in the method.

[0851] When the communication device 20 is used to implement the function of the verification network element in the above method embodiments, the receiving unit 201 is used to perform the receiving step of the verification network element, the sending unit 203 is used to perform the sending step of the verification network element, and the management unit 202 is used to perform the processing step of the verification network element.

[0852] For example, when the communication device 20 is used to implement the function of verifying network elements in the above method embodiments, the receiving unit 201 is used to obtain first signature information and first path information, wherein the first path information includes information of the previous hop node of the first node, information of the first node, and information of the next hop node of the first node, wherein the first node is deployed on the first NTN device; the management unit 202 is used to determine the public key of the first node based on the information of the first node; the management unit 202 is also used to verify the validity of the first signature information based on the public key of the first node and the first path information.

[0853] For example, when the device 20 is used to perform Figures 3 to 10 When the method is in use, the receiving unit 201 can be used to execute the step of receiving information in the method; the management unit 202 can be used to execute the processing step in the method; and the sending unit 203 can be used to execute the step of sending informatio...

Claims

1. A communication method, characterized in that, The method is applied to a first node deployed on a first non-terrestrial network (NTN) device, and the method includes: Receive data from the previous hop node; Based on the key of the first node, the first path information is signed to obtain first signature information, wherein the first path information includes: the information of the previous hop node, the information of the first node, and the information of the second node; The data, the first path information, and the first signature information are sent to the second node.

2. The method according to claim 1, characterized in that, The first path information also includes: the time information of the first node processing the data.

3. The method according to claim 1 or 2, characterized in that, Before signing the first path information based on the key of the first node to obtain the first signature information, the method further includes: Based on the first information, a secure signature is determined for the first path information, wherein the first information is at least one of first location information, first address information, or information of the terminal sending the data, wherein the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, the landing network element being a network element deployed on the ground for receiving the data, and the first address information is used to indicate the address of the terminal.

4. The method according to claim 3, characterized in that, The first node is configured with a mapping relationship between the first information and the first security policy; Wherein, determining to perform a secure signature on the first path information based on the first information includes: Based on the mapping relationship and the first information, the first security policy is determined, and the first security policy is used to instruct the first path information to be securely signed.

5. The method according to claim 1 or 2, characterized in that, Before signing the first path information based on the key of the first node to obtain the first signature information, the method further includes: Based on the first information, it is determined that the first path information is securely signed, and that the node processing the data is located at the position indicated by the first location information. The first information is at least one of the first location information, the first address information, or the information of the terminal sending the data. The first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the landing network element, wherein the landing network element is a terrestrial network element used to receive the data, and the first address information is used to indicate the address of the terminal.

6. The method according to claim 5, characterized in that, The first node is configured with a mapping relationship between the first information and the second security policy; The step of determining, based on the first information, to perform a secure signature on the first path information and to determine that the node processing the data is located at the position indicated by the first location information includes: Based on the mapping relationship and the first information, a second security policy is determined. The second security policy is used to instruct the first path information to be securely signed, and to instruct the node processing the data to be located at the position indicated by the first location information.

7. The method according to claim 1 or 2, characterized in that, Before signing the first path information based on the key of the first node to obtain the first signature information, the method further includes: Receive first indication information from the previous hop node, the first indication information being used to instruct the first path information to be securely signed.

8. The method according to claim 7, characterized in that, The first indication information is also used to indicate that the node processing the data is at the location indicated by the first location information, wherein the first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data.

9. The method according to any one of claims 1 to 8, characterized in that, The first node is configured with a third security policy, which is used to indicate that the node processing the data is at the location indicated by the first location information. The method further includes: Based on the third security policy, the second node is determined, wherein the second node is located at the position indicated by the first location information.

10. The method according to claim 9, characterized in that, The determination of the second node based on the third security policy includes: Based on the third security policy, the first routing path is determined, wherein on the first routing path, the second node is the next-hop node of the first node, and the node on the first routing path is located at the position indicated by the first location information.

11. The method according to claim 9, characterized in that, The determination of the second node based on the third security policy includes: Based on the third security strategy and ephemeris information, the second node is determined to be located at the position indicated by the first location information.

12. The method according to any one of claims 1 to 8, characterized in that, Before sending the data, the first path information, and the first signature information to the second node, the method further includes: Receive first configuration information from a first network element, the first configuration information being used to configure a first routing path; Based on the information of the landing network element, the first routing path is determined, wherein the landing network element is a network element deployed on the ground for receiving the data, and the first routing path is a routing path with the destination network element being the landing network element, wherein on the first routing path, the second node is the next-hop node of the first node.

13. The method according to claim 12, characterized in that, The method further includes: Send second information to the first network element, the second information being used to instruct the verification network element to send information about the first routing path; and / or, Send the information of the first routing path to the second node.

14. The method according to any one of claims 1 to 13, characterized in that, The method further includes: Send a second instruction message to the second node, the second instruction message being used to instruct the second node to perform a secure signature.

15. A communication method, characterized in that, The method is applied to a terminal, and the method includes: Send third information to the first node deployed on the first NTN device. The third information is used to trigger the first node to perform a secure signature on the first path information. The first path information includes: information of the terminal, information of the first node, and information of the next-hop node of the first node. Send data to the first node.

16. The method according to claim 15, characterized in that, The third information is also used to trigger the first node to send the data to the node at the location indicated by the first location information.

17. The method according to claim 15 or 16, characterized in that, The third piece of information is at least one of the following: Indication information for the first location; First address information; The information of the terminal; or, First indication information, the first indication information is used to indicate that the first path information is securely signed, and / or, the first indication information is used to indicate that the node processing the data is at the position indicated by the first location information; Wherein, the first address information is used to indicate the address of the terminal, and the first location information is used to indicate the location of the terminal, the location indicated by the terminal, or the location of the landing network element, wherein the landing network element is a network element deployed on the ground for receiving the data.

18. The method according to claim 17, characterized in that, Before sending the third information to the first node deployed on the first NTN device, the method further includes: Receive third indication information from the second network element, the third indication information being used to indicate that the first path information is securely signed, and / or, the third indication information being used to indicate that the node processing the data is at the position indicated by the first location information.

19. The method according to any one of claims 15 to 18, characterized in that, The method further includes: Based on the key of the terminal, the information of the terminal and the information of the first node are signed to obtain the second signature information; Send the second signature information to the first node.

20. A communication method, characterized in that, The method is applied to verify network elements, and the method includes: Obtain first signature information and first path information, wherein the first path information includes information of the previous hop node of the first node, information of the first node, and information of the next hop node of the first node, wherein the first node is deployed on the first NTN device; Based on the information of the first node, determine the public key of the first node; The validity of the first signature information is verified based on the public key of the first node and the first path information.

21. The method according to claim 20, characterized in that, The method further includes: Information about a first routing path is received from a first network element, wherein the first routing path is determined by the first network element, and the information about the first routing path includes information about each node used for data transmission. Based on the information of the first routing path, verify the validity of the first path information.

22. The method according to claim 21, characterized in that, The method further includes: Based on the path information of each node transmitting the data, the information of the second routing path is determined. The information of the second routing path includes the information of each node transmitting the data, and the information of the second routing path includes the information of the first path. The step of verifying the validity of the first path information based on the information of the first routing path includes: Verify the consistency between the second routing path and the first routing path.

23. The method according to any one of claims 20 to 22, characterized in that, The first path information further includes: the time information of the first node processing data; wherein, the method further includes: Based on the time information, it is verified whether the first node is located at the position indicated by the first location information when processing the data, wherein the first location information is used to indicate the location of the terminal sending the data, the location indicated by the terminal, or the location of the landing network element receiving the data.

24. The method according to claim 23, characterized in that, The step of verifying whether the first node is located at the position indicated by the first location information when processing the data based on the time information includes: Based on the time information, second location information is obtained, wherein the second location information is used to indicate the location of the first node at the time indicated by the time information; Based on the second location information and the first location information, it is determined whether the first node is located at the position indicated by the first location information when processing the data.

25. The method according to claim 24, characterized in that, Obtaining the second location information based on the time information includes: Send a request message to the second network element. The request message is used to request the position of the first node at the time indicated by the time information. The request message includes the time information. Receive a response message from the second network element, the response message including the second location information.

26. The method according to claim 25, characterized in that, The request message also includes the identifier of the first node, wherein, before sending the request message to the second network element, the method further includes: Receive second configuration information, which is used to configure the mapping relationship between the address information of the first node and the identifier of the first node; Based on the mapping relationship and the address information of the first node, the identifier of the first node is determined and carried in the request message.

27. The method according to any one of claims 20 to 26, characterized in that, The method further includes: Receive second configuration information, which is used to configure the public key of the first node.

28. A communication device, characterized in that, It includes at least one module or at least one unit, said at least one module or said at least one unit being used to perform the method of any one of claims 1 to 27.

29. A communication device, characterized in that, include: At least one processor, the at least one processor being configured to execute a computer program or instructions to cause the method of any one of claims 1 to 27 to be performed.

30. The communication device according to claim 29, characterized in that, The communication device further includes a memory for storing the computer program or the instructions.

31. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are run, the method of any one of claims 1 to 27 is performed.

32. A computer program product, characterized in that, Includes a computer program or instructions, which, when executed, implement the method as described in any one of claims 1 to 27.

Images