Communication method and apparatus

Abstract

A communication method and apparatus, which relate to the technical field of communications. In the communication method, a terminal can acquire policy information, such that a first access type can be determined on the basis of the policy information, and session establishment or session modification can then be initiated by means of the first access type. In this way, a terminal can establish a session in an appropriate access type. For example, the terminal can initiate session establishment or session modification by means of a first access type to which first service information is applicable, so that the situation in which a service transmission requirement cannot be met due to a service type not matching an access type, thereby ensuring the service transmission performance.

Description

A communication method and apparatus

[0001] This application claims priority to the Chinese patent application No. 202411292460.6, filed on September 13, 2024, with the State Intellectual Property Office of China, and the Chinese patent application No. 202411292460.6 has the title of "A communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present application relates to the field of communication technology, and in particular, to a communication method and apparatus. BACKGROUND

[0003] With the development of wireless communication technology, the types of services that a network can provide gradually diversify. Among them, the types of services can be represented by network slices.

[0004] However, in non-terrestrial network (NTN) technology, the network slice requested by a terminal can be unsuitable for the current access type of the terminal, such as a low-orbit access type, a medium-orbit access type, or a high-orbit access type. For example, when a terminal accesses a low-orbit satellite, the terminal requests a high-reliability video communication service from a core network (which is unsuitable for a low-orbit satellite), and because the radio access technologies / frequency selection priority (RFSP) received by the base station in the registration process is determined based on the network slice requested by the terminal, the terminal still establishes a session through the low-orbit satellite. That is, the terminal establishes a session at an inappropriate access type. This can affect the performance of service transmission. SUMMARY

[0005] The present application provides a communication method and apparatus, which can enable a terminal to initiate session establishment or session modification at a suitable access type, thereby ensuring the performance of service transmission.

[0006] In a first aspect, a communication method is provided. The method can be performed by a terminal, or can be performed by a module (such as a processor, a chip, or a chip system) applied to the terminal, and can also be implemented by a logic node, a logic module, or software that can implement all or part of the functions of the terminal. Taking the method applied to the terminal as an example, in the method, the terminal can obtain policy information, the policy information being used to indicate a correspondence between at least one type of service information and a first access type, the first access type being an access type suitable for the at least one type of service information. In this way, the terminal can determine the first access type based on the policy information, the first access type including at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type, so that the terminal can initiate session establishment or session modification through the first access type.

[0007] It can be seen that in the above embodiments, the terminal can obtain the policy information, and thus can determine the first access type based on the policy information, and then can initiate the session establishment or the session modification through the first access type. This enables the terminal to establish the session through a suitable access type, for example, the terminal can initiate the session establishment or the session modification through the first access type to which the first service information is applicable, reduces the situation that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and thus guarantees the performance of the service transmission.

[0008] In a possible implementation, the terminal obtaining the first association relationship comprises: the terminal receiving the policy information from a policy control network element or an access management network element.

[0009] In a possible implementation, the terminal determining the first access type based on the policy information comprises: the terminal determining first service information of the terminal, the first service information belonging to at least one service information; and the terminal determining, based on the first service information and the policy information, a first access type to which the first service information is applicable.

[0010] It can be seen that in the above embodiments, the terminal can determine the first service information, and thus determine the first access type to which the first service information is applicable based on the first service information and the policy information, so that the terminal can establish the session through a suitable access type, for example, the terminal can initiate the session establishment or the session modification through the first access type to which the first service information is applicable, reduces the situation that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and thus guarantees the performance of the service transmission.

[0011] In a second aspect, a communication method is provided. The method can be performed by a policy control network element, or can be performed by a module (such as a processor, a chip, or a chip system) applied to the policy control network element, and can also be implemented by a logical node, a logical module, or software that can realize all or part of the functions of the policy control network element. Alternatively, the method can be performed by an access management network element, or can be performed by a module (such as a processor, a chip, or a chip system) applied to the access management network element, and can also be implemented by a logical node, a logical module, or software that can realize all or part of the functions of the access management network element. Taking the case that the method is applied to the policy control network element as an example, in the method, the policy control network element can determine policy information, the policy information being used to indicate a corresponding relationship between at least one service information and a first access type, the first access type being an access type to which the at least one service information is applicable, and the first access type including at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type. In this way, the policy control network element can send the policy information to a terminal.

[0012] It can be seen that in the above embodiments, the policy control network element can indicate the terminal with the policy information, so that the terminal can determine the first access type based on the policy information, and then can initiate the session establishment or session modification through the first access type. This makes the terminal establish the session through the appropriate access type, for example, the terminal can initiate the session establishment or session modification through the first access type to which the first service information is applicable, reduces the situation that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and guarantees the performance of service transmission.

[0013] In a possible implementation, the policy control network element determines the policy information, including: the policy control network element acquires the subscription information of the terminal from the data management network element, and / or acquires the first indication information from the application function network element, so as to determine the policy information based on the subscription information and / or the first indication information. Wherein, the subscription information of the terminal or the first indication information is used to indicate the orbit information of the non-terrestrial network device accessible by the terminal and the second service information, the second service information is associated with the orbit information, the second service information belongs to at least one service information, and the orbit information includes an orbit height parameter and / or an orbit type, and the orbit type includes a low orbit, a medium orbit, a high orbit or a multi-orbit.

[0014] In a third aspect, a communication method is provided. The method can be performed by an access management network element, or by a module (such as a processor, a chip, or a chip system) applied to the access management network element, and can also be implemented by a logic node, a logic module, or software that can implement all or part of the function of the access management network element. Alternatively, the method can be performed by a session management network element, or by a module (such as a processor, a chip, or a chip system) applied to the session management network element, and can also be implemented by a logic node, a logic module, or software that can implement all or part of the function of the session management network element. Taking the method applied to the access management network element or the session management network element as an example, the access management network element or the session management network element can determine a first access type to which the third service information is applicable, the first access type including at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type, and then send a 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.

[0015] It can be seen that, in the above embodiments, the access management network element or the session management network element can determine the first access type to which the third service information is applicable, so that the first RFSP index corresponding to the first access type can be sent, which enables the access network device to perform redirection, such as redirecting the terminal to another cell, etc. This can trigger the terminal to re-perform the registration process, such as re-initiating session establishment or session modification, so as to guarantee the consistency of the service type and the access type as much as possible, reduce the situation that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and guarantee the performance of service transmission.

[0016] In a possible implementation, the access management network element determines the first access type to which the third service information is applicable, including: the access management network element acquires the 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 is applicable, including: the session management network element acquires the first association relationship, and determines the first access type based on the first association relationship and the third service information.

[0017] It can be seen that, in the above embodiments, the access management network element or the session management network element can determine the first access type based on the first association relationship and the third service information, which can reduce the time delay problem caused by the transmission of the first access type from other network elements to the access management network element or the session management network element.

[0018] In a possible implementation, the access management network element acquires the first association relationship, including: the access management network element receives the 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, including: the session management network element receives the first association relationship from the OAM device or the data management network element.

[0019] In a possible implementation, the access management network element determines the first access type to which the third service information is applicable, including: the access management network element receives 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 is applicable, including: the session management network element receives the first access type from the access management network element.

[0020] It can be seen that, in the above embodiments, the access management network element can acquire the first access type from the session management network element, which simplifies the processing complexity on the side of the access management network element. Alternatively, the session management network element can acquire the first access type from the access management network element, which simplifies the processing complexity on the side of the session management network element.

[0021] In a possible implementation, the method further includes: sending, by the access management network element, the third service information to the session management network element.

[0022] In a possible implementation, the sending, by the access management network element, of the first RFSP index corresponding to the first access type includes: sending, by the access management network element, the first RFSP index in a case where a first condition is met. Alternatively, the sending, by the session management network element, of the first RFSP index corresponding to the first access type includes: sending, by the session management network element, the first RFSP index in a case where the first condition is met. The first condition includes: the first access type being different from a current access type of the terminal and / or a non-terrestrial network device applicable to the third service information being different from a non-terrestrial network device accessed by the terminal.

[0023] It can be seen that, in the above embodiments, the access management network element or the session management network element can send the first RFSP index in a case where the first condition is met, so as to trigger the access network device to perform redirection, for example, to redirect the terminal to another cell, in a case where the first access type is different from a current access type of the terminal and / or a non-terrestrial network device applicable to the third service information is different from a non-terrestrial network device accessed by the terminal. This can trigger the terminal to re-perform a registration process, for example, to re-initiate session establishment or session modification, so as to guarantee the consistency of the service type and the access type as much as possible, reduce the case where the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and guarantee the performance of service transmission.

[0024] In a possible implementation, the first association relationship includes a correspondence relationship among the first access type, at least one service information supported by the first access type, and N non-terrestrial network devices, N being a positive integer, and the method further includes: determining, by the access management network element or the session management network element, the non-terrestrial network device applicable to the third service information based on the first association relationship and the third service information.

[0025] In a possible implementation, the method further includes: receiving, by the access management network element, the non-terrestrial network device applicable to the third service information from the session management network element. Alternatively, receiving, by the session management network element, the non-terrestrial network device applicable to the third service information from the access management network element.

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

[0027] It can be seen that in the above embodiments, the access management network element or the session management network element can obtain the first RFSP index from the data management network element, which simplifies the processing complexity of the access management network element side or the session management network element side, and also guarantees that the first RFSP index is the RFSP index subscribed by the terminal. Alternatively, the access management network element or the session management network element can determine the first RFSP index based on the second association relationship and the first access type, which reduces the time delay problem caused by transmitting the first RFSP index from other network elements to the access management network element or the session management network element.

[0028] In a 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 the first RFSP index, and the second indication information including the first access type. Alternatively, the session management network element sends the second indication information to the data management network element.

[0029] In a possible implementation, the access management network element obtaining the second association relationship includes: the access management network element receiving the second association relationship from an OAM device or the data management network element. Alternatively, the session management network element obtaining the second association relationship includes: the session management network element receiving the second association relationship from an OAM device or the data management network element.

[0030] In a possible implementation, the second association relationship includes a correspondence between the first access type, at least one RFSP index, and M non-terrestrial network devices, the M non-terrestrial network devices including a non-terrestrial network device to which the third service information is applicable, M being a positive integer, and the access management network element determining the first RFSP index based on the second association relationship and the first access type includes: 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 device to which the third service information is applicable. Alternatively, the session management network element determining the first RFSP index based on the second association relationship and the first access type includes: 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 device to which the third service information is applicable.

[0031] In a possible implementation, the second indication information is further used to indicate the non-terrestrial network device to which the third service information is applicable.

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

[0033] In a fourth aspect, a communication method is provided, which can be performed by a data management network element, or by a module (e.g., a processor, a chip, or a chip system) applied to the data management network element, or by a logic node, a logic module, or software that can implement all or part of the function of the data management network element. Taking the method applied to the 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 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, so that the first RFSP index can be sent 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 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, so that the first RFSP index can be sent to the session management network element.

[0034] It can be seen that, in the above embodiments, the data management network element determines the first RFSP index corresponding to the first access type in combination with the access type to which the third service information is applicable, so that the first RFSP index can be sent to the access management network element or the session management network element, thereby not only reducing the processing complexity of the access management network element side or the session management network element side, but also guaranteeing that the first RFSP index is the RFSP index to which the terminal is subscribed.

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

[0036] It can be seen that, in 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, thereby guaranteeing that the first RFSP index is the RFSP index to which the terminal is subscribed.

[0037] In a possible implementation, the second association relationship includes a corresponding relationship between the first access type, at least one RFSP index, and M non-terrestrial network devices, the M non-terrestrial network devices including the non-terrestrial network device to which the third service information is applicable, M being a positive integer, and the data management network element determining the first RFSP index based on the second association relationship and the first access type includes: the data management network element determining the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network device to which the third service information is applicable.

[0038] In a possible implementation, the second indication information is further used to indicate the non-terrestrial network device to which the third service information is applicable.

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

[0040] In a fifth aspect, a communication method is provided. The method can be performed by an access management network element, or can be performed by a module (for example, a processor, a chip, or a chip system) applied to the access management network element, and can also be implemented by a logic node, a logic module, or software that can implement all or part of the function of the access management network element. Taking the method applied to the access management network element as an example, the access management network element can receive a registration request from a terminal, the registration request including a cause value for establishing a connection, the cause value corresponding to a first access type, the first access type including at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type. In this way, the access management network element can send a first RFSP index corresponding to the first access type to an access network device, the first RFSP index being used to trigger the access network device to perform redirection.

