Information association method, satellite communication method, AMF entity, and communication system

Abstract

The present disclosure provides an information association method, a satellite communication method, an AMF entity, and a communication system. The information association method comprises: in an AMF entity, configuring an association relationship between an access node identifier and satellite backhaul information.

Description

Information association method, satellite communication method, AMF entity and communication system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure is based on and claims priority to an application with CN application number 202311756279.1 and filing date December 20, 2023. The disclosure content of this CN application is hereby incorporated into this disclosure as a whole. Technical Field

[0003] The present disclosure relates to the field of communications, and in particular to an information association method, a satellite communication method, an AMF (Access and Mobility Management Function) entity, and a communication system. Background Art

[0004] The current 3GPP (3rd Generation Partnership Project) Rel-18 proposes an architecture for using satellites as backhaul between the access network (R)AN and 5GC, involving scenarios where single satellites, multi-hop satellites between satellites, and satellites of various orbit types are used for backhaul.

[0005] Summary of the Invention

[0006] In a first aspect of the present disclosure, an information association method is provided, which is performed by an access and mobility management function AMF entity, including: configuring an association relationship between an access node identifier and satellite return information in the access and mobility management function AMF entity.

[0007] In some embodiments, configuring the association relationship between the access node identifier and the satellite return information in the AMF entity includes: configuring a satellite return information list in the attributes in the AMFFunction information object class IOC, wherein the association relationship is the satellite return information list; configuring the access node identifier and the satellite return information in a data type corresponding to the satellite return information list, wherein the satellite return information includes satellite identification information and satellite return type.

[0008] In some embodiments, the constraint conditions for the existence of the satellite return information list are configured in the attribute constraint conditions in the AMFFunction information object class IOC.

[0009] In some embodiments, the constraint condition is that the AMF entity supports reporting satellite return information to the session management function SMF entity, and indicates the satellite return type change to the SMF entity.

[0010] In some embodiments, the satellite return type in the satellite return information includes: geostationary orbit satellite GEO, medium orbit satellite MEO, low orbit satellite LEO, other satellite return type OTHER_SAT, dynamic geostationary orbit satellite DYNAMIC_GEO, dynamic medium orbit satellite DYNAMIC_MEO, dynamic low orbit satellite DYNAMIC_LEO, dynamic other satellite return type DYNAMIC_OTHER_SAT, and at least one of non-satellite return type NON_SATELLITE.

[0011] In some embodiments, a constraint condition for the existence of the satellite identification information in the satellite return information is that there is a satellite with a user plane function (UPF) entity deployed in the satellite return link.

[0012] In some embodiments, the access node identifier includes: a public land mobile network identifier PLMN ID, and any one of the following: a non-3GPP interworking function identifier N3IWF ID, a next-generation base station identifier gNB ID, a next-generation evolved base station identifier NG-eNB ID, a wireless access gateway function identifier W-AGF ID, a trusted non-3GPP gateway function identifier TNGF ID, or a trusted WLAN interworking function identifier TWIF ID.

[0013] In a second aspect of the present disclosure, an AMF entity is provided, comprising: a first processing module configured to configure an association between an access node identifier and satellite backhaul information in an access and mobility management function AMF entity.

[0014] In a third aspect of the present disclosure, an AMF entity is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute a method as described in any of the above embodiments based on instructions stored in the memory.

[0015] In a fourth aspect of the present disclosure, a satellite communication method is provided, which is performed by an access and mobility management function AMF entity, including: when a user equipment accesses an access node, obtaining satellite backhaul information associated with the access node according to a preset association relationship; when satellite backhaul is used for the access node, reporting the satellite backhaul information to a session management function SMF entity.

[0016] In some embodiments, the preset association relationship is created, wherein the creation of the preset association relationship includes: configuring an association relationship between the access node identifier and the satellite return information in the AMF entity.

[0017] In some embodiments, configuring the association relationship between the access node identifier and the satellite return information in the AMF entity includes: configuring a satellite return information list in the attributes in the AMFFunction information object class IOC, wherein the association relationship is the satellite return information list; configuring the access node identifier and the satellite return information in a data type corresponding to the satellite return information list, wherein the satellite return information includes satellite identification information and satellite return type.

