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

Abstract

The invention provides an information association method, a satellite communication method, an AMF entity and a communication system. The information association method comprises the step of configuring an association relationship between an access node identifier and satellite return information in an AMF entity.

Description

Technical Field

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

[0002] Currently, 3GPP (3rd Generation Partnership Project) Rel-18 has proposed an architecture that uses satellites as the backhaul between the access network (RAN) and 5GC, covering scenarios of using single satellites, multi-hop inter-satellite links, and satellites of multiple orbit types as the backhaul. Summary of the Invention

[0003] The inventors have noticed that the 3GPP network architecture working group (SA2) requires the AMF entity to be able to determine the satellite backhaul type adopted by the base station access node based on the configuration of the network management system. However, in the management, orchestration, and charging working group (SA5), the network management system has not defined the configuration and management method of satellite backhaul information and does not support the association of satellite backhaul information with access node information.

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

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

[0006] In some embodiments, configuring the association relationship between the access node identifier and the satellite backhaul information in the AMF entity includes: configuring a satellite backhaul information list in the attributes of the AMF Function Information Object Class IOC, where the association relationship is the satellite backhaul information list; configuring the access node identifier and the satellite backhaul information in the data type corresponding to the satellite backhaul information list, where the satellite backhaul information includes satellite identifier information and satellite backhaul type.

[0007] In some embodiments, configure a constraint condition for the existence of the satellite backhaul information list in the attribute constraint conditions of the AMF Function Information Object Class IOC.

[0008] In some embodiments, the constraint is that the AMF entity supports reporting satellite backhaul information to the session management function (SMF) entity and indicating a change in the satellite backhaul type to the SMF entity.

[0009] In some embodiments, the satellite backhaul types in the satellite backhaul information include at least one of: geostationary earth orbit satellite (GEO), medium earth orbit satellite (MEO), low earth orbit satellite (LEO), other satellite backhaul type (OTHER_SAT), dynamic geostationary earth orbit satellite (DYNAMIC_GEO), dynamic medium earth orbit satellite (DYNAMIC_MEO), dynamic low earth orbit satellite (DYNAMIC_LEO), dynamic other satellite backhaul type (DYNAMIC_OTHER_SAT), and non-satellite backhaul type (NON_SATELLITE).

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

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

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

[0013] In a third aspect of the present disclosure, there is provided an AMF entity, including: a memory; a processor coupled to the memory, the processor being configured to execute instructions stored in the memory to implement the method according to any one of the above embodiments.

[0014] In a fourth aspect of the present disclosure, there is provided a satellite communication method executed 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; and when satellite backhaul is used for the access node, reporting the satellite backhaul information to a session management function (SMF) entity.

[0015] In some embodiments, the preset association relationship is created, where creating the preset association relationship includes: configuring an association relationship between an access node identifier and satellite backhaul information in the AMF entity.

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

[0017] In some embodiments, a constraint condition for the existence of the satellite backhaul information list is configured in an attribute constraint condition in the AMFFunction information object class IOC.

[0018] In some embodiments, the constraint condition is that the AMF entity supports reporting satellite backhaul information to a session management function SMF entity and indicating a change in the satellite backhaul type to the SMF entity.

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

[0020] In some embodiments, a constraint condition for the existence of the satellite identification information in the satellite backhaul information is that there is a satellite in the satellite backhaul link where a user plane function UPF entity is deployed.

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

[0022] In a fifth aspect of the present disclosure, an AMF entity is provided, including: 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; a third processing module configured to report the satellite backhaul information to a session management function (SMF) entity when the satellite backhaul is used for the access node.

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

[0024] In a seventh aspect of the present disclosure, a communication system is provided, including: 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; an SMF entity configured to establish a session according to the satellite backhaul information sent by the AMF entity.

[0025] According to an eighth aspect of the embodiments 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, a method as described in any of the above embodiments is implemented.

[0026] Other features and advantages of the present disclosure will become clear through the following detailed description of exemplary embodiments of the present disclosure with reference to the accompanying drawings. Description of the Drawings

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or in the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0028] Figure 1 A flowchart of an information association method according to an embodiment of the present disclosure;

