Communication method and device

Abstract

A communication method and apparatus, relating to the technical field of communications, in the communication method, a terminal can acquire policy information, so that a first access type can be determined based on the policy information, and session establishment or session modification can be initiated through the first access type. Therefore, the terminal can establish the session in the appropriate access type, for example, the terminal can initiate session establishment or session modification through the first access type suitable for the first service information, the situation that the service transmission requirement cannot be met due to mismatching of the service type and the access type is reduced, and the service transmission performance is guaranteed.

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] With the development of wireless communication technology, the types of services that networks can provide are becoming increasingly diversified. Among these, service types can be characterized by network slicing.

[0003] However, in non-terrestrial network (NTN) technologies, the network slice requested by a terminal may not be applicable to the terminal's current access type, such as LEO, MOR, or GOR. For example, when a terminal accesses a LEO satellite, it requests a highly reliable video communication service from the core network (this is not applicable to LEO satellites). Since the radio access technologies / frequency selection priority (RFSP) received by the base station during the registration process is determined based on the network slice requested by the terminal, the terminal will still establish a session via LEO satellite. In other words, the terminal establishes a session with an inappropriate access type. This can affect the performance of service transmission. Summary of the Invention

[0004] This application provides a communication method and apparatus that enables a terminal to initiate session establishment or session modification under an appropriate access type, thereby ensuring the performance of service transmission.

[0005] Firstly, a communication method is provided. This method can be executed by a terminal, or by a module applied to the terminal (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal's functions. Taking the application of this method to a terminal as an example, in this method, the terminal can obtain policy information. The policy information is used to indicate the correspondence between at least one type of service information and a first access type, where the first access type is the access type to which at least one service information is applicable. Thus, the terminal can determine the first access type based on the policy information. The first access type includes at least one of the following: a low-track access type, a mid-track access type, a high-track access type, or a multi-track access type, thereby initiating session establishment or session modification through the first access type.

[0006] As can be seen from the above embodiments, the terminal can obtain policy information, thereby determining the first access type based on the policy information, and then initiating session establishment or session modification through the first access type. This allows the terminal to establish a session with an appropriate access type. For example, the terminal can initiate session establishment or session modification through the first access type applicable to the first service information, reducing the situation where service transmission requirements cannot be met due to mismatch between service type and access type, thus ensuring the performance of service transmission.

[0007] In one possible implementation, the terminal obtains the first association relationship by receiving policy information from a policy control network element or an access management network element.

[0008] In one possible implementation, the terminal determines a first access type based on policy information, including: the terminal determining first service information of the terminal, wherein the first service information belongs to at least one type of service information; and the terminal determining the first access type to which the first service information applies based on the first service information and the policy information.

[0009] As can be seen from the above embodiments, the terminal can determine the first service information, and then determine the first access type applicable to the first service information based on the first service information and the policy information, so that the terminal can establish a session in a suitable access type. For example, the terminal can initiate session establishment or session modification through the first access type applicable to the first service information, which reduces the situation where service transmission requirements cannot be met due to mismatch between service type and access type, thus ensuring the performance of service transmission.

[0010] Secondly, a communication method is provided. This method can be executed by a policy control network element, or by a module (e.g., processor, chip, or chip system) applied to the policy control network element, or by a logical node, logical module, or software capable of implementing all or part of the policy control network element's functions. Alternatively, this method can be executed by an access management network element, or by a module (e.g., processor, chip, or chip system) applied to the access management network element, or by a logical node, logical module, or software capable of implementing all or part of the access management network element's functions. Taking the application of this method to a policy control network element as an example, in this method, the policy control network element can determine policy information. The policy information is used to indicate the correspondence between at least one type of service information and a first access type. The first access type is the access type to which at least one service information is applicable, and the first access type includes at least one of the following: low-track access type, mid-track access type, high-track access type, or multi-track access type. In this way, the policy control network element can send policy information to the terminal.

[0011] As can be seen from the above embodiments, the policy control network element can indicate policy information to the terminal, enabling the terminal to determine the first access type based on the policy information, and then initiate session establishment or session modification through the first access type. This allows the terminal to establish a session with the appropriate access type. For example, the terminal can initiate session establishment or session modification through the first access type applicable to the first service information, reducing the situation where service transmission requirements cannot be met due to mismatch between service type and access type, thus ensuring the performance of service transmission.

[0012] In one possible implementation, the policy control network element determines policy information by: acquiring subscription information of the terminal from the data management network element, and / or acquiring first indication information from the application function network element, thereby determining policy information based on the subscription information and / or the first indication information. The terminal's subscription information or the first indication information is used to indicate the track information and second service information of the non-terrestrial network devices that the terminal can access. The second service information is associated with the track information and belongs to at least one type of service information. The track information includes track altitude parameters and / or track type, and the track type includes low-Earth orbit, medium-Earth orbit, high-Earth orbit, or multi-track.

[0013] Thirdly, a communication method is provided. This method can be executed by an access management network element, or by a module (e.g., processor, chip, or chip system) applied to the access management network element, or by a logical node, logical module, or software capable of implementing all or part of the functions of the access management network element. Alternatively, this method can be executed by a session management network element, or by a module (e.g., processor, chip, or chip system) applied to the session management network element, or by a logical node, logical module, or software capable of implementing all or part of the functions of the session management network element. Taking the application of this method to an access management network element or a session management network element as an example, the access management network element or session management network element can determine the first access type to which the third service information applies. The first access type includes at least one of the following: low-track access type, mid-track access type, high-track access type, or multi-track access type, thereby sending a first radio access technology / frequency selection priority (RFSP) index corresponding to the first access type. The first RFSP index is used to trigger the access network device to perform redirection.

[0014] As can be seen from the above embodiments, the access management network element or session management network element can determine the first access type applicable to the third service information, and thus send the first RFSP index corresponding to the first access type. This allows the access network device to perform redirection, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or session modification, thereby ensuring the consistency between the service type and the access type as much as possible, reducing the situation where service transmission requirements cannot be met due to mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0015] In one possible implementation, the access management network element determines the first access type to which the third service information applies, including: the access management network element obtains a first association relationship, and determines the first access type based on the first association relationship and the third service information. Alternatively, the session management network element determines the first access type to which the third service information applies, including: the session management network element obtains a first association relationship, and determines the first access type based on the first association relationship and the third service information.

[0016] As can be seen, in the above embodiments, the access management network element or the session management network element can determine the first access type on its own based on the first association relationship and the third service information. This can reduce the latency problem caused by other network elements determining the first access type and then transmitting it to the access management network element or the session management network element.

[0017] In one possible implementation, the access management network element acquires the first association relationship by receiving a first association relationship from an operation, administration and maintenance (OAM) device or a data management network element. Alternatively, the session management network element acquires the first association relationship by receiving a first association relationship from an OAM device or a data management network element.

[0018] In one possible implementation, the access management network element determines the first access type to which the third service information applies, including: the access management network element receiving the first access type from the session management network element. Alternatively, the session management network element determines the first access type to which the third service information applies, including: the session management network element receiving the first access type from the access management network element.

[0019] As can be seen, in the above embodiments, the access management network element can obtain the first access type from the session management network element, simplifying the processing complexity on the access management network element side. Alternatively, the session management network element can obtain the first access type from the access management network element, simplifying the processing complexity on the session management network element side.

[0020] In one possible implementation, the above method further includes: the access management network element sending third service information to the session management network element.

[0021] In one possible implementation, the access management network element sends the first RFSP index corresponding to the first access type, including: the access management network element sending the first RFSP index when a first condition is met. Alternatively, the session management network element sends the first RFSP index corresponding to the first access type, including: the session management network element sending the first RFSP index when a first condition is met. The first condition includes: the first access type is different from the terminal's current access type and / or the non-terrestrial network device to which the third service information applies is different from the non-terrestrial network device to which the terminal requests access.

[0022] As can be seen from the above embodiments, the access management network element or session management network element can send the first RFSP index when the first condition is met. This enables the access network device to perform redirection when the first access type is different from the terminal's current access type and / or the non-terrestrial network device to which the third service information applies is different from the non-terrestrial network device to which the terminal requests access. For example, the terminal may be redirected to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or session modification, thereby ensuring the consistency of service type and access type as much as possible, reducing the situation where service transmission requirements cannot be met due to mismatch between service type and access type, and ensuring the performance of service transmission.

[0023] In one possible implementation, the first association relationship includes a first access type, at least one service information supported by the first access type, and a correspondence between N non-terrestrial network devices, where N is a positive integer. The method further includes: an access management network element or a session management network element determining the non-terrestrial network devices to which the third service information applies based on the first association relationship and the third service information.

[0024] In one possible implementation, the method further includes: the access management network element receiving non-terrestrial network equipment for which third service information applies from the session management network element. Alternatively, the session management network element receives non-terrestrial network equipment for which third service information applies from the access management network element.

[0025] In one possible implementation, the method further includes: an access management network element or a session management network element receiving a first RFSP index from a data management network element. Alternatively, the access management network element or the session management network element obtains a second association relationship, and determines a first RFSP index based on the second association relationship and a first access type. The second association relationship includes a correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0026] As can be seen from the above embodiments, the access management network element or session management network element can obtain the first RFSP index from the data management network element, simplifying the processing complexity on the access management network element side or the session management network element side, and also ensuring that the first RFSP index is the RFSP index subscribed to by the terminal. Alternatively, the access management network element or session management network element can determine the first RFSP index itself based on the second association relationship and the first access type, reducing the latency problem caused by determining the first RFSP index from other network elements and then transmitting it to the access management network element or session management network element.

[0027] In one possible implementation, the method further includes: the access management network element sending second indication information to the data management network element or the session management network element, the second indication information being used to obtain a first RFSP index, the second indication information including a first access type. Alternatively, the session management network element sends the second indication information to the data management network element.

[0028] In one possible implementation, the access management network element acquires the second association relationship by receiving a second association relationship from an OAM device or a data management network element. Alternatively, the session management network element acquires the second association relationship by receiving a second association relationship from an OAM device or a data management network element.

[0029] In one possible implementation, the second association relationship includes a correspondence between a first access type, at least one RFSP index, and M non-terrestrial network devices, where the M non-terrestrial network devices include those to which the third service information applies, and M is a positive integer. The access management network element determines the first RFSP index based on the second association relationship and the first access type, including: the access management network element determining the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies. Alternatively, the session management network element determines the first RFSP index based on the second association relationship and the first access type, including: the session management network element determining the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies.

[0030] In one possible implementation, the second indication information is also used to indicate the non-terrestrial network equipment to which the third service information applies.

[0031] In one possible implementation, the third service information includes the network slice and / or data network name (DNN) requested by the terminal. Alternatively, the third service information includes the network slice and / or DNN assigned to the terminal.

[0032] Fourthly, a communication method is provided. This method can be executed by a data management network element, or by a module (e.g., processor, chip, or chip system) applied to the data management network element, or by a logical node, logical module, or software capable of implementing all or part of the functions of the data management network element. Taking the application of this method to a data management network element as an example, the data management network element can receive second indication information from an access management network element. The second indication information is used to obtain a first RFSP index corresponding to a first access type, where the first access type is the access type applicable to the third service information, thereby enabling the data management network element to send the first RFSP index to the access management network element. Alternatively, the data management network element can receive second indication information from a session management network element. The second indication information is used to obtain a first RFSP index corresponding to a first access type, where the first access type is the access type applicable to the third service information, thereby enabling the data management network element to send the first RFSP index to the session management network element.

[0033] As can be seen from the above embodiments, the data management network element determines the first RFSP index corresponding to the first access type by combining the access type applicable to the third service information. This allows the access management network element or session management network element to send the first RFSP index, which not only reduces the processing complexity on the access management network element side or session management network element side, but also ensures that the first RFSP index is the RFSP index subscribed to by the terminal.

[0034] In one possible implementation, the method further includes: a data management network element obtaining a second association relationship, and determining a first RFSP index based on the second association relationship and a first access type, wherein the second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0035] As can be seen from the above embodiments, the data management network element can determine the first RFSP index based on the second association relationship and the first access type, ensuring that the first RFSP index is the RFSP index subscribed to by the terminal.

[0036] In one possible implementation, the second association relationship includes the correspondence between the first access type, at least one RFSP index, and M non-terrestrial network devices, where the M non-terrestrial network devices include the non-terrestrial network devices to which the third service information applies, and M is a positive integer. The data management network element determines the first RFSP index based on the second association relationship and the first access type, including: the data management network element determines the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies.

[0037] In one possible implementation, the second indication information is also used to indicate the non-terrestrial network equipment to which the third service information applies.

[0038] In one possible implementation, the third service information includes the network slice and / or DNN requested by the terminal. Alternatively, the third service information includes the network slice and / or DNN allocated to the terminal.