[0018] In some embodiments, the constraint conditions for the existence of the satellite return information list are configured in the attribute constraint conditions in the AMFFunction information object class IOC.

[0019] In some embodiments, the constraint condition is that the AMF entity supports reporting satellite return information to the session management function SMF entity, and indicates the satellite return type change to the SMF entity.

[0020] In some embodiments, the satellite return type in the satellite return information includes: geostationary orbit satellite GEO, medium orbit satellite MEO, low orbit satellite LEO, other satellite return type OTHER_SAT, dynamic geostationary orbit satellite DYNAMIC_GEO, dynamic medium orbit satellite DYNAMIC_MEO, dynamic low orbit satellite DYNAMIC_LEO, dynamic other satellite return type DYNAMIC_OTHER_SAT, and at least one of non-satellite return type NON_SATELLITE.

[0021] In some embodiments, a constraint condition for the existence of the satellite identification information in the satellite return information is that there is a satellite with a user plane function (UPF) entity deployed in the satellite return link.

[0022] In some embodiments, the access node identifier includes: a public land mobile network identifier PLMN ID, and any one of the following: a non-3GPP interworking function identifier N3IWF ID, a next-generation base station identifier gNB ID, a next-generation evolved base station identifier NG-eNB ID, a wireless access gateway function identifier W-AGF ID, a trusted non-3GPP gateway function identifier TNGF ID, or a trusted WLAN interworking function identifier TWIF ID.

[0023] In a fifth aspect of the present disclosure, an AMF entity is provided, comprising: a second processing module, configured to obtain satellite backhaul information associated with the access node according to a preset association relationship when a user equipment accesses the access node; and a third processing module, configured to report the satellite backhaul information to a session management function SMF entity when satellite backhaul is used for the access node.

[0024] In a sixth aspect of the present disclosure, an AMF entity is provided, comprising: a memory; and a processor coupled to the memory, the processor being configured to execute a method as described in any of the above embodiments based on instructions stored in the memory.

[0025] In the seventh aspect of the present disclosure, a communication system is provided, comprising: an AMF entity as described in any of the above embodiments; an access node configured to send access information to the AMF entity when a user terminal accesses; and an SMF entity configured to establish a session based on the satellite return information sent by the AMF entity.

[0026] According to an eighth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method described in any of the above embodiments is implemented.

[0027] According to a ninth aspect of an embodiment of the present disclosure, a computer program is provided, comprising computer instructions, wherein when the computer instructions are executed by a processor, the method described in any one of the above embodiments is implemented.

[0028] Other features and advantages of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0030] FIG1 is a schematic flow chart of an information association method according to an embodiment of the present disclosure;

[0031] FIG2 is a schematic diagram of the structure of an AMF entity according to an embodiment of the present disclosure;

[0032] FIG3 is a schematic structural diagram of an AMF entity according to another embodiment of the present disclosure;

[0033] FIG4 is a schematic flow chart of a satellite communication method according to an embodiment of the present disclosure;

[0034] FIG5 is a schematic structural diagram of an AMF entity according to another embodiment of the present disclosure;

[0035] FIG6 is a schematic structural diagram of an AMF entity according to another embodiment of the present disclosure;

[0036] FIG7 is a schematic structural diagram of an AMF entity according to another embodiment of the present disclosure;

[0037] FIG8 is a schematic structural diagram of a communication system according to an embodiment of the present disclosure;

[0038] FIG9 is a schematic flow chart of a satellite communication method according to another embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is in no way intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present disclosure.

[0040] Unless specifically stated otherwise, the relative arrangement of components and steps, the numerical expressions and numerical values ​​set forth in these embodiments do not limit the scope of the present disclosure.

[0041] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

[0042] Technologies, methods, and equipment known to ordinary technicians in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods, and equipment should be considered part of the specification.

[0043] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not limiting. Therefore, other examples of the exemplary embodiments may have different values.

[0044] It should be noted that like reference numerals and letters refer to like items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.

[0045] The inventors note that the 3GPP Network Architecture Working Group (SA2) requires the AMF entity to be able to determine the satellite backhaul type used by a base station access node based on the network management system configuration. However, in the Management, Orchestration, and Billing Working Group (SA5), the network management system has not yet defined the configuration and management methods for satellite backhaul information, and does not support the association of satellite backhaul information with access node information.

