Communication method and device

Abstract

The invention relates to the technical field of communication, in particular to a communication method and device, and aims to support that ground network equipment can address network elements in a ground home network of terminal equipment under a core network full-sky architecture (for example, a user data storage network element architecture is deployed in a non-ground network). The method may be executed by a second network element located in a non-terrestrial network, the method comprising: acquiring first information, the first information being used for indicating a first network element, the first network element being a network element in a terrestrial HPLMN of a terminal device; and sending the first information to the ground network equipment.

Description

Technical Field

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

[0002] Store-and-forward (S&F) technology in non-terrestrial networks (NTNs) is primarily used in scenarios where the satellite cannot simultaneously connect to both the terminal device and the terrestrial network; that is, the service link and the feeder link cannot be available at the same time. Store-and-forward refers to the process where, when the satellite and the terminal device are connected (i.e., the service link is available), the satellite stores user data; when the satellite and the terrestrial network are connected (i.e., the feeder link is available), the user data is forwarded to the terrestrial network, for example, to a ground-based agent or satellite store-and-forward center (SSFC). The ground agent or SSFC then forwards the user data to the corresponding network node.

[0003] In NTN systems, the S&F mode supports a fully satellite-based core network architecture, meaning that all core network functions can be deployed on one or more satellites. However, even with this fully satellite-based architecture, terrestrial network devices such as ground agents or SSFCs still need to address network elements in the terminal device's home terrestrial network to process or retrieve user information. How to support terrestrial network devices addressing network elements in the terminal device's home terrestrial network remains to be solved. Summary of the Invention

[0004] This application provides a communication method and apparatus to support the ability of terrestrial network devices to address network elements in the terrestrial home network of terminal devices under a fully space-based core network architecture, and to support the processing or acquisition of user information corresponding to the terminal devices.

[0005] Firstly, embodiments of this application provide a communication method. This method can be executed by a second network element, which can be a network element in a non-terrestrial network, such as an on-board agent or core network element deployed in a non-terrestrial network. It can also refer to a non-terrestrial network device carrying the second network element (such as a satellite or high-altitude platform), or a component (such as a processor, module, chip, or chip system) within the non-terrestrial network device carrying the second network element that implements the method. This method can be applied to a fully space-based core network architecture, such as a non-terrestrial network with a user data storage network element deployed, where the non-terrestrial network can support processes such as registration and authentication of terminal devices. Taking the execution of this method by a second network element as an example, the method includes: obtaining first information, the first information being used to indicate a first network element, where the first network element is a network element in the terminal device's home public land mobile network (HPLMN); and sending the first information to a terrestrial network device.

[0006] For example: the first network element can be a network element that processes or obtains user information corresponding to the terminal device.

[0007] Using the above method, under the core network full-space architecture (i.e., the whole core network (CN) architecture), the second network element can send the first information of the network element in the ground HPLMN used to indicate the terminal device to the ground network device, supporting the ground network device to address the network element in the ground home network of the terminal device, thereby supporting the processing or acquisition of user information corresponding to the terminal device.

[0008] In one possible design, obtaining the first information includes: obtaining the first information from a terminal device; or obtaining the first information from a third network element, wherein the third network element is a network element in a non-terrestrial network (such as a core network element in a non-terrestrial network), and the third network element is different from the second network element. For example: the first information of the third network element may be obtained from the terminal device, determined based on information reported by the terminal device, configured in the third network element, or obtained by the third network element from other non-terrestrial core network elements.

[0009] The above design enables the second network element to obtain the first information from the terminal device or other network elements in the non-terrestrial network, which helps the second network element to obtain the first information used to instruct the first network element more accurately and efficiently.

[0010] In one possible design, the first network element is a billing function network element, and the method further includes: sending data corresponding to the terminal device or the amount of data corresponding to the terminal device to the terrestrial network device, wherein the amount of data is determined based on the data corresponding to the terminal device.

[0011] With the above design, when the first network element is a billing function network element, the second network element can send the data corresponding to the terminal device or the data volume corresponding to the terminal device to the ground network device, thereby supporting the ground network device to send the data volume to the ground billing function network element for billing the terminal device.

[0012] In one possible design, the first network element is a policy control function network element, and the method further includes: sending policy control information and / or billing information corresponding to the terminal equipment to the terrestrial network equipment.

[0013] With the above design, when the first network element is a policy control function network element, the second network element can send the policy control information and / or billing information corresponding to the terminal equipment to the terrestrial network equipment, so that the policy control function network element can provide the communication service corresponding to the policy control information, or provide the identifier or address of the billing function network element used for billing the terminal equipment.

[0014] In one possible design, a non-terrestrial network (such as a radio access network in a non-terrestrial network) broadcasts the identifier of at least one PLMN, to which the HPLMN belongs.

[0015] The above design enables non-terrestrial networks to provide services to at least one PLMN (i.e., at least one network), broadcasting the identifier of the at least one PLMN providing the service, so that terminal devices belonging to the at least one PLMN can access the non-terrestrial network.

[0016] In one possible design, the first information includes the identifier of the HPLMN, and obtaining the first information includes: obtaining the identifier of the HPLMN carried in the identifier of the terminal device.

[0017] Through the above design, in the case of the HPLMN identifier of the non-terrestrial network broadcast terminal equipment, the second network element can obtain the HPLMN identifier of the terminal equipment from the identifier of the terminal equipment (such as the subscription concealed identifier (SUCI)).

[0018] In one possible design, the first information includes the identifier and / or address of the first network element. Obtaining the first information includes: obtaining the identifier and / or address of the first network element based on the identifier of the terminal device and a first mapping table, wherein the first mapping table includes at least one of the following: a mapping relationship between the identifier of the terminal device and the identifier and / or address of the first network element; or, a mapping relationship between a first field in the identifier of the terminal device and the identifier and / or address of the first network element.

[0019] Through the above design, the second network element can obtain the identifier and / or address of the first network element in the terrestrial HPLMN corresponding to the terminal device based on the identifier of the terminal device and the mapping relationship between the identifier of the terminal device (or the first field in the identifier) ​​and the identifier and / or address of the first network element, thereby enabling the terrestrial network device to address the first network element in the terrestrial HPLMN corresponding to the terminal device.

[0020] In one possible design, the method further includes: a non-terrestrial network (such as a radio access network in a non-terrestrial network) broadcasting an identifier of a first PLMN, which is different from an HPLMN.

[0021] The above design enables the second network element to provide services to at least one PLMN (i.e., at least one network), but broadcasts a unified identifier of the first PLMN for the at least one PLMN providing services, allowing terminal devices to access the non-terrestrial network of the first PLMN.

[0022] In one possible design, the first information includes the identifier of the HPLMN. Obtaining the first information includes: receiving an uplink message from the terminal device, the uplink message carrying the identifier of the HPLMN; or, obtaining the identifier of the HPLMN based on the identifier of the terminal device, wherein the identifier of the terminal device carries the identifier of the first PLMN and the identifier of the HPLMN.

[0023] For example, an uplink message may include at least one of the following: a random access uplink message, a registration or attach request, an authentication or authorization response, a non-access stratum (NAS) security mode completion message, an access stratum (AS) security mode completion message, a session establishment request, or a tracking area update (TAU) request.

[0024] With the above design, in cases where the identifier of the first PLMN broadcast on the non-terrestrial network is different from the identifier of the HPLMN of the terminal device, the terminal device can actively report the identifier of the terrestrial HPLMN, or carry the identifiers of the first PLMN and HPLMN in its identifier, so that the second network element can know the identifier of the terminal device's HPLMN.

[0025] In one possible design, the first information includes the identifier of the HPLMN. Obtaining the first information includes: obtaining the identifier of the HPLMN based on the identifier of the terminal device and a second mapping table, wherein the second mapping table includes at least one of the following: a mapping relationship between the identifier of the terminal device and the identifier of the HPLMN; or, a mapping relationship between a second field in the identifier of the terminal device and the identifier of the HPLMN.

[0026] Through the above design, in cases where the identifier of the first PLMN broadcast by the non-terrestrial network is different from the identifier of the HPLMN of the terminal device, the second network element is supported to obtain the identifier of the ground HPLMN of the terminal device based on the identifier of the terminal device (such as the identifier of the first PLMN corresponding to the terminal device) and the mapping relationship between the identifier of the terminal device (or the second field in the identifier) ​​and the identifier of the ground HPLMN of the terminal device, and use it to address the first network element in the ground HPLMN of the terminal device.

[0027] In one possible design, the first information includes the identifier of the terminal device. Through this design, the terrestrial network device can also obtain the identifier or address of the first network element in the terrestrial HPLMN based on the identifier of the terminal device, and then address the first network element in the terrestrial HPLMN.

[0028] In one possible design, the identifier of the terminal device includes one or more of the following: subscription permanent identifier (SUPI), international mobile subscriber identity (IMSI), subscription concealed identifier (SUCI), globally unique temporary user equipment (UE) identity (GUTI), 5G globally unique temporary UE identifier (5G-GUTI), or generic public subscription identifier (GPSI).

[0029] It is understood that the aforementioned first mapping table and / or second mapping table can be stored in the second network element or in other network elements in the non-terrestrial network. The second network element can call the first mapping table and / or second mapping table from other network elements.

[0030] The network element that sends user information (such as data volume or policy control information) to terrestrial network equipment can be a second network element or other network elements in the non-terrestrial network. For example, the second network element can be an on-board agent in the non-terrestrial network, which can send user information to non-terrestrial network equipment. Alternatively, access and mobility management function network elements in the non-terrestrial network can also send user information to terrestrial network equipment.

[0031] Secondly, embodiments of this application provide a communication method that can be executed by a terrestrial network device. This terrestrial network device can refer to a terrestrial agent, SSFC, ground station, or terrestrial device with deployed core network elements, etc. It can also refer to components within the terrestrial network device that implement the method (e.g., processors, modules, chips, or chip systems), or logical modules or software capable of implementing all or part of the functions of the terrestrial network device. The method includes: receiving first information from a second network element, the first information indicating a first network element, where the first network element is a network element in the terrestrial HPLMN of the terminal device, and the second network element is a network element in a non-terrestrial network, where a user data storage network element is deployed; and sending user information corresponding to the terminal device to the first network element.

[0032] For example: the first network element can be a network element that processes or obtains user information corresponding to the terminal device.

[0033] In one possible design, the first network element is a billing function network element, and the method further includes: receiving data or the amount of data corresponding to a terminal device from a non-terrestrial network, wherein the amount of data is determined based on the data corresponding to the terminal device; wherein the user information includes the amount of data corresponding to the terminal device, and the first network element bills the terminal device based on the amount of data.

[0034] In one possible design, the first network element is a policy control function network element, and the method further includes: receiving policy control information and / or billing information corresponding to a terminal device from a non-terrestrial network; wherein the user information includes policy control information, and the first network element provides communication services to the terminal device based on the policy control information; and / or, the user information includes billing information, and the first network element provides the terrestrial network device with the identifier or address of the billing function network element corresponding to the terminal device based on the billing information.

[0035] In one possible design, a non-terrestrial network (such as a radio access network in a non-terrestrial network) broadcasts the identifier of at least one PLMN, to which the HPLMN belongs.

[0036] In one possible design, the identifier of the first PLMN is broadcast via a non-terrestrial network, and the first PLMN is different from the HPLMN.

[0037] In one possible design, the first information includes at least one of the following: the identifier of the HPLMN, the identifier of the first network element, the address of the first network element, or the identifier of the terminal device.

[0038] In one possible design, the first information includes the identifier of the terminal device; sending the user information corresponding to the terminal device to the first network element includes: obtaining second information based on the first information, the second information including at least one of the identifier of the HPLMN, the identifier of the first network element, or the address of the first network element; and sending the user information corresponding to the terminal device to the first network element based on the second information.

[0039] In one possible design, the terminal device is identified as a virtual or temporary identifier, which carries the identifier of the HPLMN.