[0029] Figure 2 A structural diagram of an AMF entity according to an embodiment of the present disclosure;

[0030] Figure 3 A structural diagram of an AMF entity according to another embodiment of the present disclosure;

[0031] Figure 4 A flowchart of a satellite communication method according to an embodiment of the present disclosure;

[0032] Figure 5Structural schematic diagram of an AMF entity according to another embodiment of the present disclosure;

[0033] Figure 6 Structural schematic diagram of an AMF entity according to another embodiment of the present disclosure;

[0034] Figure 7 Structural schematic diagram of an AMF entity according to another embodiment of the present disclosure;

[0035] Figure 8 Structural schematic diagram of a communication system according to an embodiment of the present disclosure;

[0036] Figure 9 Flow schematic diagram of a satellite communication method according to another embodiment of the present disclosure. Detailed implementation manners

[0037] Next, the technical solutions in the embodiments of the present disclosure will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only a 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 in no way constitutes a limitation to the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present disclosure.

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

[0039] Meanwhile, it should be understood that, for the sake of convenience of description, the sizes of the various parts shown in the drawings are not drawn in actual proportional relationships.

[0040] Technologies, methods and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, the technologies, methods and devices should be regarded as part of the specification.

[0041] In all the examples shown and discussed here, any specific values should be construed as merely exemplary, rather than as limitations. Therefore, other examples of the exemplary embodiments may have different values.

[0042] It should be noted that like reference numerals and letters denote like items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further discussed in subsequent drawings.

[0043] Figure 1 Flow schematic diagram of an information association method according to an embodiment of the present disclosure. In some embodiments, the following information association method is executed by an AMF entity.

[0044] In step 101, receive the access node identifier and satellite backhaul information.

[0045] In some embodiments, the access node identifier includes: PLMN (Public Land Mobile Network) ID, and any one of the following: N3IWF (Non-3GPP InterWorking Function) ID, gNB (next Generation NodeB) ID, NG-eNB (next generation-eNodeB) ID, W-AGF (Wireline Access Gateway Function) ID, TNGF (Trusted Non-3GPP Gateway Function) ID, TWIF (Trusted WLAN Interworking Function) ID, etc.

[0046] In step 102, configure the association relationship between the access node identifier and the satellite backhaul information in the AMF entity.

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

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

[0049]

[0050]

[0051] Table 1

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

[0053] 2) Configure the constraints existing in the satellite backhaul information list in the property constraints in the AMF Function IOC.

[0054] In some embodiments, the constraints are that the AMF entity supports reporting satellite backhaul information to the SMF (Session Management Function) entity and indicating a change in the satellite backhaul type to the SMF entity, as shown in Table 2.

[0055]

[0056] Table 2

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

[0058]

[0059]

[0060] Table 3

[0061] In some embodiments, the satellite backhaul types include GEO (Geosynchronous Earth Orbit Satellite), MEO (Medium-Earth Orbit Satellite), LEO (Low-Earth Orbit Satellite), OTHER_SAT (other satellite backhaul types), DYNAMIC_GEO (dynamic geosynchronous earth orbit satellite), DYNAMIC_MEO (dynamic medium-earth orbit satellite), DYNAMIC_LEO (dynamic low-earth orbit satellite), DYNAMIC_OTHER_SAT (dynamic other satellite backhaul types), and NON_SATELLITE (non-satellite backhaul type).

[0062] In some embodiments, the data type of the globalRanNodeID is as shown in Table 4.

[0063]

[0064] Table 4

[0065] In some embodiments, the constraint condition for the satellite identification information in the satellite backhaul information is that there is a satellite with a deployed UPF (User Plane Function) entity in the satellite backhaul link. For example, the constraint condition for geoSatelliteId is shown in Table 5.

[0066]

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

[0068]

[0069]

[0070]

[0071] Table 6

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

[0073] 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 values of this attribute instance are unique (i.e., there are no duplicate attribute values). isNullable is used to identify whether the attribute can carry no information. defaultValue is the default value, and None indicates that there is no defined default value.