[0039] Fifthly, a communication method is provided. This method can be executed by an access management network element, or by a module (e.g., processor, chip, or chip system) applied to the access management network element, or by a logical node, logical module, or software capable of implementing all or part of the functions of the access management network element. Taking the application of this method to an access management network element as an example, the access management network element can receive a registration request from a terminal. The registration request includes a reason value for establishing a connection, and the reason value corresponds to a first access type. The first access type includes at least one of the following: low-rail access type, mid-rail access type, high-rail access type, or multi-rail access type. Thus, the access management network element can send a first RFSP index corresponding to the first access type to the access network device. The first RFSP index is used to trigger the access network device to perform redirection.

[0040] As can be seen from the above embodiments, the access management network element determines the first access type based on the reason value for establishing the connection, thereby sending the first RFSP index corresponding to the first access type. This allows the access network device to perform redirection, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or session modification, thereby ensuring the consistency between the service type and the access type as much as possible, reducing the situation where service transmission requirements cannot be met due to mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0041] In one possible implementation, the cause value is used to indicate at least one of the following: terminal-initiated data (Mo-Data), terminal-initiated short message (Mo-SMS), or terminal-initiated mission critical.

[0042] In one possible implementation, the method further includes: the access management network element obtaining a third association relationship, and determining a first access type based on the service indicated by the cause value and the third association relationship. The third association relationship includes the correspondence between the service indicated by the cause value and the first access type.

[0043] As can be seen from the above embodiments, the access management network element can determine the first access type on its own based on the service indicated by the cause value and the third association relationship. This can reduce the latency problem caused by other network elements determining the first access type and then transmitting it to the access management network element.

[0044] In one possible implementation, the access management network element acquires the third association relationship by receiving a third association relationship from an OAM device or a data management network element.

[0045] In one possible implementation, the access management network element sends a first RFSP index corresponding to a first access type to the access network device, including: when the first access type is different from the current access type of the terminal, the access management network element sends the first RFSP index to the access network device.

[0046] As can be seen from the above embodiments, the access management network element can send the first RFSP index when the first access type is different from the terminal's current access type. This enables the access network device to perform redirection when the first access type is different from the terminal's current access type, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or session modification, thereby ensuring the consistency between service type and access type as much as possible, reducing the situation where service transmission requirements cannot be met due to mismatch between service type and access type, and ensuring the performance of service transmission.

[0047] In one possible implementation, the method further includes: the access management network element receiving a first RFSP index from the data management network element. Alternatively, the access management network element obtains a second association relationship, and determines the first RFSP index based on the second association relationship and the first access type. The second association relationship includes a correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0048] As can be seen from the above embodiments, the access management network element can obtain the first RFSP index from the data management network element, simplifying the processing complexity on the access management network element side or the session management network element side, and also ensuring that the first RFSP index is the RFSP index subscribed to by the terminal. Alternatively, the access management network element can determine the first RFSP index itself based on the second association relationship and the first access type, reducing the latency problem caused by determining the first RFSP index from other network elements and then transmitting it to the access management network element or the session management network element.

[0049] In one possible implementation, the method further includes: the access management network element sending second indication information to the data management network element, the second indication information being used to obtain a first RFSP index, the second indication information including a first access type.

[0050] A sixth aspect provides a communication device comprising units or modules for implementing the method as described in any one of the first to fifth aspects. The communication device may be a terminal, a module of a terminal (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the terminal's functions. Alternatively, the communication device may be a core network element, a module of a core network element (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the core network element's functions. In one possible implementation, the core network element may be a policy control network element, an access management network element, a session management network element, or a data management network element, etc.

[0051] A seventh aspect provides a communication device, comprising at least one processor; wherein the at least one processor is configured to perform the method described in any one of the first to fifth aspects. The communication device may be a terminal, a module of a terminal (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the terminal's functions. Alternatively, the communication device may be a core network element, a module of a core network element (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the core network element's functions. In one possible implementation, the core network element may be a policy control network element, an access management network element, a session management network element, or a data management network element, etc. The at least one processor may execute a computer program or instructions stored in a memory to cause the above-described method to be performed. The memory may be included in the communication device or located outside the communication device. Furthermore, the communication device may also include an interface.

[0052] Eighthly, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions that, when executed, cause a computer to perform the method as described in any one of the first to fifth aspects.

[0053] Ninth aspect, a computer program product is provided, the computer program product comprising: computer program code, which, when executed by a computer, causes the computer to perform the method described in any one of the first to fifth aspects.

[0054] A tenth aspect provides a chip or chip system including at least one processor and an interface, the processor being configured to read and execute instructions stored in a memory, wherein when the instructions are executed, the chip performs the method as described in any one of the first to fifth aspects.

[0055] Eleventhly, a communication system is provided, comprising a terminal for performing the method as described in any one of the first aspects and a policy control network element or access management network element for performing the method as described in any one of the second aspects.

[0056] In a twelfth aspect, a communication system is provided, comprising an access management network element for performing the method as described in any one of the third aspects, and an access network device communicating with the access management network element. Alternatively, it may include a session management network element for performing the method as described in any one of the third aspects, and an access network device communicating with the session management network element. Optionally, it may further include a data management network element for performing the method as described in any one of the fourth aspects.

[0057] In a thirteenth aspect, a communication system is provided, comprising an access management network element for performing the method as described in any one of the fifth aspects, and an access network device communicating with the access management network element. Optionally, it further comprises a data management network element for performing the method as described in any one of the fourth aspects. Attached Figure Description

[0058] Figure 1 This application provides an infrastructure for a communication system.

[0059] Figure 2 This is a schematic diagram of the RAN architecture of an NTN-based device to which the embodiments of this application apply;

[0060] Figure 3 A flowchart illustrating a communication method provided in an embodiment of this application;

[0061] Figure 4 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0062] Figure 5 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0063] Figure 6 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0064] Figure 7 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0065] Figure 8 A flowchart illustrating yet another communication method provided in an embodiment of this application;

[0066] Figure 9 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0067] Figure 10This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0068] The technical solutions in the embodiments of this application will be described below with reference to the accompanying drawings. The terms "system" and "network" in the embodiments of this application can be used interchangeably. Unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship; for example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "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 can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be one or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish network elements and similar items with essentially the same function. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Additionally, the numbering of steps in the various embodiments described in this application is only for distinguishing different steps and is not used to limit the order of steps. For example, step 201 may occur before step 202, or may occur after step 202, or may occur simultaneously with step 202.

[0069] References to "one embodiment" or "some embodiments" in the embodiments described in this application mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0070] The following detailed embodiments further illustrate the objectives, technical solutions, and beneficial effects of this application. It should be understood that the following are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made based on the technical solutions of this application should be included within the scope of protection of this application.

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

[0072] The method provided in this application can be applied to various communication systems, such as Internet of Things (IoT) systems, narrowband Internet of Things (NB-IoT) systems, long-term evolution (LTE) systems, 5th-generation (5G) communication systems, new radio (NR) systems, or new communication systems emerging in future communication developments. IoT networks may include, but are not limited to, vehicle-to-everything (V2X) networks. Communication methods in V2X systems can be collectively referred to as vehicle-to-everything (V2X), where X can represent anything. For example, V2X may include: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc. The method provided in this application embodiment can also be applied to non-terrestrial network (NTN) communication (also known as non-land network communication), or scenarios where NTN and terrestrial network (TN) are integrated.

[0073] The method provided in this application can be applied to wireless local area network (WLAN) systems, such as Wi-Fi. The method provided in this application can also be applied to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series protocols, such as the 802.11be protocol, the 802.11bn protocol, or next-generation protocols of the 802.11bn protocol, etc., and will not be listed individually.

[0074] The method provided in this application can be applied between two entities in a communication system, such as one entity sending information to or receiving information sent by the other entity. In a wireless communication system, communication devices are included, and these devices can communicate wirelessly using air interface resources. Air interface resources may include at least one of time-domain resources, frequency-domain resources, code resources, and spatial resources; this application does not limit this. For example, the aforementioned two entities may include a network device and a terminal, or may include a chip that can be placed in a network device and a chip that can be placed in a terminal, etc. Of course, as standards or products advance, other types of entities may emerge subsequently; this application does not limit this.

[0075] To facilitate understanding of the embodiments of this application, Figure 1 The 5G network architecture shown is used as an example to introduce the communication system. For example, you can refer to the 3rd Generation Partnership Project (3GPP) technical specifications (TS) 23.501, and the functions of each network element can also be found in other 3GPP technical specifications. Figure 1 As shown, the network architecture includes: a terminal portion, an access network (AN) portion, and a core network portion. Optionally, this network architecture may also include a data network (DN) portion and / or an application network element portion. The terminal accesses the core network through the access network, and the core network communicates with the DN or application network elements.

[0076] The following section will provide a detailed explanation of each part of the system architecture.

[0077] I. Terminal device

[0078] A terminal is an entity on the user side used to receive signals, or transmit signals, or both. Terminals are used to provide users with one or more of the following: voice services and data connectivity services. A terminal can be a device that includes wireless transceiver capabilities and can cooperate with network equipment to provide communication services to users. Specifically, a terminal can refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication equipment, user agent, user apparatus, or roadside unit (RSU). Terminals can also be drones, Internet of Things (IoT) devices, stations (STs) in wireless local area networks (WLANs), cellular phones, smartphones, cordless phones, wireless data cards, tablets, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistant (PDA) devices, laptop computers, machine type communication (MTC) terminals, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices (also known as wearable smart devices), virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in remote medical care, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in smart grids, and transportation security devices. Wireless terminals in smart cities, smart homes, etc., can be used in various contexts such as safety, security, and safety. The terminal can also be a terminal in a 5G system or a terminal in a next-generation communication system; this application does not limit the specific application to these possibilities.

[0079] The embodiments of this application do not limit the device form of the terminal. The device used to implement the functions of the terminal can be the terminal itself; it can also be a device that supports the terminal in implementing the functions, such as a chip system. The device can be installed in the terminal or used in conjunction with the terminal. In the embodiments of this application, the chip system can be composed of chips or can include chips and other discrete devices.

[0080] II. AN section

[0081] The AN portion includes AN devices. These AN devices are used in mobile communication systems to connect terminals to the wireless network. As nodes in the radio access network, AN devices can also be referred to as access network elements, base stations, radio access network (RAN) nodes (or devices, or network elements), access points (APs), or network devices, etc. The RAN equipment in this application embodiment includes, but is not limited to: evolved universal terrestrial radio access network (E-UTRAN), next-generation base station (g nodeB, gNB), evolved node B (eNB), radio network controller (RNC), node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved nodeB, or home node B, HNB), baseband unit (BBU), wireless fidelity (WiFi) access point, world interoperability for microwave access (WiMAX) base station, transmitting and receiving point (TRP), transmitting point (TP), or mobile switching center, etc. In systems employing different wireless access technologies, the names of devices with base station functions may vary. For example, in 5G communication systems, they are called RAN or gNB (5G NodeB); in LTE systems, they are called evolved NodeB (eNB or eNodeB); and in third-generation (3G) communication systems, they are called Node B, etc. In some deployments of AN (Antenna Unit) devices, the AN device may include centralized units (CU) and distributed units (DU). In other deployments, the CU can be further divided into CU-control plane (CP) and CU-user plane (UP). In still other deployments, the AN device may also include an antenna unit (RO).In some deployments of AN devices, the AN device can be an open radio access network (ORAN) architecture, a cloud radio access network (cloud RAN), etc. ORAN can also be called a virtualized RAN. For example, when the AN device is an ORAN architecture, the AN device in this application embodiment can be an access network element in the ORAN, or a module of an access network element, etc. In the ORAN system, CU can also be called open (O)-CU, DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0082] 3. DN

[0083] A Data Network (DN) is a network located outside the mobile communication system that can provide services to users. For example, the DN can be a packet data network (PDN), such as the Internet, Internet Protocol Multimedia Service (IMS) networks, certain application-specific data networks, Ethernet, Internet Protocol (IP) local area networks, etc. This application embodiment does not limit this to any particular type. Multiple services can be deployed on the DN, providing data, voice, and SMS services to terminals. The DN can have multiple application servers (AS), each of which can provide at least one service.

[0084] IV. Application Network Elements

[0085] Application network elements primarily support interaction with the 3GPP core network to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side. In 5G communication systems, this application network element can be an application function (AF) network element. In future communication systems, the application network element can still be an AF network element, or it can have other names; this application embodiment does not limit this.

[0086] The network elements in the core network can be divided into two categories: user plane function network elements (also referred to as user plane network elements) and control plane function network elements (also referred to as control plane network elements). The control plane function network elements include access management network elements, session management network elements, data management network elements, and policy control network elements.

[0087] User plane network elements are responsible for forwarding and receiving user data in terminal devices. They can receive user data from the data network and transmit it to the terminal device through the access network equipment; user plane network elements can also receive user data from the terminal device through the access network equipment and forward it to the data network. The transmission resources and scheduling functions in the user plane network element that provide services to the terminal device are managed and controlled by the session management network element. In 5G communication systems, this user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names; this application embodiment does not limit this.