[0046] Accordingly, the present disclosure provides an information association method, which establishes an association relationship between an access node identifier and satellite backhaul information so as to determine the satellite backhaul type used by the user equipment according to the access node to which the user equipment is connected.

[0047] Figure 1 is a flow chart of an information association method according to an embodiment of the present disclosure. In some embodiments, the following information association method is performed by an AMF entity.

[0048] In step 101, an access node identifier and satellite return information are received.

[0049] In some embodiments, the access node identifier includes: PLMN (Public Land Mobile Network) ID (identifier), and any one of the following: N3IWF (Non-3GPP InterWorking Function, non-3GPP interworking function) ID, gNB (next Generation NodeB, next generation base station, i.e. 5G base station) ID, NG-eNB (next generation-eNodeB, next generation evolved base station, i.e. 4G base station that can be connected to 5GC) ID, W-AGF (Wireline Access Gateway Function, wireless access gateway function) ID, TNGF (Trusted Non-3GPP Gateway Function, trusted non-3GPP gateway function) ID, TWIF (Trusted WLAN Interworking Function, trusted WLAN interworking function) ID, etc.

[0050] In step 102, an association between the access node identifier and the satellite return information is configured in the AMF entity.

[0051] In some embodiments, the association between the access node identifier and the satellite return information is established in the following manner.

[0052] 1) Configure SatelliteBackhaulInfoList in the Attribute of AMFFunction IOC (Information Object Class), as shown in Table 1. It should be noted that the association relationship is the satellite backhaul information list.

[0053] Table 1

[0054] It should be noted that, in Table 1, the symbol T represents True, the symbol F represents False, the symbol M represents required, the symbol O represents optional, and the symbol CM represents conditional required.

[0055] 2) Configure the constraints on the satellite return information list in the attribute constraints in the AMFFunction IOC.

[0056] In some embodiments, the constraint condition is that the AMF entity supports reporting satellite return information to the SMF (Session Management Function) entity, and indicates the satellite return type change to the SMF entity, as shown in Table 2.

[0057] Table 2

[0058] 3) Configure the access node identifier and satellite return information in the data type (datatype) corresponding to the satellite return information list, where the satellite return information includes satellite identifier information and satellite return type, as shown in Table 3.

[0059] Table 3

[0060] In some embodiments, the satellite return type includes GEO (Geosynchronous Earth Orbit Satellite), MEO (Medium-Earth Orbit Satellite), LEO (Low-Earth Orbit Satellite), OTHER_SAT (other satellite return type), DYNAMIC_GEO (dynamic geostationary orbit satellite), DYNAMIC_MEO (dynamic medium orbit earth satellite), DYNAMIC_LEO (dynamic low orbit earth satellite), DYNAMIC_OTHER_SAT (dynamic other satellite return type), NON_SATELLITE (non-satellite return type).

[0061] In some embodiments, the data type (dataType) of globalRanNodeID is as shown in Table 4.

[0062] Table 4

[0063] In some embodiments, the satellite identification information in the satellite return information is constrained by the presence of a satellite with a UPF (User Plane Function) entity deployed in the satellite return link. For example, the constraints for geoSatelliteId are shown in Table 5.

[0064] Table 5

[0065] In some embodiments, the definitions of the above attribute information are shown in Table 6.

[0066] Table 6

[0067] In Table 6, PLMN represents the Public Land Mobile Network, and NCI represents the NR (New Radio) cell identifier (NR Cell Identifier) ​​of the gNB cell.

[0068] In addition, isOrdered is used to specify whether the values ​​of this attribute instance are arranged in order. isUnique is used to specify whether the value of this attribute instance is unique (that is, there are no duplicate attribute values). isNullable is used to indicate whether the attribute can carry no information. defaultValue is the default value, and None indicates that there is no defined default value.

[0069] It should be noted here that the relevant explanation of Multiplicity is shown in Table 7.

[0070] Table 7

[0071] In some embodiments, the association between the access node identifier and the satellite return information is shown in Table 8.

[0072] Table 8