[0074] It should be noted here that the relevant explanations of Multiplicity are shown in Table 7.

[0075]

[0076] Table 7

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

[0078]

[0079] Table 8

[0080] As shown in Table 8, the identifier of the access node 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.

[0081] In the information association method provided in the above embodiments of the present disclosure, by establishing an association relationship between the access node identifier and the satellite backhaul information, it is possible to determine the satellite backhaul type used by the user equipment according to the access node accessed by the user equipment.

[0082] Figure 2 It is a schematic structural diagram of an AMF entity according to an embodiment of the present disclosure. As Figure 2 shown, the AMF entity 20 includes a first processing module 21.

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

[0084] 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 NodeB 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).

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

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

[0087] 2) Configure the constraint conditions for the existence of the satellite backhaul information list in the attribute constraint conditions in the AMFFunction IOC.

[0088] In some embodiments, the constraint conditions are that the AMF entity supports reporting satellite backhaul information to the SMF entity and indicating a change in the satellite backhaul type to the SMF entity, as shown in Table 2.

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

[0090] In some embodiments, the satellite backhaul types include GEO, MEO, LEO, OTHER_SAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO, DYNAMIC_OTHER_SAT, and NON_SATELLITE.

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

[0092] In some embodiments, the definitions of the relevant attribute information in Tables 1-3 are shown in Table 6.

[0093] In the AMF entity provided in the above embodiments of the present disclosure, an association relationship is established between the access node identifier and the satellite backhaul information, so as to be able to determine the satellite backhaul type used by the user equipment according to the access node accessed by the user equipment.

[0094] Figure 3 Schematic diagram of the structure of the AMF entity according to another embodiment of the present disclosure. As Figure 3 shown, the AMF entity includes a memory 31 and a processor 32.

[0095] The memory 31 is used to store instructions. The processor 32 is coupled to the memory 31, and the processor 32 is configured to execute based on the instructions stored in the memory to implement the methods involved in any of the embodiments as Figure 1 described.

[0096] As Figure 3 shown, the AMF entity further includes a communication interface 33 for information interaction with other devices. At the same time, the AMF entity further includes a bus 34, and the processor 32, the communication interface 33, and the memory 31 complete mutual communication through the bus 34.

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

[0098] In addition, the processor 32 may be a central processing unit CPU, or may be an application-specific integrated circuit ASIC, or may be one or more integrated circuits configured to implement the embodiments of the present disclosure.

[0099] The present disclosure also relates to a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, they implement the methods as Figure 1 The method involved in any of the embodiments.

[0100] Figure 4 FIG. is a schematic flowchart 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.

[0101] In step 401, when a user equipment accesses an access node, according to a preset association relationship, obtain satellite backhaul information associated with the access node.

[0102] 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 Node B 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).

[0103] In step 402, when satellite backhaul is used for the access node, report the satellite backhaul information to the SMF entity so that the SMF entity can establish a session according to the satellite backhaul information.

[0104] In some embodiments, create a preset association relationship. The creation of the preset association relationship includes: configuring the association relationship between the access node identifier and the satellite backhaul information in the AMFFunction.

[0105] In some embodiments, establish the association relationship between the access node identifier and the satellite backhaul information in the following manner.

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

[0107] 2) Configure the constraint conditions for the existence of the satellite backhaul information list in the attribute constraint conditions in the AMFFunction IOC.

[0108] In some embodiments, the constraint conditions are that the AMF entity supports reporting satellite backhaul information to the SMF entity and indicating a change in the satellite backhaul type to the SMF entity, as shown in Table 2.

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

[0110] In some embodiments, the satellite backhaul types include GEO, MEO, LEO, OTHER_SAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO, DYNAMIC_OTHER_SAT, and NON_SATELLITE.

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

[0112] In some embodiments, the definitions of the relevant attribute information in Tables 1 - 3 are shown in Table 6.

[0113] Figure 5 It is a schematic structural diagram of the AMF entity according to another embodiment of the present disclosure. As Figure 5 shown, the AMF entity 20 includes a second processing module 22 and a third processing module 23.

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