[0088] The access management network element is a control plane network element provided by the operator's network, responsible for access control and mobility management of terminal devices accessing the operator's network. This includes functions such as mobility state management, allocation of temporary user identities, authentication, and user management. In 5G communication systems, this access management network element can be an access and mobility management function (AMF) network element. In future communication systems, the access management network element may still be an AMF network element, or it may have other names; this application does not limit this.

[0089] The session management network element is primarily responsible for session management in mobile networks, such as session establishment, session modification, and session release. Specific functions include assigning IP addresses to users and selecting user plane network elements that provide packet forwarding capabilities. In 5G communication systems, this session management network element can be a session management function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or it may have other names; this application does not limit the specifics.

[0090] The data management network element is used for generating authentication credentials, processing user identifiers (such as storing and managing permanent user identities), access control, and managing subscription data. In 5G communication systems, this data management network element can be a unified data management (UDM) network element. In future communication systems, unified data management can still be a UDM network element, or it can have other names; this application embodiment does not limit this.

[0091] The policy control network element primarily supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and is also responsible for acquiring user subscription information related to policy decisions. In 4G communication systems, this policy control network element can be a policy and charging rules function (PCRF) network element. In 5G communication systems, this policy control network element can be a policy control function (PCF) network element. In future communication systems, the policy control network element can still be a PCF network element, or it can have other names; this application embodiment does not limit this.

[0092] The above mainly introduces the network elements that may be involved in various embodiments of this application. Additionally... Figure 1 Other network elements are also involved, but will not be discussed in detail here. For example, the core network may also include policy control function (PCF) network elements and unified data repository (UDR) network elements. Figure 1 (Not shown in the image) Network elements with network repository function (NRF), network exposure function (NEF), authentication server function (AUSF), network slice selection function (NSSF), etc.

[0093] Figure 1 The document also demonstrates the interfaces between multiple communication devices in the communication system. For example, N1, N2, N3, N4, N5, N6, N7, N8, N9, N10, N11, N12, N15, Nnnsf, Nnef, Nnrf, Nausf, Namf, Npcf, Nudm, Naf, Nsmf, etc., are interface sequence numbers, which can be found in 3GPP TS23.501 and are not restricted here. Among them, Nnnsf, Nnef, Nnrf, Nausf, Namf, Npcf, Nudm, Naf, Nsmf, etc., are the service interfaces provided by NSSF, NEF, NRF, AUSF, AMF, PCF, UDM, AF, and SMF, respectively, used to invoke the corresponding service operations.

[0094] Understandable, Figure 1The network elements or functions shown can be network components in hardware devices, software functions running on dedicated hardware, virtualization functions instantiated on a platform (e.g., a cloud platform), or a combination of both. One possible implementation is that the aforementioned network element or function can be implemented by a single device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this. Furthermore, for ease of description, the term "network element" can be omitted below. For example, in this application's embodiments, the SMF network element and SMF have the same meaning; the word "network element" is omitted for convenience, and so on. It should also be noted that this application does not limit the names of each network element in the communication system. For example, in communication systems of different standards, each network element can have other names; and for example, when multiple network elements are integrated into the same physical device, that physical device can also have other names.

[0095] To facilitate understanding of the content of this solution, some terms used in the embodiments of this application will be explained below, so that those skilled in the art can understand them. This part is only for the purpose of understanding and should not be regarded as a specific limitation of this application.

[0096] I. NTN

[0097] In this embodiment, network devices deployed in the air can be referred to as NTN devices, and network devices deployed on the ground can be referred to as TN devices. An NTN communication system includes at least one NTN device, while network devices in a TN communication system are TN devices. A TN device, relative to an NTN device, is a stationary or slower-moving network device. In other words, an NTN device, relative to a TN device, can be a high-speed mobile network device.

[0098] NTN equipment can include satellites, high-altitude platforms (HAPs), drones, or hot air balloons, etc., without limitation. Satellites can be medium Earth orbit (MEO) satellites, low Earth orbit (LEO) satellites, high altitude platform stations (HAPS), evolved NodeBs (eNBs), or 5G base stations (gNBs), etc. GEO satellites are also called high-orbit satellites, MEO satellites are also called medium-orbit satellites, and LEO satellites are also called low-orbit satellites. For example, orbits above the Earth's surface exceeding 20,000 kilometers (km) are called high-orbit, orbits between 8,000 km and 20,000 km are called medium-orbit, and orbits between 500 km and 2,000 km are called low-orbit. This is merely an example; this application does not limit the specific altitude ranges of low-orbit, medium-orbit, and high-orbit.

[0099] In the case of NTN equipment being satellites, the satellites may have different functions in different scenarios, specifically:

[0100] 1. In Figure 2 In a transparent satellite architecture shown in Figure 2-1, the radio access network (RAN) may include remote radio units (RRUs) and base stations (such as...). Figure 2 The RRU can include a satellite and an NTN gateway. The satellite is used for radio frequency filtering and frequency conversion and amplification to ensure that the waveform signal repeated by the payload remains unchanged. That is, the satellite primarily acts as a Layer 1 (L1) relay device, used to regenerate physical layer signals (i.e., radio frequency filtering, frequency conversion, and amplification), without involving other higher protocol layers. The NTN gateway supports all functions for forwarding new radio-Uu (NR-Uu) interface signals. The NR-Uu interface is the interface between the terminal and the base station in the protocol.

[0101] 2. In Figure 2 In the regenerative satellite architecture without inter-satellite link shown in Figure 2-2, the RAN includes satellites and NTN gateways. The satellites act as base stations, possessing base station processing functions. The NTN gateway is a transport network layer node and supports the corresponding transport protocols. The satellites and NTN gateways are connected via a satellite radio interface (SRI), with the NG interface (NG over SRI) responsible for higher-level information transmission.

[0102] 3. In Figure 2 In a regenerative satellite architecture with inter-satellite links, as shown in Figures 2-3, and... Figure 2 Similar to 2-2, the difference is that SRI exists, and multiple satellites can be connected via the Xn interface. The Xn interface is carried over SRI.

[0103] 4. In Figure 2 In a regenerative satellite architecture with distributed unit (DU) processing capabilities, as shown in Figure 2-4, the satellite acts as a DU within the base station, jointly performing base station functions with the central unit (CU). An NTN gateway exists between the DU on the satellite and the CU on the ground. The NTN gateway is a transport network layer node that supports the corresponding transport protocols. The satellite and the NTN gateway are connected via an F1 interface, which is carried over the SRI (F1 over SRI).

[0104] 5. In a satellite architecture with integrated access and backhaul (IAB) functionality, the satellite acts as a base station with IAB functionality.

[0105] Among them, when the satellite acts as a Layer 1 relay device (i.e. Figure 2In the transparent satellite architecture shown in Figure 2-1, the communication system may further include a base station. The base station can be an evolved universal terrestrial radio access (E-UTRA) system, an NR system, or a future radio access system as defined in the 3rd generation partnership project (3GPP). It can also be a WiFi system, enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), massive machine-type communication (mMTC), a long-range Internet of Things (LoRa) system, or a vehicle-to-everything (V2X) system. The base station may also include two or more of the above-mentioned different radio access systems. The base station may also be an open radio access network (RAN) (O-RAN).

[0106] II. Network Slicing

[0107] To meet the diverse needs of various industries in different scenarios, operators require providing connectivity and communication services with varying functions and Quality of Service (QoS). To reduce the complexity of technical implementation, virtualization technology is used within a communication network to slice the entire network resources. Services with different connectivity capabilities are deployed on different network slices, thereby creating virtual, independent logical networks for control plane and user plane network functions to meet the QoS requirements of different services. This approach of logically isolating network slices on a single physical infrastructure provides resource utilization efficiency and flexibility. From a service type perspective, a network slice can be specifically defined as one or more combinations of hardware, software, policies, and spectrum dynamically deployed by a network operator to meet the QoS requirements of a specific user set.

[0108] Currently, 5G networks define three main categories of typical application scenarios: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (uRLLC), and massive machine-type communication (mMTC). Based on these three typical scenarios, 5G networks can be divided into three types of network slices: eMBB, mMTC, and uRLLC. It should be understood that this application is not limited to the network slices listed here; in practical applications, other types of network slices may exist, and this application does not limit these.

[0109] Optionally, network slices can be uniquely identified using a network slice identifier. For example, single network slice selection assistance information (S-NSSAI). This is merely an example of a network slice identifier, and this application does not limit it; any content that can uniquely identify a network slice can be used as the network slice identifier in this application.

[0110] III. DNN

[0111] DNN can be used to select the SMF and UPF for establishing a protocol data unit (PDU) session, and can also be used to determine the policy applied to that PDU session.

[0112] A DNN may include at least one of the following:

[0113] 1. Network Identification (ID): This part represents an external network and is required.

[0114] 2. Carrier identifier: This part indicates which carrier it belongs to, and is optional.

[0115] IV. UE route selection policy (URSP)

[0116] URSP, also known as User Equipment Routing Policy, is used to associate an application with an established Protocol Data Unit (PDU) session, establish a new PDU session for an application, or transfer an application to a non-3GPP access for transmission.

[0117] A URSP can include the association between at least one application and at least one network slice; for example, at least one application corresponds one-to-one with at least one network slice. Optionally, an application can be described in the URSP by an application identifier, and a network slice can be described by a network slice identifier. See Table 1 for details of the URSP in this case. In Table 1, a URSP can include at least one of the following: rule priority, traffic descriptor, application descriptors, IP descriptors, domain descriptors, non-IP descriptors, DNN, connection capabilities, personal IoT ID (PIN ID), connectivity group ID, or list of route selection descriptors, etc.

[0118] Table 1

[0119]

[0120]

[0121] Optionally, the aforementioned application identifier (or application index or application number, etc.) includes at least one of the following: application name, application IP address / port number, application descriptor, domain descriptor, non-IP descriptor, personal IoT identifier, or connection group identifier, etc. For example, the application identifier may be an Internet Protocol Multimedia Service (IMS) communication service identifier (ICS) or an IMS application identification (IARI). Optionally, the application identifier mentioned in this application may be any numerical value or symbol that can distinguish, mark, or locate an application, and is not limited herein.

[0122] V. Redirection

[0123] In this application, the redirection process involves the access network device instructing the terminal to attempt to camp on a cell at a specified frequency point via redirected carrier info. The redirection info may include the redirected frequency point. Optionally, the redirection info may also indicate the redirected RAT. For example, the redirection info may include NR carrier info, instructing the terminal to attempt to camp on an NR cell. Alternatively, the redirection info may include E-UTRA redirected carrier info (EUTRA), instructing the terminal to attempt to camp on an E-UTRA cell.

[0124] Optionally, the redirection information can be included in the radio resource control (RRC) release message.

[0125] When an RRC release message includes redirection information, the terminal should attempt to camp on a suitable cell on the redirected frequency indicated by the redirection information. If the terminal cannot find a suitable cell on the redirected frequency, it may attempt to camp on a suitable cell on a specified RAT. If the terminal also fails to find a suitable cell on the specified RAT, it can use its stored information to perform a cell selection process to find a suitable cell. In this case, the terminal may select and camp on a non-redirected frequency or a cell on a non-redirected RAT.

[0126] VI. Track Information

[0127] In this application, track information includes track height parameters and / or track type.

[0128] The track height parameter refers to the height of the track to which the non-terrestrial network device belongs. This height refers to the distance from the non-terrestrial network device to the ground, such as vertical height. Optionally, the number of tracks to which a non-terrestrial network device belongs can be one or more, and is not limited here.

[0129] Track type refers to the type of track to which the non-terrestrial network equipment belongs, including low-track, medium-track, high-track, or multi-track. When a non-terrestrial network equipment belongs to multiple tracks, it can be considered a multi-track system. That is, a multi-track system can include at least two types of tracks: low-track, medium-track, and high-track. For example, a non-terrestrial network equipment may belong to two tracks, one of which is a low-track track and the other is a high-track track.

[0130] VII. Access Type

[0131] As an example, in this application, the access type (such as the first access type, etc.) can characterize the air interface technology by which the terminal accesses the core network. For example, the access type can refer to the track type of non-terrestrial network equipment. That is, the access type can include at least one of the following: low-Earth orbit access type, medium-Earth orbit access type, high-Earth orbit access type, or multi-Earth orbit access type. In this case, the access type and track information can be used interchangeably.

[0132] As another example, in this application, the non-terrestrial network device is a drone, a low-altitude flight device, or a very low orbit satellite, and the access type (such as the first access type, etc.) can characterize the access type of the drone, the low-altitude flight device, or the very low orbit satellite.

[0133] As another example, in this application, the access type (such as the first access type, etc.) can characterize the access type of NR, LTE, or NB-IoT.

[0134] It should be noted that the above are some possible examples of access types. In actual application scenarios, the access type may include a combination of one or more of the above examples, and this application does not limit this.