[0073] As shown in Table 8, the access node identifier uses the standard global base station identifier (global gNBId), and its format is <mcc> <mnc> - <gnbidlength> - <gnbid>, where mcc is the Mobile Country Code, mnc is the Mobile Network Code, gNBIdLength is the base station identifier length, and gNBId is the base station identifier.

[0074] In the information association method provided in the above embodiment of the present disclosure, an association relationship is established between the access node identifier and the satellite backhaul information so that the satellite backhaul type used by the user equipment can be determined according to the access node to which the user equipment is connected.

[0075] FIG2 is a schematic diagram of the structure of an AMF entity according to an embodiment of the present disclosure. As shown in FIG2 , the AMF entity 20 includes a first processing module 21.

[0076] The first processing module 21 is configured to configure an association between the access node identifier and the satellite return information in the AMF entity.

[0077] In some embodiments, the access node identifier includes: a public land mobile network identifier PLMN ID, and any one of the following: a non-3GPP interworking function identifier N3IWF ID, a next-generation base station identifier gNB ID, a next-generation evolved base station identifier NG-eNB ID, a wireless access gateway function identifier W-AGF ID, a trusted non-3GPP gateway function identifier TNGF ID, or a trusted WLAN interworking function identifier TWIF ID.

[0078] In some embodiments, the association between the access node identifier and the satellite return information is established in the following manner.

[0079] 1) Configure satelliteBackhaulInfoList in the Attribute of the AMFFunction IOC, as shown in Table 1. It should be noted that the association relationship is the satellite backhaul information list.

[0080] 2) Configure the constraints on the satellite return information list in the attribute constraints in the AMFFunction IOC.

[0081] In some embodiments, the constraints are that the AMF entity supports reporting satellite return information to the SMF entity, and indicating changes in satellite return type to the SMF entity, as shown in Table 2.

[0082] 3) Configure the access node identifier and satellite return information in the data type corresponding to the satellite return information list, wherein the satellite return information includes satellite identifier information and satellite return type, as shown in Table 3.

[0083] In some embodiments, the satellite return type includes GEO, MEO, LEO, OTHER_SAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO, DYNAMIC_OTHER_SAT, and NON_SATELLITE.

[0084] In some embodiments, the constraint condition for the existence of satellite identification information in the satellite return information is that there is a satellite with a UPF entity deployed in the satellite return link.

[0085] In some embodiments, the definition of the relevant attribute information in Tables 1-3 is shown in Table 6.

[0086] In the AMF entity provided in the above embodiment of the present disclosure, an association relationship between the access node identifier and the satellite backhaul information is established so that the satellite backhaul type used by the user equipment can be determined according to the access node to which the user equipment is connected.

[0087] FIG3 is a schematic diagram of the structure of an AMF entity according to another embodiment of the present disclosure. As shown in FIG3 , the AMF entity includes a memory 31 and a processor 32.

[0088] The memory 31 is used to store instructions. The processor 32 is coupled to the memory 31 . The processor 32 is configured to execute the method involved in any embodiment in FIG. 1 based on the instructions stored in the memory.

[0089] As shown in Figure 3, the AMF entity also includes a communication interface 33 for interacting with other devices. At the same time, the AMF entity also includes a bus 34, through which the processor 32, the communication interface 33, and the memory 31 communicate with each other.

[0090] Memory 31 may include high-speed RAM memory or non-volatile memory, such as at least one disk drive. Memory 31 may also be a memory array. Memory 31 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0091] Furthermore, the processor 32 may be a central processing unit (CPU), or may be an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the present disclosure.

[0092] The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method involved in any embodiment of FIG. 1 is implemented.

[0093] Figure 4 is a flow chart of a satellite communication method according to an embodiment of the present disclosure. In some embodiments, the following satellite communication method is performed by an AMF entity.

[0094] In step 401, when a user equipment accesses an access node, satellite return information associated with the access node is obtained according to a preset association relationship.

[0095] In some embodiments, the access node identifier includes: a public land mobile network identifier PLMN ID, and any one of the following: a non-3GPP interworking function identifier N3IWF ID, a next-generation base station identifier gNB ID, a next-generation evolved base station identifier NG-eNB ID, a wireless access gateway function identifier W-AGF ID, a trusted non-3GPP gateway function identifier TNGF ID, or a trusted WLAN interworking function identifier TWIF ID.