[0041] As can be seen, in the above embodiments, the access management network element determines the first access type based on the cause value for establishing a connection, so as to send the first RFSP index corresponding to the first access type, which enables the access network device to perform redirection, for example, to redirect the terminal to another cell, and the like. This can trigger the terminal to re-perform a registration process, for example, to re-initiate session establishment or session modification, thereby ensuring the consistency of the service type and the access type as much as possible, reducing the situation that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and ensuring the performance of service transmission.

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

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

[0044] As can be seen, in the above embodiments, 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, which can reduce the time delay problem caused by the determination of the first access type by other network elements and the subsequent transmission to the access management network element.

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

[0046] In a possible implementation, the access management network element sends the first RFSP index corresponding to the first access type to the access network device, including: the access management network element sending the first RFSP index to the access network device in the case that the first access type is different from the current access type of the terminal.

[0047] It can be seen that, in the above embodiments, the access management network element can send the first RFSP index in the case that the first access type is different from the current access type of the terminal, so as to trigger the access network device to perform redirection, for example, to redirect the terminal to another cell, and the like. This can trigger the terminal to re-perform a registration process, for example, to re-initiate a session establishment or a session modification, thereby ensuring the consistency of the service type and the access type as much as possible, reducing the case that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and ensuring the performance of service transmission.

[0048] In a possible implementation, the above method further includes: the access management network element receiving the first RFSP index from a data management network element. Or, the access management network element acquires a second association relationship, determines the first RFSP index based on the second association relationship and the first access type, the second association relationship including a corresponding relationship between the first access type and at least one RFSP index, and the at least one RFSP index including the first RFSP index.

[0049] It can be seen that, in the above embodiments, the access management network element can acquire the first RFSP index from the data management network element, which simplifies the processing complexity of the access management network element side or the session management network element side, and also ensures that the first RFSP index is the RFSP index subscribed by the terminal. Alternatively, the access management network element can determine the first RFSP index based on the second association relationship and the first access type, thereby reducing the time delay problem caused by transmitting the first RFSP index from other network elements to the access management network element or the session management network element.

[0050] In a possible implementation, the above 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 acquire the first RFSP index, and the second indication information including the first access type.

[0051] In a sixth aspect, a communication apparatus is provided, which comprises means or modules for implementing any of the methods in any of the first to fifth aspects. The communication apparatus can be a terminal, or a module (for example, a processor, a chip, or a chip system, etc.) of the terminal, or a logical node, a logical module, or software capable of implementing all or part of the functions of the terminal. Alternatively, the communication apparatus can be a core network element, or a module (for example, a processor, a chip, or a chip system, etc.) of the core network element, or a logical node, a logical module, or software capable of implementing all or part of the functions of the core network element. In a possible implementation, the core network element can be a policy control network element, an access management network element, a session management network element, a data management network element, etc.

[0052] In a seventh aspect, a communication apparatus is provided, which comprises at least one processor. The at least one processor is configured to implement any of the methods in any of the first to fifth aspects. The communication apparatus can be a terminal, or a module (for example, a processor, a chip, or a chip system, etc.) of the terminal, or a logical node, a logical module, or software capable of implementing all or part of the functions of the terminal. Alternatively, the communication apparatus can be a core network element, or a module (for example, a processor, a chip, or a chip system, etc.) of the core network element, or a logical node, a logical module, or software capable of implementing all or part of the functions of the core network element. In a possible implementation, the core network element can be a policy control network element, an access management network element, a session management network element, a data management network element, etc. The at least one processor can execute a computer program or instructions in a memory, so that the above method is executed. The memory can be included in the communication apparatus, or located outside the communication apparatus. In addition, the communication apparatus can further comprise an interface.

[0053] In an eighth aspect, a computer readable storage medium is provided, which stores computer instructions. When the computer instructions are executed, the computer executes any of the methods in any of the first to fifth aspects.

[0054] In a ninth aspect, a computer program product is provided, which comprises computer program codes. When the computer program codes are run by a computer, the computer executes any of the methods in any of the first to fifth aspects.

[0055] In a tenth aspect, a chip or chip system is provided, which comprises at least one processor and an interface. The processor is configured to read and execute instructions stored in a memory. When the instructions are run, the chip executes any of the methods in any of the first to fifth aspects.

[0056] In an eleventh aspect, there is provided a communication system comprising a terminal configured to perform the method of any of the first aspects and a policy control network element or an access management network element configured to perform the method of any of the second aspects.

[0057] In a twelfth aspect, there is provided a communication system comprising an access management network element configured to perform the method of any of the third aspects and an access network device in communication with the access management network element. Or a session management network element configured to perform the method of any of the third aspects and an access network device in communication with the session management network element. Optionally, further comprising a data management network element configured to perform the method of any of the fourth aspects.

[0058] In a thirteenth aspect, there is provided a communication system comprising an access management network element configured to perform the method of any of the fifth aspects and an access network device in communication with the access management network element. Optionally, further comprising a data management network element configured to perform the method of any of the fourth aspects. BRIEF DESCRIPTION OF DRAWINGS

[0059] Fig. 1 is a basic architecture of a communication system according to an embodiment of the present application;

[0060] Fig. 2 is a schematic diagram of a RAN architecture based on NTN devices according to an embodiment of the present application;

[0061] Fig. 3 is a flow diagram of a communication method according to an embodiment of the present application;

[0062] Fig. 4 is a flow diagram of another communication method according to an embodiment of the present application;

[0063] Fig. 5 is a flow diagram of another communication method according to an embodiment of the present application;

[0064] Fig. 6 is a flow diagram of another communication method according to an embodiment of the present application;

[0065] Fig. 7 is a flow diagram of another communication method according to an embodiment of the present application;

[0066] Fig. 8 is a flow diagram of another communication method according to an embodiment of the present application;

[0067] Fig. 9 is a schematic diagram of a communication apparatus according to an embodiment of the present application;

[0068] Fig. 10 is a schematic diagram of another communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0069] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. In the embodiments of the present application, the terms "system" and "network" can be used interchangeably. Unless otherwise specified, " / " represents an "or" relationship between the objects before and after the " / " symbol, for example, A / B can represent A or B; in the present application, "and / or" is only a description of the relationship between the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent the following three cases: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. In addition, in the description of the present application, "multiple" means two or more than two. "At least one of the following" or similar expressions means any combination of the items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be one or more. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, "first", "second", and the like are used to distinguish the same items or similar items with the same function. Those skilled in the art can understand that "first", "second", and the like do not limit the number and execution order, and "first", "second", and the like do not necessarily mean different. In addition, the numbering of steps in each embodiment of the present application is only to distinguish different steps and does not limit the order of the steps. For example, step 201 can occur before step 202, or it can occur after step 202, or it can occur at the same time as step 202.

[0070] In the embodiments of the present application, the reference to "one embodiment" or "some embodiments" means that the specific features, structures or characteristics described in connection with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in other some embodiments", "in further some embodiments" and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "include", "contain", "have" and their variants mean "include but not limited to", unless otherwise specifically emphasized.

[0071] The following detailed description further describes the objectives, technical solutions and advantages of the present application. It should be understood that the following is only a specific embodiment of the present application and does not limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made on the basis of the technical solutions of the present application shall be included in the protection scope of the present application.

[0072] In various embodiments of the present application, the terms and / or descriptions of different embodiments are consistent and can be referred to each other if there is no special description and logical conflict, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0073] The method provided by the embodiments of the present application can be applied to various communication systems, for example, can be an internet of things (IoT) system, a narrow band internet of things (NB-IoT) system, a long term evolution (LTE) system, a 5th-generation (5G) communication system, a new radio (NR) system or a new communication system in future communication development. Among them, the IoT network may, for example, include but not limited to vehicle networking. The communication mode in the vehicle networking system can be collectively referred to as vehicle-to-everything (V2X, X can represent any thing). For example, V2X can 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 by the embodiments of the present application can also be applied to non-terrestrial network (NTN) communication (also can be called non-terrestrial network communication), or the scene of fusion of NTN and terrestrial network (TN).

[0074] The method provided by the embodiments of the present application can be applied to a wireless local area network (WLAN) system, such as Wi-Fi, etc. The method provided by the embodiments of the present application can be applicable to institute of electrical and electronics engineers (IEEE) 802.11 series protocols, for example, 802.11be protocol, 802.11bn protocol or the next generation of 802.11bn protocol, etc., which will not be listed one by one.

[0075] The method provided by the embodiments of the present application can be applied to two entities in a communication system, for example, one of the two entities can send information to the other entity, or receive information sent by the other entity. In a wireless communication system, communication devices are included, and the communication devices can perform wireless communication by using air interface resources. The air interface resources can include at least one of time domain resources, frequency domain resources, code resources and space resources, and the present application does not make any limitation in this regard. For example, the two entities can include a network device and a terminal, or a chip that can be placed in the network device, and a chip that can be placed in the terminal, and the like. Of course, with the development of standards or products, other types of entities can also appear in the future, and the embodiments of the present application do not make any limitation in this regard.

[0076] In order to facilitate understanding of the embodiments of the present application, the 5G network architecture shown in FIG. 1 is taken as an example to introduce the communication system. For example, reference can be made to the 3rd generation partnership project (3GPP) technical specification (TS) 23.501, and the functions of various network elements and the like can also be referred to other technical specifications of 3GPP. As shown in FIG. 1, it includes a terminal part, an access network (AN) part, and a core network part. Optionally, the network architecture can also include a data network (DN) part and / or an application network element part. The terminal accesses the core network through the access network, and the core network communicates with the DN or the application network element.

[0077] The various parts involved in the system architecture will be described in detail below.

[0078] I. Terminal (terminal device)

[0079] A terminal is an entity that receives a signal or transmits a signal or receives a signal and transmits a signal on a user side. The terminal is used to provide one or more of voice services and data connectivity services to a user. The terminal can be a device that includes a wireless transceiving function and can cooperate with a network device to provide communication services to a user. Specifically, the terminal can refer to a user equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, a remote terminal, a mobile device, a terminal, a wireless communication device, a user agent, a user apparatus, or a road side unit (RSU). The terminal can also be a drone, an internet of things (IoT) device, a station (ST) in a wireless local area network (WLAN), a cellular phone, a smart phone, a cordless phone, a wireless data card, a tablet computer, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a laptop computer, a machine type communication (MTC) terminal, a handheld device with a wireless communication function, a computing device, or other processing devices connected to a wireless modem, a vehicle-mounted device, a wearable device (which can also be referred to as a wearable smart device), a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in remote medical treatment, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, and the like. The terminal can also be a terminal in a 5G system or a terminal in a next-generation communication system, and embodiments of the present application do not limit the same.

[0080] Embodiments of the present application do not limit the device form of the terminal, and the device for implementing the function of the terminal can be the terminal; or can be a device capable of supporting the terminal to implement the function, such as a chip system. The device can be installed in the terminal or used in matching with the terminal. In embodiments of the present application, the chip system can be composed of a chip, or can include the chip and other discrete devices.

[0081] II. AN part

[0082] The AN part includes an AN device. The AN device is a device that accesses a terminal to a wireless network in a mobile communication system. The AN device, as a node in a radio access network, can also be referred to as an access network element, a base station, a radio access network (RAN) node (or device, or element), an access point (AP), or a network device, etc. The RAN device in the embodiments of the present application includes but is not limited to: an evolved universal terrestrial radio access network (E-UTRAN), a next-generation base station (gNB), an evolved node B (eNB), a radio network controller (RNC), a node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved node B, or a home node B, HNB), a baseband unit (BBU), a wireless fidelity (WiFi) access point, a world interoperability for microwave access (WiMAX) base station, a transmitting and receiving point (TRP), a transmitting point (TP), or a mobile switching center, etc. In systems using different wireless access technologies, the names of devices with base station functions may be different, for example, in a 5G communication system, it is called RAN or gNB (5G NodeB); in an LTE system, it is called an evolved node B (eNB or eNodeB); in a third generation (3rd generation, 3G) communication system, it is called a node B (Node B), etc. In some deployments of the AN device, the AN device can include a centralized unit (CU) and a distributed unit (DU), etc. In other deployments of the AN device, the CU can also be divided into a CU-control plane (CP) and a CU-user plane (UP), etc. In still other deployments of the AN device, the AN device can also include a radio unit (RO).In yet some deployments of the AN device, the AN device can be an open radio access network (ORAN) architecture, a cloud RAN, or the like. The ORAN can also be referred to as a virtualized RAN. For example, when the AN device is an ORAN architecture, the AN device of embodiments of the present application can be an access network element in the ORAN, or a module of the access network element, or the like. In the ORAN system, the CU can also be referred to as an open (O)-CU, the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. For the sake of convenience of description, the CU, the CU-CP, the CU-UP, the DU, and the RU are taken as examples for description in the present application. Any one of the CU (or the CU-CP, the CU-UP), the DU, and the RU in the present application can be implemented by a software module, a hardware module, or a combination of the software module and the hardware module.