[0040] In one possible design, the identifier of the terminal device is a virtual or temporary identifier. Based on the first information, the second information is obtained, including: obtaining the second information based on the virtual or temporary identifier of the terminal device and a third mapping table, wherein the third mapping table includes at least one of the following: the mapping relationship between the virtual or temporary identifier of the terminal device and the second information; or, the mapping relationship between the third field in the virtual or temporary identifier of the terminal device and the second information.

[0041] In one possible design, the identifier of the terminal device includes one or more of the following: SUPI, IMSI, SUCI, GUTI, 5G-GUTI, or GPSI.

[0042] Thirdly, embodiments of this application provide a communication device that has the function of implementing the methods described in the first or second aspect above. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, such as an interface unit and a processing unit.

[0043] In one possible design, the device can be a chip or an integrated circuit.

[0044] In one possible design, the device includes a memory and a processor, the memory for storing instructions executed by the processor, and when the instructions are executed by the processor, the device can perform the method of the first aspect or the second aspect.

[0045] Fourthly, embodiments of this application provide a communication device, which includes an interface circuit and a processor, with the processor and the interface circuit coupled to each other. The interface circuit is used for inputting and / or outputting signals, and the processor uses logic circuits or executing instructions to implement the methods of the first or second aspect described above. It is understood that the interface circuit can be a transceiver, a transceiver device, or an input / output interface.

[0046] Optionally, the communication device may also include a memory for storing instructions executed by the processor, or storing input data required by the processor to execute instructions, or storing data generated after the processor executes instructions. The memory may be a physically independent unit, or it may be coupled to the processor, or the processor may include the memory (i.e., the processor and the memory are integrated together).

[0047] In one possible implementation, the communication device is a chip or chip system.

[0048] Fifthly, embodiments of this application provide a communication system, which includes a second network element and a terrestrial network device. The second network element is used to implement the method described in the first aspect; the terrestrial network device is used to implement the method described in the second aspect.

[0049] In a sixth aspect, embodiments of this application provide a computer-readable storage medium storing a computer program or instructions, which, when executed by a processor, can implement the methods described in the first or second aspect.

[0050] In a seventh aspect, embodiments of this application also provide a computer program product, including a computer program or instructions, which, when executed by a processor, can implement the methods of the first or second aspect described above.

[0051] Eighthly, embodiments of this application also provide a chip system including a processor, the processor being coupled to a memory, the memory being used to store programs or instructions, and when the program or instructions are executed by the processor, the methods of the first or second aspect described above can be implemented.

[0052] The technical effects achievable by aspects two through eight above are similar to those achievable by aspect one above, and will not be repeated here. Attached Figure Description

[0053] Figure 1 This is a schematic diagram of a store-and-forward scenario in an NTN system provided in an embodiment of this application;

[0054] Figure 2 A schematic diagram of the NTN architecture provided in the embodiments of this application;

[0055] Figure 3 This is a schematic diagram of the 5G network architecture provided in an embodiment of this application;

[0056] Figure 4 This is a schematic diagram of CHF network element selection provided in an embodiment of this application;

[0057] Figure 5 This is a billing diagram under the NTN architecture provided in an embodiment of this application;

[0058] Figure 6 , Figure 8 , Figure 9 , Figure 10 , Figure 12 This is a schematic diagram of a communication method provided in an embodiment of this application;

[0059] Figure 7 A schematic diagram of the SUCI structure provided in the embodiments of this application;

[0060] Figure 11 A schematic diagram illustrating the identification of the HPLMN of the terminal device transmitted via uplink messages, as provided in this application embodiment;

[0061] Figure 13 and Figure 14 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Detailed Implementation

[0062] In an NTN system, the link between a satellite and terminal equipment is called a service link, and the link between a satellite and ground equipment (such as a ground station) is called a feed link. Due to the relative motion of the satellite to the Earth's surface or the satellite's low to medium Earth orbit, the service link and feed link may not be available simultaneously. Figure 1 As shown, at time T1, the satellite can connect to the terminal device but cannot connect to the ground station. That is, the service link between the satellite and the terminal device is available, but the power supply link between the satellite and the ground station is unavailable. At time T3, the satellite can connect to the ground station but cannot connect to the terminal device. That is, the power supply link between the satellite and the ground station is available, but the service link between the satellite and the terminal device is unavailable.

[0063] During periods of power supply or service link interruption, satellites can store user data through S&F (Service and Data Facility) operations. For example, after a terminal device registers with the network, when it sends data to the satellite, the satellite stores that data. Once the satellite's power supply link becomes available, it forwards the stored data, along with other necessary information, to ground equipment. The ground equipment can then forward the data to its destination network node. S&F technology can be applied to satellite service operations that are not real-time or where latency is permissible.

[0064] Based on the deployment of core network equipment on satellites, the NTN system currently supports two satellite architectures in S&F mode: a core network separation architecture and a fully satellite-based core network architecture. The specific architecture deployed on satellites depends on the operator. The core network separation architecture allows some core network (CN) elements to be deployed on satellites. For example, the access and mobility management function (AMF) can be divided into two parts: one part is carried on satellite, called non-terrestrial AMF (AMF-NT), and the other part is carried on the ground, called terrestrial AMF (AMF-T). AMF-NT and AMF-T can communicate with each other. Other core network elements, such as user data management (UDM) elements, can be deployed on the ground.

[0065] The whole-space core network architecture, also known as the whole CN architecture, allows all core network functions to be deployed on satellites. In a whole CN architecture, the radio access network (RAN) and the CN can be deployed (or carried) on satellites, and terminal devices can access the network through the RAN deployed on the satellite. For a whole CN architecture, network elements that store user data, such as the unified data management (UDM) element, may have some or all of their functions deployed on the satellite. On-board agents may also be deployed on satellites, while ground agents or SSFCs may be deployed on the ground. The function of the on-board agent may be to store data and related protocols, while the role of the ground agent or SSFC is to forward data to the corresponding network nodes.

[0066] Reference Figure 2 The NTN architecture diagram shown illustrates that, for a whole CN architecture, the satellite can deploy (or carry) RAN, CN, and on-board agent, with the on-board agent being an optional network element. Terminal equipment ( Figure 2 (Taking the UE as an example, the terminal device can access the NTN through the RAN deployed on the satellite, establish a connection with the satellite, and send data to the satellite. Ground-based SSFCs or ground agents are deployed to receive data from the satellite when the power supply link is available; they are also responsible for forwarding the data from the satellite to the corresponding network nodes.)

[0067] Among them, terminal equipment, also known as terminal, UE, mobile station (MS), mobile terminal, etc., is a device or equipment with wireless communication function. It can be deployed on land, including indoor or outdoor, handheld or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites). Terminal devices can be widely used in various scenarios, such as machine-type communication (MTC), the Internet of Things (IoT), vehicle-to-everything (V2X), virtual reality (VR), augmented reality (AR), industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, and smart homes. Terminal devices can include mobile phones, subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistants (PDAs), computers, tablets, modems, handsets, laptop computers, customer-premises equipment (CPE), and smart points of sale. POS machines, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, MTC devices, etc. Additionally, in this application embodiment, "terminal device" can also refer to a device used to implement the functions of the terminal device, such as a chip system. This device can be installed in the terminal device, wherein the chip system can be composed of chips or include chips and other discrete components. The embodiments of this application do not limit the specific technology or specific device form used in the terminal device.

[0068] The RAN can be a cellular network related to the 3rd Generation Partnership Project (3GPP), such as a 4th generation (4G) mobile communication network, a 5th generation (5G) mobile communication network, or a future communication network. RAN 100 can also be an open RAN (O-RAN or ORAN), or a cloud radio access network (CRAN), etc. The RAN can also be a communication network integrating two or more of the above systems. In the embodiments of this application, the RAN can be carried on a satellite, which can be a medium Earth orbit (MEO) satellite, a low Earth orbit (LEO) satellite, or a high altitude platform station (HAPS), etc., meaning the RAN equipment or nodes can be MEO satellites, LEO satellites, or high altitude platforms, etc.

[0069] The CN can be a 4G mobile communication network, a 5G mobile communication network, or a future communication network. The CN can include multiple network function (NF) network elements (or entities). Taking the CN as the core network of a 5G mobile communication network as an example, the CN can include access and mobility management function (AMF), session management function (SMF) network elements, policy control function (PCF) network elements, user data management (UDM) network elements, authentication server function (AUSF) network elements, network exposure function (NEF) network elements, user plane function (UPF) network elements, etc.

[0070] For a whole CN architecture, i.e., a core network fully in orbit, satellites can serve multiple terrestrial networks (or multiple terrestrial network operators). There are two possible methods: 1) The satellite broadcasts the PLMN identifiers (IDs) of multiple terrestrial networks, such as PLMN ID#A, PLMN ID#B, PLMN ID#C, etc. The PLMN ID contained in the identifier reported by the terminal device (such as the International Mobile Subscriber Identity (IMSI), Subscription Concealed Identifier (SUCI), or SUPI) is the PLMN ID of its corresponding terrestrial network; 2) The satellite serves multiple terrestrial networks but broadcasts a unified PLMN ID. The PLMN ID contained in the identifier reported by the terminal device (such as IMSI, SUCI, or SUPI) is the unified PLMN ID broadcast by the satellite.

[0071] However, under the whole CN architecture, operations such as billing and dynamic policy control information acquisition still require terrestrial network devices such as terrestrial agents or SSFCs to address network elements in the terminal device's home terrestrial network (such as charging function (CHF) network elements, converged charging system (CSS) or PCF network elements) to complete. How to support terrestrial network devices addressing network elements in the terminal device's home terrestrial network remains to be solved.

[0072] Figure 3 This is a schematic diagram of a possible 5G network architecture provided in an embodiment of this application. In scenarios where the core network is deployed on the ground, UDM network elements, SMF network elements, CHF network elements, etc., are deployed on the ground. The SMF network element can address the CHF network element and interact with the CHF network element to complete the billing of the terminal device.

[0073] Figure 4 A schematic diagram illustrating a possible CHF network element selection for an embodiment of this application, referring to... Figure 4The SMF network element shown can select the CHF (Call Detailed Request) during Protocol Data Unit (PDU) session establishment. Following the order of priority from highest to lowest, the selection can be: 1) One or more of the following information provided by the PCF network element for the PDU session: CHF network element ID, CHF set ID, or CHF network element address. The SMF network element selects the CHF network element based on this information; 2) The SMF network element can obtain relevant billing characteristics (such as the billing characteristics of the terminal device's subscription) from the UDM network element and selects the CHF network element based on these characteristics; 3) The SMF network element discovers the CHF network element based on the CHF network element address stored in the network repository function (NRF); 4) The SMF network element selects the CHF network element based on its locally configured billing attributes. The billing characteristics / attributes are user subscription information that characterizes the call detail record (CDR) generation method and are used for CHF network element selection, such as selecting a CHF network element that supports the corresponding CDR generation method.

[0074] For a whole CN architecture, core network elements such as SMF and UDM are deployed on satellites. These satellite-based core network elements may not have direct interfaces with terrestrial core network elements, and the satellite (or non-terrestrial network) may provide services to multiple terrestrial networks. Terminal devices accessing the satellite may correspond to the core networks of different terrestrial networks. For example, a satellite broadcasts the PLMN IDs of multiple terrestrial networks, such as PLMN ID#A, PLMN ID#B, and PLMN ID#C. Terminal devices accessing the satellite may correspond to the core network of PLMN ID#A, PLMN ID#B, or PLMN ID#C. Therefore, how terrestrial network devices address the CHF or PCF network elements in the terminal device's home terrestrial network when performing billing or dynamic policy function information retrieval is a problem that needs to be solved.

[0075] Based on this, embodiments of this application provide a communication method and apparatus to support terrestrial network devices in a whole CN architecture to address network elements in the terrestrial home network of a terminal device, and to support the processing or acquisition of user information corresponding to the terminal device. The embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0076] For example: Figure 5As shown, under the whole CN architecture, when billing terminal devices, terrestrial network devices (such as CCFC or terrestrial agents) can address the CHF network element or CCS in the terminal device's home terrestrial network for billing purposes. The CCS can consist of four different modules: charging function (CHF), account balance management function (ABMF), charging gateway function (CGF), and rating function (RF).