[0096] In step 402, in the case where satellite backhaul is used for the access node, the satellite backhaul information is reported to the SMF entity so that the SMF entity establishes a session based on the satellite backhaul information.

[0097] In some embodiments, creating a preset association relationship includes configuring an association relationship between the access node identifier and the satellite return information in an AMFFunction.

[0098] In some embodiments, the association between the access node identifier and the satellite return information is established in the following manner.

[0099] 1) Configure satelliteBackhaulInfoList in the Attribute of the AMFFunction IOC, as shown in Table 1. It should be noted that the association relationship is the satellite backhaul information list.

[0100] 2) Configure the constraints on the satellite return information list in the attribute constraints in the AMFFunction IOC.

[0101] In some embodiments, the constraints are that the AMF entity supports reporting satellite return information to the SMF entity, and indicating changes in satellite return type to the SMF entity, as shown in Table 2.

[0102] 3) Configure the access node identifier and satellite return information in the data type corresponding to the satellite return information list, where the satellite return information includes satellite identifier information and satellite return type, as shown in Table 3.

[0103] In some embodiments, the satellite return type includes GEO, MEO, LEO, OTHER_SAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO, DYNAMIC_OTHER_SAT, and NON_SATELLITE.

[0104] In some embodiments, the constraint condition for the existence of satellite identification information in the satellite return information is that there is a satellite with a UPF entity deployed in the satellite return link.

[0105] In some embodiments, the definition of the relevant attribute information in Tables 1-3 is shown in Table 6.

[0106] FIG5 is a schematic diagram of the structure of an AMF entity according to another embodiment of the present disclosure. As shown in FIG5 , the AMF entity 20 includes a second processing module 22 and a third processing module 23.

[0107] The second processing module 22 is configured to obtain satellite return information associated with the access node according to a preset association relationship when the user equipment accesses the access node.

[0108] In some embodiments, the access node identifier includes: a public land mobile network identifier PLMN ID, and any one of the following: a non-3GPP interworking function identifier N3IWF ID, a next-generation base station identifier gNB ID, a next-generation evolved base station identifier NG-eNB ID, a wireless access gateway function identifier W-AGF ID, a trusted non-3GPP gateway function identifier TNGF ID, or a trusted WLAN interworking function identifier TWIF ID.

[0109] The third processing module 23 is configured to report the satellite backhaul information to the SMF entity when satellite backhaul is used for the access node, so that the SMF entity establishes a session based on the satellite backhaul information.

[0110] Figure 6 is a schematic diagram of the structure of an AMF entity in another embodiment of the present disclosure. The difference between Figure 6 and Figure 5 is that in the embodiment shown in Figure 6, the AMF entity 20 also includes a first processing module 21.

[0111] In some embodiments, the first processing module 21 establishes an association between the access node identifier and the satellite return information in the following manner.

[0112] 1) Configure satelliteBackhaulInfoList in the Attribute area of ​​the AMFFunction IOC, as shown in Table 1. It should be noted that the association relationship is the satellite backhaul information list.

[0113] 2) Configure the constraints on the satellite return information list in the attribute constraints in the AMFFunction IOC.

[0114] In some embodiments, the constraints are that the AMF entity supports reporting satellite return information to the SMF entity, and indicating changes in satellite return type to the SMF entity, as shown in Table 2.

[0115] 3) Configure the access node identifier and satellite return information in the data type corresponding to the satellite return information list, where the satellite return information includes satellite identifier information and satellite return type, as shown in Table 3.

[0116] In some embodiments, the satellite return type includes GEO, MEO, LEO, OTHER_SAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO, DYNAMIC_OTHER_SAT, and NON_SATELLITE.

[0117] In some embodiments, the constraint condition for the existence of satellite identification information in the satellite return information is that there is a satellite with a UPF entity deployed in the satellite return link.

[0118] In some embodiments, the definition of the relevant attribute information in Tables 1-3 is shown in Table 6.