[0135] Optionally, access types (such as the first access type, etc.) can be associated with frequency bands. For example, access types (such as the first access type, etc.) can be associated with frequency bands one by one. That is to say, access types (such as the first access type, etc.) can be described interchangeably with frequency bands, and this application does not limit this.

[0136] The embodiments of this application will be described in detail below, taking at least one of the following access types: low-rail access type, medium-rail access type, high-rail access type, and multi-rail access type.

[0137] See Figure 3 , Figure 3 This is a flowchart illustrating a communication method provided in an embodiment of this application. For example... Figure 3 As shown, the method includes, but is not limited to, the following steps:

[0138] 301. The policy control network element determines policy information, which is used to indicate the correspondence between at least one type of service information and a first access type. The first access type is the access type to which at least one type of service information is applicable. The first access type includes at least one of the following: low-rail access type, medium-rail access type, high-rail access type, or multi-rail access type.

[0139] For example, policy control network elements can determine policy information in the following ways, specifically:

[0140] 1. The policy control network element locally stores the correspondence between at least one type of service information and the first access type. In this way, the policy control network element can determine the policy information itself.

[0141] 2. The policy control network element obtains the terminal's subscription information from the data management network element. The terminal's subscription information is used to indicate the track information and second service information of the non-terrestrial network devices that the terminal can access. The second service information is associated with the track information. In this way, the policy control network element can determine policy information based on the subscription information.

[0142] Optionally, the second service information belongs to at least one type of service information, and the track information associated with the second service information includes track altitude parameters and / or track type. Optionally, the track information can also be replaced by access type.

[0143] 3. The policy control network element obtains first indication information from the application function network element. The first indication information is used to indicate the track information of the non-terrestrial network devices that the terminal can access, as well as second service information, with the second service information associated with the track information. In this way, the policy control network element can determine policy information based on the first indication information.

[0144] Optionally, policy information can be used to indicate one or more access types, and at least one type of service information corresponding to each access type.

[0145] Optionally, the strategy information may be existing strategy information and / or newly added strategy information, and this application does not limit this.

[0146] Existing policy information can be policy information from existing versions of communication standards, such as URSP. That is, policy information from existing versions of communication standards has been updated with relevant content, such as one or more access types and at least one type of service information corresponding to each access type. For example, when the policy information is URSP, one or more access types can be indicated by routing list descriptors in the URSP, and at least one type of service information corresponding to each access type can be indicated by service descriptors in the URSP.

[0147] The added policy information can be newly defined policy information, such as policy information in future communication standards.

[0148] Optionally, the strategy information can be a mapping information, and the specific form is not limited.

[0149] For ease of description, the following explanation uses the example of a first access type corresponding to at least one type of service information, and should not be construed as a limitation of this application. For example, in Table 2, the first access type includes the low-Earth orbit access type, corresponding to service information 1 and service information 2. That is to say, the first access type corresponds to at least one type of service information, or it can be understood as: the access type to which one or more types of service information are applicable is the first access type. Here, the first access type refers to the type of track to which the non-terrestrial network equipment belongs, i.e., the track type of the non-terrestrial network equipment. In one possible implementation, the first access type and the track type can be described interchangeably, and this is not limited here.

[0150] Table 2

[0151]

[0152] Optionally, in Figure 3 In the embodiments described, service information (such as first service information or second service information) can be used to describe the services used by the terminal and / or the objects transmitting data. For example, it includes application identifiers and / or service types.

[0153] Business types can be granular or coarse-grained.

[0154] At a coarse-grained level, service types can be categorized into data services, voice services, video services, short message services (SMS), or mission critical services, etc.

[0155] At a finer granular level, data services can be divided into calling data services (Mo-Data) and called data services (MT-Data). Mo-Data refers to data services initiated by the terminal. MT-Data refers to data services passively received by the terminal.

[0156] At a finer granular level, voice services can be categorized into IMS-based telephone voice, circuit-switched (CS) telephone voice, and voice over the internet. IMS-based telephone voice can include Voice over New Radio (VoNR) and / or Voice over Long Term Evolution (VoLTE), etc. CS-based telephone voice can include voice over circuit-switched fallback (CSFB), etc. Voice over the internet can include instant messaging voice services, etc. Alternatively, voice services can be divided into calling voice services and called voice services. Calling voice services refer to voice services initiated by the terminal. Called voice services refer to voice services passively received by the terminal.

[0157] At a more granular level, video services can be categorized into IMS-based video, internet-based video calls, and internet-based online video. IMS-based video can include high-definition video calls (Video Over Long Term Evolution, ViLTE), internet-based video calls can include instant messaging applications, and internet-based online video can include various videos on a web browser. Alternatively, video services can be divided into calling video services and called video services. Calling video services refer to video services initiated by the terminal. Called video services refer to video services passively received by the terminal.

[0158] For finer-grained analysis, SMS services can be categorized into IMS-based SMS, CS-based SMS, and Internet-based SMS. Data services can include web browsing and map applications. Alternatively, SMS services can be divided into calling SMS (Mo-SMS) and called SMS (MT-SMS). Calling SMS refers to SMS messages initiated by the terminal. Called SMS refers to SMS messages passively received by the terminal.

[0159] Optionally, the service type can be described interchangeably with network slice. As an example, a network slice can be associated with a DNN, such that a network slice can be associated with a DNN one-to-one. Therefore, in this application, the service type can be replaced with: network slice and / or DNN.

[0160] Optionally, step 301 may be an optional step.

[0161] 302. Terminal obtains policy information.

[0162] Accordingly, the policy control network element sends policy information to the terminal.

[0163] The correspondence between at least one type of service information indicated by the policy information and the first access type can be indicated to the terminal directly or indirectly by the policy control network element or the access management network element, or it can be predefined; this application does not limit this. For example, the policy information may include the correspondence between at least one type of service information and the first access type. In this way, the terminal can know which service information applies to which access type.

[0164] Optionally, policy information can be carried in UE configuration update (UCU) messages, UE parameter update (UPU) messages, application-level messages, network selection configuration control messages, or other messages.

[0165] Optionally, the policy control network element in steps 301 and 302 above can be replaced by an access management network element. In this case, policy information can be carried in non-access stratum (NAS) messages or protocol data unit (PDU) sessions.

[0166] Optionally, steps 301 and 302 described above can be implemented in the terminal's registration process or other processes. The specific registration process can refer to existing registration processes, such as those already present in existing versions of communication standards. Alternatively, it can refer to newly added registration processes, such as those in future communication standards; no specific limitations are imposed here.

[0167] 303. The terminal determines the first access type based on the policy information.

[0168] For example, a terminal can determine its first service information, and then determine the first access type applicable to the first service information based on the first service information and policy information. The first service information belongs to at least one type of service information. For instance, when the policy information is a URSP (Universal Routing List Service), the service descriptor in the URSP indicates at least one type of service information, which includes the first service information. Therefore, the terminal can match the service information in the service descriptor based on the first service information, and then determine the first access type indicated by the routing list descriptor in the URSP. In this way, the terminal achieves the determination of the first access type applicable to the first service information based on the first service information and policy information.

[0169] 304. The terminal initiates session establishment or session modification through the first access type.

[0170] For example, the terminal selects one of at least one non-terrestrial network devices corresponding to the first access type to initiate session establishment or session modification. For instance, the terminal may send a session establishment request message or a session modification request message to the non-terrestrial network device. Optionally, the session establishment request message may be a PDU session establishment request message, and the session modification request message may be a PDU session modification request message; no limitation is made here.

[0171] Optionally, the session establishment request message or session modification request message may include session parameter information requested by the terminal for access, such as network slices and / or DNNs. For example, when the policy information is URSP, the routing list descriptor in the URSP may also indicate session parameter information, such as network slices and / or DNNs. Thus, the terminal can carry network slices and / or DNNs in the session establishment request message or session modification request message. Optionally, the network slice requested by the terminal for access may be called a requested NSSAI, which is the NSSAI provided by the terminal to the serving public land mobile network (PLMN) during the registration process, or the NSSAI configured locally by the terminal.

[0172] Optionally, the session parameter information may also include other information, which can be referenced from existing session establishment or modification procedures, such as those in existing versions of communication standards. Alternatively, it can be referenced from newly added session establishment or modification procedures, such as those in future communication standards; no specific limitations are imposed here.

[0173] As can be seen from the above embodiments, the policy control network element can indicate policy information to the terminal, enabling the terminal to determine the first access type based on the policy information, and then initiate session establishment or session modification through the first access type. This allows the terminal to establish a session with the appropriate access type. For example, the terminal can initiate session establishment or session modification through the first access type applicable to the first service information, reducing the situation where service transmission requirements cannot be met due to mismatch between service type and access type, thus ensuring the performance of service transmission.

[0174] See Figure 4 , Figure 4 This is a flowchart illustrating a communication method provided in an embodiment of this application. For example... Figure 4 As shown, the method includes, but is not limited to, the following steps:

[0175] 401. The access management network element determines the first access type applicable to the third service information. The first access type includes at least one of the following: low-rail access type, medium-rail access type, high-rail access type, or multi-rail access type.

[0176] The access management network element can determine the first access type to which the third service information applies in several ways, specifically:

[0177] 1. The access management network element obtains the first association relationship, and determines the first access type based on the first association relationship and the third service information.

[0178] 2. The access management network element receives the first access type from the session management network element. This is equivalent to the session management network element obtaining the first association relationship, determining the first access type based on the first association relationship and the third service information, and then instructing the access management network element accordingly. In this case, the access management network element can also send the third service information to the session management network element.

[0179] Optionally, the aforementioned first association relationship may be indicated to the access management network element by certain network elements directly or indirectly, or it may be predefined; this application does not limit this. For example, the access management network element may receive the first association relationship from the OAM device or the data management network element. Optionally, when the first association relationship comes from the data management network element, it can be considered that the first association relationship is a contracted or authorized association relationship.

[0180] As an example, the first association relationship includes a correspondence between one or more access types and at least one type of service information supported by each access type. For instance, the first association relationship includes a correspondence between a first access type and at least one type of service information supported by the first access type. Here, the first access type refers to the type of track to which the non-terrestrial network device belongs, i.e., the track type of the non-terrestrial network device. In one possible implementation, the first access type and track type can be described interchangeably, and this is not limited thereto.

[0181] As another example, the first association includes one or more access types, at least one service information supported by each access type, and a correspondence between at least one non-terrestrial network device. For example, the first association includes a first access type, at least one service information supported by the first access type, and a correspondence between N non-terrestrial network devices, where N is a positive integer.

[0182] The following section introduces the 'Service Information Supported by the First Access Type'.

[0183] exist Figure 4 In the embodiments described above, service information (such as third-party service information) can be used to describe the services used by the terminal. For example, it may include the service type, which can be referenced... Figure 3 The description of step 301 will not be repeated here.

[0184] Optionally, the service type can be described interchangeably with network slice. As an example, a network slice can be associated with a DNN, such as a one-to-one association between a network slice and a DNN. Therefore, the service type can be replaced with: network slice and / or DNN. For example, the third service information may include the network slice and / or DNN requested by the terminal. Alternatively, the third service information may include the network slice and / or DNN assigned to the terminal.

[0185] Optionally, the network slice and / or DNN requested by the terminal can be carried in the session establishment request message. Optionally, the session establishment request message can be a PDU session establishment request message. Optionally, the session establishment request message may also include other information, which can be referred to in existing session establishment procedures, such as the session establishment procedures in existing versions of communication standards. Or refer to newly added session establishment procedures, such as the session establishment procedures in future communication standards, which are not limited here.

[0186] Optionally, the network slice allocated to the terminal can be the intersection of the network slice requested by the terminal and the network slice supported by the access management network element. For example, the network slice requested by the terminal includes network slice 1 and network slice 2, and the network slices supported by the access management network element include network slice 1, network slice 3 and network slice 4. The network slice allocated to the terminal can be network slice 1.

[0187] Optionally, the network slice allocated to the terminal can be referred to as the allowed network slice, and the allowed network slice can be called the allowed NSSAI.

[0188] The following section uses network slices and DNNs requested by the terminal as examples to introduce several possible correspondences in the first association relationship.

[0189] Table 3 illustrates the one-to-one correspondence between access types and service information. Specifically, in Table 3, when the access type is a low-track access type, the service information is network slice 1 and DNN1. When the access type is a mid-track access type, the service information is network slice 2 and DNN2.

[0190] Table 3

[0191]

[0192] Table 4 illustrates the one-to-many relationship between access type and service information. Specifically, in Table 4, when the access type is a low-level access type, the service information includes network slice 1 and DNN1, as well as network slice 2 and DNN2.

[0193] Table 4

[0194]

[0195] Table 5 illustrates the many-to-one relationship between access type and service information. Specifically, in Table 5, when the access type is low-track access type or mid-track access type, the service information is network slice 1 and DNN1.

[0196] Table 5

[0197]

[0198] Table 6 illustrates the many-to-many relationship between access type and service information. Specifically, in Table 6, when the access type is a low-track access type or a mid-track access type, the service information includes network slice 1 and DNN1, as well as network slice 2 and DNN2.