[0115] 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 Node B 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).

[0116] The third processing module 23 is configured to report the satellite backhaul information to the SMF entity when the satellite backhaul is used for the access node, so that the SMF entity can establish a session according to the satellite backhaul information.

[0117] Figure 6 It is a schematic structural diagram of the AMF entity according to another embodiment of the present disclosure. Figure 6 and Figure 5 is different in that in the Figure 6 shown embodiment, the AMF entity 20 further includes a first processing module 21.

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

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

[0120] 2) Configure the constraint conditions for the existence of the satellite backhaul information list in the attribute constraint conditions of the AMFFunction IOC.

[0121] In some embodiments, the constraint conditions are that the AMF entity supports reporting satellite backhaul information to the SMF entity and indicating a change in the satellite backhaul type to the SMF entity, as shown in Table 2.

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

[0123] In some embodiments, the satellite backhaul types include GEO, MEO, LEO, OTHER_SAT, DYNAMIC_GEO, DYNAMIC_MEO, DYNAMIC_LEO, DYNAMIC_OTHER_SAT, NON_SATELLITE.

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

[0125] In some embodiments, the definitions of the relevant attribute information in Tables 1 - 3 are shown in Table 6.

[0126] Figure 7 This is a schematic structural diagram of the AMF entity according to another embodiment of the present disclosure. As Figure 7 shown, the AMF entity includes a memory 71, a processor 72, a communication interface 73, and a bus 74. Figure 7 and Figure 3 The difference from Figure 7 is that in the Figure 4 shown embodiment, the processor 72 is configured to execute the methods involved in any one of the embodiments as described in

[0127] The present disclosure also relates to a computer-readable storage medium, where the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the methods involved in any one of the embodiments as described in Figure 4 are implemented.

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

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

[0130] The SMF entity 83 is configured to establish a session according to the satellite backhaul information sent by the AMF entity 82.

[0131] Figure 9 It is a schematic flow diagram of a satellite communication method according to another embodiment of the present disclosure.

[0132] In step 901, the user equipment accesses the access node.

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

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

[0135] In step 904, when the 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 can establish a session according to the satellite backhaul information.

[0136] By implementing the above embodiments of the present disclosure, since the AMF only calls the satellite backhaul information of the specified access node, the AMF device resources are effectively saved. In addition, since the satellite backhaul information associated with different access nodes can be customized and updated, it is more applicable to the scenario where the satellite backhaul information changes over time. At the same time, since the present disclosure directly configures the satellite backhaul information associated with the access node into the AMF, the satellite backhaul information is allowed to be transmitted between AMF network elements, effectively improving the disaster tolerance ability.

[0137] In some embodiments, the functional units described above may be implemented as a general-purpose processor, a programmable logic controller (PLC), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof for performing the functions described in this disclosure.

[0138] Those of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium. The storage medium mentioned above can be a read-only memory, a magnetic disk, an optical disk, etc.

[0139] 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 present disclosure to the disclosed form. Many modifications and variations are obvious to those of ordinary skill in the art. The embodiments are chosen and described in order to best explain the principles of the present disclosure and its practical applications, and to enable those of ordinary skill in the art to understand the present disclosure so as to design various embodiments with various modifications suitable for specific purposes.< / gnbid> < / gnbidlength> < / mnc> < / mcc>

Claims

1. An information association method, comprising: Configure the association relationship between the access node identifier and the satellite backhaul information in the Access and Mobility Management Function (AMF) entity.

2. The method according to claim 1, wherein, Configuring the association relationship between the access node identifier and the satellite backhaul information in the AMF entity includes: Configure the satellite backhaul information list in the attributes of the AMFFunction Information Object Class (IOC), where the association relationship is the satellite backhaul information list; Configure the access node identifier and the satellite backhaul information in the data type corresponding to the satellite backhaul information list, where the satellite backhaul information includes satellite identification information and satellite backhaul type.

3. The method according to claim 2, wherein, Configure the constraint conditions for the existence of the satellite backhaul information list in the attribute constraint conditions of the AMFFunction Information Object Class (IOC).