[0119] Figure 7 is a schematic diagram of the structure of an AMF entity in another embodiment of the present disclosure. As shown in Figure 7, the AMF entity includes a memory 71, a processor 72, a communication interface 73, and a bus 74. The difference between Figure 7 and Figure 3 is that in the embodiment shown in Figure 7, the processor 72 is configured to execute instructions stored in the memory to implement the method involved in any of the embodiments of Figure 4.

[0120] The present disclosure also relates to a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method involved in any embodiment of FIG. 4 is implemented.

[0121] Figure 8 is a schematic diagram of the structure of a communication system according to an embodiment of the present disclosure. As shown in Figure 8, the communication system includes an access node 81, an AMF entity 82, and an SMF entity 83. The AMF entity 82 is the AMF entity involved in any of the embodiments in Figures 5-7.

[0122] The access node 81 is configured to send access information to the AMF entity 82 when the user terminal accesses.

[0123] The SMF entity 83 is configured to establish a session based on the satellite return information sent by the AMF entity 82.

[0124] FIG9 is a schematic flow chart of a satellite communication method according to another embodiment of the present disclosure.

[0125] In step 901, a user equipment accesses an access node.

[0126] In step 902, when the user equipment accesses the access node, the access node sends access information to the AMF entity, where the access information includes the access node identifier.

[0127] In step 903, the AMF entity obtains satellite return information associated with the access node identifier according to the preset association relationship.

[0128] In step 904, when satellite backhaul is used for the access node, the AMF entity sends the satellite backhaul information to the SMF entity so that the SMF entity establishes a session based on the satellite backhaul information.

[0129] By implementing the above-described embodiments of the present disclosure, the AMF only calls the satellite return information of a specified access node, effectively saving AMF equipment resources. Furthermore, since the satellite return information associated with different access nodes can be customized and updated, it is more suitable for scenarios where satellite return information changes over time. Furthermore, by directly configuring the satellite return information associated with the access node into the AMF, the present disclosure allows satellite return information to be transmitted between AMF network elements, effectively improving disaster recovery capabilities.

[0130] In some embodiments, the functional units described above may be implemented as general-purpose processors, programmable logic controllers (PLC), digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any appropriate combination thereof, for performing the functions described in the present disclosure.

[0131] Those skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or by a program to instruct the relevant hardware, and the program may be stored in a computer-readable storage medium, which may be a read-only memory, a disk, or an optical disk, etc.

[0132] The description of the present disclosure is provided for purposes of illustration and description and is not intended to be exhaustive or to limit the disclosure to the disclosed form. Many modifications and variations will be apparent to those skilled in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure and to enable those skilled in the art to understand the present disclosure and design various embodiments with various modifications suitable for specific applications.< / gnbid> < / gnbidlength> < / mnc> < / mcc>

Claims

1. An information association method, comprising: The association between the access node identifier and the satellite return information is configured in the access and mobility management function AMF entity.

2. The information association method according to claim 1, wherein: Configuring the association relationship between the access node identifier and the satellite return information in the AMF entity includes: Configure the satellite return information list in the attributes of the AMFFunction information object class IOC, wherein the association relationship is the satellite return information list; The access node identifier and the satellite return information are configured in a data type corresponding to the satellite return information list, wherein the satellite return information includes satellite identifier information and satellite return type.

3. The information association method according to claim 2, wherein: The constraint conditions for the existence of the satellite return information list are configured in the attribute constraint conditions in the AMFFunction information object class IOC.

4. The information association method according to claim 3, wherein: The constraint condition is that the AMF entity supports reporting satellite return information to the session management function SMF entity, and indicates the satellite return type change to the SMF entity.

5. The information association method according to any one of claims 1 to 4, wherein: The satellite return types in the satellite return information include: geostationary orbit satellite GEO, medium orbit satellite MEO, low orbit satellite LEO, other satellite return types OTHER_SAT, dynamic geostationary orbit satellite DYNAMIC_GEO, dynamic medium orbit satellite DYNAMIC_MEO, dynamic low orbit satellite DYNAMIC_LEO, dynamic other satellite return type DYNAMIC_OTHER_SAT, and at least one of non-satellite return type NON_SATELLITE.

6. The information association method according to any one of claims 1 to 5, wherein: The constraint condition for the satellite identification information in the satellite return information is that there is A satellite with a user plane function (UPF) entity deployed.