[0199] Table 6

[0200]

[0201]

[0202] Table 7 illustrates the one-to-one correspondence between access type, service information, and non-terrestrial network device. Specifically, in Table 4, when the access type is low-Earth orbit access, the service information is network slice 1 and DNN1, and the non-terrestrial network device is non-terrestrial network device 1. When the access type is mid-Earth orbit access, the service information is network slice 2 and DNN2, and the non-terrestrial network device is non-terrestrial network device 2.

[0203] Table 7

[0204]

[0205] Table 8 illustrates a one-to-many relationship between access type, service information, and any one of the non-terrestrial network devices. Specifically, in Table 8, when the access type is LOR access type, the service information includes network slice 1 and DNN1, as well as network slice 2 and DNN2, and the non-terrestrial network devices include non-terrestrial network device 1 and non-terrestrial network device 2.

[0206] Table 8

[0207]

[0208] Table 9 illustrates a many-to-one relationship between access type, service information, and any item in the non-terrestrial network device list. Specifically, in Table 5, when the access type is low-orbit or mid-orbit access type, the service information is network slice 1 and DNN1, and the non-terrestrial network device is non-terrestrial network device 1.

[0209] Table 9

[0210]

[0211] Table 10 illustrates a many-to-many relationship between access type, service information, and any item in the non-terrestrial network equipment. Specifically, in Table 10, when the access type is low-Earth orbit access type or mid-Earth orbit access type, the service information includes network slice 1 and DNN1, as well as network slice 2 and DNN2, and the non-terrestrial network equipment includes non-terrestrial network equipment 1 and non-terrestrial network equipment 2.

[0212] Table 10

[0213]

[0214] It should be noted that Tables 3 to 10 above are some examples of the correspondence between 'access type and service information and one or more non-terrestrial network devices'. In practical applications, the first association can be achieved through any row and / or any column of any one or more of the tables 3 to 10 above, and this application does not limit this.

[0215] Optionally, in the aforementioned first association relationship, at least one type of service information supported by the first access type may include third service information. Thus, the access management network element can determine the first access type based on the first association relationship and the third service information. For example, if the access type and service information have a many-to-many or many-to-one relationship, the access management network element can determine multiple access types based on the first association relationship and the third service information, and then randomly select one access type from these multiple access types as the first access type.

[0216] Optionally, when the first association relationship includes a first access type, at least one service information supported by the first access type, and a correspondence between N non-terrestrial network devices, the access management network element can also determine the non-terrestrial network device to which the third service information applies based on the first association relationship and the third service information. For example, if the access type and non-terrestrial network device have a one-to-many or many-to-many relationship, the access management network element can determine multiple non-terrestrial network devices based on the first association relationship and the third service information, and then randomly select one non-terrestrial network device from among the multiple non-terrestrial network devices as the non-terrestrial network device to which the third service information applies.

[0217] 402. The access management network element sends the first RFSP index corresponding to the first access type. The first RFSP index is used to trigger the access network device to perform redirection.

[0218] Accordingly, the access network device obtains the first RFSP index.

[0219] For example, the access management network element can receive a first RFSP index from the data management network element. For instance, the access management network element can send second indication information to the data management network element, the second indication information being used to obtain the first RFSP index corresponding to the first access type. Thus, the data management network element can send the first RFSP index to the access management network element. Optionally, when the first RFSP index comes from the data management network element, it can be considered that the first RFSP index is a subscribed or authorized RFSP index. Optionally, the second indication information is also used to indicate the non-terrestrial network equipment to which the third service information applies.

[0220] For example, the access management network element obtains the second association relationship, thereby determining the first RFSP index based on the second association relationship and the first access type.

[0221] Optionally, the second association relationship can be indicated to the access management network element by certain network elements directly or indirectly, or it can be predefined; this application does not limit this. For example, the access management network element can receive the second association relationship from the OAM device or the data management network element. Optionally, when the second association relationship comes from the data management network element, it can be considered that the second association relationship is a contracted or authorized association relationship.

[0222] As an example, the second association includes one or more access types and at least one RFSP index corresponding to each access type. For instance, the second association includes a correspondence between a first access type and at least one RFSP index.

[0223] As another example, the second association includes a correspondence between one or more access types, at least one RFSP index corresponding to each access type, and at least one non-terrestrial network device. For example, the second association includes a correspondence between a first access type, at least one RFSP index, and M non-terrestrial network devices, where M non-terrestrial network devices include the non-terrestrial network devices to which the third service information applies, and M is a positive integer.

[0224] The following describes several possible correspondences in the second association relationship.

[0225] Table 11 illustrates the one-to-one correspondence between access types and RFSP indices. Specifically, in Table 11, when the access type is a low-rail access type, the RFSP index is RFSP index 1. When the access type is a mid-rail access type, the RFSP index is RFSP index 2.

[0226] Table 11

[0227] Access type RFSP Index Low Rail Access Type RFSP Index 1 Medium Rail Access Type RFSP Index 2 … …

[0228] Table 12 illustrates the one-to-many relationship between access types and RFSP indices. Specifically, in Table 12, when the access type is a low-rail access type, the RFSP index includes RFSP index 1 and RFSP index 2.

[0229] Table 12

[0230] Access type RFSP Index Low Rail Access Type RFSP Index 1, RFSP Index 2 … …

[0231] Table 13 illustrates the many-to-one relationship between access types and RFSP indices. Specifically, in Table 13, when the access type is a low-rail access type or a mid-rail access type, the RFSP index is RFSP index 1.

[0232] Table 13

[0233] Access type RFSP Index Low-rail access type, medium-rail access type RFSP Index 1 … …

[0234] Table 14 illustrates the many-to-many relationship between access types and RFSP indices. Specifically, in Table 14, when the access type is a low-rail access type and a mid-rail access type, the RFSP indices are RFSP index 1 and RFSP index 2.

[0235] Table 14

[0236] Access type RFSP Index Low-rail access type, medium-rail access type RFSP Index 1, RFSP Index 2 … …

[0237] Table 15 illustrates the one-to-one correspondence between access type, RFSP index, and non-terrestrial network device. Specifically, in Table 15, when the access type is LOR (Low Rail) access, the RFSP index is RFSP index 1, and the non-terrestrial network device is non-terrestrial network device 1. When the access type is MOR (Medium Rail) access, the RFSP index is RFSP index 2, and the non-terrestrial network device is non-terrestrial network device 2.

[0238] Table 15

[0239]

[0240]

[0241] Table 16 illustrates a one-to-many relationship between access type and any item in the RFSP index and non-terrestrial network device. Specifically, in Table 16, when the access type is LOR access type, the RFSP index includes RFSP index 1 and RFSP index 2, and the non-terrestrial network device includes non-terrestrial network device 1 and non-terrestrial network device 2.

[0242] Table 16

[0243]

[0244] Table 17 illustrates a many-to-one relationship between access type and either the RFSP index or the non-terrestrial network device. Specifically, in Table 17, when the access type is either LOR or MOR, the RFSP index is RFSP index 1, and the non-terrestrial network device is non-terrestrial network device 1.

[0245] Table 17

[0246] Access type RFSP Index Non-terrestrial network equipment Low-rail access type, medium-rail access type RFSP Index 1 Non-terrestrial network equipment 1 … … …

[0247] Table 18 illustrates a many-to-many relationship between access type and any item in the RFSP index and non-terrestrial network device. Specifically, in Table 18, when the access type is low-orbit access type and mid-orbit access type, the RFSP index is RFSP index 1 and RFSP index 2, and the non-terrestrial network device includes non-terrestrial network device 1 and non-terrestrial network device 2.

[0248] Table 18

[0249]

[0250] It should be noted that Tables 11 to 18 above are some examples of the correspondence between 'access type and RFSP index and one or more non-terrestrial network devices'. In practical applications, the second association can be implemented through any row and / or any column of any one or more of the tables 11 to 18 above, and this application does not limit this.

[0251] Optionally, in the aforementioned second association relationship, at least one RFSP index corresponding to the first access type includes the first RFSP index. Thus, the access management network element can determine the first RFSP index based on the second association relationship and the first access type. For example, if the access type and RFSP index have a many-to-many or many-to-one relationship, the access management network element can determine multiple RFSP indices based on the second association relationship and the first access type, and then randomly select one RFSP index from these multiple RFSP indices as the first RFSP index.

[0252] Optionally, when the second association relationship includes the correspondence between the first access type, at least one RFSP index, and M non-terrestrial network devices, the access management network element can determine the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies. For example, if the RFSP index has a many-to-many or many-to-one relationship with any one or more of the access type and non-terrestrial network devices, the access management network element can determine multiple RFSP indices based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies, and then randomly select one RFSP index from the multiple RFSP indices as the first RFSP index.

[0253] The following section describes the circumstances under which the access management network element sends the first RFSP index.

[0254] Optionally, the access management network element sends a first RFSP index if the first condition is met. Optionally, the first condition includes: the first access type is different from the terminal's current access type and / or the non-terrestrial network device to which the third service information applies is different from the non-terrestrial network device to which the terminal requests access.

[0255] Optionally, the current access type of the terminal can be understood as the specified type of non-terrestrial network equipment accessed by the terminal before, during, or after the access management network element obtains the third service information. For example, the specified type of non-terrestrial network equipment accessed by the terminal after the access management network element obtains the third service information can be understood as the specified type of non-terrestrial network equipment accessed by the terminal before the access management network element sends the first RFSP index. This application does not limit this.

[0256] Optionally, when the access management network element receives the first access type from the session management network element, the access management network element can also obtain the third service information applicable to the non-terrestrial network equipment from the session management network element.

[0257] Optionally, the non-terrestrial network device that the terminal requests access to can be carried in the same message or a different message as the network slice and / or DNN requested by the terminal. This message could be, for example, a session request message, such as a PDU session establishment request message.

[0258] Optionally, in Figure 4 In the embodiments described, the process of 'determining the first access type to which the third service information applies and the first RFSP index corresponding to the first access type' can be executed by the access management network element or the session management network element alone, or by the access management network element and the session management network element jointly. Alternatively, the process of 'determining the first access type to which the third service information applies' can be executed by the access management network element or the session management network element alone, while the process of 'determining the first RFSP index corresponding to the first access type' can be executed by the data management network element.

[0259] For example, the process of 'determining the first access type to which the third service information applies and the first RFSP index corresponding to the first access type' is performed independently by the access management network element. For instance, determining the first access type to which the third service information applies may include: obtaining a first association relationship, and determining the first access type based on the first association relationship and the third service information. For instance, determining the first RFSP index corresponding to the first access type may include: the access management network element determining the first RFSP index based on a second association relationship and the first access type, where the second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0260] For example, the process of 'determining the first access type to which the third service information applies and the first RFSP index corresponding to the first access type' is performed independently by the session management network element. Optionally, when the process of 'determining the first access type to which the third service information applies' is performed independently by the session management network element, the access management network element may also send the third service information to the session management network element so that the session management network element can determine the first access type to which the third service information applies.

[0261] For example, the session management network element determining the applicable first access type for the third service information may include: obtaining a first association relationship, and determining the first access type based on the first association relationship and the third service information. The method by which the session management network element obtains the first association relationship can be referenced from the method by which the access management network element obtains the first association relationship, and will not be elaborated here. The method by which the session management network element determines the first access type based on the first association relationship and the third service information can also be referenced from the method by which the access management network element determines the first access type based on the first association relationship and the third service information, and will not be elaborated here.

[0262] For example, the session management network element determining the first RFSP index corresponding to the first access type may include: the session management network element determining the first RFSP index based on a second association relationship and the first access type, wherein the second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index. The method by which the session management network element obtains the second association relationship can be referenced from the method by which the access management network element obtains the second association relationship, and will not be elaborated here. The method by which the session management network element determines the first RFSP index based on the second association relationship and the first access type can also be referenced from the method by which the access management network element determines the first RFSP index based on the second association relationship and the first access type, and will not be elaborated here.

[0263] For example, the process of 'determining the first access type to which the third service information applies' is performed independently by the access management network element, and the process of 'determining the first RFSP index corresponding to the first access type' is performed independently by the session management network element or the data management network element. Optionally, when the process of 'determining the first RFSP index corresponding to the first access type' is performed independently by the session management network element or the data management network element, the access management network element may also indicate the first access type to the session management network element or the data management network element.

[0264] For example, the session management network element receives second indication information from the access management network element. This second indication information is used to obtain the first RFSP index corresponding to the first access type, and includes the first access type. In this way, the session management network element can determine the first RFSP index based on the second association and the first access type.

[0265] For example, the data management network element receives second indication information from the access management network element. This second indication information is used to obtain the first RFSP index corresponding to the first access type, and includes the first access type. Thus, the data management network element can determine the first RFSP index based on the second association relationship and the first access type. Optionally, the data management network element can store the second association relationship locally or obtain it from the OAM device. The method by which the data management network element determines the first RFSP index based on the second association relationship and the first access type can be referenced from the method by which the access management network element determines the first RFSP index based on the second association relationship and the first access type, and will not be elaborated upon here.