[0077] Furthermore, in the description of this application, terms such as "first" and "second" are used only to distinguish multiple objects and are not used to limit the size, content, order, sequence, priority, or importance of the multiple objects. For example, "first information" and "second information" do not indicate a difference in priority or importance between the two pieces of information.

[0078] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "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. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "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, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0079] Non-terrestrial networks can refer to networks deployed on non-terrestrial network devices (such as satellites or high-altitude platforms). For example, a non-terrestrial network can refer to a PLMN deployed on a satellite, which may include a RAN and a CN.

[0080] The communication method provided in this application embodiment can be executed by a second network element and a terrestrial network device. The second network element can be a network element in a non-terrestrial network, such as an on-board agent, AMF network element, or mobility management entity (MME) deployed in a non-terrestrial network. It can also refer to a non-terrestrial network device carrying the second network element (such as a satellite or high-altitude platform), or a component (e.g., processor, module, chip, or chip system) within the non-terrestrial network device carrying the second network element that implements the method. The terrestrial network device can refer to a terrestrial agent, SSFC, ground station, or terrestrial equipment deployed with core network elements (such as AMF network elements). It can also refer to a component (e.g., processor, module, chip, or chip system) within the terrestrial network device that implements the method, or a logic module or software capable of implementing all or part of the functions of the terrestrial network device.

[0081] Figure 6 This is one of the schematic diagrams of a communication method provided in an embodiment of this application. The method includes:

[0082] S601: The second network element obtains the first information, wherein the first information is used to indicate the first network element, and the first network element is a network element in the ground HPLMN of the terminal equipment.

[0083] The communication method provided in this application is applicable to whole CN architecture or scenarios, meaning that all core network functions can be deployed in the non-terrestrial network where the second network element is located. For example, the non-terrestrial network deploys not only the RAN but also core network elements such as user data storage network elements (e.g., UDM network elements or unified data repository (UDR) network elements). The user data storage network elements store the terminal device's subscription data, security context, etc. Compared to a core network separation architecture, the whole CN architecture's non-terrestrial network can directly support processes such as terminal device registration and authentication.

[0084] As an example: if the core network is a 4G core network, the user data storage network element can be a Home Subscriber Server (HSS), and the mobility management network element can be a Mobility Management Entity (MME). If the core network is a 5G core network, the user data storage network element can be a UDM or UDR network element, and the mobility management network element can be an AMF network element. It is understood that this application does not preclude the possibility of using other names for the core network elements in 4G mobile communication networks, 5G mobile communication networks, and other future communication networks. For example, in future communication networks, some or all of the aforementioned core network elements (such as user data storage network elements) may use the terminology from 5G networks, or they may use other names.

[0085] In some implementations, a non-terrestrial network (or non-terrestrial network equipment deployed on a non-terrestrial network, such as satellites) can provide services to at least one PLMN (i.e., a terrestrial network) and broadcast the identifier (such as a PLMN ID) of at least one PLMN. Terminal devices belonging to the aforementioned at least one PLMN can access the non-terrestrial network. It should be noted that the PLMN identifier broadcast by the non-terrestrial network can refer to the RAN, RAN equipment, or RAN nodes broadcasting the PLMN identifier within the non-terrestrial network. For example, if the non-terrestrial network is deployed on a satellite, the RAN within the non-terrestrial network can refer to the RAN deployed on the satellite, and the RAN equipment or RAN nodes can refer to the satellite itself.

[0086] As an example: A non-terrestrial network can provide services to terrestrial PLMN#A, PLMN#B, and PLMN ID#C. When the service link is available, i.e., when the communication link between the non-terrestrial network and the terminal device is available, the terminal device can receive the identifiers of PLMN ID#A, PLMN ID#B, and PLMN ID#C broadcast by the non-terrestrial network, such as PLMN ID#A, PLMN ID#B, and PLMN ID#C broadcast by the non-terrestrial network. After receiving the broadcast message, the terminal device can access the non-terrestrial network and establish a direct or indirect connection with the second network element in the non-terrestrial network.

[0087] After the second network element establishes a connection with the terminal device, it can obtain first information used to indicate the first network element. The first network element is a network element in the terminal device's terrestrial HPLMN. The first information may include one or more of the following: the identifier of the terminal device's HPLMN, the identifier of the first network element, or the address of the first network element. The address of the first network element may be its Internet Protocol (IP) address or Media Access Control (MAC) address, etc.

[0088] Taking the HPLMN of the terminal device as PLMN#A, and the first information including the identifier of the HPLMN of the terminal device as an example, the terminal device can send the identifier of the terminal device to the second network element during the registration, attachment or TAU request process, and the second network element can obtain the identifier of the HPLMN carried in the identifier of the terminal device (such as PLMN ID#A).

[0089] In one possible implementation, for a scenario where a non-terrestrial network provides services to at least one PLMN (i.e., a terrestrial network), the second network element may also be configured with a first mapping table. The first mapping table may include the mapping relationship between the identifiers of terminal devices (i.e., terminal devices belonging to the at least one PLMN) in the at least one PLMN providing services through the non-terrestrial network and the identifiers and / or addresses of the first network element. After receiving the identifier of the terminal device, the second network element may obtain the identifier and / or address of the first network element corresponding to the terminal device based on the identifier and / or address of the first network element that has a mapping relationship with the identifier of the terminal device in the first mapping table.

[0090] Alternatively, the first mapping table may also include the mapping relationship between the first field of the identifier of each terminal device in at least one PLMN providing services from the second network element and the identifier and / or address of the first network element. The first field may be the identifier of all or part of the terminal devices, for example, it may be the field corresponding to the PLMN identifier in the terminal device's identifier or a field including the PLMN identifier.

[0091] Taking the field corresponding to the PLMN identifier in the terminal device identifier as an example, the first mapping table can include the mapping relationship between the identifier of at least one PLMN providing services through a non-terrestrial network and the identifier and / or address (such as IP address) of the first network element. For example, as shown in Table 1, if the non-terrestrial network provides services to PLMN#A, PLMN ID#B, and PLMN ID#C, the first mapping table can include the mapping relationship between PLMN#A's PLMN ID#A (the identifier of PLMN#A) and NF1#A, NF1#D, and NF1#F (the identifiers of the first network element) of NF1 (the first network element) in PLMN#A, as well as addresses #1A, #1D, and #1F (the addresses of the first network element); the mapping relationship between PLMN#B's PLMN ID#B and NF1#B of NF1 in PLMN#B, as well as address #1B; and the mapping relationship between PLMN#C's PLMN ID#C and NF1#C of NF1 in PLMN#C, as well as address #1C. If the first field in the identifier of the terminal device is PLMN ID#A, then the second network element can obtain the identifier of the first network element (NF1) in the HPLMN of the terminal device as NF1#A, NF1#D, NF1#F, and the address as address #1A, address #1D, address #1F.

[0092] It is understood that, in the embodiments of this application, the number of first network elements can be at least one. For example, when there are multiple first network elements, they can be multiple network elements with the same function, or they can be multiple network elements with different functions, or they can include multiple network elements with the same function and multiple network elements with different functions.

[0093] Table 1

[0094]

[0095] In some implementations, a non-terrestrial network (or non-terrestrial network equipment that deploys a non-terrestrial network, such as satellites) can provide services to at least one PLMN (i.e., a terrestrial network), broadcasting the identifier of the first PLMN, which is different from the identifier of the at least one PLMN providing the service. Terminal devices belonging to the aforementioned at least one PLMN can receive the identifier of the first PLMN and access the non-terrestrial network.

[0096] As an example: the first PLMN is PLMN#D. The non-terrestrial network can provide services for the terrestrial PLMN#A, PLMN#B and PLMN ID#C, but the non-terrestrial network does not broadcast the identifiers of PLMN ID#A, PLMN ID#B and PLMN ID#C, that is, it does not broadcast PLMN ID#A, PLMN ID#B and PLMN ID#C, but broadcasts the identifier of PLMN#D, that is, it broadcasts PLMN ID#D.

[0097] One possible approach is to assume the terminal device is a terrestrial terminal device belonging to PLMN#A. The terminal device can be configured with an identifier corresponding to PLMN#D (e.g., SUPI#D), from which PLMNID#D can be derived. When the service link is available—that is, when the communication link between the non-terrestrial network and the terminal device is available—the terminal device can receive the PLMN ID#D broadcast by the non-terrestrial network, initiate access, and establish a connection with the non-terrestrial network, thus accessing the non-terrestrial network.

[0098] In the case where the non-terrestrial network broadcasts the identifier of the first PLMN instead of the identifier of the terminal device's terrestrial HPLMMN, the terminal device can carry the identifier of its terrestrial HPLMMN in the uplink message sent to the non-terrestrial network, so that the second network element in the non-terrestrial network can obtain the identifier of the terminal device's terrestrial HPLMMN.

[0099] Alternatively, the identifier (such as SUCI) sent by the terminal device to the non-terrestrial network may carry the identifier of the first PLMN and the identifier of the terrestrial HPLMMN. The second network element in the non-terrestrial network may also obtain the identifier of the HPLMMN of the terminal device based on the identifier of the terminal device.

[0100] Reference Figure 7The diagram shows the SUCI structure. SUCI can be obtained based on SUPI encryption. SUCI can include SUPI type, home network (HN) ID, routing ID, protection scheme ID, HN public key ID, and scheme output fields. The SUPI type is determined based on the SUPI type in the SUPI and indicates the type of SUPI. The HN ID can be determined based on the mobile country code (MCC) and mobile network code (MNC) in the SUPI, where the MCC and MNC constitute the PLMN identifier. The routing ID indicates routing information, and the protection scheme ID and public key ID indicate the encryption scheme and public key. The scheme output is the content obtained by encrypting the mobile subscriber identification number (MSIN) information from the SUPI.