7. The information association method according to any one of claims 1 to 6, wherein: The access node identifier includes: a public land mobile network identifier PLMNID, and any one of the following: a non-3GPP interworking function identifier N3IWFID, a next-generation base station identifier gNBID, a next-generation evolved base station identifier NG-eNBID, a wireless access gateway function identifier W-AGFID, a trusted non-3GPP gateway function identifier TNGFID, or a trusted WLAN interworking function identifier TWIFID.

8. An AMF entity, comprising: The first processing module is configured to configure an association between an access node identifier and satellite return information in an access and mobility management function AMF entity.

9. An AMF entity, comprising Memory; A processor is coupled to the memory, and the processor is configured to execute the information association method according to any one of claims 1 to 7 based on instructions stored in the memory.

10. A satellite communication method, performed by an access and mobility management function AMF entity, comprising: When the user equipment accesses the access node, obtaining satellite return information associated with the access node according to a preset association relationship; In case satellite backhaul is used for the access node, the satellite backhaul information is reported to the session management function SMF entity.

11. The satellite communication method according to claim 10, further comprising: Creating the preset association relationship, wherein creating the preset association relationship comprises: An association between the access node identifier and the satellite return information is configured in the AMF entity.

12. The satellite communication method according to claim 11, wherein: Configuring the association relationship between the access node identifier and the satellite return information in the AMF entity includes: The satellite return information list is configured in the attributes of the AMFFunction information object class IOC, where The associated relationship is the satellite return information list; The access node identifier and the satellite return information are configured in a data type corresponding to the satellite return information list, wherein the satellite return information includes satellite identifier information and satellite return type.

13. The satellite communication method according to claim 12, wherein: The constraint conditions for the existence of the satellite return information list are configured in the attribute constraint conditions in the AMFFunction information object class IOC.

14. The satellite communication method according to claim 13, wherein: The constraint condition is that the AMF entity supports reporting satellite return information to the session management function SMF entity, and indicates the satellite return type change to the SMF entity.

15. The satellite communication method according to any one of claims 11 to 14, wherein: The satellite return types in the satellite return information include: geostationary orbit satellite GEO, medium orbit satellite MEO, low orbit satellite LEO, other satellite return types OTHER_SAT, dynamic geostationary orbit satellite DYNAMIC_GEO, dynamic medium orbit satellite DYNAMIC_MEO, dynamic low orbit satellite DYNAMIC_LEO, dynamic other satellite return type DYNAMIC_OTHER_SAT, and at least one of non-satellite return type NON_SATELLITE.

16. The satellite communication method according to any one of claims 11 to 15, wherein: The constraint condition for the satellite identification information in the satellite return information is that there is a satellite with a user plane function UPF entity deployed in the satellite return link.

17. The satellite communication method according to any one of claims 11 to 16, wherein: The access node identifier includes: a public land mobile network identifier PLMNID, and any one of the following: a non-3GPP interworking function identifier N3IWFID, a next-generation base station identifier gNBID, a next-generation evolved base station identifier NG-eNBID, a wireless access gateway function identifier W-AGFID, a trusted non-3GPP gateway function identifier TNGFID, or a trusted WLAN interworking function identifier TWIFID.

18. An AMF entity, comprising: The second processing module is configured to obtain satellite return information associated with the access node according to a preset association relationship when the user equipment accesses the access node; The third processing module is configured to report the satellite backhaul information to the session management function SMF entity when the satellite backhaul is used for the access node.

19. An AMF entity, comprising: Memory; A processor is coupled to the memory, and the processor is configured to execute the satellite communication method according to any one of claims 10 to 17 based on instructions stored in the memory.

20. A communication system comprising: An AMF entity as claimed in any one of claims 18 to 19; The access node is configured to send access information to the AMF entity when a user terminal accesses the device; The SMF entity is configured to establish a session based on the satellite return information sent by the AMF entity.

21. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by the processor, any one of the information association methods described in claims 1-7 and the satellite communication methods described in claims 10-17 is implemented.

22. A computer program, comprising computer instructions, wherein when the computer instructions are executed by a processor, any one of the information association methods according to claims 1-7 and the satellite communication methods according to claims 10-17 is implemented.

Images