[0266] It should be noted that the above are some examples of which network elements 'determine the first access type corresponding to the third service information and the first RFSP index corresponding to the first access type'. These examples can also be combined in other ways to achieve 'determining the first access type corresponding to the third service information and the first RFSP index corresponding to the first access type'. This application does not list them all.

[0267] As can be seen from the above embodiments, the access management network element or session management network element can determine the first access type applicable to the third service information, thereby sending the first RFSP index corresponding to the first access type. This allows the access network device to perform redirection, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or modification, thereby ensuring the consistency between the service type and the access type as much as possible, reducing the situation where service transmission requirements cannot be met due to mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0268] above Figure 4 The method embodiments shown include many possible implementation schemes, which will be discussed below. Figure 5 and Figure 6 Each of the accompanying diagrams provides an example illustrating a portion of the implementation schemes. Specifically, in... Figure 5 and Figure 6 In any of the attached figures, the terminal is represented by UE, the access network device by RAN, the access management network element by AMF, the unified data management network element by UDM, and the session management network element by SMF. Figure 5 and Figure 6 For any related concepts, operations, or logical relationships not explained in any of the attached diagrams, please refer to [the relevant documentation / reference]. Figure 4 The corresponding descriptions in the illustrated embodiments will not be repeated here.

[0269] See Figure 5 , Figure 5 This is a flowchart illustrating another communication method provided in an embodiment of this application. Figure 5As shown, the method includes, but is not limited to, the following steps:

[0270] 501. The UE sends a session establishment request message, which includes third-party service information.

[0271] Accordingly, the AMF receives a session establishment request message.

[0272] 502. The AMF determines the first access type to which the third service information applies. The first access type includes at least one of the following: low rail access type, medium rail access type, high rail access type, or multi-rail access type.

[0273] 503. The AMF sends a second indication message to the UDM. The second indication message is used to obtain the first RFSP index corresponding to the first access type.

[0274] Accordingly, UDM receives a second instruction from AMF.

[0275] 504. UDM sends the first RFSP index to AMF.

[0276] Accordingly, the AMF receives the first RFSP index from the UDM.

[0277] 505. The AMF sends the first RFSP index to the RAN. The first RFSP index is used to trigger the access network equipment to perform redirection.

[0278] Accordingly, the RAN receives the first RFSP index from the AMF.

[0279] As can be seen from the above embodiments, the AMF can obtain the third service information from the session establishment request message from the UE, thereby determining the first access type applicable to the third service information. Based on the first access type, the AMF obtains the first RFSP index corresponding to the first access type from the UDM and indicates the first RFSP index to the RAN. This allows the RAN to perform redirection, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or modification, thereby ensuring the consistency between the service type and the access type as much as possible, reducing the possibility of service transmission requirements not being met due to mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0280] See Figure 6 , Figure 6 This is a flowchart illustrating another communication method provided in an embodiment of this application. Figure 6 As shown, the method includes, but is not limited to, the following steps:

[0281] 601. The UE sends a session establishment request message, which includes third-party service information.

[0282] Accordingly, the AMF receives a session establishment request message.

[0283] 602. AMF sends third service information to SMF.

[0284] Accordingly, the SMF receives third service information from the AMF.

[0285] 603. The SMF determines the first access type to which the third service information applies. The first access type includes at least one of the following: low-rail access type, medium-rail access type, high-rail access type, or multi-rail access type.

[0286] 604. The SMF sends a second indication message to the UDM. The second indication message is used to obtain the first RFSP index corresponding to the first access type.

[0287] Accordingly, the UDM receives a second instruction from the SMF.

[0288] 605. UDM sends the first RFSP index to SMF.

[0289] Accordingly, the SMF receives the first RFSP index from the UDM.

[0290] 606. The SMF sends the first RFSP index to the RAN. The first RFSP index is used to trigger the access network equipment to perform redirection.

[0291] Accordingly, the RAN receives the first RFSP index from the SMF.

[0292] For example, the SMF sends the first RFSP index to the AMF, and the AMF sends the first RFSP index to the RAN.

[0293] As can be seen from the above embodiments, the AMF can obtain the third service information from the session establishment request message from the UE and indicate the third service information to the SMF. This allows the SMF to determine the first access type to which the third service information applies. Based on the first access type, the SMF obtains the first RFSP index corresponding to the first access type from the UDM and indicates the first RFSP index to the RAN. This allows the RAN to perform redirection, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or modification, thereby ensuring the consistency between the service type and the access type as much as possible, reducing the possibility of service transmission requirements not being met due to mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0294] See Figure 7 , Figure 7 This is a flowchart illustrating a communication method provided in an embodiment of this application. For example... Figure 7As shown, the method includes, but is not limited to, the following steps:

[0295] 701. The terminal sends a registration request to the access management network element. The registration request includes a reason value for establishing a connection. The reason value corresponds to a first access type. The first access type includes at least one of the following: low-rail access type, medium-rail access type, high-rail access type, or multi-rail access type.

[0296] Accordingly, the access management network element receives the registration request from the terminal.

[0297] Optionally, the terminal can initiate a registration process through a registration request. The reason value indicates the reason for triggering the registration process. Alternatively, it can be understood as: the reason value indicates the reason why the terminal sent the registration request. Or, the reason value can be called an establishment cause value. For example, in this application, the reason value can be used to indicate the service (or service type) that initiated the registration process, which includes, but is not limited to, one or more of the following: terminal-initiated data (Mo-Data), terminal-initiated short message (Mo-SMS), or terminal-initiated mission critical service (Mission Critical). It can also be described as the reason value indicating at least one of the following: Mo-Data, Mo-SMS, or Mission Critical.

[0298] Optionally, there is a correspondence between services and access types. Specifically, the correspondence between services and access types can be shown in Table 19. For example, when the access type is low-rail access type, the reason value indicates Mo-Data and Mo-SMS, and so on, which will not be elaborated here.

[0299] Table 19

[0300] Access type business Low Rail Access Type Mo-Data, Mo-SMS Medium Rail Access Type Mission Critical High-speed rail access type Mo-SMS Low-rail access type, medium-rail access type Mo-Data, Mo-SMS, Mission Critical … …

[0301] Optionally, the relationship between the service and the access type can be one-to-one, one-to-many, many-to-one, or many-to-many, and this application does not limit this.

[0302] Optionally, the correspondence between services and access types can be indicated to the access management network element by certain network elements directly or indirectly, or predefined; this application does not limit this. For example, taking the correspondence between services indicated by the cause value and the first access type as an example, the access management network element can receive a third association relationship from the OAM device or the data management network element. The third association relationship includes the correspondence between services indicated by the cause value and the first access type. Optionally, when the third association relationship comes from the data management network element, it can be considered as a subscribed or authorized association relationship.

[0303] The following describes how to determine the first access type corresponding to the cause value.

[0304] For example, the access management network element can determine the first access type based on the service indicated by the cause value and the third association relationship. For instance, if the service and access type have a one-to-many or many-to-many relationship, the access management network element can determine multiple access types based on the service indicated by the cause value and the third association relationship, and thus randomly select one access type from the multiple access types as the first access type.

[0305] For example, the access management network element can receive a first access type from the session management network element. In this case, the access management network element can send a cause value to the session management network element, enabling the session management network element to determine the first access type based on the service and third association indicated by the cause value. For instance, if the service and access type have a one-to-many or many-to-many relationship, the session management network element can determine multiple access types based on the service and third association indicated by the cause value, and thus randomly select one access type from these multiple access types as the first access type, and then indicate the first access type to the access management network element.

[0306] 702. The access management network element sends the first RFSP index corresponding to the first access type to the access network device. The first RFSP index is used to trigger the access network device to perform redirection.

[0307] Accordingly, the access network device receives the first RFSP index from the access management network element.

[0308] Optionally, the process of the access management network element determining the first RFSP index corresponding to the first access type in step 702 can participate in... Figure 4 The relevant description of step 402 will not be repeated here.

[0309] Optionally, the access management network element sending the first RFSP index to the access network device may include: the access management network element sending the first RFSP index to the access network device when the first access type is different from the terminal's current access type. Optionally, the terminal's current access type can be understood as the specified type of non-terrestrial network equipment accessed by the terminal before, when, or after the access management network element obtains the third service information. For example, the specified type of non-terrestrial network equipment accessed by the terminal after the access management network element obtains the third service information can be understood as the specified type of non-terrestrial network equipment accessed by the terminal before the access management network element sends the first RFSP index; this application does not limit this.

[0310] Optionally, in Figure 7In the embodiments described, the process of 'determining the first access type corresponding to the cause value and the first RFSP index corresponding to the first access type' can be executed by the access management network element or the session management network element alone, or by the access management network element and the session management network element jointly. Alternatively, the process of 'determining the first access type to which the third service information applies' can be executed by the access management network element or the session management network element alone, while the process of 'determining the first RFSP index corresponding to the first access type' can be executed by the data management network element.

[0311] For example, the process of 'determining the first access type corresponding to the cause value and the first RFSP index corresponding to the first access type' is performed independently by the access management network element. For instance, determining the first access type corresponding to the cause value may include: obtaining a third association relationship, and determining the first access type based on the third association relationship and the service indicated by the cause value. For instance, determining the first RFSP index corresponding to the first access type may include: the access management network element determining the first RFSP index based on a second association relationship and the first access type, where the second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0312] For example, the process of 'determining the first access type corresponding to the cause value and the first RFSP index corresponding to the first access type' is performed independently by the session management network element. Optionally, when the process of 'determining the first access type corresponding to the cause value' is performed independently by the session management network element, the access management network element may also send the cause value to the session management network element so that the session management network element can determine the first access type corresponding to the cause value.

[0313] For example, the session management network element determining the first access type corresponding to the cause value may include: obtaining a third association relationship, and determining the first access type based on the third association relationship and the service indicated by the cause value. The method by which the session management network element obtains the third association relationship can be referenced from the method by which the access management network element obtains the third association relationship, and will not be elaborated here. The method by which the session management network element determines the first access type based on the third association relationship and the service indicated by the cause value can also be referenced from the method by which the access management network element determines the first access type based on the third association relationship and the service indicated by the cause value, and will not be elaborated here.

[0314] For example, the session management network element determining the first RFSP index corresponding to the first access type may include: the session management network element determining the first RFSP index based on a second association relationship and the first access type, wherein the second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index. The method by which the session management network element obtains the second association relationship can be referenced from the method by which the access management network element obtains the second association relationship, and will not be elaborated here. The method by which the session management network element determines the first RFSP index based on the second association relationship and the first access type can also be referenced from the method by which the access management network element determines the first RFSP index based on the second association relationship and the first access type, and will not be elaborated here.

[0315] For example, 'determining the first access type corresponding to the cause value' is performed independently by the access management network element, and 'determining the first RFSP index corresponding to the first access type' is performed independently by the session management network element or the data management network element. Optionally, when 'the first access type corresponding to the cause value' is performed independently by the session management network element or the data management network element, the access management network element may also indicate the first access type to the session management network element or the data management network element.

[0316] For example, the session management network element receives second indication information from the access management network element. This second indication information is used to obtain the first RFSP index corresponding to the first access type, and includes the first access type. In this way, the session management network element can determine the first RFSP index based on the second association and the first access type.

[0317] For example, the data management network element receives second indication information from the access management network element. This second indication information is used to obtain the first RFSP index corresponding to the first access type, and includes the first access type. Thus, the data management network element can determine the first RFSP index based on the second association relationship and the first access type. Optionally, the data management network element can store the second association relationship locally or obtain it from the OAM device. The method by which the data management network element determines the first RFSP index based on the second association relationship and the first access type can be referenced from the method by which the access management network element determines the first RFSP index based on the second association relationship and the first access type, and will not be elaborated upon here.

[0318] It should be noted that the above are some examples of which network elements 'determine the first access type corresponding to the cause value and the first RFSP index corresponding to the first access type'. Other combinations of these examples can also be made to achieve 'determine the first access type corresponding to the cause value and the first RFSP index corresponding to the first access type'. This application does not list them all.

[0319] As can be seen from the above embodiments, the access management network element determines the first access type based on the reason value for establishing the connection, thereby sending the first RFSP index corresponding to the first access type. This allows the access network device to perform redirection, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or modification, thereby ensuring the consistency between the service type and the access type as much as possible, reducing the situation where service transmission requirements cannot be met due to mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0320] above Figure 7 The method embodiments shown include many possible implementation schemes, which will be discussed below. Figure 8 Examples of some of the implementation schemes are provided. Among them, in... Figure 8 In this document, the terminal is referred to as UE, the access network equipment as RAN, the access management network element as AMF, and the unified data management network element as UDM. Figure 8 For any unexplained related concepts, operations, or logical relationships, please refer to [link / reference]. Figure 7 The corresponding descriptions in the illustrated embodiments will not be repeated here.