[0101] In this embodiment, the contents of the routing ID field and the HN public key ID field in the SUCI can be replaced with the identifier of the HPLMN of the terminal device (such as PLMN ID#A); or the identifier of the HPLMN of the terminal device can be carried in the scheme output; or, a new field can be added to the SUCI to carry the identifier of the HPLMN of the terminal device, so that the SUCI can carry not only the identifier of the first PLMN, but also the identifier of the HPLMN of the terminal device. Similarly, a new field can be added to the SUPI to carry the identifier of the HPLMN of the terminal device, so that the SUPI can carry not only the identifier of the first PLMN, but also the identifier of the HPLMN of the terminal device.

[0102] In one possible implementation, when the identifier of the first PLMN is broadcast on a non-terrestrial network, instead of the identifier of the HPLMN of the terminal device, the PLMN identifier carried in the terminal device's identifier may be the identifier of the first PLMN. A second mapping table can also be configured in the second network element. This second mapping table can include a mapping relationship between the identifier of the terminal device in at least one PLMN providing services through a non-terrestrial network and the identifier of the terminal device's terrestrial HPLMN. After receiving the identifier of the terminal device, the second network element can obtain the identifier of the terminal device's HPLMN based on the terminal device's identifier and the second mapping table.

[0103] Additionally, the second mapping table may also include the mapping relationship between the second field of the identifier of a terminal device in at least one PLMN providing services via a non-terrestrial network and the identifier of the terminal device's HPLMN. After receiving the identifier of the terminal device, the second network element can obtain the identifier of the terminal device's HPLMN based on the second field of the terminal device identifier and the second mapping table. The second field can be all or part of the terminal device's identifier. For example, the second field can be a portion of the terminal device's identifier that has a mapping relationship with the identifier of the terminal device's HPLMN.

[0104] Of course, the second mapping table may also include the mapping relationship between the identifier (or the second field in the identifier) ​​of each terminal device in at least one PLMN providing services through a non-terrestrial network and the identifier and / or address of the first network element. After receiving the identifier of the terminal device, the second network element can obtain the identifier and / or address of the first network element based on the second field in the identifier of the terminal device and the second mapping table.

[0105] It is understandable that the identifier of the terminal device received or obtained by the second network element can be a temporary identifier, a virtual identifier, or a permanent identifier of the terminal device, and the identifier of the terminal device can also be included in the first information.

[0106] S602: The second network element sends the first information to the ground network device, and the ground network device receives the first information accordingly.

[0107] S603: The terrestrial network equipment sends the user information corresponding to the terminal equipment to the first network element.

[0108] When the power supply link between the non-terrestrial network (or the non-terrestrial network equipment deployed there, such as satellites) and the terrestrial network equipment is available, i.e., when the communication link between the non-terrestrial network and the terrestrial equipment is available, the second network element can send the first information to the terrestrial network equipment. After receiving the first information, the second network element can send the user information corresponding to the terminal equipment to the first network element indicated by the first information. The first network element can be a billing function network element (such as a CHF network element), a policy control function network element (such as a PCF network element), or other network elements that dynamically process or acquire user information.

[0109] In one possible implementation, the first information may include the identifier of the HPLMN of the terminal device, the identifier of the first network element in the HPLMN, the address of the first network element in the HPLMN, or the identifier of the terminal device, etc.

[0110] If the first information includes the identifier of the HPLMN of the terminal device, the non-terrestrial network can address the first network element based on the identifier of the HPLMN.

[0111] For example, a mapping relationship between the identifier of the HPLMN and the identifier and / or address of the first network element in the HPLMN can be pre-configured in the terrestrial network equipment. The terrestrial network equipment can obtain the identifier and / or address of the first network element based on this mapping relationship and address the first network element. Alternatively, the terrestrial network equipment can also obtain the identifier or address of network elements such as user data storage associated with the HPLMN identifier based on the HPLMN identifier, and obtain the identifier and / or address of the first network element from the network elements such as user data storage associated with the HPLMN identifier, thereby addressing the first network element. It is understood that this application does not limit the method by which the terrestrial equipment addresses the first network element in the HPLMN based on the identifier of the terminal equipment's HPLMN.

[0112] Taking the first network element as the billing function network element as an example, the terrestrial network equipment can obtain (or address) the billing function network element based on the first information, and send user data to the billing function network element. The user data includes the data volume corresponding to the terminal device, which is used by the billing function network element to bill the terminal device based on the data volume. The data volume corresponding to the terminal device can be sent to the terrestrial network equipment by the second network element, or it can be obtained by the terrestrial network equipment by statistically analyzing the data volume of the terminal device received from the second network element. This application does not limit this.

[0113] Taking the first network element as a policy control function network element as an example, the second network element can also send policy control information corresponding to the terminal device to the terrestrial network equipment. The terrestrial network equipment can obtain (or address) the policy control function network element based on the first information, and send user information including the policy control information to the policy control function network element. The policy control function network element then provides communication services to the terminal device based on the policy control information. And / or, the second network element can also send billing information corresponding to the terminal device to the terrestrial network equipment. The terrestrial network equipment can obtain the policy control function network element based on the first information, and send user information including the billing information to the policy control function network element. The policy control function network element then provides the terrestrial network equipment with the identifier or address of the billing function network element corresponding to the terminal device based on the billing information. The billing information can include billing characteristics / attributes, which can characterize the call detail record (CDR) generation method and are used for selecting billing function network elements, such as selecting billing function network elements that support the corresponding CDR generation method.

[0114] Of course, in some implementations, the first information can also refer to the identification information of the terminal device. Alternatively, the terrestrial network device can obtain one or more of the following information based on the terminal device's identification information: the identifier of the HPLMN of the terminal device, the identifier of the first network element in the terrestrial HPLMN, or the address of the first network element in the terrestrial HPLMN, thereby addressing the first network element in the terrestrial HPLMN of the terminal device. The implementation of the terrestrial network device obtaining the identifier of the HPLMN of the terminal device, the identifier of the first network element in the terrestrial HPLMN, or the address of the first network element in the terrestrial HPLMN based on the terminal device's identification information can refer to the above-described implementation of the second network element obtaining the identifier of the HPLMN of the terminal device, the identifier of the first network element in the terrestrial HPLMN, or the address of the first network element in the terrestrial HPLMN based on the terminal device's identification information, and will not be elaborated further.

[0115] Furthermore, it should be noted that the acquisition of the first information by the aforementioned second network element is not limited to the second network element acquiring the first information from the terminal device (such as receiving the terminal device's identifier from the terminal device), or determining the first information (such as the terminal device's identifier, the first network element's identifier, or its address) based on information reported by the terminal device (such as the terminal device's identifier). The aforementioned second network element can also acquire the first information from a third network element, which is a network element in a non-terrestrial network (such as a core network element in a non-terrestrial network), and is different from the second network element. The first information in the third network element can be acquired from the terminal device, determined based on information reported by the terminal device, configured in the third network element, or acquired by the third network element from other non-terrestrial core network elements; this application does not limit this. For example, the third network element can receive the terminal device's identifier, determine the first information (such as the terminal device's identifier, the first network element's identifier, or its address) based on the terminal device's identifier, and the first information can be sent from the third network element to the second network element, or the second network element can request the first information from the third network element.

[0116] The following example uses the first network element as the CHF network element, user data as the data volume corresponding to the terminal device, non-terrestrial network as the network deployed on the satellite, and the second network element as the on-board agent. Figure 8 , Figure 9 , Figure 10 , Figure 12 Specific embodiments, for the above Figure 6 The embodiments are described below.

[0117] PLMN#A, PLMN#B, and PLMN#C, which are provided by satellite (or non-terrestrial networks) as terrestrial network operators, broadcast PLMN ID#A, PLMN ID#B, and PLMN ID#C. A first mapping table is configured in satellite network elements (such as RAN deployed on the satellite, network elements in the CN (such as UDM network elements), or on-board agents). For example, the first mapping table includes the mapping relationship between the identifier of any PLMN providing services via satellite and the identifier and / or address of the CHF network element within that PLMN. Figure 8 This is a second schematic diagram of a communication method provided in an embodiment of this application. The method includes:

[0118] S801: Satellite broadcast of PLMN ID#A, PLMN ID#B and PLMN ID#C.

[0119] When the service link is available—that is, when the communication link between the satellite and the terminal equipment is available—the satellite (such as the RAN deployed on the satellite) can broadcast the identifiers of the PLMN#A, PLMN#B, and PLMN#C it is providing services, i.e., broadcast PLMN ID#A, PLMN ID#B, and PLMN ID#C. Additionally, the satellite can also broadcast information such as S&F indications, indicating that the satellite is in S&F operating mode.

[0120] S802: The satellite establishes a connection with the terminal equipment.

[0121] Terminal devices (such as those belonging to PLMN#A) can initiate access and establish a connection with the satellite. This connection can be established through one or more of the following: attach or register, packet data network (PDN) connection, protocol data unit (PDU) session, or IP multimedia subsystem (IMS) registration. This application does not limit the connection established between the satellite and the terminal device. During the connection establishment process, the terminal device can send its own identifier (such as SUCI) to the CN network element deployed on the satellite, and the CN network element can obtain the terminal device's identifier.

[0122] S803: The terminal device sends uplink data to the satellite, and the satellite receives the uplink data accordingly.

[0123] It is understandable that step S803 is optional. For example, step S803 can be executed only when the terminal device has uplink data to send to the satellite; if the terminal device does not have uplink data to send to the satellite, step S803 will not be executed. Furthermore, uplink data can also be called uplink data transfer (UL data transfer). If uplink data exists, it can be directly sent or forwarded to the onboard agent.

[0124] S804: Terminal device deregisters or deattaches.

[0125] It is understood that step S804 is optional. The terminal device or satellite can trigger the terminal device to register or de-attach and disconnect the terminal device from the satellite if the set conditions are met.

[0126] As an example: after uplink data transmission is completed, the terminal device can register with the satellite (i.e., the non-terrestrial network corresponding to the satellite) and disconnect from the satellite; or, if the duration of no data transmission with the satellite reaches a set duration threshold, the terminal device can register with the satellite (i.e., the non-terrestrial network corresponding to the satellite) and disconnect from the satellite.

[0127] S805: The onboard agent sends first information to the ground network equipment, and the ground network equipment receives the first information accordingly. The first information is used to indicate the CHF network element in the ground HPLMN of the terminal equipment.

[0128] When the feeder link is available, that is, when the communication link between the satellite and the ground network equipment is available, the onboard agent can send the first information to the ground network equipment.

[0129] The on-board agent can obtain the first information based on the HPLMN identifier (i.e., PLMN ID#A) carried in the terminal device's identifier. The first information may include one or more of the following: the HPLMN identifier of the terminal device, the identifier and / or address of the CHF network element in the terrestrial HPLMN.

[0130] As an example: the on-board agent can obtain the HPLMN identifier of the terminal device based on the identifier of the terminal device. The on-board agent can also obtain the identifier and / or address of the CHF network element that has a mapping relationship with the identifier of the HPLMN of the terminal device based on the first mapping table, that is, the identifier and / or address of the CHF network element in the ground HPLMN of the terminal device.

[0131] In addition, the on-board agent can also obtain at least one of the following from other network elements, such as network elements in the RAN or CN (e.g., AMF network element, or SMF network element, etc.): the identifier of the HPLMN, the identifier of the CHF network element, or the address of the CHF network element of the terminal device. Alternatively, other network elements can proactively send at least one of the following to the on-board agent: the identifier of the HPLMN, the identifier of the CHF network element, or the address of the CHF network element of the terminal device.

[0132] Understandably, if the satellite serves only one PLMN, the on-board agent may not need to configure the mapping relationship between the PLMN's identifier and the CHF's identifier and / or address within that PLMN, i.e., it does not need to configure the first mapping table. The on-board agent can directly store at least one of the following information: the identifier of the PLMN served by the satellite, the CHF's identifier, or the CHF's address. Any terminal device that establishes a connection with the satellite belongs to that PLMN (i.e., the terminal device's HPLMN is that PLMN). The first information can be directly obtained based on the identifier, CHF's identifier, or CHF's address stored by the on-board agent.

[0133] It should be noted that the on-board agent can obtain the first information either before or after the power supply link becomes available. This application does not limit the timing of the on-board agent obtaining the first information.

[0134] In some implementations, when forwarding data corresponding to a terminal device to a terrestrial network device, the on-board agent may send at least one of the following information to the terrestrial network device: first information, the amount of data corresponding to the terminal device, and the identifier of the terminal device. Alternatively, if billing and forwarding data are independent, the on-board agent may send the first information and the amount of data corresponding to the terminal device to the terrestrial network device separately, without sending them together with the data corresponding to the terminal device. This application does not limit the method by which the on-board agent sends the data and / or the amount of data (i.e., the amount of data corresponding to the terminal device) and the first information corresponding to the terminal device to the terrestrial network device; the above information may be sent through the same message or through multiple messages.

[0135] S806A: Billing process for terrestrial network equipment and CHF network elements.

[0136] The terrestrial network equipment can obtain (or address) the CHF network element in the terrestrial HPLMN of the terminal equipment based on the first information, and send the data volume and the identifier of the terminal equipment to the CHF network element. The CHF network element can then charge the terminal equipment based on the data volume of the terminal equipment.

[0137] If the ground network equipment does not receive the data volume corresponding to the terminal equipment from the satellite agent, the ground network equipment can count the data volume corresponding to the terminal equipment.

[0138] S806B: The terrestrial network equipment sends the data, first information and / or the identifier of the terminal equipment to the SMF network element.

[0139] Terrestrial network equipment can establish PDU session connections with SMF network elements, sending data and first information corresponding to the terminal device to the SMF network element. The SMF network element then forwards the data corresponding to the terminal device to the destination network node. Furthermore, the SMF network element can calculate the data volume corresponding to the terminal device and, based on the first information, send the data volume and the terminal device's identifier to the CHF network element in the terrestrial HPLMN corresponding to the terminal device. This information is used by the CHF network element to perform billing for the terminal device based on the data volume.

[0140] It is understandable that the aforementioned CHF network element can also be replaced by CSS, with CSS handling billing for the terminal devices. The aforementioned terrestrial network equipment can be a ground station, a terrestrial agent, an SSFC, or other network elements located on the ground (or in a terrestrial network). The second network element sending the first information can be, in addition to the aforementioned satellite agent, other network elements (or satellite network elements) outside of terrestrial networks, such as the AMF network element on a satellite. The aforementioned satellite agent as the second network element is merely an example.

[0141] Taking PLMN#A, PLMN#B, and PLMN#C, which still provide services to terrestrial network operators via satellite (or non-terrestrial networks), and broadcasting PLMN ID#A, PLMN ID#B, and PLMN ID#C as an example, the first piece of information can be the identifier of the terminal device. Based on the identifier of the terminal device, the terrestrial network device can obtain one of the following information: the identifier of the terrestrial HPLMN of the terminal device, the identifier of the CHF network element in the terrestrial HPLMN, or the address of the CHF network element in the terrestrial HPLMN, thereby performing billing operations for the terminal device. Figure 9 This is the third schematic diagram of a communication method provided in an embodiment of this application. The method includes:

[0142] S901: Satellite broadcast of PLMN ID#A, PLMN ID#B and PLMN ID#C.

[0143] When the service link is available, i.e., when the communication link between the satellite and the terminal equipment is available, the satellite (such as the RAN deployed on the satellite) can broadcast the identifiers of the PLMN#A, PLMN#B, and PLMN#C it provides services, i.e., broadcast PLMN ID#A, PLMN ID#B, and PLMN ID#C. Additionally, the satellite can also broadcast information such as S&Findication to indicate whether the satellite is in S&F operating mode.

[0144] S902: The satellite establishes a connection with the terminal equipment.

[0145] Terminal devices (such as those belonging to PLMN#A) establish connections with satellites. These connections can include one or more of the following: attach or registration, PDN connection, PDU session, IMS registration, etc. This application does not limit the specific connection established between the satellite and the terminal device. During the connection establishment process, the terminal device can send its own identifier (such as SUCI) to the CN network element deployed on the satellite, and the CN network element can obtain the terminal device's identifier.

[0146] S903: The terminal device sends uplink data to the satellite, and the satellite receives the uplink data accordingly.

[0147] It is understandable that step S903 is optional. For example, step S903 can be executed only when the terminal device has uplink data to be sent to the satellite; if the terminal device does not have uplink data to be sent to the satellite, step S903 will not be executed. Furthermore, uplink data can also be referred to as UL data transfer. If uplink data exists, it can be directly sent or forwarded to the onboard agent.

[0148] S904: Terminal device deregisters or deattaches.

[0149] It is understood that step S904 is optional. The terminal device or satellite can trigger the terminal device to register or de-attach and disconnect the terminal device from the satellite if the set conditions are met.

[0150] As an example: after uplink data transmission is completed, the terminal device can register with the satellite (i.e., the non-terrestrial network corresponding to the satellite) and disconnect from the satellite; or, if the duration of no data transmission with the satellite reaches a set duration threshold, the terminal device can register with the satellite (i.e., the non-terrestrial network corresponding to the satellite) and disconnect from the satellite.

[0151] S905: The onboard agent sends the terminal device's identifier (i.e., the first information) and the corresponding data to the ground network equipment. Correspondingly, the ground network equipment receives the terminal device's identifier and the corresponding data.

[0152] When the power supply link is available, that is, when the communication link between the satellite and the ground network equipment is available, the on-board agent can send the terminal equipment's identifier and the corresponding data (such as uplink data) to the ground network equipment.

[0153] S906: The terrestrial network device obtains second information based on the identifier of the terminal device. The second information includes at least one of the following: the identifier of the HPLMN of the terminal device, the identifier of the CHF network element in the terrestrial HPLMN of the terminal device, or the address of the CHF network element in the terrestrial HPLMN of the terminal device.

[0154] The terrestrial network equipment can obtain the HPLMN identifier of the terminal device based on the terminal device's identifier. For example, if the terminal device's identifier is SUCI, carrying the terminal device's HPLMN identifier, the terrestrial network equipment can obtain the terminal device's HPLMN identifier from the terminal device's identifier. Alternatively, if the terminal device's identifier is a virtual / temporary identifier that does not carry the terminal device's HPLMN identifier, a field can be added to this virtual / temporary identifier to carry the terminal device's HPLMN identifier. This field is added to the virtual / temporary identifier sent by the on-board agent, and the terrestrial network equipment can also obtain the terminal device's HPLMN identifier from the terminal device's virtual / temporary identifier.

[0155] In some implementations, the terminal device is identified as a virtual / temporary identifier. The third mapping table stored by the terrestrial network device may include a mapping relationship between the virtual / temporary identifier of the terminal device and the second information of the terminal device, or a mapping relationship between the third field of the virtual / temporary identifier of the terminal device and the second information of the terminal device. After the terrestrial network device obtains the virtual / temporary identifier of the terminal device, it can obtain the second information corresponding to the virtual / temporary identifier (or the third field of the virtual / temporary identifier) ​​of the terminal device based on the virtual / temporary identifier of the terminal device and the third mapping table. The second information includes at least one of the following: the identifier of the HPLMN corresponding to the terminal device, the identifier of the CHF network element in the terrestrial HPLMN of the terminal device, or the address of the CHF network element in the terrestrial HPLMN of the terminal device.

[0156] The virtual / temporary identifier of the terminal device can be the terminal device's GUTI, 5G-GUTI, mobile phone number (GPSI), virtual mobile phone number, etc.

[0157] S907A: Billing process for terrestrial network equipment and CHF network elements.

[0158] The terrestrial network equipment can obtain (or address) the CHF network element in the terrestrial HPLMN of the terminal equipment based on the second information, and send the data volume (such as uplink data) corresponding to the terminal equipment and the identifier of the terminal equipment to the CHF network element. The CHF network element can then charge the terminal equipment based on the data volume corresponding to the terminal equipment.

[0159] If the ground network equipment does not receive the data volume corresponding to the terminal equipment from the satellite agent, the ground network equipment can count the data volume corresponding to the terminal equipment.

[0160] S907B: Terrestrial network equipment sends data, secondary information, and the identifier of the terminal equipment to the SMF network element.

[0161] Of course, terrestrial network equipment can also establish PDU session connections with SMF network elements, sending the data and second information corresponding to the terminal device to the SMF network element. The SMF network element then forwards the data corresponding to the terminal device to the destination network node. Furthermore, the SMF network element can calculate the data volume corresponding to the terminal device and, based on the second information, send the data volume and the terminal device's identifier to the CHF network element in the terrestrial HPLMN corresponding to the terminal device. This information is used by the CHF network element to bill the terminal device based on the data volume.

[0162] It is understandable that the aforementioned CHF network element can also be a CSS, which is used to bill terminal devices. The aforementioned terrestrial network equipment can be a ground station, a terrestrial agent, an SSFC, or other network elements located on the ground (or terrestrial network). The second network element sending the first information can be, in addition to the aforementioned satellite agent, other network elements in non-terrestrial networks (or satellite network elements), such as AMF network elements on a satellite. The aforementioned second network element being a satellite agent is merely an example.

[0163] The system provides services to PLMN#A, PLMN#B, and PLMN#C for terrestrial network operators via satellite (or a non-terrestrial network deployed on a satellite). It does not broadcast the identifiers of PLMN#A, PLMN#B, and PLMN#C (such as PLMN ID#A, PLMN ID#B, and PLMN ID#C), but broadcasts a unified identifier for PLMN#D (such as PLMN ID#D). The PLMN identifier in the terminal device's identifier (such as SUCI, SUPI, or IMSI) is the aforementioned unified PLMN#D identifier. The terminal device can report the identifier of the terrestrial HPLMN, thereby supporting terrestrial network devices to address the corresponding CHF network element and supporting billing in NTN scenarios. Figure 10This is a fourth schematic diagram of a communication method provided in an embodiment of this application. The method includes:

[0164] S1001: Satellite Broadcast PLMN ID#D.

[0165] When the service link is available, that is, when the communication link between the satellite and the terminal equipment is available, the satellite can broadcast the identifier of PLMN#D (i.e., the first PLMN), i.e., PLMN ID#D. In addition, the satellite can also broadcast information such as S&F indication, which indicates whether the satellite is in S&F operating mode.

[0166] S1002: The satellite establishes a connection with the terminal equipment.

[0167] Terminal devices (such as those belonging to PLMN#A) can be configured with an identifier corresponding to PLMN ID#D to initiate access and establish a connection with the satellite. The terminal device can establish one or more of the following connections with the satellite: attach or registration, PDN connection, PDU session, IMS registration, etc. This application does not limit the connection established between the satellite and the terminal device. During the connection establishment process, the terminal device can send its own identifier (such as SUCI corresponding to PLMN#D) to the CN network element deployed on the satellite, and the CN network element can obtain the terminal device's identifier.

[0168] S1003: The terminal device sends uplink data to the satellite, and the satellite receives the uplink data accordingly.

[0169] It is understood that step S1003 is optional. For example, step S1003 can be executed only when the terminal device has uplink data to send to the satellite; if the terminal device does not have uplink data to send to the satellite, step S1003 is not executed. Uplink data can also be called uplink data transmission. If uplink data exists, it can be directly sent or forwarded to the on-board agent.

[0170] In addition, the terminal device can also send the identifier of the terminal device's HPLMN (such as PLMN ID#A) through uplink messages, which is used by terrestrial network equipment and other devices to address the CHF network elements in the terrestrial HPLMN of the terminal device.

[0171] It is understood that uplink data and HPLMN identifiers can be sent in the same uplink message or in different uplink messages, and this application does not limit this.

[0172] S1004: Terminal device deregisters or deattaches.

[0173] It is understood that step S1004 is optional. The terminal device or satellite can trigger the terminal device to register or de-attach and disconnect the terminal device from the satellite if the set conditions are met.

[0174] As an example: after uplink data transmission is completed, the terminal device can register with the satellite (i.e., the non-terrestrial network corresponding to the satellite) and disconnect from the satellite; or, if the duration of no data transmission with the satellite reaches a set duration threshold, the terminal device can register with the satellite (i.e., the non-terrestrial network corresponding to the satellite) and disconnect from the satellite.

[0175] S1005: The onboard agent sends the first information to the ground network equipment, and the ground network equipment receives the first information accordingly.

[0176] The first information includes at least one of the following: the identifier of the HPLMN of the terminal device, the identifier of the CHF network element in the ground HPLMN of the terminal device, or the address of the CHF network element in the ground HPLMN of the terminal device, and the identifier of the terminal device. The identifier of the CHF network element in the ground HPLMN of the terminal device, or the address of the CHF network element in the ground HPLMN of the terminal device, can be obtained by the on-board agent based on a pre-configured mapping relationship between the identifier of the HPLMN of the terminal device and the identifier and / or the address of the CHF network element in the ground HPLMN of the terminal device.

[0177] When the power supply link is available, that is, when the communication link between the satellite and the ground network equipment is available, the on-board agent can send the first information to the ground network equipment, and can also send information such as the identifier of the terminal equipment (if the first information does not contain the identifier of the terminal equipment) and the data corresponding to the terminal equipment (such as uplink data).

[0178] It should be noted that the on-board agent can obtain the first information either before or after the power supply link becomes available. This application does not limit the timing of the on-board agent obtaining the first information.

[0179] In some implementations, the on-board agent can send the first information, the data volume corresponding to the terminal device, and the terminal device's identifier to the ground network device when forwarding data corresponding to the terminal device. Alternatively, if billing and forwarding data are independent, the on-board agent can send the first information and the data volume corresponding to the terminal device separately to the ground network device, without sending them together with the data corresponding to the terminal device. This application does not limit the method by which the on-board agent sends the data and / or data volume (i.e., the data volume of the data corresponding to the terminal device) and the first information to the ground network device; the above information can be sent through the same message or through multiple messages.

[0180] S1006A: Billing process for terrestrial network equipment and CHF network elements.

[0181] The terrestrial network equipment can obtain (or address) the CHF network element in the terrestrial HPLMN of the terminal equipment based on the first information, and send the data volume and the identifier of the terminal equipment to the CHF network element. The CHF network element can then charge the terminal equipment based on the data volume of the terminal equipment.

[0182] If the ground network equipment does not receive the data volume corresponding to the terminal equipment from the satellite agent, the ground network equipment can count the data volume corresponding to the terminal equipment.

[0183] S1006B: The terrestrial network equipment sends the data, first information, and the identifier of the terminal equipment to the SMF network element.

[0184] Terrestrial network equipment can establish PDU session connections with SMF network elements, sending data and first information corresponding to the terminal device to the SMF network element. The SMF network element then forwards the data corresponding to the terminal device to the destination network node. Furthermore, the SMF network element can calculate the data volume corresponding to the terminal device and, based on the first information, send the data volume and the terminal device's identifier to the CHF network element in the terrestrial HPLMN corresponding to the terminal device. This information is used by the CHF network element to perform billing for the terminal device based on the data volume.

[0185] It is understandable that the aforementioned CHF network element can also be a CSS, which is used to bill terminal devices. The aforementioned terrestrial network equipment can be a ground station, a terrestrial agent, an SSFC, or other network elements located on the ground (or terrestrial network). The second network element sending the first information can be, in addition to the aforementioned satellite agent, other network elements in non-terrestrial networks (or satellite network elements), such as AMF network elements on a satellite. The aforementioned second network element being a satellite agent is merely an example.

[0186] The uplink message for the identifier of the HPLMN carrying the terminal equipment can be a random access message, registration request, authentication or certification response, NAS security completion message, AS security completion message, session establishment request, or TAU request, etc. Figure 11 This illustration shows a possible method for sending the identifier of an HPLMN (Hyperlink Node Name) of a terminal device via uplink messages, as provided in this application embodiment. It should be noted that... Figure 11 The AMF, AUSF, or UDM network elements mentioned are network elements in the CN deployed on the satellite.

[0187] Option A: Include the HPLMN identifier of the terminal device in the registration request, as shown below. Figure 11 Step S1101 in the process.

[0188] S1101: The terminal device sends a registration request to the AMF network element.

[0189] When the service link is available, i.e., when the communication link between the satellite and the terminal device is available, the satellite can broadcast the identifier of the first PLMN (e.g., PLMN#D). The terminal device can be configured with a dual subscriber identity module (SIM), such as a SIM card corresponding to PLMN#D and a SIM card corresponding to the HPLMN (e.g., PLMN#A) of the terminal device. After receiving the identifier of the first PLMN broadcast by the satellite, the terminal device can send a registration request to the AMF network element on the satellite. The registration request can carry the SUCI of the terminal device and the identifier of the HPLMN of the terminal device. The SUCI of the terminal device is the SUCI of the first PLMN of the terminal device, that is, the network identifier in the SUCI of the terminal device is the identifier of the first PLMN (e.g., PLMN#D).

[0190] One possible implementation involves configuring a subscriber identity module (SIM) in the terminal device, such as a SIM card corresponding to PLMN#D. The terminal device also includes information about the terrestrial home network (e.g., PLMN#A) corresponding to PLMN#D. After receiving the identifier of the first PLMN broadcast by satellite, the terminal device can send a registration request to the AMF network element on the satellite. This registration request can carry the terminal device's SUCI and the identifier of its HPLMN. The terminal device's SUCI is the SUCI of the first PLMN corresponding to the terminal device; that is, the network identifier in the terminal device's SUCI is the identifier of the first PLMN (e.g., PLMN#D).

[0191] S1102: The AMF network element adds the service network name to the registration request and sends the registration request to the AMF network element on the satellite.

[0192] The service network name includes the identifier of the first PLMN broadcast by satellite.

[0193] S1103: The AUSF network element sends an authentication request (Authenticate_GetRequest) to the UDM network element on the satellite.

[0194] The authentication request may include information such as the terminal device's SUCI, HPLMN identifier, and service network name.

[0195] S1104: UDM network element decrypts SUCI to obtain the SUPI of terminal device and stores the mapping relationship between the SUPI of terminal device and the identifier of HPLMN.

[0196] UDM network elements can decrypt the SUCI of terminal devices, obtain the SUPI of terminal devices, and store the mapping relationship between the SUPI of terminal devices and the identifiers of HPLMN. The mapping relationship between the SUPI of terminal devices and the identifiers of HPLMN can be sent by the UDM network element to other satellite network elements, such as satellite agents, AMF network elements, etc., or other satellite network elements can request the mapping relationship between the SUPI of terminal devices and the identifiers of HPLMN from the UDM network element.

[0197] S1105: UDM network elements can send authentication retrieval responses (Authentication_GetResponse) to AUSF network elements.

[0198] The authentication response may carry the 5G home environment authentication vector (HE AV) and the terminal device's SUPI. The 5G HE AV is the authentication vector and may contain random data (RAND), an authentication token (AUTN), the expected response (XRES*), and the AUSF key (K). AUSF ).

[0199] S1106: AUSF network elements can send authentication responses (such as authentication_authenticate response) to AMF network elements. These responses may carry the 5G serving environment authentication vector (SE AV) and the terminal device's SUPI. The SUPI is optional. The 5G SE AV may contain RAND, AUTN, and HXRES*, where HXRES* is a hash value generated based on XRES*.

[0200] Option B: Include the HPLMN identifier of the terminal device in the authentication response, refer to... Figure 11 Step S1108 in the process.

[0201] S1107: The AMF network element sends an authentication request to the terminal device. This authentication request may include 5G SE AV, which contains RAND and AUTN.

[0202] S1108: After the terminal device completes network authentication (e.g., authentication based on 5G SE AV), it can send an authentication response to the AMF network element. The authentication response can carry the identifier of the terminal device's HPLMN.

[0203] S1109: AMF network elements can send authentication requests (such as authentication_authenticate request) to AUSF network elements. The authentication request carries the identifier of the HPLMN of the terminal device.

[0204] The AUSF network element can store the mapping relationship between the SUPI and HPLMN identifiers of terminal devices. The AUSF network element can send the mapping relationship between the SUPI and HPLMN identifiers of terminal devices to other satellite network elements, such as satellite agents and AMF network elements, or other satellite network elements can request the mapping relationship between the SUPI and HPLMN identifiers of terminal devices from the AUSF network element.

[0205] S1110: AUSF completes the authentication of the network side and sends an authentication response (such as Authentication_Authenticate Response) to the AMF network element.

[0206] AMF network elements can also store the mapping relationship between the SUPI of terminal devices and the identifiers of HPLMN. The mapping relationship between the SUPI and HPLMN identifiers of terminal devices can be sent by the AMF network element to other satellite network elements, such as satellite agents, or other satellite network elements can request the mapping relationship between the SUPI and HPLMN identifiers of terminal devices from the AMF network element.

[0207] Option C: Include the HPLMN identifier of the terminal device in the NAS security completion message, refer to... Figure 11 Step S1112 in the process.

[0208] S1111: The AMF network element sends a NAS security mode command message to the terminal device.

[0209] The NAS security mode command message can carry information such as the security algorithm selected by NAS negotiation and the security capabilities of the terminal device.

[0210] S1112: The terminal device sends a NAS security mode complete message to the AMF network element. The NAS security mode complete message carries the HPLMN identifier.

[0211] AMF network elements can also store the mapping relationship between the SUPI of terminal devices and the identifiers of HPLMN. The mapping relationship between the SUPI and HPLMN identifiers of terminal devices can be sent by the AMF network element to other satellite network elements, such as satellite agents, or other satellite network elements can request the mapping relationship between the SUPI and HPLMN identifiers of terminal devices from the AMF network element.

[0212] Option D: The identifier of the terminal device's HPLMN is carried in the Access Layer (AS) security completion message, as shown in the following example. Figure 11 Step S1114 in the process.

[0213] S1113: After NAS security negotiation is established, the RAN can send an AS security mode command message to the terminal device. The AS security mode command message can carry information such as the security algorithm selected during AS negotiation.

[0214] S1114: The terminal device sends an AS security mode complete message to the RAN. The AS security mode complete message may carry the HPLMN identifier.

[0215] The RAN can store the mapping relationship between the SUPI of the terminal equipment and the identifier of the HPLMN. The RAN network element can send the mapping relationship between the SUPI of the terminal equipment and the identifier of the HPLMN to other satellite network elements, such as satellite agents, AMF network elements, etc., or other satellite network elements can request the mapping relationship between the SUPI of the terminal equipment and the identifier of the HPLMN from the RAN.

[0216] S1115: AMF sends Registration Accept to the terminal device.

[0217] Option E: Include the HPLMN identifier of the terminal device in the session establishment request message (such as a PDU session establishment request), refer to... Figure 11 Step S1106 in the process.

[0218] S1116: The terminal device sends a PDU session request to the AMF network element, carrying the identifier of the terminal device's HPLMN in the PDU session request.

[0219] AMF network elements can also store the mapping relationship between the SUPI and HPLMN identifiers of terminal devices. The mapping relationship between the SUPI and HPLMN identifiers of terminal devices can be sent by the AMF network element to other satellite network elements, such as satellite agents, AMF network elements, etc., or other satellite network elements can request the mapping relationship between the SUPI and HPLMN identifiers of terminal devices from the AMF network element.

[0220] Using satellite (or non-terrestrial network) to provide services for PLMN#A, PLMN#B, and PLMN#C of terrestrial network operators, the system does not broadcast the identifiers of PLMN#A, PLMN#B, and PLMN#C (such as PLMN ID#A, PLMN ID#B, and PLMN ID#C), but broadcasts a unified identifier of PLMN#D (such as PLMN ID#D). The PLMN identifier in the terminal device identifier (such as SUCI, SUPI, or IMSI) is the aforementioned unified PLMN#D identifier. The terminal device can report the identifier of the terrestrial HPLMN. The UDM network element is configured with a mapping relationship between the terminal device identifier (such as SUPI) and the HPLMN identifier, thereby supporting terrestrial network devices to address the corresponding CHF network element. This supports billing in NTN scenarios as an example. Figure 12 The fifth schematic diagram of the communication method provided in the embodiments of this application includes:

[0221] S1201: Satellite Broadcast PLMN ID#D.

[0222] When the service link is available, that is, when the communication link between the satellite and the terminal equipment is available, the satellite can broadcast the identifier of the first PLMN (such as PLMN#D), i.e., PLMN ID#D.

[0223] S1202: The terminal device sends a registration request to the AMF network element.

[0224] In one possible implementation, the terminal device can be configured with dual SIM cards, such as a SIM card corresponding to PLMN#D and a SIM card corresponding to the HPLMN (e.g., PLMN#A) of the terminal device. After receiving the identifier of the first PLMN broadcast by the satellite, the terminal device can send a registration request to the AMF network element on the satellite. The registration request can carry the SUCI of the terminal device, where the SUCI of the terminal device is the SUCI of the first PLMN of the terminal device, and the network identifier in the SUCI of the terminal device is the identifier of the first PLMN.

[0225] In another possible implementation, a single SIM card, such as a SIM card corresponding to PLMN#D, can be configured in the terminal device. The terminal device is also configured with HPLMN (such as PLMN#A) information corresponding to PLMN#D. After receiving the identifier of the first PLMN broadcast by the satellite, the terminal device can send a registration request to the AMF network element on the satellite. The registration request can carry the SUCI of the terminal device, where the SUCI of the terminal device is the SUCI of the first PLMN corresponding to the terminal device, and the network identifier in the SUCI of the terminal device is the identifier of the first PLMN.

[0226] S1203: The AMF network element adds the service network name to the registration request and sends the registration request to the AMF network element on the satellite.

[0227] The service network name includes the identifier of the first PLMN broadcast by satellite.

[0228] S1204: The AUSF network element sends an authentication request (Authenticate_GetRequest) to the UDM network element on the satellite.

[0229] The authentication request can include information such as the terminal device's SUCI and service network name.

[0230] S1205: The UDM network element obtains the HPLMN identifier of the terminal device based on the identifier of the terminal device.

[0231] UDM network elements can decrypt the SUCI of terminal devices to obtain the SUPI of the terminal devices. A mapping relationship between the identifier of a terminal device (such as SUPI) and the identifier of an HPLMN can be pre-configured in the UDM network element. After obtaining the SUPI of a terminal device, the UDM network element can obtain the identifier of the HPLMN mapped to that SUPI based on the mapping relationship between the terminal device identifier (such as SUPI) and the HPLMN identifier.

[0232] UDM network elements can also send the mapping relationship between the SUPI and HPLMN identifiers of the terminal device to other satellite network elements, such as satellite agents and AMF network elements, or other satellite network elements can request the mapping relationship between the SUPI and HPLMN identifiers of the terminal device from the UDM network element.

[0233] S1206: UDM network elements can send an authentication retrieval response (Authentication_GetResponse) to AUSF network elements.

[0234] The authentication response can carry the 5G HE AV and the terminal device's SUPI, as well as the HPLMN identifier of the terminal device. The 5G HE AV is the authentication vector.

[0235] S1207: AUSF network elements can send authentication responses (such as Authenticatione_Authenticate Response) to AMF network elements. These responses can carry 5G SE AV and the terminal device's SUPI. The 5G SE AV is the authentication vector, while the SUPI is optional.

[0236] S1208: The AMF network element sends an authentication request to the terminal device, and the terminal device sends an authentication response to the AMF.

[0237] Among them, 5G SE AV can be carried in the authentication request sent by the AMF network element to the terminal device.

[0238] S1209: The AMF network element sends an authentication request (such as Authentication_Authenticate Request) to the AUSF network element.

[0239] S1210: The AFS completes authentication of the network side and sends an authentication response (Authentication_Authenticate Response) to the AMF network element. The authentication response may include the identifier of the terminal device (such as SUPI) and the identifier of the HPLMN.

[0240] AMF network elements can also store the mapping relationship between the SUPI of terminal devices and the identifiers of HPLMN. The mapping relationship between the SUPI and HPLMN identifiers of terminal devices can be sent by the AMF network element to other satellite network elements, such as satellite agents, or other satellite network elements can request the mapping relationship between the SUPI and HPLMN identifiers of terminal devices from the AMF network element.

[0241] S1211: The terminal device completes the secure establishment with the satellite, registration response, and PDU session establishment.

[0242] S1212: The terminal device sends uplink data to the AMF network element.

[0243] It is understood that step S1212 is optional. For example, step S1212 can be executed only when the terminal device has uplink data to send to the satellite; if the terminal device does not have uplink data to send to the satellite, step S1212 will not be executed. Uplink data can also be called uplink data transmission. If uplink data exists, it can be directly sent or forwarded to the on-board agent.

[0244] S1213: AMF network element obtains first information.

[0245] AMF network elements can decrypt the SUPI of the terminal device based on the SUCI carried in the uplink message, and obtain the first information, such as the identifier of the HPLMN corresponding to the terminal device, based on the stored mapping relationship between the SUPI and the HPLMN identifier.

[0246] It is understood that the first information includes at least one of the following: the identifier of the HPLMN of the terminal device, the identifier of the CHF network element in the terrestrial HPLMN of the terminal device, or the address of the CHF network element in the terrestrial HPLMN of the terminal device. The identifier or address of the CHF network element in the terrestrial HPLMN of the terminal device can be obtained by the AMF network element based on a pre-configured mapping relationship between the identifier of the HPLMN of the terminal device and the identifiers and / or addresses of the CHF network elements in the terrestrial HPLMN of the terminal device.

[0247] S1214: The AMF network element sends the first information and the data corresponding to the terminal device (such as uplink data) to the satellite agent.

[0248] S1215: The on-board agent sends the first information and the terminal equipment's data to the ground network equipment, and the ground network equipment receives the first information and the terminal equipment's data (such as uplink data).

[0249] When the power supply link is available, that is, when the communication link between the satellite and the ground network equipment is available, the on-board agent can send the first information to the ground network equipment, and can also send information such as the identifier of the terminal equipment and the data corresponding to the terminal equipment to the ground network equipment.

[0250] It should be noted that the on-board agent can obtain the first information either before or after the power supply link becomes available. This application does not limit the timing of the on-board agent obtaining the first information.

[0251] In some implementations, the on-board agent can send the first information, the data volume corresponding to the terminal device, and the terminal device's identifier to the ground network device when forwarding data corresponding to the terminal device. Alternatively, if billing and forwarding data are independent, the on-board agent can send the first information and the data volume corresponding to the terminal device separately to the ground network device, without sending them together with the data corresponding to the terminal device. This application does not limit the method by which the on-board agent sends the data and / or data volume (i.e., the data volume of the data corresponding to the terminal device) and the first information to the ground network device; the above information can be sent through the same message or through multiple messages.

[0252] S1216: Billing process for terrestrial network equipment and CHF network elements.

[0253] The terrestrial network equipment can obtain (or address) the CHF network element in the HPLMN of the terminal device based on the first information, and send the data volume corresponding to the terminal device and the identifier of the terminal device to the CHF network element. This information is used by the CHF network element to bill the terminal device based on the data volume corresponding to the terminal device. If the terrestrial network equipment does not receive the data volume corresponding to the terminal device from the satellite agent, the terrestrial network equipment can calculate the data volume corresponding to the terminal device.

[0254] Alternatively, terrestrial network equipment can establish a PDU session connection with an SMF network element, sending the data corresponding to the terminal device and first information to the SMF network element. The SMF network element then forwards the data corresponding to the terminal device to the destination node. The SMF network element can also calculate the data volume corresponding to the terminal device and, based on the first information, send the data volume and the terminal device's identifier to the CHF network element in the terrestrial HPLMN corresponding to the terminal device. This information is used by the CHF network element to bill the terminal device based on the data volume. It is understood that the aforementioned CHF network element can also be a CSS (Cybernetic Component Controller), which then performs billing for the terminal device.

[0255] The aforementioned terrestrial network equipment can be a ground station, a ground agent, an SSFC, or other network elements located on the ground (or in a terrestrial network). The second network element sending the first information can be, in addition to the aforementioned on-board agent, other network elements (or on-board network elements) outside of terrestrial networks, such as AMF network elements on a satellite. The use of an on-board agent as the second network element is merely an example. For instance, in... Figure 12 In the example, the AMF network element can have the function of S&F, and the AMF network element can directly send the first information and the corresponding data of the terminal device to the ground network device.

[0256] The communication device provided in the embodiments of this application will be described below. Please refer to... Figure 13 , Figure 13 This is a schematic diagram of a communication device according to an embodiment of this application. The communication device may include units or modules corresponding to all or part of the steps in the above method embodiments, and can be used to execute the steps executed by the second network element or terrestrial network device in the above embodiments. Please refer to the relevant descriptions in the above method embodiments for details.

[0257] like Figure 13 As shown, the communication device 1300 includes a processing unit 1310 and an interface unit 1320, wherein the processing unit 1310 may be a processor or a processing circuit, and the interface unit 1320 may be a transceiver unit or an input / output interface. The communication device 1300 can be used to implement the steps performed by the second network element or terrestrial network equipment in the above embodiments.

[0258] When the communication device 1300 is used to implement the steps performed by the second network element in the above embodiments:

[0259] The processing unit 1310 is used to acquire first information, which is used to indicate a first network element, the first network element being a network element in the ground HPLMN of the terminal device; wherein a user data storage network element is deployed on the second network element.

[0260] Interface unit 1320 is used to send first information to ground network equipment.

[0261] In one possible design, the first network element is a billing function network element, and the interface unit 1320 is also used to send data corresponding to the terminal device or the amount of data corresponding to the terminal device to the terrestrial network equipment. The amount of data is determined according to the data corresponding to the terminal device.

[0262] In one possible design, the first network element is a policy control function network element, and the interface unit 1320 is also used to send policy control information and / or billing information corresponding to the terminal equipment to the terrestrial network equipment.

[0263] In one possible design, the non-terrestrial network broadcasts the identifier of at least one PLMN, and the HPLMN belongs to at least one PLMN.

[0264] In one possible design, the first network element is the network element that processes or obtains user information corresponding to the terminal device.

[0265] In one possible design, the first information includes the identifier of the HPLMN. When the processing unit 1310 obtains the first information, it is specifically used to obtain the identifier of the HPLMN carried in the identifier of the terminal device.

[0266] In one possible design, the first information includes the identifier and / or address of the first network element. When the processing unit 1310 obtains the first information, it is specifically used to obtain the identifier and / or address of the first network element based on the identifier of the terminal device and the first mapping table. The first mapping table includes at least one of the following: the mapping relationship between the identifier of the terminal device and the identifier and / or address of the first network element; or, the mapping relationship between the first field in the identifier of the terminal device and the identifier and / or address of the first network element.

[0267] In one possible design, the identifier of the first PLMN is broadcast via a non-terrestrial network, and the first PLMN is different from the HPLMN.

[0268] In one possible design, the first information includes the identifier of the HPLMN. When the processing unit 1310 obtains the first information, it is specifically used to receive an uplink message from the terminal device through the interface unit 1320, wherein the uplink message carries the identifier of the HPLMN; or, based on the identifier of the terminal device, the identifier of the HPLMN is obtained, wherein the identifier of the terminal device carries the identifier of the first PLMN and the identifier of the HPLMN.

[0269] In one possible design, the uplink message includes at least one of the following: random access message, registration or attach request, authentication or authorization response, NAS security mode completion message, AS security mode completion message, session establishment request, or TAU request.

[0270] In one possible design, the first information includes the identifier of the HPLMN. When the processing unit 1310 obtains the first information, it is specifically used to obtain the identifier of the HPLMN based on the identifier of the terminal device and the second mapping table. The second mapping table includes at least one of the following: the mapping relationship between the identifier of the terminal device and the identifier of the HPLMN; or, the mapping relationship between the second field in the identifier of the terminal device and the identifier of the HPLMN.

[0271] In one possible design, the first information includes the identifier of the terminal device.

[0272] In one possible design, the identifier of the terminal device includes one or more of the following: SUPI, IMSI, SUCI, GUTI, 5G-GUTI, or GPSI.

[0273] When the communication device 1300 is used to implement the steps performed by the terrestrial network device in the above embodiments:

[0274] Interface unit 1320 is used to receive first information from a second network element, the first information being used to indicate a first network element, the first network element being a network element in the terrestrial HPLMN of the terminal device, wherein the second network element is a network element in a non-terrestrial network, and a user data storage network element is deployed in the non-terrestrial network; and to send user information corresponding to the terminal device to the first network element.

[0275] In one possible design, the first network element is a billing function network element. The interface unit 1320 is also used to receive data or the amount of data corresponding to the terminal device from the non-terrestrial network. The amount of data is determined based on the data corresponding to the terminal device. The user information includes the amount of data corresponding to the terminal device. The first network element bills the terminal device based on the amount of data.

[0276] In one possible design, the first network element is a policy control function network element, and the interface unit 1320 is also used to receive policy control information and / or billing information corresponding to the terminal equipment from the non-terrestrial network; wherein, the user information includes policy control information, and the first network element provides communication services to the terminal equipment based on the policy control information; and / or, the user information includes billing information, and the first network element provides the terrestrial network equipment with the identifier or address of the billing function network element corresponding to the terminal equipment based on the billing information.

[0277] In one possible design, the first network element is a network element that processes or acquires user information corresponding to the terminal device.

[0278] In one possible design, the non-terrestrial network broadcasts the identifier of at least one PLMN, and the HPLMN belongs to at least one PLMN.

[0279] In one possible design, the identifier of the first PLMN is broadcast via a non-terrestrial network, and the first PLMN is different from the HPLMN.

[0280] In one possible design, the first information includes at least one of the following: the identifier of the HPLMN, the identifier of the first network element, or the address of the first network element.

[0281] In one possible design, the first information includes the identifier of the terminal device; the processing unit 1310 is used to obtain second information based on the first information, the second information including at least one of the identifier of the HPLMN, the identifier of the first network element, or the address of the first network element; when the interface unit 1320 sends the user information corresponding to the terminal device to the first network element, it is specifically used to send the user information corresponding to the terminal device to the first network element based on the second information.

[0282] In one possible design, the terminal device is identified as a virtual or temporary identifier, which carries the identifier of the HPLMN.

[0283] In one possible design, the identifier of the terminal device is a virtual or temporary identifier. When the processing unit 1310 obtains the second information based on the first information, it is specifically used to obtain the second information based on the virtual or temporary identifier of the terminal device and a third mapping table. The third mapping table includes at least one of the following: the mapping relationship between the virtual or temporary identifier of the terminal device and the second information; or, the mapping relationship between the third field in the virtual or temporary identifier of the terminal device and the second information.

[0284] In one possible design, the identifier of the terminal device includes one or more of the following: SUPI, IMSI, SUCI, GUTI, 5G-GUTI, or GPSI.

[0285] like Figure 14 As shown, this application also provides a communication device 1400, including a processor 1410 and a communication interface 1420. The processor 1410 and the communication interface 1420 are coupled to each other. It is understood that the communication interface 1420 can be a transceiver, an input / output interface, an input interface, an output interface, an interface circuit, etc. Optionally, the communication device 1400 may further include a memory 1430 for storing instructions executed by the processor 1410, or storing input data required by the processor 1410 to execute instructions, or storing data generated after the processor 1410 executes instructions. The memory 1430 can be a physically independent unit, or it can be coupled to the processor 1410, or the processor 1410 may include the memory 1430.

[0286] When the communication device 1400 is used to implement the steps executed by the second network element or terrestrial network device in the above embodiments, the processor 1410 can be used to implement the function of the processing unit 1310, and the communication interface 1420 can be used to implement the function of the interface unit 1320.

[0287] In this application embodiment, the processor (e.g., processor 1410) can be one or more central processing units (CPUs). If the processor is a CPU, it can be a single-core CPU or a multi-core CPU. The processor can also be one or a combination of several of the following: CPU, general-purpose processor, application-specific integrated circuit (ASIC), digital signal processor (DSP), microprocessor unit (MPU), microcontroller unit (MCU), graphics processing unit (GPU), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, artificial intelligence processor (AI processor), or neural processing unit (NPU). The processor can implement or execute the methods, steps, and logic block diagrams disclosed in this application embodiment. The steps of the methods disclosed in this application embodiment can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0288] In this embodiment, the memory (e.g., memory 1430) may include, but is not limited to, cache, read-only memory (ROM), random access memory (RAM), synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. Memory is any other medium capable of carrying or storing desired program code having an instruction or data structure form and accessible by a computer, but is not limited thereto. The memory in this embodiment may also be a circuit or any other device capable of implementing storage functions for storing computer programs or instructions, and / or data.

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

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

[0291] In the various embodiments of 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. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0292] Additionally, it should be understood that in the embodiments of this application, the term "exemplary" is used to indicate that it is an example, illustration, or description. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0293] In this application, "sending information" can be understood as one device sending information to another device, or as one logic module within a device sending information to another logic module. For example, "device A sending information" can be understood as device A sending information to another device (device B), or as logic module 1 in device A sending information to logic module 2 in device A. In this application, "receiving information" can be understood as one device receiving information from another device, or as one logic module within a device receiving information from another logic module. For example, "device A receiving information" can be understood as device A receiving information from another device (such as device B), or as logic module 1 in device A receiving information from logic module 2 in device A. In this application, "sending information to… (e.g., device B)" or the related illustrations in the accompanying drawings can be understood as the destination of the information being device B. This can include sending information directly or indirectly to device B. The phrases "receiving information from... (e.g., device A)," "receiving information from... (e.g., device A)," or "receiving information sent by (e.g., device A)," or the relevant illustrations in the accompanying drawings, can be understood as indicating that the source of the information is device A, which may include receiving information directly or indirectly from device A. The information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be repeated here.

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

Claims

1. A communication method, characterized in that, Applied to a second network element, which is a network element in a non-terrestrial network, wherein a user data storage network element is deployed in the non-terrestrial network, including: Obtain first information, which is used to indicate a first network element, and the first network element is a network element in the home public land mobile network (HPLMN) of the terminal device. Send the first information to the ground network equipment.

2. The method as described in claim 1, characterized in that, The first network element is a billing function network element, and the method further includes: The data corresponding to the terminal device or the amount of data corresponding to the terminal device is sent to the terrestrial network equipment, wherein the amount of data is determined based on the data corresponding to the terminal device.

3. The method as described in claim 1, characterized in that, The first network element is a policy control function network element, and the method further includes: Send policy control information and / or billing information corresponding to the terminal device to the terrestrial network equipment.

4. The method according to any one of claims 1-3, characterized in that, The first network element is a network element that processes or acquires user information corresponding to the terminal device.

5. The method according to any one of claims 1-4, characterized in that, The non-terrestrial network broadcasts the identifier of at least one Public Land Mobile Network (PLMN), to which the HPLMN belongs.

6. The method as described in claim 5, characterized in that, The first information includes the identifier of the HPLMN, and obtaining the first information includes: Obtain the identifier of the HPLMN carried in the identifier of the terminal device.

7. The method as described in claim 5, characterized in that, The first information includes the identifier and / or address of the first network element, and obtaining the first information includes: Based on the identifier of the terminal device and the first mapping table, the identifier and / or address of the first network element are obtained, wherein the first mapping table includes at least one of the following: The mapping relationship between the identifier of the terminal device and the identifier and / or address of the first network element; or, The mapping relationship between the first field in the identifier of the terminal device and the identifier and / or address of the first network element.

8. The method according to any one of claims 1-4, characterized in that, The non-terrestrial network broadcasts the identifier of the first PLMN, which is different from the HPLMN.

9. The method as described in claim 8, characterized in that, The first information includes the identifier of the HPLMN, and obtaining the first information includes: Receive an uplink message from the terminal device, the uplink message carrying the identifier of the HPLMN; or, Based on the identifier of the terminal device, the identifier of the HPLMN is obtained, wherein the identifier of the terminal device carries the identifier of the first PLMN and the identifier of the HPLMN.

10. The method as described in claim 9, characterized in that, The uplink message includes at least one of the following: Random access uplink messages, registration or attach requests, authentication or authorization responses, non-access stratum (NAS) security mode completion messages, access stratum (AS) security mode completion messages, session establishment requests, or tracking area update (TAU) requests.

11. The method as described in claim 8, characterized in that, The first information includes the identifier of the HPLMN, and obtaining the first information includes: Based on the identifier of the terminal device and the second mapping table, the identifier of the HPLMN is obtained, wherein the second mapping table includes at least one of the following: The mapping relationship between the identifier of the terminal device and the identifier of the HPLMN; or, The mapping relationship between the second field of the terminal device's identifier and the identifier of the HPLMN.

12. The method according to any one of claims 1-11, characterized in that, The first information includes the identifier of the terminal device.

13. The method according to any one of claims 1-12, characterized in that, The identifier of the terminal device includes one or more of the following: Permanent User Identifier (SUPI), International Mobile Subscriber Identity (IMSI), Hidden User Identifier (SUCI), Globally Unique Temporary User Equipment Identifier (GUTI), 5G Globally Unique Temporary UE Identifier (5G-GUTI), or Universal Public User Identifier (GPSI).

14. A communication method, characterized in that, Applications in terrestrial network equipment, including: Receive first information from the second network element, the first information being used to indicate the first network element, the first network element being a network element in the home public land mobile network (HPLMN) of the terminal device, wherein the second network element is a network element in a non-terrestrial network, and the non-terrestrial network is equipped with a user data storage network element. Send the user information corresponding to the terminal device to the first network element.

15. The method as described in claim 14, characterized in that, The first network element is a billing function network element, and the method further includes: Receive data or the amount of data corresponding to the terminal device from the non-terrestrial network, wherein the amount of data is determined based on the data corresponding to the terminal device; The user information includes the amount of data corresponding to the terminal device, and the first network element bills the terminal device based on the amount of data.

16. The method as described in claim 14, characterized in that, The first network element is a policy control function network element, and the method further includes: Receive policy control information and / or billing information corresponding to the terminal device from the non-terrestrial network; Wherein, the user information includes the policy control information, and the first network element provides communication services to the terminal device based on the policy control information; and / or, The user information includes the billing information, and the first network element provides the terrestrial network equipment with the identifier or address of the billing function network element corresponding to the terminal device based on the billing information.

17. The method according to any one of claims 14-16, characterized in that, The first network element is a network element that processes or acquires user information corresponding to the terminal device.

18. The method according to any one of claims 14-17, characterized in that, The non-terrestrial network broadcasts the identifier of at least one Public Land Mobile Network (PLMN), to which the HPLMN belongs.

19. The method according to any one of claims 14-17, characterized in that, The non-terrestrial network broadcasts the identifier of the first PLMN, which is different from the HPLMN.

20. The method according to any one of claims 14-19, characterized in that, The first information includes at least one of the following: The identifier of the HPLMN, the identifier of the first network element, or the address of the first network element.

21. The method according to any one of claims 14-19, characterized in that, The first information includes the identifier of the terminal device; Sending the user information corresponding to the terminal device to the first network element includes: Based on the first information, second information is obtained, the second information including at least one of the identifier of the HPLMN, the identifier of the first network element, or the address of the first network element; Based on the second information, the user information corresponding to the terminal device is sent to the first network element.

22. The method as described in claim 21, characterized in that, The terminal device is identified as a virtual or temporary identifier, which carries the identifier of the HPLMN.

23. The method as described in claim 21, characterized in that, The identifier of the terminal device is a virtual or temporary identifier, and the step of obtaining the second information based on the first information includes: The second information is obtained based on the virtual or temporary identifier of the terminal device and a third mapping table, wherein the third mapping table includes at least one of the following: The mapping relationship between the virtual or temporary identifier of the terminal device and the second information; or... The mapping relationship between the third field in the virtual or temporary identifier of the terminal device and the second information.

24. The method according to any one of claims 14-23, characterized in that, The identifier of the terminal device includes one or more of the following: Permanent User Identifier (SUPI), International Mobile Subscriber Identity (IMSI), Hidden User Identifier (SUCI), Globally Unique Temporary User Equipment Identifier (GUTI), 5G Globally Unique Temporary UE Identifier (5G-GUTI), or Universal Public User Identifier (GPSI).

25. A communication device, characterized in that, It includes modules or units for performing the method as described in any one of claims 1-13; or, it includes modules or units for performing the method as described in any one of claims 14-24.

26. A computer program product, characterized in that, It includes a computer program or instructions that, when executed by a processor, cause the method of any one of claims 1-13 to be implemented; or cause the method of any one of claims 14-24 to be implemented.

27. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions that, when executed by a processor, cause the method as described in any one of claims 1-13 to be implemented; or cause the method as described in any one of claims 14-24 to be implemented.

28. A communication system, characterized in that, include: The second network element and the terrestrial network equipment, wherein the second network element is a network element in the non-terrestrial network, and the non-terrestrial network is equipped with a user data storage network element; The second network element is used to perform the method as described in any one of claims 1-13; The terrestrial network device is used to perform the method as described in any one of claims 14-24.

Images