[0083] III. DN

[0084] The DN is a network outside the mobile communication system, and can provide services for users. For example, the DN can be a packet data network (PDN), such as the Internet, an internet protocol multi-media service (IMS) network, a data network dedicated to some application, an Ethernet network, an internet protocol (IP) local network, or the like, and embodiments of the present application do not limit the DN. The DN can deploy various services, and can provide data, voice, short message, or the like for terminals. The DN can have multiple application servers (ASs), and each AS can provide at least one service.

[0085] IV. Application Network Element

[0086] The application network element mainly supports interaction with the 3GPP core network to provide services, such as affecting data routing decisions, policy control functions, or providing some services of a third party to the network side. In the 5G communication system, the 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 can have other names, and embodiments of the present application do not limit the application network element.

[0087] V. Core Network Part

[0088] The network elements in the core network part can be divided into two categories: user plane function network elements (which can also be referred to as user plane network elements) and control plane function network elements (which can also be 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, etc.

[0089] The user plane network element is responsible for the forwarding and receiving of user data in the terminal device. It can receive user data from a data network and transmit it to the terminal device through an access network device. The user plane network element can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions provided by the user plane network element for the terminal device are managed and controlled by the session management network element. In the 5G communication system, the 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, which are not limited by the embodiments of the present application.

[0090] The access management network element is a control plane network element provided by an operator network, responsible for access control and mobility management of terminal devices accessing the operator network, including functions such as mobile state management, allocation of user temporary identity, authentication and user management, etc. In the 5G communication system, the access management network element can be an access and mobility management function (AMF) network element. In future communication systems, the access management network element can still be an AMF network element, or it can have other names, which are not limited by the embodiments of the present application.

[0091] The session management network element is mainly responsible for session management in the mobile network, such as session establishment, session modification, and session release. Specific functions include allocating IP addresses for users, selecting user plane network elements that provide message forwarding functions, etc. In the 5G communication system, the session management network element can be a session management function (SMF) network element. In future communication systems, the session management network element can still be an SMF network element, or it can have other names, which are not limited by the embodiments of the present application.

[0092] The data management network element is used to generate authentication credentials, handle user identities (such as storing and managing user permanent identities), perform access control and manage subscription data, etc. In the 5G communication system, the data management network element can be a unified data management (UDM) network element. In future communication systems, the unified data management can still be a UDM network element, or it can have other names, which are not limited by the embodiments of the present application.

[0093] The policy control network element mainly supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network function, and is responsible for obtaining user subscription information related to policy decision. In the 4G communication system, the policy control network element can be a policy and charging rules function (PCRF) network element. In the 5G communication system, the 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 also have other names, which are not limited by the embodiments of the present application.

[0094] As described above, the network elements that the embodiments of the present application can involve are mainly introduced, and in addition, other network elements are also involved in FIG. 1, which will not be described in detail here. For example, the core network can further include a policy control function (PCF) network element, a unified data repository (UDR) network element (not shown in FIG. 1), a network repository function (NRF) network element, a network exposure function (NEF) network element, an authentication server function (AUSF) network element, a network slice selection function (NSSF), and the like.

[0095] In FIG. 1, interfaces between multiple communication devices in the communication system are also shown. For example, N1, N2, N3, N4, N5, N6, N7, N8, N9, N10, N11, N12, N15, Nnnsf, Nnef, Nnrf, Nausf, Namf, Npcf, Nudm, Naf, Nsmf, and the like are interface serial numbers, which can be referred to 3GPP TS 23.501, which is not limited here. Among them, Nnnsf, Nnef, Nnrf, Nausf, Namf, Npcf, Nudm, Naf, Nsmf, and the like are service interfaces provided by the above-mentioned NSSF, NEF, NRF, AUSF, AMF, PCF, UDM, AF, and SMF, respectively, for invoking corresponding service operations.

[0096] It can be understood that the network elements or functions shown in FIG. 1 can be network elements in a hardware device, or software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (for example, a cloud platform), or a combination of the above. In one possible implementation, the network elements or functions described above can be implemented by one device, or by multiple devices together, or by a functional module in one device, and the embodiments of the present application do not make specific limitations thereon. In addition, in the following, in order to facilitate description, the term "network element" can be omitted. For example, the SMF network element in the embodiments of the present application has the same meaning as the SMF, and only the term "network element" is omitted for the convenience of description, and the rest are similar. It should be noted that the embodiments of the present application also do not limit the names of the network elements in the communication system. For example, in different communication systems, the network elements can have other names; for example, when multiple network elements are integrated in the same physical device, the physical device can also have other names.

[0097] In order to facilitate understanding of the content of the present scheme, the following will explain some of the terms involved in the embodiments of the present application, so as to facilitate understanding by those skilled in the art, and this part is only for the convenience of understanding, and cannot be regarded as a specific limitation of the present application.

[0098] I. NTN

[0099] In the embodiments of the present application, the network equipment deployed in the air can be referred to as NTN equipment, and the network equipment deployed on the ground can be referred to as TN equipment. The NTN communication system includes at least one NTN equipment, and the network equipment in the TN communication system is TN equipment. The TN equipment is a network equipment that is stationary or moves slowly relative to the NTN equipment. That is, the NTN equipment can be a high-speed moving network equipment relative to the TN equipment.

[0100] The NTN device can include a satellite, a high-altitude platform (HAP), a drone, or a hot air balloon, etc., without limitation. The satellite can be a medium earth orbit (MEO) satellite of none-geostationary earth orbit (NGEO), a low earth orbit (LEO) satellite, a high altitude platform station (HAPS), an evolved NodeB (eNB) or a 5G base station (gNB), etc. The GEO satellite is also called a high-orbit satellite, the MEO satellite is also called a medium-orbit satellite, and the LEO satellite is also called a low-orbit satellite. Exemplarily, an orbit with a height from the earth's surface of more than 20,000 kilometers (km) is called a high orbit, an orbit with a height from the earth's surface of 8,000 km to 20,000 km is called a medium orbit, and an orbit with a height from the earth's surface of 500 km to 2,000 km is called a low orbit. Here, only as an example, the specific height range of the low orbit, the medium orbit, and the high orbit is not limited in the present application.

[0101] In the case where the NTN device is a satellite, the satellite can have different functions in different scenarios, specifically:

[0102] 1. In a transparent satellite architecture shown in 2-1 of FIG. 2, the radio access network (RAN) can include a remote radio unit (RRU) and a base station (such as gNB of FIG. 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 is un-changed. That is, the satellite mainly acts as a layer 1 (L1 for short) relay device for regenerating the physical layer signal (i.e., the processing of radio frequency filtering, frequency conversion and amplification), without other higher protocol layers. The NTN gateway supports the function of forwarding all new radio-Uu (NR-Uu) interface signals. The NR-Uu interface is the interface between the terminal and the base station in the protocol.

[0103] 2. In a regenerative satellite without inter-satellite link architecture as shown in 2-2 of FIG. 2, the RAN includes satellites and NTN gateways. The satellite acts as a base station with the processing function of a base station. The NTN gateway is a transport network layer node and supports the corresponding transport protocol. The satellite and the NTN gateway are connected through a satellite radio interface (SRI), and the NG interface is carried over the SRI (NG over SRI), responsible for the transmission of higher layer information.

[0104] 3. In a regenerative satellite with inter-satellite link architecture as shown in 2-3 of FIG. 2, similar to 2-2 of FIG. 2, the difference is that there is an SRI, and multiple satellites can be connected through an Xn interface. Among them, the Xn interface is carried over the SRI (Xn over SRI).

[0105] 4. In a regenerative satellite architecture with distributed unit (DU) processing function of a base station as shown in 2-4 of FIG. 2, the satellite acts as a DU in the base station, and performs the base station function together with the central unit (CU). Between the DU on the satellite and the CU on the ground, there is an NTN gateway. The NTN gateway is a transport network layer node and supports the corresponding transport protocol. The satellite and the NTN gateway are connected through an F1 interface, and the F1 interface is carried over the SRI (F1 over SRI).

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

[0107] When the satellite is a layer 1 relay device (i.e., in a kind of transparent satellite architecture shown in 2-1 of FIG. 2), the communication system can further include a base station, which can be an evolved universal terrestrial radio access (E-UTRA) system, an NR system, and a future wireless access system defined in the 3rd generation partnership project (3GPP), a WiFi system, an enhanced mobile broadband (eMBB), an ultra reliable low latency communication (URLLC), a massive machine type of communication (mMTC), a long range (LoRa) system, or a vehicle-to-everything (V2X) system. The base station can also include two or more different wireless access systems. The base station can also be an open radio access network (RAN) (O-RAN).

[0108] II. Network Slicing

[0109] To meet the needs of different scenarios in different industries, operators need to provide connection communication services with different functions and quality of service (QoS). In order to reduce the complexity of technical implementation, within a communication network, the entire network resource is sliced by using virtualization technology, and different connection capabilities of the same service are deployed on different network slices, so as to realize virtual independent logical networks of control plane network functions and user plane network functions, and to meet the QoS requirements of different services. This way of logical isolation using various network slices on one physical infrastructure can provide resource utilization efficiency and flexibility. From the perspective of service type, network slicing 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 of a specific user set.

[0110] Currently, 5G network defines three typical application scenarios, respectively, enhanced mobile broadband (enhance mobile broadband, eMBB), ultra-reliable and low-latency communication (ultra reliable low latency communication, uRLLC) and massive Internet of Things communication (massive machine type communication, mMTC). For the three typical scenarios defined for 5G network, 5G network can be divided into eMBB, mMTC and uRLLC three network slices. It should be understood that the present application is not limited to the network slices listed here, and in actual application, there can be other types of network slices, which are not limited by the present application.

[0111] Optionally, the network slice can be uniquely identified by a network slice identifier. For example, single network slice selection assistance information (single network slice selection assistance information, S-NSSAI). Here is only an example of network slice identifier, and the present application is not limited, any content that can uniquely identify the network slice can be used as the network slice identifier in the present application.

[0112] III. DNN

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

[0114] The DNN can include at least one of the following:

[0115] 1. Network identification (identification, ID), which represents an external network and is mandatory.

[0116] 2. Operator identification, which indicates which operator it belongs to, and is optional.

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

[0118] URSP can also be referred to as user equipment route selection policy, which is used to associate an application to an already established protocol data unit (protocol data unit, PDU) session, establish a new PDU session for the application, or transfer the application to non-3GPP access for transmission.

[0119] The URSP can include an association relationship between at least one application and at least one network slice, for example, at least one application corresponds to at least one network slice. Optionally, an application in the URSP can be described by an application identifier, and a network slice can be described by a network slice identifier. At this time, the URSP can refer to Table 1 for details. In Table 1, the URSP can include at least one of the following: rule priority, traffic descriptor, application descriptor, IP descriptor, domain descriptor, Non-IP descriptor, DNN, connection capability, PIN ID, connectivity group ID, or list of route selection descriptors.

[0120] Table 1

[0121] Optionally, the 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, PIN ID, or connectivity group ID, etc. For example, the application identifier can be an IMS communication service identifier (ICS) or an identification of IMS applications (IARI). Optionally, the application identifier mentioned in the present application can be any value or symbol that can distinguish, mark or locate an application, which is not limited herein.

[0122] V. Redirection

[0123] In this application, the redirection procedure is that the access network device instructs the terminal to attempt to camp on a cell on a specified frequency point through redirected carrier info. The redirected carrier info can include a redirected frequency point. Optionally, the redirected carrier info can also indicate a redirected RAT. For example, the redirected carrier info includes carrier info of NR, instructing the terminal to attempt to camp on a NR cell. Or, the redirected carrier info includes redirected carrier info-EUTRA of E-UTRA, instructing the terminal to attempt to camp on a E-UTRA cell.

[0124] Optionally, the redirected carrier info can be included in a radio resource control (RRC) release message.

[0125] When the RRC release message includes the redirected carrier info, the terminal should attempt to camp on a suitable cell on the redirected frequency point indicated by the redirected carrier info. If the terminal cannot find a suitable cell to camp on the redirected frequency point, the terminal can attempt to camp on a suitable cell on a specified RAT. If the terminal cannot find a suitable cell on the specified RAT, the terminal can perform a cell selection procedure using the information stored by the terminal to find a suitable cell to camp on. At this time, the terminal can select and camp on a cell on a non-redirected frequency point or a non-redirected RAT.

[0126] Six, orbit information

[0127] In this application, the orbit information includes an orbit height parameter and / or an orbit type.

[0128] The orbit height parameter is the height of the orbit to which the non-terrestrial network device belongs. The height refers to the distance from the non-terrestrial network device to the ground, such as the vertical height. Optionally, the number of orbits to which the non-terrestrial network device belongs can be one or more, which is not limited herein.

[0129] The orbit type is the type of the orbit to which the non-terrestrial network device belongs, including low orbit, medium orbit, high orbit, or multi-orbit. When the number of orbits to which the non-terrestrial network device belongs is multiple, the type of the orbit to which the non-terrestrial network device belongs can be considered as multi-orbit. That is, the multi-orbit can include at least two of the low orbit, the medium orbit, and the high orbit. For example, the number of orbits to which the non-terrestrial network device belongs is two, one of which is a low orbit and the other of which is a high orbit.

[0130] Seven, access type

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

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

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

[0134] It should be noted that the above lists several possible examples of access types, and in actual application scenarios, the access type can include a combination of one or more of the above examples, which is not limited in this application.

[0135] Optionally, the access type (such as the first access type, etc.) can be associated with a frequency band. For example, the access type (such as the first access type, etc.) can be associated with a frequency band one by one. That is, the access type (such as the first access type, etc.) can be described interchangeably with the frequency band, which is not limited in this application.

[0136] The following takes at least one of the low-orbit access type, the medium-orbit access type, the high-orbit access type, and the multi-orbit access type as an example to introduce the embodiments of the application in detail.

[0137] Referring to FIG. 3, FIG. 3 is a flow diagram of a communication method according to an embodiment of the present application. As shown in FIG. 3, the method includes but is not limited to the following steps:

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

[0139] For example, the policy control network element determines the policy information can be implemented in the following ways, specifically:

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

[0141] 2. The policy control network element obtains the subscription information of the terminal from the data management network element, the subscription information of the terminal is used to indicate the orbit information of the non-terrestrial network device accessible by the terminal and the second service information, and the second service information is associated with the orbit information. In this way, the policy control network element can determine the policy information based on the subscription information.

[0142] Optionally, the second service information belongs to at least one service information, and the orbit information associated with the second service information includes an orbit height parameter and / or an orbit type. Optionally, the orbit information can also be replaced by an access type.

[0143] 3. The policy control network element obtains the first indication information from the application function network element, the first indication information is used to indicate the orbit information of the non-terrestrial network device accessible by the terminal and the second service information, and the second service information is associated with the orbit information. In this way, the policy control network element can determine the policy information based on the first indication information.

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

[0145] Optionally, the policy information can be existing policy information and / or newly added policy information, which is not limited in the present application.

[0146] The existing policy information can be policy information in an existing version of a communication standard, for example, URSP. That is, the policy information in the existing version of the communication standard adds corresponding content, such as one or more access types and at least one service information corresponding to each access type. For example, when the policy information is URSP, the one or more access types can be indicated by a route selection list description word in the URSP, and the at least one service information corresponding to each access type can be indicated by a service description word in the URSP.

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

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

[0149] For ease of description, the following takes the first access type corresponding to at least one service information as an example for description, which should not be regarded as a limitation to the present application. For example, in Table 2, the first access type includes a low-orbit access type, and corresponds to service information 1 and service information 2. That is, the first access type corresponds to at least one service information, or it can be understood that the access type to which one or more service information is applicable is the first access type. Among them, the first access type refers to the type of the orbit to which the non-terrestrial network device belongs, that is, the orbit type of the non-terrestrial network device. In a possible implementation, the first access type and the orbit type can be described interchangeably, which is not limited here.

[0150] Table 2

[0151] Optionally, in the embodiment described in FIG. 3, the service information (such as the first service information or the second service information, etc.) can be used to describe the service used by the terminal and / or the object of the transmitted data. For example, it includes an application identifier and / or a service type.

[0152] The service type can have coarse and fine granularity.

[0153] For coarse granularity, the service type can be divided into data service, voice service, video service, short message service (SMS), or mission critical service, etc.

[0154] For fine granularity, the data service can be divided into Mo-Data and MT-Data. Mo-Data refers to a data service initiated by the terminal. MT-Data refers to a data service passively received by the terminal.

[0155] For fine granularity, the voice service can be divided into IMS-based telephone voice, CS-based telephone voice, and Internet-based voice, etc. The IMS-based telephone voice can be voice over new radio (VoNR) and / or voice over long term evolution (VoLTE), etc. The CS-based telephone voice can be a voice through circuit switched fallback (CSFB), etc. The Internet-based voice can be an instant messaging voice service, etc. Alternatively, the voice service can be divided into Mo-Voice and MT-Voice. Mo-Voice refers to a voice service initiated by the terminal. MT-Voice refers to a voice service passively received by the terminal.

[0156] For the fine granularity, the video service can be classified into IMS-based video, Internet-based video call and Internet-based online video. The IMS-based video can be video over long term evolution (ViLTE) and the like, the Internet-based video call can be instant messaging application video and the like, and the Internet-based online video can be various videos on the browser. Alternatively, the video service can be classified into Mo-Video service and MT-Video service. The Mo-Video service refers to the video service initiated by the terminal. The MT-Video service refers to the video service passively received by the terminal.

[0157] For the fine granularity, the short message service can be classified into IMS-based short message, CS-based short message and Internet-based short message. The data service can be web browsing and map application and the like. Alternatively, the short message service can be classified into Mo-SMS and MT-SMS. The Mo-SMS refers to the short message service initiated by the terminal. The MT-SMS refers to the short message service passively received by the terminal.

[0158] Alternatively, the service type can be interchangeably described with the network slice. As an example, the network slice can be associated with the DNN, for example, the network slice can be one-to-one associated with the DNN. Therefore, in the present application, the service type can be replaced by: network slice and / or DNN.

[0159] Alternatively, the step 301 can be an optional step.

[0160] 302. The terminal acquires the policy information.

[0161] Correspondingly, the policy control network element sends the policy information to the terminal.

[0162] The corresponding relationship between the at least one service information and the first access type indicated by the policy information can be indicated to the terminal by the policy control network element or the access management network element in a direct or indirect manner, or predefined, which is not limited in the present application. For example, the policy information can include the corresponding relationship between the at least one service information and the first access type. In this way, the terminal can know which service information is applicable to which access type.

[0163] Alternatively, the policy information can be carried in a UE configuration update (UCU) message, a UE parameter update (UPU) message, an application level message, a control message of network selection configuration or other messages.

[0164] Optionally, the policy control network element in the step 301 and the step 302 can be replaced by an access management network element. In this case, the policy information can be carried in a non-access stratum (NAS) message or a protocol data unit (PDU) session.

[0165] Optionally, the step 301 and the step 302 can be implemented in a registration procedure of the terminal or other procedures. The specific registration procedure can refer to an existing registration procedure, for example, a registration procedure in an existing version of a communication standard. Or refer to a newly added registration procedure, for example, a registration procedure in a future communication standard, which is not limited here.

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

[0167] For example, the terminal can determine the first service information of the terminal, and thus can determine the first access type suitable for the first service information based on the first service information and the policy information. The first service information belongs to at least one service information. For example, when the policy information is URSP, the service description word in the URSP indicates at least one service information, and the at least one service information includes the first service information. Therefore, the terminal can match the service information in the service description word based on the first service information, and then determine the first access type indicated by the route selection list description word in the URSP. In this way, the terminal determines the first access type suitable for the first service information based on the first service information and the policy information.

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

[0169] For example, the terminal selects one non-terrestrial network device from the at least one non-terrestrial network device corresponding to the first access type to initiate the session establishment or the session modification. For example, the terminal can send a session establishment request message or a session modification request message to the non-terrestrial network device. Optionally, the session establishment request message can be a PDU session establishment request message, and the session modification request message can be a PDU session modification request message, which is not limited here.

[0170] Optionally, the session establishment request message or the session modification request message can comprise session parameter information requested by the terminal to access, such as a network slice and / or a DNN. For example, when the policy information is URSP, the routing list description word in the URSP can also indicate the session parameter information, such as a network slice and / or a DNN. In this way, the terminal can carry the network slice and / or the DNN in the session establishment request message or the session modification request message. Optionally, the network slice requested by the terminal to access can be referred to as a requested NSSAI, which is the NSSAI provided by the terminal to a serving public land mobile (communication) network (PLMN) in a registration procedure, or the NSSAI locally configured by the terminal.

[0171] Optionally, the session parameter information can also comprise other information, which can be specifically referred to an existing session establishment or modification procedure, for example, a session establishment or modification procedure in an existing version of a communication standard. Or referred to a newly added session establishment or modification procedure, for example, a session establishment or modification procedure in a future communication standard, which is not limited here.

[0172] It can be seen that in the above embodiments, the policy control network element can indicate the policy information to the terminal, so that the terminal can determine the first access type based on the policy information, and then can initiate the session establishment or the session modification through the first access type. This enables the terminal to establish a session through a suitable access type, for example, the terminal can initiate the session establishment or the session modification through the first access type applicable to the first service information, reducing the situation that the business transmission demand cannot be met due to the mismatch between the service type and the access type, which guarantees the performance of the business transmission.

[0173] Referring to FIG. 4, FIG. 4 is a flow diagram of a communication method provided by an embodiment of the present application. As shown in FIG. 4, the method comprises but is not limited to the following steps:

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

[0175] The access management network element determining the first access type applicable to the third service information can have the following implementation manners, specifically:

[0176] 1. 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.

[0177] 2. The access management network element receives the first access type from the session management network element. That is, the session management network element obtains the first association relationship, and based on the first association relationship and the third service information, determines the first access type, and then instructs the access management network element. In this case, the access management network element can also send the third service information to the session management network element.

[0178] Optionally, the first association relationship described above can be indicated to the access management network element by some network element in a direct or indirect manner, or be predefined, which is not limited in the present application. For example, the access management network element can receive the first association relationship from an OAM device or a 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 signed or authorized association relationship.

[0179] As an example, the first association relationship includes a corresponding relationship between one or more access types and at least one service information supported by each access type. For example, the first association relationship includes a corresponding relationship between the first access type and at least one service information supported by the first access type. Wherein, the first access type refers to the type of the orbit to which the non-terrestrial network device belongs, that is, the orbit type of the non-terrestrial network device. In a possible implementation, the first access type and the orbit type can be described interchangeably, which is not limited herein.

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

[0181] The'service information supported by the first access type' is described below.

[0182] In the embodiment described in FIG. 4, the service information (such as the third service information, etc.) can be used to describe the service used by the terminal. For example, it includes the service type, which can refer to the description of step 301 of FIG. 3, which is not described here.

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

[0184] 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 can further include other information, which can refer to the existing session establishment procedure, for example, the session establishment procedure in the existing version of the communication standard. Or refer to the newly added session establishment procedure, for example, the session establishment procedure in the future communication standard, which is not limited here.

[0185] 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 slice supported by the access management network element includes network slice 1, network slice 3 and network slice 4. The network slice allocated to the terminal can be network slice 1.

[0186] Optionally, the network slice allocated to the terminal can be referred to as the allowed network slice, which can be referred to as allowed NSSAI.

[0187] The following describes several possible corresponding modes in the first association relationship, taking the service information as the network slice and DNN requested by the terminal as an example.

[0188] Table 3 illustrates a one-to-one correspondence between the access type and the service information. Specifically, in Table 3, when the access type is a low-orbit access type, the service information is network slice 1 and DNN 1. When the access type is a medium-orbit access type, the service information is network slice 2 and DNN 2.

[0189] Table 3

[0190] Table 4 illustrates a one-to-many correspondence between the access type and the service information. Specifically, in Table 4, when the access type is a low-orbit access type, the service information includes network slice 1 and DNN 1, and also includes network slice 2 and DNN 2.

[0191] Table 4

[0192] Table 5 illustrates a many-to-one correspondence between the access type and the service information. Specifically, in Table 5, when the access type is a low-orbit access type and a medium-orbit access type, the service information is network slice 1 and DNN 1.

[0193] Table 5

[0194] Table 6 illustrates a many-to-many correspondence between the access type and the service information. Specifically, in Table 6, when the access type is a low-orbit access type and a medium-orbit access type, the service information includes network slice 1 and DNN 1, and also includes network slice 2 and DNN 2.

[0195] Table 6

[0196] Table 7 illustrates that the access type, the service information and the non-terrestrial network device are one-to-one correspondence. Specifically, in Table 4, when the access type is the low-orbit access type, the service information is network slice 1 and DNN 1, and the non-terrestrial network device is non-terrestrial network device 1. When the access type is the medium-orbit access type, the service information is network slice 2 and DNN 2, and the non-terrestrial network device is non-terrestrial network device 2.

[0197] Table 7

[0198] Table 8 illustrates that the access type is one-to-many with any one of the service information and the non-terrestrial network device. Specifically, in Table 8, when the access type is the low-orbit access type, the service information includes network slice 1 and DNN 1, and also includes network slice 2 and DNN 2, and the non-terrestrial network device includes non-terrestrial network device 1 and non-terrestrial network device 2.

[0199] Table 8

[0200] Table 9 illustrates that the access type is many-to-one with any one of the service information and the non-terrestrial network device. Specifically, in Table 5, when the access type is the low-orbit access type and the medium-orbit access type, the service information is network slice 1 and DNN 1, and the non-terrestrial network device is non-terrestrial network device 1.

[0201] Table 9

[0202] Table 10 illustrates that the access type is many-to-many with any one of the service information and the non-terrestrial network device. Specifically, in Table 10, when the access type is the low-orbit access type and the medium-orbit access type, the service information includes network slice 1 and DNN 1, and also includes network slice 2 and DNN 2, and the non-terrestrial network device includes non-terrestrial network device 1 and non-terrestrial network device 2.

[0203] Table 10

[0204] It should be noted that the above Tables 3 to 10 are some examples of the correspondence between the access type and one or more of the service information and the non-terrestrial network device, and in actual application, the first association relationship can be implemented by any row and / or any column of any one or more of the above Tables 3 to 10, which is not limited in the present application.

[0205] Optionally, in the first association relationship, the at least one service information supported by the first access type can comprise third service information. In this way, the access management network element can determine the first access type based on the first association relationship and the third service information. For example, the access type and the service information are in a many-to-many or many-to-one relationship, and the access management network element determines multiple access types based on the first association relationship and the third service information, and then randomly selects one access type from the multiple access types as the first access type.

[0206] Optionally, when the first association relationship comprises the correspondence between the first access type, the at least one service information supported by the first access type, and the 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, the access type and the non-terrestrial network device are in a one-to-many or many-to-many relationship, and the access management network element determines multiple non-terrestrial network devices based on the first association relationship and the third service information, and then randomly selects one non-terrestrial network device from the multiple non-terrestrial network devices as the non-terrestrial network device to which the third service information applies.

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

[0208] Correspondingly, the access network device acquires the first RFSP index.

[0209] For example, the access management network element can send second indication information to the data management network element, and the second indication information is used to acquire the first RFSP index corresponding to the first access type. In this way, the data management network element can send the first RFSP index to the access management network element. Optionally, when the first RFSP index is from the data management network element, the first RFSP index can be considered as a subscribed or authorized RFSP index. Optionally, the second indication information is also used to indicate the non-terrestrial network device to which the third service information applies.

[0210] For example, the access management network element acquires the second association relationship, and thus can determine the first RFSP index based on the second association relationship and the first access type.

[0211] Optionally, the second association relationship can be indicated to the access management network element by some network element in a direct or indirect manner, or be predefined, which is not limited in the present application. For example, the access management network element can acquire the second association relationship from an OAM device or a data management network element. Optionally, when the second association relationship is from the data management network element, the second association relationship can be considered as a subscribed or authorized association relationship.

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

[0213] As another example, the second association relationship includes a correspondence relationship 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 relationship includes a correspondence relationship between a first access type, at least one RFSP index, and M non-terrestrial network devices, the M non-terrestrial network devices including a non-terrestrial network device to which the third service information applies, and M is a positive integer.

[0214] The following describes several possible correspondence modes in the second association relationship.

[0215] Table 11 illustrates a one-to-one correspondence relationship between the access type and the RFSP index. Specifically, in Table 11, when the access type is a low-orbit access type, the RFSP index is RFSP index 1. When the access type is a medium-orbit access type, the RFSP index is RFSP index 2.

[0216] Table 11

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

[0218] Table 12

[0219] Table 13 illustrates a many-to-one correspondence relationship between the access type and the RFSP index. Specifically, in Table 13, when the access type is a low-orbit access type and a medium-orbit access type, the RFSP index is RFSP index 1.

[0220] Table 13

[0221] Table 14 illustrates a many-to-many correspondence relationship between the access type and the RFSP index. Specifically, in Table 14, when the access type is a low-orbit access type and a medium-orbit access type, the RFSP index is RFSP index 1 and RFSP index 2.

[0222] Table 14

[0223] Table 15 illustrates that the access type, the RFSP index and the non-terrestrial network device are one-to-one correspondence. Specifically, in Table 15, when the access type is the low-orbit access type, the RFSP index is the RFSP index 1, and the non-terrestrial network device is the non-terrestrial network device 1. When the access type is the medium-orbit access type, the RFSP index is the RFSP index 2, and the non-terrestrial network device is the non-terrestrial network device 2.

[0224] Table 15

[0225] Table 16 illustrates that the access type is one-to-many correspondence with any one of the RFSP index and the non-terrestrial network device. Specifically, in Table 16, when the access type is the low-orbit access type, the RFSP index includes the RFSP index 1 and the RFSP index 2, and the non-terrestrial network device includes the non-terrestrial network device 1 and the non-terrestrial network device 2.

[0226] Table 16

[0227] Table 17 illustrates that the access type is many-to-one correspondence with any one of the RFSP index and the non-terrestrial network device. Specifically, in Table 17, when the access type is the low-orbit access type and the medium-orbit access type, the RFSP index is the RFSP index 1, and the non-terrestrial network device is the non-terrestrial network device 1.

[0228] Table 17

[0229] Table 18 illustrates that the access type is many-to-many correspondence with any one of the RFSP index and the non-terrestrial network device. Specifically, in Table 18, when the access type is the low-orbit access type and the medium-orbit access type, the RFSP index is the RFSP index 1 and the RFSP index 2, and the non-terrestrial network device includes the non-terrestrial network device 1 and the non-terrestrial network device 2.

[0230] Table 18

[0231] It should be noted that the above Tables 11 to 18 are some examples of the correspondence between the access type and one or more of the RFSP index and the non-terrestrial network device, and in actual application, the second association relationship can be implemented by any row and / or any column of any one or more of the above Tables 11 to 18, which is not limited in the present application.

[0232] Optionally, in the second association relationship, the at least one RFSP index corresponding to the first access type includes the first RFSP index. In this way, the access management network element can determine the first RFSP index based on the second association relationship and the first access type. For example, the access type and the RFSP index are in a many-to-many or many-to-one relationship, and the access management network element determines multiple RFSP indexes based on the second association relationship and the first access type, and then randomly selects one RFSP index from the multiple RFSP indexes as the first RFSP index.

[0233] Optionally, when the second association relationship includes the correspondence between the first access type, the at least one RFSP index, and the 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 device to which the third service information applies. For example, the RFSP index is in a many-to-many or many-to-one relationship with any one or more of the access type and the non-terrestrial network device, and the access management network element determines multiple RFSP indexes based on the second association relationship, the first access type, and the non-terrestrial network device to which the third service information applies, and then randomly selects one RFSP index from the multiple RFSP indexes as the first RFSP index.

[0234] The following describes the case in which the access management network element sends the first RFSP index.

[0235] Optionally, the access management network element sends the first RFSP index when a first condition is met. Optionally, the first condition includes that the first access type is different from the current access type of the terminal 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.

[0236] Optionally, the current access type of the terminal can be understood as a specified type of the non-terrestrial network device accessed by the terminal before or after the access management network element obtains the third service information. For example, the specified type of the non-terrestrial network device accessed by the terminal after the access management network element obtains the third service information can be understood as the specified type of the non-terrestrial network device accessed by the terminal before the access management network element sends the first RFSP index, which is not limited in the present application.

[0237] 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 non-terrestrial network device to which the third service information applies from the session management network element.

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

[0239] Optionally, in the embodiment described in Figure 4, the process of 'determining the first access type to which the third service information is applicable and the first RFSP index corresponding to the first access type' can be performed by the access management network element or the session management network element alone, or jointly performed by the access management network element and the session management network element. Alternatively, 'determining the first access type to which the third service information is applicable' is performed by the access management network element or the session management network element alone, and the process of 'determining the first RFSP index corresponding to the first access type' can be performed by the data management network element.

[0240] For example, the 'determining the first access type to which the third service information is applicable and the first RFSP index corresponding to the first access type' is performed by the access management network element alone. For example, the access management network element determining the first access type to which the third service information is applicable can include: obtaining the first association relationship, and determining the first access type based on the first association relationship and the third service information. For example, the access management network element determining the first RFSP index corresponding to the first access type can include: the access management network element determining the first RFSP index based on the second association relationship and the first access type, the second association relationship including the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index including the first RFSP index.

[0241] For example, the 'determining the first access type to which the third service information is applicable and the first RFSP index corresponding to the first access type' is performed by the session management network element alone. Optionally, when the 'determining the first access type to which the third service information is applicable' is performed by the session management network element alone, the access management network element can also send the third service information to the session management network element, so that the session management network element determines the first access type to which the third service information is applicable.

[0242] For example, the session management network element determining the first access type to which the third service information is applicable can include: obtaining the first association relationship, and determining the first access type based on the first association relationship and the third service information. Wherein, the way for the session management network element to obtain the first association relationship can refer to the way for the access management network element to obtain the first association relationship, which is not described here. The way for the session management network element to determine the first access type based on the first association relationship and the third service information can refer to the way for the access management network element to determine the first access type based on the first association relationship and the third service information, which is not described here.

[0243] For example, the session management network element determining the first RFSP index corresponding to the first access type can comprise: the session management network element determining the first RFSP index based on the second association relationship and the first access type, the second association relationship comprising a correspondence relationship between the first access type and at least one RFSP index, the at least one RFSP index comprising the first RFSP index. Wherein, the manner in which the session management network element obtains the second association relationship can refer to the manner in which the access management network element obtains the second association relationship, and details are not repeated here. The manner in which the session management network element determines the first RFSP index based on the second association relationship and the first access type can refer to the manner in which the access management network element determines the first RFSP index based on the second association relationship and the first access type, and details are not repeated here.

[0244] For example, the 'determining the first access type to which the third service information applies' is performed by the access management network element alone, and the 'determining the first RFSP index corresponding to the first access type' is performed by the session management network element or the data management network element alone. Alternatively, when the 'determining the first RFSP index corresponding to the first access type' is performed by the session management network element or the data management network element alone, the access management network element can also indicate the first access type to the session management network element or the data management network element.

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

[0246] For example, the data management network element receives the second indication information from the access management network element, the second indication information being used to obtain the first RFSP index corresponding to the first access type, and the second indication information comprising the first access type. In this way, the data management network element can determine the first RFSP index based on the second association relationship and the first access type. Alternatively, the data management network element can locally store the second association relationship or obtain the second association relationship from the OAM device. Wherein, the manner in which the data management network element determines the first RFSP index based on the second association relationship and the first access type can refer to the manner in which the access management network element determines the first RFSP index based on the second association relationship and the first access type, and details are not repeated here.

[0247] It should be noted that the above is some examples of which network element 'determines the first access type to which the third service information corresponds and the first RFSP index corresponding to the first access type', and other combinations of these examples can also be used to achieve 'determining the first access type to which the third service information corresponds and the first RFSP index corresponding to the first access type', which will not be enumerated one by one.

[0248] It can be seen that in the above embodiments, the access management network element or the session management network element can determine the first access type to which the third service information is applicable, so that the first RFSP index corresponding to the first access type can be sent, which enables the access network device to perform redirection, such as redirecting the terminal to another cell, etc. This can trigger the terminal to re-perform the registration process, such as re-initiating session establishment or modification, so as to ensure the consistency of the service type and the access type as much as possible, reduce the situation that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and ensure the performance of service transmission.

[0249] The method embodiments shown in FIG. 4 include many possible implementation schemes. Some implementation schemes will be described below with reference to any one of FIG. 5 and FIG. 6. In any one of FIG. 5 and FIG. 6, the terminal is UE, the access network device is RAN, the access management network element is AMF, the unified data management network element is UDM, and the session management network element is SMF. The related concepts or operations or logical relationships not explained in any one of FIG. 5 and FIG. 6 can be referred to the corresponding description in the embodiment shown in FIG. 4, and thus will not be described again.

[0250] Referring to FIG. 5, FIG. 5 is a flowchart of another communication method provided by the embodiments of the present application. As shown in FIG. 5, the method includes but is not limited to the following steps:

[0251] 501. The UE sends a session establishment request message, and the session establishment request message includes third service information.

[0252] Correspondingly, the AMF receives the session establishment request message.

[0253] 502. The AMF determines a first access type to which the third service information is applicable, and the first access type includes at least one of the following: a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type.

[0254] 503. The AMF sends second indication information to the UDM, and the second indication information is used to obtain a first RFSP index corresponding to the first access type.

[0255] Correspondingly, the UDM receives the second indication information from the AMF.

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

[0257] Correspondingly, the AMF receives the first RFSP index from the UDM.

[0258] 505. The AMF sends the first RFSP index to the RAN, and the first RFSP index is used to trigger the access network device to perform redirection.

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

[0260] It can be seen that in the above embodiments, the AMF can obtain the third service information in the session establishment request message from the UE, so as to determine the first access type to which the third service information is applicable, and then obtain the first RFSP index corresponding to the first access type from the UDM based on the first access type, and indicate the first RFSP index to the RAN, which enables the RAN to perform redirection, such as redirecting the terminal to another cell, etc. This can trigger the terminal to re-perform the registration process, such as re-initiating session establishment or modification, so as to guarantee the consistency of the service type and the access type as much as possible, reduce the situation that the service transmission requirement cannot be met due to the mismatch between the service type and the access type, and guarantee the performance of service transmission.

[0261] Referring to FIG. 6, FIG. 6 is a flow diagram of another communication method provided by the embodiments of the present application. As shown in FIG. 6, the method includes but is not limited to the following steps:

[0262] 601. The UE sends a session establishment request message, wherein the session establishment request message includes third service information.

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

[0264] 602. The AMF sends the third service information to the SMF.

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

[0266] 603. The SMF determines a first access type to which the third service information is applicable, wherein the first access type includes at least one of the following: a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type.

[0267] 604. The SMF sends second indication information to the UDM, wherein the second indication information is used to obtain a first RFSP index corresponding to the first access type.

[0268] Accordingly, the UDM receives the second indication information from the SMF.

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

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

[0271] 606. The SMF sends the first RFSP index to the RAN, wherein the first RFSP index is used to trigger the access network device to perform redirection.

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

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

[0274] It can be seen that in the above embodiments, the AMF can obtain the third service information in the session establishment request message from the UE, and indicate the third service information to the SMF, so that the SMF can determine the first access type to which the third service information applies, and then obtain the first RFSP index corresponding to the first access type from the UDM based on the first access type, and indicate the first RFSP index to the RAN, which makes the RAN can perform redirection, such as redirecting the terminal to another cell, etc. This may trigger the terminal to re-execute the registration process, such as re-initiating session establishment or modification, so as to guarantee the consistency of the service type and the access type as much as possible, reduce the situation that the service transmission demand cannot be met due to the mismatch between the service type and the access type, and guarantee the performance of service transmission.

[0275] Referring to FIG. 7, FIG. 7 is a flow diagram of a communication method according to an embodiment of the present application. As shown in FIG. 7, the method includes but is not limited to the following steps:

[0276] 701. The terminal sends a registration request to an access management network element, the registration request including a cause value for establishing a connection, the cause value corresponding to a first access type, the first access type including at least one of the following: a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type.

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

[0278] Optionally, the terminal can initiate a registration process through the registration request. Wherein, the cause value is used to indicate the reason for triggering the registration process. Or it can be understood that: the cause value is used to indicate the reason for the terminal sending the registration request. Or in other words, the cause value can be called an establishment cause value. For example, in the present application, the cause value can be used to indicate the service (or service type) that initiates 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 cause value being used to indicate at least one of the following: Mo-Data, Mo-SMS, or Mission Critical.

[0279] Optionally, there is a corresponding relationship between the service and the access type. Specifically, the corresponding relationship between the service and the access type can be as shown in Table 19. For example, when the access type is the low-orbit access type, the cause value indicates Mo-Data and Mo-SMS, and the rest is similar, which is not described here.

[0280] Table 19

[0281] Optionally, the service and the access type can be in a one-to-one, one-to-many, many-to-one, or many-to-many relationship, which is not limited in the present application.

[0282] Optionally, the corresponding relationship between the service and the access type can be indicated by some network elements to the access management network element in a direct or indirect manner, or be predefined, which is not limited in the present application. For example, taking the corresponding relationship between the service 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 an OAM device or a data management network element, and the third association relationship includes the corresponding relationship between the service 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 that the third association relationship is a signed or authorized association relationship.

[0283] Next, how to determine the first access type corresponding to the cause value is introduced.

[0284] 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 example, the service and the access type are in a one-to-many or many-to-many relationship, and the access management network element can determine multiple access types based on the service indicated by the cause value and the third association relationship, so that one access type can be randomly selected from the multiple access types as the first access type.

[0285] For example, the access management network element can receive the first access type from the session management network element. In this case, the access management network element can send the cause value to the session management network element, so that the session management network element determines the first access type based on the service indicated by the cause value and the third association relationship. For example, the service and the access type are in a one-to-many or many-to-many relationship, and the session management network element can determine multiple access types based on the service indicated by the cause value and the third association relationship, so that one access type can be randomly selected from the multiple access types as the first access type, and then the first access type is indicated to the access management network element.

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

[0287] Correspondingly, the access network device receives the first RFSP index from the access management network element.

[0288] Optionally, the process that the access management network element determines the first RFSP index corresponding to the first access type in step 702 can refer to the related description of step 402 in FIG. 4, which will not be repeated here.

[0289] Optionally, the access management network element sending the first RFSP index to the access network device can include: the access management network element sending the first RFSP index to the access network device in the case that the first access type is different from the current access type of the terminal. Optionally, the current access type of the terminal can be understood as the specified type of the non-terrestrial network device accessed by the terminal before or after the access management network element obtains the third service information. For example, the specified type of the non-terrestrial network device accessed by the terminal after the access management network element obtains the third service information can be understood as the specified type of the non-terrestrial network device accessed by the terminal before the access management network element sends the first RFSP index, which is not limited in the present application.

[0290] Optionally, in the embodiment described in FIG. 7, the process of ‘determining the first access type corresponding to the reason value and the first RFSP index corresponding to the first access type’ can be performed by the access management network element or the session management network element alone, or jointly performed by the access management network element and the session management network element. Alternatively, ‘determining the first access type applicable to the third service information’ is performed by the access management network element or the session management network element alone, and the process of ‘determining the first RFSP index corresponding to the first access type’ can be performed by the data management network element.

[0291] For example, ‘determining the first access type corresponding to the reason value and the first RFSP index corresponding to the first access type’ is performed by the access management network element alone. For example, the access management network element determining the first access type corresponding to the reason value can include: obtaining the third association relationship, and determining the first access type based on the third association relationship and the service indicated by the reason value. For example, the access management network element determining the first RFSP index corresponding to the first access type can include: the access management network element determining the first RFSP index based on the second association relationship and the first access type, the second association relationship including the correspondence between the first access type and at least one RFSP index, and the at least one RFSP index including the first RFSP index.

[0292] For example, ‘determining the first access type corresponding to the reason value and the first RFSP index corresponding to the first access type’ is performed by the session management network element alone. Optionally, when ‘determining the first access type corresponding to the reason value’ is performed by the session management network element alone, the access management network element can also send the reason value to the session management network element, so that the session management network element determines the first access type corresponding to the reason value.

[0293] For example, the session management network element determining the first access type corresponding to the cause value can 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 session management network element can obtain the third association relationship in the same manner as the access management network element, and details are not repeated here. The session management network element can determine the first access type based on the third association relationship and the service indicated by the cause value in the same manner as the access management network element, and details are not repeated here.

[0294] For example, the session management network element determining the first RFSP index corresponding to the first access type can include: the session management network element determining the first RFSP index based on a second association relationship and the first access type, the second association relationship including a corresponding relationship between the first access type and at least one RFSP index, and the at least one RFSP index including the first RFSP index. The session management network element can obtain the second association relationship in the same manner as the access management network element, and details are not repeated here. The session management network element can determine the first RFSP index based on the second association relationship and the first access type in the same manner as the access management network element, and details are not repeated here.

[0295] For example, the session management network element determining the first RFSP index corresponding to the first access type can include: the session management network element determining the first RFSP index based on a second association relationship and the first access type, the second association relationship including a corresponding relationship between the first access type and at least one RFSP index, and the at least one RFSP index including the first RFSP index. The session management network element can obtain the second association relationship in the same manner as the access management network element, and details are not repeated here. The session management network element can determine the first RFSP index based on the second association relationship and the first access type in the same manner as the access management network element, and details are not repeated here.

[0296] For example, the session management network element receiving second indication information from the access management network element, the second indication information being used to obtain the first RFSP index corresponding to the first access type, and the second indication information including the first access type. In this way, the session management network element can determine the first RFSP index based on the second association relationship and the first access type.

[0297] For example, the data management network element receives second indication information from the access management network element, the second indication information is used to obtain the first RFSP index corresponding to the first access type, and the second indication information includes the first access type. In this way, 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 locally store the second association relationship or obtain the second association relationship from the OAM device. Wherein, the manner in which the data management network element determines the first RFSP index based on the second association relationship and the first access type can refer to the manner in which the access management network element determines the first RFSP index based on the second association relationship and the first access type, and details are not repeated here.

[0298] It should be pointed out that the above is some examples of which network element 'determines the first access type corresponding to the cause value and the first RFSP index corresponding to the first access type', and other combinations of these examples can also be implemented to achieve 'determining the first access type corresponding to the cause value and the first RFSP index corresponding to the first access type', which will not be enumerated one by one.

[0299] As can be seen, in the above embodiments, the access management network element determines the first access type based on the cause value of establishing a connection, so that the first RFSP index corresponding to the first access type can be sent, which enables the access network device to perform redirection, such as redirecting the terminal to another cell, etc. This can trigger the terminal to re-execute the registration process, such as re-initiating session establishment or modification, so as to ensure the consistency of the service type and the access type as much as possible, reduce the situation that the service transmission demand cannot be met due to the mismatch between the service type and the access type, and ensure the performance of service transmission.

[0300] The method embodiment shown in FIG. 7 includes many possible implementation schemes, some of which will be exemplified below in conjunction with FIG. 8. In FIG. 8, the terminal is UE, the access network device is RAN, the access management network element is AMF, and the unified data management network element is UDM. The related concepts or operations or logical relationships not explained in FIG. 8 can refer to the corresponding description in the embodiment shown in FIG. 7, and thus will not be repeated here.

[0301] 801. The UE sends a registration request to the AMF, the registration request including a cause value of establishing a connection, the cause value corresponding to a first access type, the first access type including at least one of the following: a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type.

[0302] Correspondingly, the AMF receives the registration request from the UE.

[0303] 802. The AMF sends second indication information to the UDM, the second indication information being used to obtain a first RFSP index corresponding to the first access type.

[0304] Accordingly, the UDM receives the second indication information from the AMF.

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

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

[0307] 804. The AMF sends the first RFSP index to the RAN, and the first RFSP index is used to trigger the access network device to perform redirection.

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

[0309] As can be seen, in the above embodiment, the AMF can learn the cause value of the UE to establish a connection, so as to determine the first access type corresponding to the cause value, and then obtain the first RFSP index corresponding to the first access type from the UDM based on the first access type, and indicate the first RFSP index to the RAN, which makes the RAN can perform redirection, such as redirecting the terminal to another cell, etc. This may trigger the terminal to re-perform the registration process, such as re-initiating session establishment or modification, so as to guarantee the consistency of the service type and the access type as much as possible, reduce the situation that the service transmission demand cannot be met due to the mismatch between the service type and the access type, and guarantee the performance of service transmission.

[0310] It can be understood that, in order to implement the above functions, the device contains the hardware structure and / or software module corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the examples described in the embodiments disclosed in the present text, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the form of hardware or computer software driven hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of the present application.

[0311] The embodiments of the present application can divide the functional modules of the terminal, the access management network element, the session management network element, the data management network element, or the policy control network element, etc. according to the above method examples, for example, each functional module can be divided according to each function, or two or more functions can be integrated in one processing module. The above integrated module can be realized in the form of hardware or software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical function division. There can be another division way when actually implemented.

[0312] Referring to FIG. 9, FIG. 9 is a structural schematic diagram of a communication apparatus provided in an embodiment of the present application. The communication apparatus 900 can be applied in the method shown in any of the embodiments shown in FIGs. 3 to 8. As shown in FIG. 9, the communication apparatus 900 comprises a processing module 901 and a transceiver module 902. The processing module 901 can be one or more processors, and the transceiver module 902 can be a transceiver or a communication interface. The communication apparatus can be used to implement the functions of the terminal, the access management network element, the session management network element, the data management network element or the policy control network element, etc. in any of the method embodiments, or to implement the functions of the network element in any of the method embodiments. The network element or network function can be a network element in a hardware device, a software function running on a special hardware, or a virtualized function instantiated on a platform (for example, a cloud platform). Optionally, the communication apparatus 900 can further comprise a storage module 903 for storing the program codes and data of the communication apparatus 900. It should be understood that whether the functional modules are subdivided or combined, the communication apparatus 900 implements the same general process as the terminal in any of the method embodiments. For example, the transceiver module 902 in the communication apparatus 900 can comprise a receiving module and / or a sending module, and of course, the transceiver module can also be referred to as a communication module. In an implementation manner, each module can correspond to a respective program code (or program instruction), and the respective program codes of these modules enable the unit to execute the corresponding process and thus implement the corresponding function when running on the processor.

[0313] In an example, when the communication apparatus is a terminal or a chip applied in the terminal, that is, a chip for the terminal, and performs the steps performed by the terminal in the method embodiments. The transceiver module 902 is configured to specifically perform the sending and / or receiving actions performed by the terminal in any of the embodiments shown in FIGs. 3 to 8, for example, to support the terminal to perform other processes of the techniques described herein. The processing module 901 can be configured to support the communication apparatus 900 to perform the processing actions in the method embodiments, for example, to support the terminal to perform other processes of the techniques described herein.

[0314] For example, the transceiver module 902 is configured to acquire policy information, the policy information being used to indicate a correspondence between at least one type of service information and a first access type, the first access type being an access type to which the at least one type of service information is applicable; and the processing module 901 is configured to determine the first access type based on the policy information, the first access type comprising at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type or a multi-orbit access type; and the transceiver module 902 is further configured to initiate session establishment or session modification through the first access type.

[0315] Optionally, when the first association relationship is acquired, the transceiver module 902 is configured to receive the policy information from a policy control network element or an access management network element.

[0316] Optionally, when determining the first access type based on the policy information, the processing module 901 is configured to: determine first service information of the terminal, the first service information belonging to at least one service information; and determine the first access type to which the first service information is applicable based on the first service information and the policy information.

[0317] An example is that the communication apparatus serves as a policy control network element or a chip applied to the policy control network element, i.e., a chip for the policy control network element, and performs the steps performed by the policy control network element in the method embodiments. The transceiver module 902 is configured to specifically perform the sending and / or receiving actions performed by the policy control network element in any of the embodiments shown in FIGS. 3 to 8, for example, other processes supporting the policy control network element to perform the techniques described herein. The processing module 901 can be configured to support the communication apparatus 900 to perform the processing actions in the method embodiments described above, for example, other processes supporting the policy control network element to perform the techniques described herein.

[0318] For example, the processing module 901 is configured to determine policy information, the policy information being used to indicate a correspondence between at least one service information and a first access type, the first access type being an access type to which the at least one service information is applicable, the first access type including at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type; and the transceiver module 902 is configured to send the policy information to the terminal.

[0319] Optionally, when determining the policy information, the processing module 901 is configured to: acquire, by the transceiver module 902, subscription information of the terminal from a data management network element, and / or acquire, by the transceiver module 902, first indication information from an application function network element; and determine the policy information based on the subscription information and / or the first indication information. The subscription information of the terminal or the first indication information is used to indicate orbit information of a non-terrestrial network device accessible by the terminal and second service information, the second service information being associated with the orbit information, the second service information belonging to the at least one service information, the orbit information including an orbit height parameter and / or an orbit type, the orbit type including a low orbit, a medium orbit, a high orbit, or a multi-orbit.

[0320] An example is that the communication apparatus serves as an access management network element or a chip applied to the access management network element, i.e., a chip for the access management network element, and performs the steps performed by the access management network element in the method embodiments. The transceiver module 902 is configured to specifically perform the sending and / or receiving actions performed by the access management network element in any of the embodiments shown in FIGS. 3 to 8, for example, other processes supporting the access management network element to perform the techniques described herein. The processing module 901 can be configured to support the communication apparatus 900 to perform the processing actions in the method embodiments described above, for example, other processes supporting the access management network element to perform the techniques described herein.

[0321] The processing module 901 is configured to determine a first access type to which the third service information is applicable, and the first access type comprises at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type. The transceiver module 902 is configured to send a first radio access technology / frequency selection priority (RFSP) index corresponding to the first access type, and the first RFSP index is used to trigger the access network device to perform redirection.

[0322] Optionally, when determining the first access type to which the third service information is applicable, the processing module 901 is configured to obtain a first association relationship by the transceiver module 902, and determine the first access type based on the first association relationship and the third service information.

[0323] Optionally, when obtaining the first association relationship, the processing module 901 is configured to receive the first association relationship from an OAM device or a data management network element by the transceiver module 902.

[0324] Optionally, when determining the first access type to which the third service information is applicable, the processing module 901 is configured to receive the first access type from a session management network element by the transceiver module 902.

[0325] Optionally, the processing module 901 is further configured to send the third service information to the session management network element.

[0326] 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 in a case where a first condition is met. The first condition comprises that the first access type is different from a current access type of the terminal and / or a non-terrestrial network device to which the third service information is applicable is different from a non-terrestrial network device accessed by the terminal.

[0327] Optionally, the first association relationship comprises a corresponding relationship among the first access type, at least one type of service information supported by the first access type, and N non-terrestrial network devices, N is a positive integer, and the processing module 901 is further configured to determine a non-terrestrial network device to which the third service information is applicable based on the first association relationship and the third service information.

[0328] Optionally, the transceiver module 902 is further configured to receive the non-terrestrial network device to which the third service information is applicable from the session management network element.

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

[0330] Optionally, the transceiver 902 is further configured to send second indication information to the data management network element, the second indication information being used to acquire the first RFSP index, the second indication information comprising the first access type.

[0331] Optionally, in acquiring the second association relationship, the transceiver 902 is configured to receive the second association relationship from the OAM device or the data management network element.

[0332] Optionally, the second association relationship comprises a correspondence between the first access type, at least one RFSP index, and M non-terrestrial network devices, the M non-terrestrial network devices comprising a non-terrestrial network device to which the third service information is applicable, M being a positive integer, and in determining the first RFSP index based on the second association relationship and the first access type, the processing module 901 is configured to determine the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network device to which the third service information is applicable.

[0333] Optionally, the transceiver 902 is configured to: receive a registration request from a terminal, the registration request comprising a cause value for establishing a connection, the cause value corresponding to the first access type, the first access type comprising at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type; and send, to an access network device, a first RFSP index corresponding to the first access type, the first RFSP index being used to trigger the access network device to perform redirection.

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

[0335] Optionally, in acquiring the third association relationship, the transceiver 902 is configured to receive the third association relationship from the OAM device or the data management network element.

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

[0337] Optionally, the transceiver 902 is further configured to send second indication information to the data management network element, the second indication information being used to acquire the first RFSP index, the second indication information comprising the first access type.

[0338] In an example, the communication apparatus is configured to perform the steps performed by the session management network element in the above method embodiments when the communication apparatus is a session management network element or a chip applied in the session management network element, i.e., a chip for the session management network element. The transceiver 902 is configured to specifically perform the sending and / or receiving actions performed by the session management network element in any of the embodiments shown in FIGS. 3 to 8, for example, other processes supporting the session management network element to perform the techniques described herein. The processing module 901 can be configured to support the communication apparatus 900 to perform the processing actions in the above method embodiments, for example, other processes supporting the session management network element to perform the techniques described herein.

[0339] For example, the processing module 901 is configured to determine a first access type to which the third service information is applicable, the first access type comprising at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type; and the transceiver 902 is configured to send a 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.

[0340] Optionally, in determining the first access type to which the third service information is applicable, the processing module 901 is configured to acquire, by the transceiver 902, a first association relationship, and determine the first access type based on the first association relationship and the third service information.

[0341] Optionally, in acquiring the first association relationship, the processing module 901 is configured to receive, by the transceiver 902, the first association relationship from an OAM device or a data management network element.

[0342] Optionally, in determining the first access type to which the third service information is applicable, the processing module 901 is configured to receive, by the transceiver 902, the first access type from an access management network element.

[0343] Optionally, the transceiver 902 is configured to transmit the first RFSP index when a first condition is met, in the transmitting of the first RFSP index corresponding to the first access type. The first condition includes that the first access type is different from a current access type of the terminal and / or a non-terrestrial network device to which the third service information is applicable is different from a non-terrestrial network device to which the terminal requests to access.

[0344] Optionally, the first association relationship includes a corresponding relationship among the first access type, at least one service information supported by the first access type, and N non-terrestrial network devices, N being a positive integer. The processing module 901 is further configured to determine the non-terrestrial network device to which the third service information is applicable based on the first association relationship and the third service information.

[0345] Optionally, the transceiver 902 is further configured to receive the non-terrestrial network device to which the third service information is applicable from an access management network element.

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

[0347] Optionally, the transceiver 902 is further configured to transmit second indication information to a data management network element, and the second indication information is used to acquire the first RFSP index, and the second indication information includes the first access type.

[0348] Optionally, in the acquiring of the second association relationship, the transceiver 902 is configured to receive the second association relationship from an OAM device or a data management network element.

[0349] Optionally, the second association relationship includes a corresponding relationship among the first access type, at least one RFSP index, and M non-terrestrial network devices, the M non-terrestrial network devices including the non-terrestrial network device to which the third service information is applicable, and M being a positive integer. In the determining of the first RFSP index based on the second association relationship and the first access type, the processing module 901 is configured to determine the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network device to which the third service information is applicable.

[0350] An example, when the communication apparatus is a data management network element or a chip applied in the data management network element, i.e., a chip for the data management network element, and performs the steps performed by the data management network element in the method embodiments described above. The transceiver module 902 is configured to specifically perform the sending and / or receiving actions performed by the data management network element in any of the embodiments shown in FIGS. 3 to 8, for example, to support the data management network element to perform other processes of the techniques described herein. The processing module 901 can be configured to support the communication apparatus 900 to perform the processing actions in the method embodiments described above, for example, to support the data management network element to perform other processes of the techniques described herein.

[0351] For example, the transceiver module 902 is configured to: receive second indication information from the 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 the access management network element. Alternatively, the transceiver module 902 is configured to: receive second indication information from the 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 the session management network element.

[0352] Optionally, the processing module 901 is configured to obtain, by the transceiver module 902, 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 including a correspondence relationship between the first access type and at least one RFSP index, the at least one RFSP index including the first RFSP index.

[0353] Optionally, the second association relationship includes a correspondence relationship between the first access type, at least one RFSP index, and M non-terrestrial network devices, the M non-terrestrial network devices including a non-terrestrial network device to which the third service information is applicable, M being a positive integer, and when determining the first RFSP index based on the second association relationship and the first access type, the processing module 901 is configured to determine the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network device to which the third service information is applicable.

[0354] In a possible implementation, when the apparatus is a chip, the transceiver module 902 can be a communication interface, a pin, or a circuit, etc. The communication interface can be used to input data to be processed to the processor, and can output the processing result of the processor to the outside. In a specific implementation, the communication interface can be a general purpose input output (GPIO) interface, and can be connected with a plurality of peripheral devices (such as a display (LCD), a camera, a radio frequency (RF) module, an antenna, etc.). The communication interface is connected with the processor through a bus.

[0355] The processing module 901 can be a processing circuit, which can be one or more processors, or all or part of the circuit in the one or more processors for control and / or processing. The processing circuit or the processor can execute computer-executed instructions stored in the storage module, so that the chip executes the method related to any of the embodiments shown in FIGS. 3 to 8. Further, the processor can include a controller, an arithmetic unit, and a register. For example, the controller is mainly responsible for instruction decoding and sending a control signal for the operation corresponding to the instruction. The arithmetic unit is mainly responsible for executing fixed-point or floating-point arithmetic operations, shift operations, and logic operations, etc., and can also execute address operations and conversion. The register is mainly responsible for saving the register operand and intermediate operation result temporarily stored in the process of instruction execution, etc. In a specific implementation, the hardware architecture of the processor can be an application-specific integrated circuit (ASIC) architecture, a microprocessor without interlocked piped stages architecture (MIPS) architecture, an advanced RISC machines (ARM) architecture, or a network processor (NP) architecture, etc. The processor can be single-core or multi-core. The storage module can be a storage module in the chip, such as a register, a cache, etc. The storage module can also be a storage module located outside the chip, such as a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.

[0356] It should be noted that the functions of the processor and the interface can be implemented by hardware design, software design, or a combination of hardware and software, which is not limited here.

[0357] Fig. 10 is a structural schematic diagram of another communication apparatus provided by the embodiments of the present application. It can be understood that the communication apparatus 1010 includes necessary means such as modules, units, elements, circuits, or interfaces, which are configured together to perform the present solution. The communication apparatus 1010 can be the terminal, the access management network element, the session management network element, the data management network element, or the policy control network element, or a component (for example, a chip) of these devices, to implement the methods described in the above method embodiments. The communication apparatus 1010 includes one or more processors 1011. The processor 1011 can be a general purpose processor or a special purpose processor. For example, it can 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 apparatus (such as a terminal, an access management network element, a session management network element, a data management network element, a policy control network element, or a chip), execute software programs, and process data of the software programs.

[0358] Optionally, in one design, the processor 1011 can include a program 1013 (which can also be referred to as code or instructions at times) that can be run on the processor 1011, so that the communication apparatus 1010 performs the methods described in the above embodiments. In another possible design, the communication apparatus 1010 includes a circuit (not shown in Fig. 10) for implementing the functions of the terminal, the access management network element, the session management network element, the data management network element, the policy control network element, and the like in the above embodiments. Optionally, the communication apparatus 1010 can include one or more memories 1012 having a program 1014 (which can also be referred to as code or instructions at times) stored thereon, and the program 1014 can be run on the memory 1012, so that the communication apparatus 1010 performs the methods described in the above method embodiments.

[0359] Optionally, the processor 1011 and / or the memory 1012 can also store data. The processor and the memory can be separately arranged or integrated together.

[0360] Optionally, when the communication apparatus 1010 is a terminal, an access management network element, a session management network element, a data management network element, or a policy control network element, it can further include a transceiver 1015 and / or an antenna 1016. The processor 1011 can also be referred to as a processing unit, which controls the communication apparatus (such as a terminal or an access network device). The transceiver 1015 can also be referred to as a transceiving unit, a transceiver, a transceiving circuit, or a transceiver, which is used to realize the transceiving function of the communication apparatus through the antenna 1016. Optionally, the transceiver 1015 can include a receiver and / or a transmitter. The receiver can be referred to as a receiving unit, a receiver, or a receiving circuit. The transmitter can be referred to as a transmitting unit, a transmitter, or a transmitting circuit.

[0361] Optionally, the communication device 1010 also includes a transceiver circuit, such as an input / output interface, or a transceiver interface, in the case of a chip for a terminal, an access management network element, a session management network element, a data management network element, or a policy control network element.

[0362] The embodiments of the present application also provide a communication device, which includes at least one processor; wherein the at least one processor is configured to perform the method of any of the embodiments shown in FIGS. 3-8.

[0363] The embodiments of the present application also provide a computer readable storage medium, which stores computer instructions, when the computer instructions are executed, causing a computer to perform the method of any of the embodiments shown in FIGS. 3-8.

[0364] The embodiments of the present application also provide a computer program product, which includes computer program codes, when the computer program codes are run by a computer, causing the computer to perform the method of any of the embodiments shown in FIGS. 3-8.

[0365] The embodiments of the present application also provide a chip, which includes at least one processor and an interface, the processor being configured to read and execute instructions stored in a memory, when the instructions are executed, causing the chip to perform the method of any of the embodiments shown in FIGS. 3-8.

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

[0367] In addition, the various embodiments of the present application are only described by taking all the steps included therein as an example, and should not be regarded as a specific limitation of the present application. For example, the order between the steps in the various embodiments can be simply changed according to the functions and inherent logic thereof; for another example, the steps in the various embodiments can be executed in whole or in part, as long as the same function as in the embodiments of the present application can be achieved.

[0368] In the present application, "sending" and "receiving" refer to the direction of signal transmission. For example, "sending information to a network device" can be understood as that the destination of the information is the network device, which can include direct transmission through the air interface, or indirect transmission through the air interface by other units or modules. "Receiving information from a network device" can be understood as that the source of the information is the network device, which can include direct reception from the network device through the air interface, or indirect reception from the network device through the air interface by other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.

[0369] In other words, sending and receiving can be between devices, for example, between a network device and a terminal; or can be within a device, for example, between components, modules, chips, software modules or hardware modules within a device through a bus, wire or interface.

[0370] In the embodiments of the present application, "when", "if", "whether" and "in the case of" all refer to the objective situation in which the device will make corresponding processing, and are not limited to time, and do not require the device to have a judgment action when implemented, nor does it mean that there are other limitations.

[0371] In the present application, the words "example", "exemplary", "for example", or "for instance" are used to indicate that the related concept is presented as an example, illustration or description. Any embodiment or design scheme described as "example", "exemplary", "for example" or "for instance" in the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the words "example", "exemplary", "for example" or "for instance" are intended to present the related concept in a specific manner.

[0372] Optionally, the names of messages and parameters between various network elements in the above embodiments are only an example, and other names can also be used in specific implementation, and the forms of the parameters are not limited to the forms listed above. For example, the parameter form can be indication, information element (IE), special interface or special message type, and the form of storing corresponding information by various network elements can be list or string, which is not limited in the present application.

[0373] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A communication method characterized by comprising: The method comprises: obtaining policy information, the policy information being used to indicate a correspondence relationship between at least one service information and a first access type, the first access type being an access type to which the at least one service information is applicable; determining the first access type based on the policy information, the first access type comprising at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type; initiating session establishment or session modification through the first access type.

2. The method of claim 1, wherein, The obtaining of the first correspondence relationship comprises: receiving the policy information from a policy control network element or an access management network element.

3. The method according to claim 1 or 2, characterized in that, The determining of the first access type based on the policy information comprises: determining first service information of a terminal, the first service information belonging to the at least one service information; determining the first access type to which the first service information is applicable based on the first service information and the policy information.

4. A communication method characterized by comprising: The method comprises: determining policy information, the policy information being used to indicate a correspondence relationship between at least one service information and a first access type, the first access type being an access type to which the at least one service information is applicable, the first access type comprising at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type; sending the policy information to a terminal.

5. The method of claim 4, wherein, The determining of the policy information comprises: obtaining subscription information of the terminal from a data management network element, and / or obtaining first indication information from an application function network element; determining the policy information based on the subscription information and / or the first indication information; wherein the subscription information of the terminal or the first indication information is used to indicate orbit information of a non-terrestrial network device accessible by the terminal and second service information, the second service information being associated with the orbit information, the second service information belonging to the at least one service information, and the orbit information comprising an orbit height parameter and / or an orbit type, the orbit type comprising a low orbit, a medium orbit, a high orbit, or a multi-orbit.

6. A communication method characterized by comprising: The method comprises: determining a first access type to which third service information is applicable, the first access type comprising at least one of a low-orbit access type, a medium-orbit access type, a high-orbit access type, or a multi-orbit access type; sending a first radio access technology / frequency selection priority (RFSP) index corresponding to the first access type, the first RFSP index being used to trigger an access network device to perform redirection.

7. The method of claim 6, wherein, The determining of the first access type to which the third service information is applicable comprises: obtaining a first correspondence relationship; determining the first access type based on the first correspondence relationship and the third service information; wherein the first correspondence relationship comprises a correspondence relationship between the first access type and at least one service information supported by the first access type, and the at least one service information comprises the third service information.

8. The method of claim 6, wherein, The determining of the first access type to which the third service information is applicable comprises: receiving the first access type from a session management network element.

9. The method of claim 8, wherein, The method further comprises: sending the third service information to the session management network element.

10. The method according to any one of claims 6-9, characterized in that, The sending of the first RFSP index corresponding to the first access type comprises: send the first RFSP index in a case that a first condition is met; wherein the first condition comprises that the first access type is different from a current access type of the terminal and / or a non-terrestrial network device to which the third service information is applicable is different from a non-terrestrial network device to which the terminal requests to access.

11. The method according to claim 7 or 10, characterized in that, The first association relationship comprises a correspondence relationship between the first access type, at least one service information supported by the first access type, and N non-terrestrial network devices, N being a positive integer, and the method further comprises: determining, based on the first association relationship and the third service information, the non-terrestrial network device to which the third service information is applicable.

12. The method of claim 8 or 9, wherein, The method further comprises: receiving, from a session management network element, the non-terrestrial network device to which the third service information is applicable.

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

14. The method of claim 13, wherein, The method further comprises: sending, to the data management network element, second indication information, wherein the second indication information is used to obtain the first RFSP index, and the second indication information comprises the first access type.

15. The method of claim 13, wherein, The second association relationship comprises a correspondence relationship between the first access type, the at least one RFSP index, and M non-terrestrial network devices, the M non-terrestrial network devices comprising the non-terrestrial network device to which the third service information is applicable, M being a positive integer, and the determining the first RFSP index based on the second association relationship and the first access type comprises: determining the first RFSP index based on the second association relationship, the first access type, and the non-terrestrial network device to which the third service information is applicable.

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

17. The method of any of claims 6-16, wherein the third service information comprises a network slice requested by the terminal and / or a data network name (DNN); or the third service information comprises a network slice allocated to the terminal and / or a DNN.

18. A communications device, characterized by The apparatus comprises means or modules for implementing the method of any of claims 1-17.

19. A communications device, characterized by The communication apparatus comprises at least one processor, wherein the at least one processor is configured to perform the method of any of claims 1-17.

20. A computer program product, characterised in that, The computer program product comprises computer program code, which, when executed by a computer, causes the computer to perform the method of any of claims 1-17.

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

22. A communication system, characterized by The apparatus comprises a terminal and a policy control network element, or a terminal and an access management network element. The apparatus comprises a terminal and a policy control network element, or a terminal and an access management network element. The terminal is configured to perform the method of any one of claims 1-3; The policy control network element or the access management network element is configured to perform the method of any one of claims 4-5.

23. A communication system, characterized by comprising an access management network element and an access network device in communication with the access management network element, or comprising a session management network element and an access network device in communication with the session management network element; The access management network element is configured to perform the method of any one of claims 6-17; The session management network element is configured to perform the method of any one of claims 6, 7, 10, 11, or 13-17.

Images