[0321] 801. The UE sends a registration request to the AMF. The registration request includes a reason value for establishing a connection. The reason value corresponds to the first access type. The first access type includes at least one of the following: low-rail access type, mid-rail access type, high-rail access type, or multi-rail access type.

[0322] Accordingly, the AMF receives registration requests from the UE.

[0323] 802. The AMF sends a second indication message to the UDM. The second indication message is used to obtain the first RFSP index corresponding to the first access type.

[0324] Accordingly, UDM receives a second instruction from AMF.

[0325] 803. UDM sends the first RFSP index to AMF.

[0326] Accordingly, the AMF receives the first RFSP index from the UDM.

[0327] 804. The AMF sends the first RFSP index to the RAN. The first RFSP index is used to trigger the access network equipment to perform redirection.

[0328] Accordingly, the RAN receives the first RFSP index from the AMF.

[0329] As can be seen in the above embodiments, the AMF can obtain the reason value for the UE to establish a connection, thereby determining the first access type corresponding to the reason value. Based on the first access type, it then obtains the first RFSP index corresponding to the first access type from the UDM and indicates the first RFSP index to the RAN. This allows the RAN to perform redirection, such as redirecting the terminal to another cell. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or modification, thereby ensuring the consistency between the service type and the access type as much as possible, reducing the possibility of service transmission requirements not being met due to mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0330] It is understood that, in order to achieve the aforementioned functions, the device includes corresponding hardware structures and / or software modules for performing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0331] This application embodiment can divide the terminal, access management network element, session management network element, data management network element, or policy control network element into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0332] See Figure 9 , Figure 9 This is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 900 can be applied to the above-described... Figures 3 to 8 In any of the embodiments shown in the figure, such as Figure 9As shown, the communication device 900 includes a processing module 901 and a transceiver module 902. The processing module 901 may be one or more processors, and the transceiver module 902 may be a transceiver or a communication interface. This communication device can be used to implement terminals, access management network elements, session management network elements, data management network elements, or policy control network elements involved in any of the above method embodiments, or to implement the functions of network elements involved in any of the above method embodiments. The network element or network function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (e.g., a cloud platform). Optionally, the communication device 900 may also include a storage module 903 for storing the program code and data of the communication device 900. It should be understood that regardless of whether these functional modules are subdivided or combined, the general flow performed by the communication device 900 in implementing any of the above method embodiments is the same. For example, the transceiver module 902 in the above communication device 900 may include a receiving module and / or a sending module; of course, the transceiver module can also be called a communication module. In one implementation, each module can have its own program code (or program instructions). When the program code corresponding to each module is run on the processor, it causes the unit to execute the corresponding process to achieve the corresponding function.

[0333] In one example, when the communication device functions as a terminal or is a chip used in a terminal, i.e., a chip for a terminal, it executes the steps performed by the terminal in the above method embodiments. The transceiver module 902 is used for specific execution. Figures 3 to 8 The sending and / or receiving actions performed by the terminal in any of the illustrated embodiments may include, for example, other processes that support the terminal in performing the techniques described herein. The processing module 901 may be used to support the communication device 900 in performing the processing actions in the above method embodiments, for example, supporting the terminal in performing other processes that support the techniques described herein.

[0334] For example, the transceiver module 902 is used to obtain policy information, which indicates the correspondence between at least one type of service information and a first access type, wherein the first access type is the access type to which at least one type of service information is applicable; the processing module 901 is used to determine the first access type based on the policy information, wherein the first access type includes at least one of the following: low-track access type, mid-track access type, high-track access type, or multi-track access type; the transceiver module 902 is also used to initiate session establishment or session modification through the first access type.

[0335] Optionally, when obtaining the first association relationship, the transceiver module 902 is used to receive policy information from the policy control network element or the access management network element.

[0336] Optionally, when determining the first access type based on policy information, the processing module 901 is used to: determine the first service information of the terminal, wherein the first service information belongs to at least one type of service information; and determine the first access type to which the first service information applies based on the first service information and policy information.

[0337] In one example, when the communication device functions as a policy control network element or is a chip applied within a policy control network element (i.e., a chip used in a policy control network element), it executes the steps performed by the policy control network element in the above method embodiments. The transceiver module 902 is used for specific execution. Figures 3 to 8 The actions of sending and / or receiving performed by the policy control network element in any of the illustrated embodiments may include, for example, other processes that support the policy control network element in performing the techniques described herein. The processing module 901 may be used to support the communication device 900 in performing the processing actions in the above method embodiments, for example, supporting the policy control network element in performing other processes that support the techniques described herein.

[0338] For example, processing module 901 is used to determine policy information, which indicates the correspondence between at least one type of service information and a first access type. The first access type is the access type to which at least one type of service information is applicable. The first access type includes at least one of the following: low-track access type, mid-track access type, high-track access type, or multi-track access type. Transceiver module 902 is used to send the policy information to the terminal.

[0339] Optionally, when determining policy information, the processing module 901 is used to obtain the terminal's subscription information from the data management network element through the transceiver module 902, and / or to obtain the first indication information from the application function network element through the transceiver module 902; and to determine the policy information based on the subscription information and / or the first indication information. The terminal's subscription information or the first indication information is used to indicate the track information and second service information of the non-terrestrial network devices that the terminal can access. The second service information is associated with the track information and belongs to at least one type of service information. The track information includes track height parameters and / or track type, and the track type includes low-Earth orbit, medium-Earth orbit, high-Earth orbit, or multi-track.

[0340] In one example, when the communication device functions as an access management network element or is a chip used in an access management network element (i.e., a chip used in an access management network element), it executes the steps performed by the access management network element in the above method embodiments. The transceiver module 902 is used for specific execution. Figures 3 to 8 The actions of sending and / or receiving performed by the access management network element in any of the illustrated embodiments may include, for example, other processes that support the access management network element in performing the techniques described herein. The processing module 901 may be used to support the communication device 900 in performing the processing actions in the above method embodiments, for example, supporting the access management network element in performing other processes that support the techniques described herein.

[0341] For example, the processing module 901 is used to determine the first access type to which the third service information applies, the first access type including at least one of the following: low-rail access type, medium-rail access type, high-rail access type or multi-rail access type; the transceiver module 902 is used to send the first radio access technology / frequency selection priority RFSP index corresponding to the first access type, the first RFSP index being used to trigger the access network device to perform redirection.

[0342] Optionally, when determining the first access type to which the third service information applies, the processing module 901 is used to obtain the first association relationship through the transceiver module 902, and determine the first access type based on the first association relationship and the third service information.

[0343] Optionally, when obtaining the first association relationship, the processing module 901 is used to receive the first association relationship from the OAM device or data management network element through the transceiver module 902.

[0344] Optionally, when determining the first access type to which the third service information applies, the processing module 901 is used to receive the first access type from the session management network element through the transceiver module 902.

[0345] Optionally, the processing module 901 is also used to send third service information to the session management network element.

[0346] Optionally, when sending the first RFSP index corresponding to the first access type, the transceiver module 902 is configured to send the first RFSP index if a first condition is met. The first condition includes: the first access type is different from the terminal's current access type and / or the non-terrestrial network device to which the third service information applies is different from the non-terrestrial network device to which the terminal requests access.

[0347] Optionally, the first association relationship includes a first access type, at least one service information supported by the first access type, and a correspondence between N non-terrestrial network devices, where N is a positive integer. The processing module 901 is further configured to determine the non-terrestrial network devices to which the third service information applies based on the first association relationship and the third service information.

[0348] Optionally, the transceiver module 902 is also used to receive third service information from the session management network element for use with non-terrestrial network devices.

[0349] Optionally, the transceiver module 902 is further configured to receive a first RFSP index from a data management network element. Alternatively, the processing module 901 is further configured to obtain a second association relationship through the transceiver module 902, and determine the first RFSP index based on the second association relationship and the first access type. The second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0350] Optionally, the transceiver module 902 is further configured to send second indication information to the data management network element, the second indication information being used to obtain the first RFSP index, and the second indication information including the first access type.

[0351] Optionally, when acquiring the second association relationship, the transceiver module 902 is used to receive the second association relationship from the OAM device or the data management network element.

[0352] Optionally, the second association relationship includes the correspondence between the first access type, at least one RFSP index, and M non-terrestrial network devices, where the M non-terrestrial network devices include the non-terrestrial network devices to which the third service information applies, and M is a positive integer. When determining the first RFSP index based on the second association relationship and the first access type, the processing module 901 is used to determine the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies.

[0353] For example, the transceiver module 902 is configured to: receive a registration request from a terminal, the registration request including a reason value for establishing a connection, the reason value corresponding to a first access type, the first access type including at least one of the following: low-rail access type, medium-rail access type, high-rail access type, or multi-rail access type; and send a first RFSP index corresponding to the first access type to the access network device, the first RFSP index being used to trigger the access network device to perform a redirection.

[0354] Optionally, the processing module 901 is further configured to obtain a third association relationship through the transceiver module 902, and determine a first access type based on the service indicated by the cause value and the third association relationship. The third association relationship includes the correspondence between the service indicated by the cause value and the first access type.

[0355] Optionally, when acquiring the third association relationship, the transceiver module 902 is used to receive the third association relationship from the OAM device or the data management network element.

[0356] Optionally, the transceiver module 902 is further configured to receive a first RFSP index from a data management network element. Alternatively, the processing module 901 is further configured to obtain a second association relationship through the transceiver module 902, and determine the first RFSP index based on the second association relationship and the first access type. The second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0357] Optionally, the transceiver module 902 is further configured to send second indication information to the data management network element, the second indication information being used to obtain the first RFSP index, and the second indication information including the first access type.

[0358] In one example, when the communication device functions as a session management network element or is a chip used in a session management network element (i.e., a chip used in a session management network element), it executes the steps performed by the session management network element in the above method embodiments. The transceiver module 902 is used for specific execution. Figures 3 to 8 The sending and / or receiving actions performed by the session management network element in any of the illustrated embodiments may include, for example, other processes that support the session management network element in performing the techniques described herein. The processing module 901 may be used to support the communication device 900 in performing the processing actions in the above method embodiments, for example, supporting the session management network element in performing other processes that support the techniques described herein.

[0359] For example, the processing module 901 is used to determine the first access type to which the third service information applies, the first access type including at least one of the following: low-rail access type, medium-rail access type, high-rail access type or multi-rail access type; the transceiver module 902 is used to send the first radio access technology / frequency selection priority RFSP index corresponding to the first access type, the first RFSP index being used to trigger the access network device to perform redirection.

[0360] Optionally, when determining the first access type to which the third service information applies, the processing module 901 is used to obtain the first association relationship through the transceiver module 902, and determine the first access type based on the first association relationship and the third service information.

[0361] Optionally, when obtaining the first association relationship, the processing module 901 is used to receive the first association relationship from the OAM device or data management network element through the transceiver module 902.

[0362] Optionally, when determining the first access type to which the third service information applies, the processing module 901 is used to receive the first access type from the access management network element through the transceiver module 902.

[0363] Optionally, when sending the first RFSP index corresponding to the first access type, the transceiver module 902 is configured to send the first RFSP index if a first condition is met. The first condition includes: the first access type is different from the terminal's current access type and / or the non-terrestrial network device to which the third service information applies is different from the non-terrestrial network device to which the terminal requests access.

[0364] Optionally, the first association relationship includes a first access type, at least one service information supported by the first access type, and a correspondence between N non-terrestrial network devices, where N is a positive integer. The processing module 901 is further configured to determine the non-terrestrial network devices to which the third service information applies based on the first association relationship and the third service information.

[0365] Optionally, the transceiver module 902 is also used to receive third service information applicable to non-terrestrial network devices from the access management network element.

[0366] Optionally, the transceiver module 902 is further configured to receive a first RFSP index from a data management network element. Alternatively, the processing module 901 is further configured to obtain a second association relationship through the transceiver module 902, and determine the first RFSP index based on the second association relationship and the first access type. The second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0367] Optionally, the transceiver module 902 is further configured to send second indication information to the data management network element, the second indication information being used to obtain the first RFSP index, and the second indication information including the first access type.

[0368] Optionally, when acquiring the second association relationship, the transceiver module 902 is used to receive the second association relationship from the OAM device or the data management network element.

[0369] Optionally, the second association relationship includes the correspondence between the first access type, at least one RFSP index, and M non-terrestrial network devices, where the M non-terrestrial network devices include the non-terrestrial network devices to which the third service information applies, and M is a positive integer. When determining the first RFSP index based on the second association relationship and the first access type, the processing module 901 is used to determine the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies.

[0370] In one example, when the communication device functions as a data management network element or is a chip used in a data management network element (i.e., a chip used in a data management network element), it executes the steps performed by the data management network element in the above method embodiments. The transceiver module 902 is used for specific execution. Figures 3 to 8The actions of sending and / or receiving performed by the data management network element in any of the illustrated embodiments may include, for example, other processes that support the data management network element in performing the techniques described herein. The processing module 901 may be used to support the communication device 900 in performing the processing actions in the above method embodiments, for example, supporting the data management network element in performing other processes that support the techniques described herein.