4. The method according to claim 3, wherein, The constraint conditions are that the AMF entity supports reporting satellite backhaul information to the Session Management Function (SMF) entity and indicating a change in the satellite backhaul type to the SMF entity.

5. The method according to any one of claims 1-4, wherein, The satellite backhaul types in the satellite backhaul information include at least one of: Geostationary Earth Orbit Satellite (GEO), Medium Earth Orbit Satellite (MEO), Low Earth Orbit Satellite (LEO), Other Satellite Backhaul Type (OTHER_SAT), Dynamic Geostationary Earth Orbit Satellite (DYNAMIC_GEO), Dynamic Medium Earth Orbit Satellite (DYNAMIC_MEO), Dynamic Low Earth Orbit Satellite (DYNAMIC_LEO), Dynamic Other Satellite Backhaul Type (DYNAMIC_OTHER_SAT), Non-Satellite Backhaul Type (NON_SATELLITE).

6. The method according to any one of claims 1-4, wherein, The constraint condition for the existence of the satellite identification information in the satellite backhaul information is that there is a satellite with a User Plane Function (UPF) entity deployed in the satellite backhaul link.

7. The method according to any one of claims 1-4, wherein, The access node identifier includes: Public Land Mobile Network Identifier (PLMNID), and any one of the following: Non-3GPP Interworking Function Identifier (N3IWF ID), Next Generation Base Station Identifier (gNB ID), Next Generation Evolved Node B Identifier (NG-eNB ID), Wireless Access Gateway Function Identifier (W-AGF ID), Trusted Non-3GPP Gateway Function Identifier (TNGF ID), or Trusted WLAN Interworking Function Identifier (TWIF ID).

8. An AMF entity, comprising: The first processing module is configured to configure the association relationship between the access node identifier and the satellite backhaul information in the Access and Mobility Management Function (AMF) entity.

9. An AMF entity, comprising a memory; a processor, coupled to the memory, the processor being configured to execute, based on instructions stored in the memory, the method according to any one of claims 1-7.

10. A satellite communication method, performed by an access and mobility management function AMF entity, comprising: In the case where the user equipment accesses the access node, obtain the satellite backhaul information associated with the access node according to the preset association relationship; In the case where the satellite backhaul is used for the access node, report the satellite backhaul information to the Session Management Function (SMF) entity.

11. The method according to claim 10, further comprising: Create the preset association relationship, where creating the preset association relationship includes: Configure the association relationship between the access node identifier and the satellite backhaul information in the AMF entity.

12. The method according to claim 11, wherein, Configuring the association relationship between the access node identifier and the satellite backhaul information in the AMF entity includes: Configure the satellite backhaul information list in the attributes of the AMFFunction Information Object Class (IOC), where the association relationship is the satellite backhaul information list; Configure the access node identifier and the satellite backhaul information in the data type corresponding to the satellite backhaul information list, where the satellite backhaul information includes satellite identification information and a satellite backhaul type.

13. The method according to claim 12, wherein, Configure the constraint conditions for the existence of the satellite backhaul information list in the attribute constraint conditions in the AMF Function information object class IOC.

14. The method according to claim 13, wherein, The constraint conditions are that the AMF entity supports reporting satellite backhaul information to the session management function SMF entity and indicating a change in the satellite backhaul type to the SMF entity.

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

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

17. The method according to any one of claims 11 - 14, 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 N3IWF ID, a next-generation base station identifier gNB ID, a next-generation evolved base station identifier NG-eNB ID, a radio 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.

18. An AMF entity, 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; 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.

19. An AMF entity, comprising: A memory; A processor, coupled to the memory, the processor being configured to execute, based on instructions stored in the memory, to implement the method according to any one of claims 10-17.

20. A communication system, comprising: An AMF entity according to any one of claims 18-19; An access node, configured to send access information to the AMF entity when a user terminal accesses; An SMF entity, configured to establish a session according to the satellite backhaul information sent by the AMF entity.

21. A computer - readable storage medium, wherein A computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the method according to any one of claims 1-7, 10-17 is implemented.

Images