[0371] For example, transceiver module 902 is configured to: receive second indication information from access management network element, the second indication information being used to obtain a first RFSP index corresponding to a first access type, the first access type being an access type to which the third service information is applicable; and send the first RFSP index to access management network element. Alternatively, transceiver module 902 is configured to: receive second indication information from session management network element, the second indication information being used to obtain a first RFSP index corresponding to a first access type, the first access type being an access type to which the third service information is applicable; and send the first RFSP index to session management network element.

[0372] Optionally, the processing module 901 is used to obtain a second association relationship through the transceiver module 902, and determine a first RFSP index based on the second association relationship and the first access type. The second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

[0373] Optionally, the second association relationship includes the correspondence between the first access type, at least one RFSP index, and M non-terrestrial network devices, where the M non-terrestrial network devices include the non-terrestrial network devices to which the third service information applies, and M is a positive integer. When determining the first RFSP index based on the second association relationship and the first access type, the processing module 901 is used to determine the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network devices to which the third service information applies.

[0374] In one possible implementation, when the aforementioned device is a chip, the transceiver module 902 can be a communication interface, pins, or circuits. The communication interface can be used to input data to be processed to the processor and can output the processor's processing results. Specifically, the communication interface can be a general purpose input / output (GPIO) interface, which can connect to multiple peripheral devices (such as LCD displays, cameras, radio frequency (RF) modules, antennas, etc.). The communication interface is connected to the processor via a bus.

[0375] The processing module 901 may be a processing circuit, which may be one or more processors, or all or part of the circuitry within one or more processors used for control and / or processing. The processing circuit or processor may execute computer execution instructions stored in the storage module to cause the chip to perform... Figures 3 to 8 The method involved in any of the embodiments shown is described. Further, the processor may include a controller, an arithmetic logic unit (ALU), and registers. For example, the controller is primarily responsible for instruction decoding and issuing control signals for the operations corresponding to the instructions. The ALU is primarily responsible for performing fixed-point or floating-point arithmetic operations, shift operations, and logical operations, and can also perform address operations and translations. The registers are primarily responsible for storing register operands and intermediate operation results temporarily stored during instruction execution. In specific implementations, the processor's hardware architecture may be an application-specific integrated circuit (ASIC) architecture, a microprocessor without interlocked piped stages architecture (MIPS) architecture, an advanced reduced instruction set machine (RISC) machine (ARM) architecture, or a network processor (NP) architecture, etc. The processor may be single-core or multi-core. The storage module may be an in-chip storage module, such as a register or cache. Storage modules can also be external to the chip, such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.

[0376] It should be noted that the functions of the processor and interface can be implemented through hardware design, software design, or a combination of both; no restrictions are imposed here.

[0377] Figure 10This is a schematic diagram of another communication device provided in an embodiment of this application. It is understood that the communication device 1010 includes necessary means such as modules, units, elements, circuits, or interfaces, appropriately configured together to execute this solution. The communication device 1010 may be the aforementioned terminal, access management network element, session management network element, data management network element, or policy control network element, or it may be a component (e.g., a chip) in these devices, used to implement the methods described in the above method embodiments. The communication device 1010 includes one or more processors 1011. The processor 1011 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (e.g., terminal, access management network element, session management network element, data management network element, policy control network element, or chip, etc.), execute software programs, and process data from the software programs.

[0378] Optionally, in one design, the processor 1011 may include a program 1013 (sometimes also referred to as code or instructions), which can be executed on the processor 1011 to cause the communication device 1010 to perform the methods described in the above embodiments. In yet another possible design, the communication device 1010 includes circuitry (…). Figure 10 (Not shown), the circuit is used to implement the functions of the terminal, access management network element, session management network element, data management network element, and policy control network element in the above embodiments. Optionally, the communication device 1010 may include one or more memories 1012, on which a program 1014 (sometimes also referred to as code or instructions) is stored. The program 1014 can be run on the memory 1012, causing the communication device 1010 to execute the methods described in the above method embodiments.

[0379] Optionally, data may also be stored in the processor 1011 and / or the memory 1012. The processor and memory may be configured separately or integrated together.

[0380] Optionally, when the communication device 1010 is a terminal, access management network element, session management network element, data management network element, or policy control network element, it may further include a transceiver 1015 and / or an antenna 1016. The processor 1011, sometimes referred to as a processing unit, controls the communication device (e.g., a terminal or access network equipment). The transceiver 1015, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the transmission and reception functions of the communication device via the antenna 1016. Optionally, the transceiver 1015 may include a receiver and / or a transmitter. The receiver may be referred to as a receiving unit, receiver, or receiving circuit. The transmitter may be referred to as a transmitting unit, transmitter, or transmitting circuit.

[0381] Optionally, if the communication device 1010 is a chip for a terminal, access management network element, session management network element, data management network element, or policy control network element, it may also include transceiver circuitry, such as an input / output interface, or a transceiver interface.

[0382] This application also provides a communication device, which includes at least one processor; wherein the at least one processor is configured to execute... Figures 3 to 8 The method described in any of the embodiments shown.

[0383] This application also provides a computer-readable storage medium storing computer instructions, which, when executed, cause the computer to perform actions such as... Figures 3 to 8 The method described in any of the embodiments shown.

[0384] This application also provides a computer program product, which includes: computer program code, which, when executed by a computer, causes the computer to perform actions such as... Figures 3 to 8 The method described in any of the embodiments shown.

[0385] This application embodiment also provides a chip, which includes at least one processor and an interface. The processor is used to read and execute instructions stored in a memory. When the instructions are executed, the chip causes the chip to perform actions such as... Figures 3 to 8 The method described in any of the embodiments shown.

[0386] Optionally, the processing performed by a single execution entity (terminal or access network device) shown in any of the above embodiments can also be divided into multiple execution entities, which can be logically and / or physically separated. For example, the processing performed by the access network device can be divided into execution by at least one of CU, DU, and RU.

[0387] Furthermore, the various embodiments of this application are merely illustrative examples of executing all the steps included, and should not be considered as specific limitations on this application. For example, the order of steps in various embodiments can be simply changed according to their function and internal logic; or, for example, all steps in various embodiments can be executed, or only a portion of them can be executed, as long as the same function as in the embodiments of this application can be achieved.

[0388] In this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to a network device" can be understood as the destination of the information being the network device, which can include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from a network device" can be understood as the source of the information being the network device, which can include direct reception from the network device via the air interface or indirect reception from the network device via the air interface from other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0389] In other words, sending and receiving can occur between devices, such as between network devices and terminals; or they can occur within a device, such as between components, modules, chips, software modules, or hardware modules within a device via a bus, wiring, or interface.

[0390] In the embodiments of this application, "when," "if," "if," and "in the case of" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a time, nor do they require the device to make a judgment action when it is implemented, nor do they mean that there are other limitations.

[0391] In this application, the words “example,” “exemplarily,” “for example,” or “such as” are used to indicate that something is an example, illustration, or description. Any embodiment or design described as “example,” “exemplarily,” “for example,” or “such as” in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the words “example,” “exemplarily,” “for example,” or “such as” is intended to present the relevant concepts in a specific manner.

[0392] Optionally, the message names or parameter names between the various network elements involved in the above embodiments are just examples, and other names may be used in specific implementations. The representation of each parameter is not limited to the forms listed above, and this application does not impose specific limitations on this. For example, the parameter form may be indication information, information element (IE), special interface, or special message type. The form in which each network element stores the corresponding information may be a list or a string, etc., and this application does not impose any limitations.

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

Claims

1. A communication method, characterized in that, include: Obtain policy information, which is used to indicate the correspondence between at least one type of service information and a first access type, wherein the first access type is the access type to which the at least one type of service information is applicable; The first access type is determined based on the strategy information, and the first access type includes at least one of the following: low rail access type, medium rail access type, high rail access type, or multi-rail access type; Initiate session establishment or session modification through the first access type.

2. The method according to claim 1, characterized in that, The process of obtaining the first association relationship includes: Receive the policy information from the policy control network element or the access management network element.

3. The method according to claim 1 or 2, characterized in that, Determining the first access type based on the policy information includes: Determine the first service information of the terminal, wherein the first service information belongs to at least one type of service information; The first access type to which the first service information applies is determined based on the first service information and the policy information.

4. A communication method, characterized in that, include: Determine policy information, which is used to indicate the correspondence between at least one type of service information and a first access type, wherein the first access type is the access type to which the at least one type of service information is applicable, and the first access type includes at least one of the following: low-track access type, mid-track access type, high-track access type, or multi-track access type; The policy information is sent to the terminal.

5. The method according to claim 4, characterized in that, The strategy determination information includes: Obtain the subscription information of the terminal from the data management network element, and / or obtain the first indication information from the application function network element; The strategy information is determined based on the contract information and / or the first indication information; The terminal's subscription information or the first indication information is used to indicate the track information and second service information of the non-terrestrial network devices that the terminal can access. The second service information is associated with the track information and belongs to the at least one type of service information. The track information includes track height parameters and / or track type, and the track type includes low-orbit, medium-orbit, high-orbit, or multi-orbit.

6. A communication method, characterized in that, include: The first access type applicable to the third service information is determined, and the first access type includes at least one of the following: low-rail access type, medium-rail access type, high-rail access type, or multi-rail access type; Send the first radio access technology / frequency selection priority (RFSP) index corresponding to the first access type. The first RFSP index is used to trigger the access network device to perform redirection.

7. The method according to claim 6, characterized in that, The determination of the first access type to which the third service information applies includes: Obtain the first association; Based on the first association relationship and the third service information, the first access type is determined; The first association relationship includes the correspondence between the first access type and at least one type of service information supported by the first access type, and the at least one type of service information includes the third type of service information.

8. The method according to claim 6, characterized in that, The determination of the first access type to which the third service information applies includes: Receive the first access type from the session management network element.

9. The method according to claim 8, characterized in that, The method further includes: The third service information is sent to the session management network element.

10. The method according to any one of claims 6-9, characterized in that, Sending the first RFSP index corresponding to the first access type includes: If the first condition is met, the first RFSP index is sent; The first condition includes: the first access type is different from the terminal's current access type and / or the non-terrestrial network device to which the third service information applies is different from the non-terrestrial network device to which the terminal requests access.

11. The method according to claim 7 or 10, characterized in that, The first association relationship includes the first access type, at least one service information supported by the first access type, and the correspondence between N non-terrestrial network devices, where N is a positive integer. The method further includes: Based on the first association relationship and the third service information, the non-terrestrial network devices to which the third service information applies are determined.

12. The method according to claim 8 or 9, characterized in that, The method further includes: Non-terrestrial network devices that receive the third service information from the session management network element.

13. The method according to any one of claims 6-12, characterized in that, The method further includes: Receive the first RFSP index from the data management network element; or, Obtain a second association relationship, and determine the first RFSP index based on the second association relationship and the first access type. The second association relationship includes the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index includes the first RFSP index.

14. The method according to claim 13, characterized in that, The method further includes: Send a second indication message to the data management network element. The second indication message is used to obtain the first RFSP index and includes the first access type.

15. The method according to claim 13, characterized in that, The second association relationship includes the correspondence between the first access type, the at least one RFSP index, and M non-terrestrial network devices, wherein the M non-terrestrial network devices include the non-terrestrial network devices to which the third service information applies, and M is a positive integer. Determining the first RFSP index based on the second association relationship and the first access type includes: Based on the second association, the first access type, and the non-terrestrial network devices to which the third service information applies, the first RFSP index is determined.

16. The method according to claim 13 or 14, characterized in that, The second indication information is also used to indicate the non-terrestrial network devices to which the third service information applies.

17. The method according to any one of claims 6-16, characterized in that, The third service information includes the network slice and / or data network name (DNN) requested by the terminal; or, The third service information includes network slices and / or DNNs allocated to the terminal.

18. A communication device, characterized in that, Includes units or modules for implementing the method as described in any one of claims 1 to 17.

19. A communication device, characterized in that, The communication device includes at least one processor; wherein the at least one processor is configured to perform the method of any one of claims 1 to 17.

20. A computer program product, characterized in that, The computer program product includes: computer program code, which, when executed by a computer, causes the computer to perform the method as described in any one of claims 1-17.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed, cause the computer to perform the method as described in any one of claims 1-17.

22. A communication system, characterized in that, This includes terminal and policy control network elements, or, it includes terminal and access management network elements; The terminal is used to perform the method as described in any one of claims 1-3; The policy control network element or the access management network element is used to execute the method as described in any one of claims 4-5.

23. A communication system, characterized in that, It includes an access management network element and an access network device that communicates with the access management network element, or it includes a session management network element and an access network device that communicates with the session management network element; The access management network element is used to perform the method as described in any one of claims 6-17; The session management network element is used to perform the method as described in any one of claims 6, 7, 10, 11 or 13-17.

Images