Communication method and apparatus

Abstract

Provided in the present application are a communication method and apparatus. The method comprises: a session management network element receiving first information, wherein the first information is used for indicating that a first session requires the support of a first capability; and when a first access network device serving the first session supports the first capability, the session management network element sending to the first access network device, on the basis of the first information, a first parameter associated with the first capability. Only when an access network device supports a corresponding capability, a parameter associated with the capability is sent to the access network device; and when the access network device does not support the corresponding capability, the parameter associated with the capability is not sent to the access network device, such that unnecessary signaling overheads can be prevented.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411643095.9, filed on November 15, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

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

[0004] Terminal devices transmit data with access network devices and core network elements by establishing sessions. In some scenarios, sessions have certain characteristics that require access network devices and core network elements to jointly support corresponding capabilities, such as supporting quality of service (QoS) handling based on protocol data unit (PDU) sets and supporting multicast broadcast sessions (MBS).

[0005] Core network elements and access network devices need to know the relevant parameters of these capabilities in order to perform the corresponding functions based on the parameters.

[0006] Therefore, it is necessary to consider how to enable access network devices to know the relevant parameters of their capabilities. Summary of the Invention

[0007] This application provides a communication method and apparatus for enabling access network devices to obtain relevant parameters of their capabilities.

[0008] Firstly, this application provides a communication method that can be executed by a session management network element, or by other devices including session management network element functions, or by a chip system (which can also be replaced by a chip) or other functional modules. The chip system or functional module is capable of implementing the functions of the session management network element, and is, for example, disposed within the session management network element. Taking the execution of this method by a session management network element as an example: the session management network element serves a first session, and a first access network device serves the first session; the session management network element receives first information from the first network element, the first information indicating that the first session requires support for a first capability; if the first access network device supports the first capability, the session management network element sends a first parameter to the first access network device based on the first information, the first parameter being associated with the first capability.

[0009] In this method, the session management network element determines that the first session requires the support of a first capability based on first information. If the first access network device serving the first session supports the first capability, the session management network element sends a first parameter associated with the first capability to the first access network device, thereby enabling the first access network device to obtain the relevant parameters of the first capability. Furthermore, the session management network element only sends the first parameter associated with the first capability to the first access network device if the first access network device supports the first capability; otherwise, it does not send the first parameter associated with the first capability to the first access network device. This avoids the signaling overhead caused by sending the first parameter associated with the first capability to the first access network device when the first access network device does not support the first capability.

[0010] In one possible implementation, the first capability includes one or more of the following: quality of service processing capability based on protocol data unit set, multicast / broadcast session capability, access network device positioning capability, access network device sensing capability, access network device timing capability, and access network device general computing capability.

[0011] In one possible implementation, during the establishment or modification of the first session, the session management network element receives first information from the first network element. Alternatively, the session management network element receives the first information, and this first information triggers the modification of the first session.

[0012] In one possible implementation, when the first access network device supports the first capability, the session management network element sends the first parameter to the first access network device based on the first information, including: when the session management network element stores the association between the identifier of the first access network device and the indication information of the first capability, the session management network element sends the first parameter to the first access network device based on the first information; or, when the session management network element stores the association between the identifier of the first group to which the first access network device belongs and the indication information of the first capability, the session management network element sends the first parameter to the first access network device based on the first information.

[0013] In this implementation, the session management network element stores whether the first access network device supports the first capability. This can reduce the signaling overhead of knowing whether the first access network device supports the first capability, and also reduce the latency of establishing a session, modifying a session, and switching access network devices.

[0014] In one possible implementation, when the first access network device supports the first capability, the session management network element sends a first parameter to the first access network device based on the first information, including: the session management network element sending a first message to a second network element, the first message being used to obtain the capability supported by the first access network device; the session management network element receiving a first response from the second network element, the first response being used to indicate the capability supported by the first access network device; and when the capability supported by the first access network device includes the first capability, the session management network element sends the first parameter to the first access network device based on the first information.

[0015] In this implementation, the session management network element learns the capabilities supported by the first access network device, which are not limited to the first capability. This makes it easier for the session management network element to query the second network element for the capabilities supported by the first access network device when the first access network device provides services for other sessions. This can reduce signaling overhead and also reduce the latency of establishing sessions, modifying sessions, and switching access network devices.

[0016] In one possible implementation, if the capabilities supported by the first access network device indicated in the first response do not include the first capability, a first indication is sent to the first network element, the first indication being used to indicate that the access network device serving the first session does not support the first capability or does not support the first capability.

[0017] In this implementation, sending a first instruction to the first network element makes it easy for the first network element to know that it cannot perform the corresponding capabilities for the first session.

[0018] In one possible implementation, when the first access network device supports the first capability, the session management network element sends a first parameter to the first access network device based on the first information, including: the session management network element sending a second message to a second network element, the second message being used to obtain the capabilities supported by access network devices located in a first area; the session management network element receiving a second response from the second network element, the second response being used to indicate the capabilities supported by access network devices located in the first area, the first access network device being located in the first area; if the capabilities supported by the first access network device indicated by the second response include the first capability, the session management network element sends the first parameter to the first access network device based on the first information. For example, the first area includes: the service area of ​​the session management network element.

[0019] In this implementation, the session management network element learns the capabilities supported by the access network devices located in the first area, which are not limited to the first access network device or the first capability. This makes it easier for the session management network element to query the second network element for the capabilities supported by the access network devices located in the first area when the access network devices in the first area provide services for other sessions. This can reduce signaling overhead and also reduce the latency of establishing sessions, modifying sessions, and switching access network devices.

[0020] In one possible implementation, if the capabilities supported by the first access network device indicated in the second response do not include the first capability, a second indication is sent to the first network element, the second indication indicating that the access network device serving the first session does not support the first capability or does not support the first capability.

[0021] In this implementation, sending a second instruction to the first network element makes it easier for the first network element to know that it cannot perform the corresponding capabilities for the first session.

[0022] In one possible implementation, when the first access network device supports the first capability, sending the first parameter to the first access network device based on the first information includes: the session management network element sending a third message to a second network element, the third message being used to obtain the capabilities supported by access network devices belonging to a first group, wherein the first access network device belongs to the first group; the session management network element receiving a third response from the second network element, the third response being used to indicate the capabilities supported by access network devices belonging to the first group; and when the capabilities supported by access network devices belonging to the first group indicated by the third response include the first capability, the session management network element sending the first parameter to the first access network device based on the first information.

[0023] In this implementation, the session management network element learns the capabilities supported by the access network devices belonging to the first group, which are not limited to the first access network device or the first capability. This makes it easier for the session management network element to query the second network element for the capabilities supported by the access network devices belonging to the first group when the access network devices belonging to the first group provide services for other sessions. This can reduce signaling overhead and also reduce the latency of establishing sessions, modifying sessions, and switching access network devices.

[0024] In one possible implementation, after receiving the first information from the first network element, the session management network element stores the association between the identifier of the first session and the indication information of the first capability.

[0025] In this implementation, after receiving the first information, the session management network element can save the association between the identifier of the first session and the indication information of the first capability, regardless of whether the first access network device supports the first capability. Thus, when an access network device handover occurs, the session management network element can determine, based on the saved association, that the first session requires support for the first capability. The session management network element can then determine whether the new access network device supports the first capability. If the new access network device supports the first capability, the session management network element sends the parameters associated with the first session to the new access network device. In the current technology, the session management network element only saves the association between the identifier of the first session and the indication information of the first capability after receiving indication information from the first access network device indicating that the first access network device supports the first capability. If the first access network device does not support the first capability, the association between the identifier of the first session and the indication information of the first capability is not saved. If this association is not saved, after the access network device is switched over, even if the switched access network device supports the first capability, the session management network element will need to wait to receive a second request from the first network element before determining whether the switched access network device supports the first capability; if no second request is received from the first network element, the session management network element will not determine whether the switched access network device supports the first capability. It can be seen that, compared with existing technologies, this implementation allows the first session to enable the first capability earlier.

[0026] In one possible implementation, the session management network element receives a fourth message from the second access network device, the fourth message being used to request the switching of the access network device serving the terminal device to the second access network device, the fourth message including the identifier of the first session and the identifier of the terminal device, the first session being the session of the terminal device; if the second access network device supports the first capability, the session management network element sends the first parameter to the second access network device based on the first information.

[0027] In one possible implementation, the session management network element triggers a determination of whether the second access network device supports the first capability based on the identifier of the first session in the fourth message and the first information.

[0028] In one possible implementation, if the first access network device supports the first capability, the session management network element sends the second parameter to the user plane network element; or, after sending the first parameter to the first access network device, the session management network element sends the second parameter to the user plane network element. The second parameter is associated with the first capability. The second parameter is determined based on relevant parameters of the first capability contained in the first information. The second parameter and the relevant parameters of the first capability contained in the first information may be partially the same, partially different, or completely identical.

[0029] In the current technology, after receiving the indication information from the first access network device that supports the first capability, the session management network element sends the second parameter to the user plane network element. In the embodiments of this application, the session management network element can send the second parameter to the user plane network element without waiting for the response from the first access network device, which can enable the first capability of the first session to be enabled earlier.

[0030] Secondly, this application provides a communication method that can be executed by a second network element, or by other devices including the functions of the second network element, or by a chip system (which can also be replaced by a chip) or other functional module. This chip system or functional module can implement the functions of the second network element, and is, for example, located in an access management network element. Taking the execution of this method by a second network element as an example: the second network element receives a fifth message from a first access network device. The fifth message requests the first access network device to register with the second network element. The fifth message includes indication information indicating the capabilities supported by the first access network device. Based on the request from the session management network element, the second network element sends a response to the session management network element, the response indicating the capabilities supported by the first access network device.

[0031] In this method, when the access network device registers with the second network element, it sends an indication of the capabilities supported by the access network device to the second network element. The session management network element can obtain the capabilities supported by the access network device from the second network element, eliminating the need for the access network device to repeatedly report the capabilities supported by the access network device to the session management network element in each session, thus avoiding signaling waste.

[0032] In one possible implementation, the capabilities supported by the first access network device include one or more of the following: quality of service processing capability based on protocol data unit set, multicast and broadcast session capability, access network device positioning capability, access network device sensing capability, access network device timing capability, and access network device general computing capability.

[0033] In one possible implementation, sending a response to the session management network element based on the request from the session management network element includes: the second network element receiving a first message from the session management network element, the first message being used to obtain the capabilities supported by the first access network device; and the second network element sending a first response to the session management network element based on the first message, the first response being used to indicate the capabilities supported by the first access network device.

[0034] In one possible implementation, sending a response to the session management network element based on the request from the session management network element includes: a second network element receiving a second message from the session management network element, the second message being used to obtain the capabilities supported by an access network device located in the first area; and the second network element sending a second response to the session management network element based on the second message, the second response being used to indicate the capabilities supported by an access network device located in the first area, the first access network device being located in the first area.

[0035] In one possible implementation, the first region includes the service area of ​​the session management network element.

[0036] In one possible implementation, the request based on the session management network element, sending a response to the session management network element, includes:

[0037] Receive a third message from the session management network element, the third message being used to obtain the capabilities supported by the access network devices belonging to the first group, the first access network devices belonging to the first group;

[0038] Based on the third message, a third response is sent to the session management network element, the third response being used to indicate the capabilities supported by the access network devices belonging to the first group.

[0039] The technical effects of the various possible implementations in the second aspect can be referenced from the technical effects of the various possible implementations in the first aspect, and will not be elaborated further.

[0040] Thirdly, this application provides a communication method that can be executed by an access network device, or by other devices including the functions of an access network device, or by a chip system (which can also be replaced by a chip) or other functional module. This chip system or functional module can implement the functions of the access network device, and is, for example, located in an access management network element. Taking the execution of this method by a first access network device as an example: the first access network device sends a fifth message to the second network element. The fifth message is used for the first access network device to register with the second network element. The fifth message includes indication information, which indicates the capabilities supported by the first access network device.

[0041] In this method, when the access network device registers with the second network element, it sends an indication of the capabilities supported by the access network device to the second network element. The session management network element can obtain the capabilities supported by the access network device from the second network element, eliminating the need for the access network device to repeatedly report the capabilities supported by the access network device to the session management network element in each session, thus avoiding signaling waste.

[0042] In one possible implementation, the fifth message includes: an identifier of the first access network device and indication information for indicating the capabilities supported by the first access network device.

[0043] In one possible implementation, the capabilities supported by the first access network device include one or more of the following: quality of service processing capability based on protocol data unit set, multicast and broadcast session capability, access network device positioning capability, access network device sensing capability, access network device timing capability, and access network device general computing capability.

[0044] Fourthly, this application provides a communication method that can be executed by a Network Open Function (NEF) element, or by other devices including network storage functionality, or by a chip system (which can also be replaced by a chip) or other functional modules. The chip system or functional module can implement the functions of an access network device, and is, for example, located within a NEF element. Taking the execution of this method by a NEF element as an example: the NEF receives a sixth message from an Application Element (AF), the sixth message requesting the activation of a first feature for a first session, the first feature requiring support from a first capability; if the first access network device does not support the first capability, the NEF sends an indication message to the AF, the indication message indicating that the first feature should not be activated for the first session, and the first access network device serves the first session.

[0045] In this method, if the first access network device does not support the first capability, the AF request is rejected, which can omit the signaling interaction between PCF, SMF, and RAN in the prior art and avoid signaling waste.

[0046] In one possible implementation, if the first access network device supports the first capability, the NEF sends a first message to the SMF, the first message indicating that the first session requires support for the first capability.

[0047] In one possible implementation, the sixth message includes the identifier of the terminal device, and the first session is the session of the terminal device; NEF obtains the identifier of the first access network device based on the identifier of the first terminal device; and determines whether the first access network device supports or does not support the first capability based on the identifier of the first access network device.

[0048] In one possible implementation, when the first access network device does not support the first capability, the NEF sending indication information to the AF includes: the NEF sending a message to a second network element, the message being used to obtain the capabilities supported by the first access network device; the NEF receiving a response from the second network element, the response being used to indicate the capabilities supported by the first access network device; and when the capabilities supported by the first access network device do not include the first capability, the NEF sending indication information to the AF.

[0049] In this implementation, the NEF learns the capabilities supported by the first access network device, which are not limited to the first capability. This makes it easier for the NEF to query the second network element for the capabilities supported by the first access network device when the first access network device serves other sessions. This can reduce signaling overhead and reduce the latency of modifying sessions.

[0050] Fifthly, a communication device is provided, which can be the session management network element described in the first aspect above. The communication device possesses the functions of the session management network element. The communication device is, for example, a functional module within the session management network element, such as a baseband device or a chip system. Alternatively, the communication device can be the second network element described in the second aspect above. The communication device possesses the functions of the second network element. The communication device is, for example, a functional module within the second network element, such as a baseband device or a chip system. Alternatively, the communication device can be the first access network device described in the third aspect above. The communication device possesses the functions of the first access network device. The communication device is, for example, a functional module within the first access network device, such as a baseband device or a chip system. Alternatively, the communication device can be the network development function network element described in the fourth aspect above. The communication device possesses the functions of the network open function network element. The communication device is, for example, a functional module within the network open function network element, such as a baseband device or a chip system.

[0051] In one optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of transmitting and receiving functions. When the transceiver unit performs the transmitting function, it can be called a transmitting unit (sometimes also called a transmitting module), and when the transceiver unit performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The transmitting unit and the receiving unit can be the same functional module, which is called the transceiver unit and can perform both transmitting and receiving functions; or, the transmitting unit and the receiving unit can be different functional modules, and the transceiver unit is a collective term for these functional modules.

[0052] In one possible implementation, the communication device further includes a storage unit (sometimes also called a storage module), and the processing unit is configured to couple with the storage unit and execute programs or instructions in the storage unit to enable the communication device to perform the functions of the session management network element described in the first aspect, or the functions of the second network element described in the second aspect, or the functions of the first access network device described in the third aspect, or the functions of the network open function network element described in the fourth aspect.

[0053] Sixthly, a communication device is provided, including an interface circuit and a processor, and optionally, a memory. The memory stores a computer program. The processor is coupled to the memory and the interface circuit. When the processor reads the computer program or instructions, it causes the communication device to execute the method performed by the session management network element in the first aspect, or the method performed by the second network element in the second aspect, or the method performed by the first access network device in the third aspect, or the method performed by the network open function network element in the fourth aspect. For example, the interface circuit is used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. The processor, through logic circuits or executable code instructions, implements the method performed by the session management network element in the first aspect, or the method performed by the second network element in the second aspect, or the method performed by the first access network device in the third aspect, or the method performed by the network open function network element in the fourth aspect.

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

[0055] In a seventh aspect, a communication device is provided, including a processor, and optionally, a memory; the processor and the memory are coupled; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, it is used to implement the function of the session management network element in the first aspect, or to implement the function of the second network element in the second aspect, or to implement the function of the first access network device in the third aspect, or to implement the function of the network open function network element in the fourth aspect.

[0056] In one possible implementation, the apparatus may further include a transceiver for transmitting signals processed by the processor or receiving signals input to the processor. The transceiver may perform transmission or reception actions performed by the session management network element in the first aspect, the second network element in the second aspect, the first access network device in the third aspect, or the network open function network element in the fourth aspect.

[0057] In one possible implementation, the processing unit in the fifth aspect can be implemented by the processor, the storage unit in the fifth aspect can be implemented by the memory, and the transceiver unit in the fifth aspect can be implemented by the transceiver.

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

[0059] Eighthly, a communication system is provided, comprising one or more of the session management network element of the first aspect, the second network element of the second aspect, and the first access network device of the third aspect. For example, the session management network element, the second network element, or the first access network device may be implemented by the communication apparatus described in the sixth or seventh aspect.

[0060] Ninthly, a communication system is provided, comprising one or more of the following: the NEF as described in the fourth aspect, a first access network device interacting with the NEF, an NRF, and an SMF. For example, the NEF can be implemented using the communication apparatus described in the sixth or seventh aspect.

[0061] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program or instructions that, when executed, cause the methods of the foregoing aspects to be implemented.

[0062] In the eleventh aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the methods in the foregoing aspects to be implemented. Attached Figure Description

[0063] Figure 1a is a schematic diagram of the architecture of a 5G communication system provided in an embodiment of this application;

[0064] Figure 1b is a schematic diagram of the architecture of another 5G communication system provided in an embodiment of this application;

[0065] Figure 1c is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0066] Figure 2 is a flowchart of a communication method in the prior art;

[0067] Figure 3 is a flowchart of a communication method in the prior art;

[0068] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0069] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0070] Figure 6 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0071] Figure 7 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0072] Figure 8 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0073] Figure 9 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0074] Figure 10 is a structural diagram of a communication device provided in this application;

[0075] Figure 11 is a structural diagram of a communication device provided in this application. Detailed Implementation

[0076] The technical solution of this application can be applied to various wireless communication systems, including but not limited to fourth-generation (4G) mobile communication technology systems (also known as long term evolution (LTE) systems), fifth-generation (5G) mobile communication technology systems (also known as new radio (NR) systems), or future mobile communication systems, etc., without any specific limitations.

[0077] Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) scenarios, such as NR-D2D scenarios, or to vehicle-to-everything (V2X) communication scenarios, such as NR-V2X scenarios. For example, they can be used in fields such as intelligent driving, assisted driving, or intelligent connected vehicles. As another example, the technical solutions provided in this application can also be applied to factory manufacturing scenarios.

[0078] Furthermore, the technical solutions provided in this application can be applied to scenarios including but not limited to: terrestrial cellular communication, non-terrestrial network (NTN), satellite communication, high altitude platform station (HAPS) communication, integrated access and backhaul (IAB) communication, and reconfigurable intelligent surface (RIS) communication.

[0079] For example, Figure 1a is a schematic diagram of a 5G communication system architecture to which this application can be applied. Specifically, Figure 1a is a schematic diagram of a 5G network architecture based on a service-oriented architecture. For example, Figure 1b is a schematic diagram of another 5G communication system architecture to which this application can be applied. Specifically, Figure 1b is a schematic diagram of a point-to-point 5G architecture. The main difference between Figure 1a and Figure 1b is that the interfaces between the network elements in Figure 1a are service-oriented interfaces, while the interfaces between the network elements in Figure 1b are point-to-point interfaces.

[0080] The 5G network architecture shown in Figures 1a and 1b may include a terminal device component, an access network component, and a core network component. Optionally, it may also include a data network (DN) and application function (AF) network element components. Terminals access the core network through the access network, and the core network communicates with the DN or AF. The functions of some of these network elements are briefly described below.

[0081] A terminal device, also known as user equipment (UE), is a device with wireless transceiver capabilities. It can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water (such as on ships); and in the air (such as on airplanes, balloons, and satellites). Terminal devices can include mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, and wireless terminals in smart homes, among others.

[0082] The (R)AN equipment in this application is a device that provides wireless communication functions for terminal devices. The (R)AN equipment is also referred to as access network equipment. The RAN equipment in this application includes, but is not limited to: next-generation base stations (g node B, gNB), evolved node B (eNB), radio network controllers (RNC), node Bs (NB), base station controllers (BSC), base transceiver stations (BTS), home base stations (e.g., home evolved node B, or home node B, HNB), baseband units (BBU), transmitting and receiving points (TRP), transmitting points (TP), mobile switching centers, etc. In systems employing different wireless access technologies, the names of devices with base station functions may vary. For example, in 5th generation (5G) systems, they are called RAN or gNB (5G NodeB); in LTE systems, they are called evolved NodeB (eNB or eNodeB); and in 3rd generation (3G) systems, they are called Node B, etc.

[0083] A Data Network (DN) can deploy various services, providing data and / or voice services to terminal devices. For example, a DN might be the private network of a smart factory. Sensors installed in the workshop can act as terminal devices. The DN deploys both sensors and a control server, with the control server providing services to the sensors. Sensors can communicate with the control server, receive instructions, and transmit collected sensor data accordingly. Another example is a DN serving as an internal office network for a company. Employees' mobile phones or computers can act as terminal devices, accessing information and data resources within the company's internal network.

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

[0085] The core network portion may include one or more of the following network elements:

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

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

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

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

[0090] Data storage network elements are responsible for storing structured data information, including subscription information, policy information, and network data or service data with standard format definitions. In 5G communication systems, data storage network elements can be unified data repositories (UDRs). In future communication systems, network open function network elements can still be UDR network elements, or they can have other names; this application does not limit this.

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

[0092] The network storage element can provide network element discovery functionality, offering network element information corresponding to the network element type based on requests from other network elements. The network storage element also provides network element management services, such as network element registration, updating, deregistration, and network element status subscription and push. In 5G communication systems, this network storage element can be a network repository function (NRF) element. In future communication systems, the network storage element can still be an NRF element, or it can have other names; this application does not limit its scope.

[0093] Network exposure function (NEF) network elements can be used to securely expose services and capabilities provided by 3GPP network function equipment to the outside world. In 5G communication systems, NEF network elements can be NEF network elements. In future communication systems, NEF network elements can still be NEF network elements, or they can have other names; this application does not limit this.

[0094] The network slice selection function (NSSF) network element can be used to select the appropriate network slice for the terminal's services. In 5G communication systems, the network slice selection network element can be an NSSF network element. In future communication systems, the network open function network element can still be an NSSF network element, or it can have other names; this application does not limit this.

[0095] Network data analytics (NWDAF) network elements can collect, analyze, and predict data from various network functions (NFs), such as policy control, session management, user plane, access management, and application function elements (through network capability open function elements). In 5G communication systems, NWDAF network elements can be network data analytics functions (NWDAF). In future communication systems, NWDAF network elements may still be NWDAF network elements, or they may have other names; this application does not limit this.

[0096] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). One possible implementation is that the aforementioned network element or function can be implemented by a single device, multiple devices working together, or a functional module within a single device; this application does not specifically limit this.

[0097] Figure 1c is a schematic diagram of a communication system architecture applicable to an embodiment of this application. The RAN can be directly connected to each network element / network function in the core network without indirect connection through the AMF. Messages transmitted between the RAN and each network element can be called N2 interface messages, and messages transmitted between the UE and each network element can be called non-access stratum (NAS) messages. NAS messages are usually carried in N2 interface messages and transmitted to each network element. NAS messages related to services served by any NF transmitted between the UE and the RAN through any NF can be simply referred to as NF-NAS. For example, NAS messages for access management transmitted between the UE and the AMF through the RAN are called AM-NAS, NAS messages for session management transmitted between the UE and the SMF through the RAN are called SM-NAS, and NAS messages for network registration transmitted between the UE and the NEF through the RAN are called NF-NAS.

[0098] Terminal devices transmit data with access network devices and core network elements by establishing sessions. In some scenarios, sessions possess certain characteristics that require both access network devices and core network elements to support corresponding capabilities. These capabilities include, for example, support for Quality of Service (QoS) handling based on Protocol Data Unit (PDU) sets and support for multicast broadcast sessions (MBS). Core network elements and access network devices need to know the relevant parameters of these capabilities in order to execute the corresponding functions based on the appropriate configuration parameters.

[0099] Figure 2 shows a flowchart of a communication method, illustrating the process by which the SMF informs the RAN of the relevant parameters for PDU Set based QoS Handling capability, and the process by which the RAN informs the SMF whether it supports PDU Set based QoS Handling capability.

[0100] Step 201: The UE sends a PDU Session Establishment Request to the AMF through the RAN. This request includes information such as the identifier of the PDU session.

[0101] Step 202: Select SMF from AMF.

[0102] Step 203: The AMF sends a PDU session - Create Session Management (SM) Context Request (Nsmf_PDUSession_CreateSMContext Request) to the SMF.

[0103] Step 204: SMF obtains the Session Management (SM) policy.

[0104] Optionally, the SMF may perform one or more of the following: subscription retrieval / subscription for updates, PDU session authentication / authorization, selection of PCF, SM policy association establishment or SMF-initiated SM policy association modification, selection of UPF, etc.

[0105] Step 205: The SMF sends N2 SM information to the RAN through the AMF, including PDU session identifier, Quality of Service Profile and other information.

[0106] The QoS Profile describes the parameters of the QoS Flow in this session. For QoS Flows that require PDU Set-based QoS Handling support, the SMF includes relevant parameters for PDU Set-based QoS Handling capabilities in the QoS Profile.

[0107] Step 206: When the RAN supports PDU Set based QoS Handling capability, it reports indication information to the SMF through the AMF. This indication information is used to indicate that the RAN supports the corresponding capability. For example, the indication information is "PDU Set based QoS Handling Support Indication".

[0108] If the SMF contains this indication information in the message, it determines that the RAN supports PDU Set based QoS Handling capability; if the message does not contain this indication information, it determines that the RAN does not support PDU Set based QoS Handling capability.

[0109] When the RAN supports PDU Set based QoS Handling capability, the SMF configures the UPF to perform PDU Set information marking operation on the corresponding QoS Flow.

[0110] As can be seen from the process in Figure 2 above, the SMF sends the relevant parameters of the PDU Set based QoS Handling capability to the RAN. Then, the RAN determines whether it supports the PDU Set based QoS Handling capability and reports it to the SMF.

[0111] Figure 3 shows a flowchart of a communication method, illustrating how the SMF informs the RAN of the relevant parameters of MBS capability, and how the RAN informs the SMF whether it supports MBS capability.

[0112] Step 301: SMF sends an MBS session establishment request message to AMF.

[0113] Step 302: The AMF sends an MBS session establishment request message to the RAN.

[0114] The message includes the MBS session identifier and MBS-related parameters, such as MBS QoS Flow Identifier, MBS QoS Flow Level QoS Parameters, etc.

[0115] Step 303: The RAN sends a response message to the SMF through the AMF.

[0116] The RAN determines whether to support MBS sessions based on MSB-related parameters. When the RAN supports establishing an MBS session, the response message includes RAN-side tunnel information and an MBS Support Indicator.

[0117] SMF determines RAN support for MBS session capabilities based on the MBS Support Indicator.

[0118] As can be seen from the process in Figure 3 above, the SMF sends the relevant parameters of the MBS capability to the RAN. Then, the RAN determines whether it supports the MSB capability and reports it to the SMF.

[0119] In Figures 2 and 3 above, the session management network element sends capability-related parameters to the access network device. After receiving these parameters, the access network device determines whether it supports the corresponding capability and sends an indication message to the session management network element to indicate whether it supports the capability. The following problem exists:

[0120] On the one hand, the session management network element sends the relevant parameters of a capability to the access network device without considering whether the access network device supports it. If the access network device does not support the corresponding capability, the relevant parameters sent by the session management network element are invalid, resulting in unnecessary signaling overhead. On the other hand, an access network device serves multiple terminal devices, and multiple terminal devices can establish sessions through this access network device. In multiple sessions, as soon as the access network device receives the relevant parameters of the capability, it informs the session management network element whether it supports the corresponding capability. This causes the access network device to repeatedly report the capabilities it supports, resulting in unnecessary signaling overhead.

[0121] Based on this, embodiments of this application provide a communication method in which a session management network element receives first information, the first information indicating that a first session requires support for a first capability; if a first access network device serving the first session supports the first capability, the session management network element sends a first parameter associated with the first capability to the first access network device according to the first information. The parameter associated with the capability is only sent to the access network device if the access network device supports the corresponding capability; if the access network device does not support the corresponding capability, the parameter associated with the capability is not sent to the access network device, thus avoiding unnecessary signaling overhead.

[0122] In addition, when the access network device registers with the second network element, it sends the capability information supported by the access network device to the second network element. The session management network element can obtain the capabilities supported by the access network device from the second network element. The access network device does not need to report the capabilities supported by the access network device to the session management network element in each session, which can avoid the signaling overhead caused by the access network device repeatedly reporting its own supported capabilities.

[0123] The relevant terms used in the embodiments of this application will be explained below. It should be noted that these explanations are for the purpose of making the embodiments of this application easier to understand, and should not be regarded as a limitation on the scope of protection claimed by this application.

[0124] 1) The first network element can be PCF, AF, NEF, etc. The second network element can be NRF.

[0125] The session management network element can communicate directly with the first network element, or indirectly through forwarding from other network elements. Similarly, the session management network element can communicate directly with the second network element, or indirectly through forwarding from other network elements.

[0126] Furthermore, the interaction between access network devices and core network elements (such as the first and second network elements) can be achieved through AMF forwarding or direct interaction. For example, in the communication systems shown in Figures 1a and 1b, the access network devices interact indirectly with the first and second network elements via AMF. Conversely, in the communication system shown in Figure 1c, the access network devices interact directly with the first and second network elements.

[0127] 2) The first session can be a PDU session or an MBS session. The terminal device initiates the first session, or the terminal device initiates the establishment process of the first session, or the first session is the terminal device's session, or the terminal device requests to establish the first session.

[0128] The first access network device serves the first session, and the session management network element serves the first session.

[0129] 3) In the embodiments of this application, "the capabilities supported by the access network device" refers to "the user plane capabilities supported by the access network device", including but not limited to: quality of service processing capabilities based on protocol data unit sets, multicast and broadcast session capabilities, access network device positioning capabilities, access network device sensing capabilities, access network device timing capabilities, and access network device general computing capabilities.

[0130] "Ability" can also be called "characteristic", "ability corresponding to characteristic", or "ability required by characteristic"; for example, "first ability" can be called "first characteristic", "ability corresponding to first characteristic", or "ability required by first characteristic".

[0131] The first information is used to indicate that the first session requires the support of the first capability. The phrase "the first session requires the support of the first capability" can also be understood as the first session having a first characteristic, and the first characteristic requiring the support of the first capability.

[0132] To better illustrate the embodiments of this application, the methods provided by the embodiments of this application are described below with reference to the accompanying drawings. Unless otherwise specified below, the steps indicated by dashed lines in the accompanying drawings corresponding to the various embodiments of this application are optional steps. It should be noted that the technical details of the multiple embodiments provided in this application can be referenced to each other, each embodiment described below can exist independently, and multiple embodiments can also be combined with each other as an embodiment in the absence of logical errors.

[0133] Figure 4 is a flowchart illustrating a communication method provided in an embodiment of this application. Figure 4 uses a first network element, a session management network element, and a first access network device as examples of the execution entities in this interactive illustration to illustrate the method. However, this embodiment does not limit the execution entities in this interactive illustration. For example, the method executed by the first network element in Figure 4 can also be executed by a module applied to the first network element (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that implements all or part of the functions of the first network element. Similarly, the method executed by the session management network element in Figure 4 can also be executed by a module applied to the session management network element (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that implements all or part of the functions of the session management network element. Likewise, the method executed by the first access network device in Figure 4 can also be executed by a module applied to the first access network device (e.g., a chip, chip system, or processor), or by a logical node, logical module, or software that implements all or part of the functions of the first access network device.

[0134] Figure 4 includes the following steps:

[0135] Step 401: The first network element sends the first information to the session management network element, and the session management network element receives the first information accordingly.

[0136] The first information is used to indicate that the first session requires the support of the first capability.

[0137] The first capability includes one or more of the following: quality of service processing capability based on protocol data unit set, multicast and broadcast session capability, access network device positioning capability, access network device sensing capability, access network device timing capability, and access network device general computing capability.

[0138] Optionally, the first information includes: the identifier of the first session and relevant parameters of the first capability. Taking PDU set based QoS handling as an example, the relevant parameters include, but are not limited to, at least one of the following: PDU set delay budget (PSDB), PDU set error rate (PSER), and PDU set integrated handling information (PSIHI). Further optionally, the first information also includes the identifier (temporary identifier) ​​and / or IP address of the terminal device, and the first session is a session of the terminal device.

[0139] Optionally, during the establishment or modification of the first session, step 401 is executed. If the first network element is a PCF, the first information can also be called the first policy, or SM policy, or session policy, or session update policy, or SM update policy. Alternatively, after the first session is established, the first network element sends the first information to the core network element (which can be the session management network element or other network elements), triggering the session modification process.

[0140] Step 402: If the first access network device supports the first capability, the session management network element sends the first parameter to the first access network device according to the first information, and the first access network device receives the first parameter accordingly.

[0141] The first parameter is associated with the first capability. The first parameter is determined based on the relevant parameters of the first capability contained in the first information. The first parameter and the relevant parameters of the first capability contained in the first information may be partially the same, partially different, or completely identical.

[0142] After receiving the first parameter, the first access network device can perform corresponding functions for the first session based on the first parameter.

[0143] After receiving the first parameter, the first access network device can save signaling by not sending an indication message to the session management network element to indicate that the first access network device supports the first capability.

[0144] Optionally, if the first access network device supports the first capability, the session management network element sends the second parameter to the user plane network element; or, after sending the first parameter to the first access network device, the session management network element sends the second parameter to the user plane network element. The second parameter is associated with the first capability. The second parameter is determined based on the relevant parameters of the first capability contained in the first information. The second parameter and the relevant parameters of the first capability contained in the first information may be partially the same, partially different, or completely identical.

[0145] In the current technology, after receiving the indication information from the first access network device that supports the first capability, the session management network element sends the second parameter to the user plane network element. In the embodiments of this application, the session management network element can send the second parameter to the user plane network element without waiting for the response from the first access network device, which can enable the first capability of the first session to be enabled earlier.

[0146] As described in step 401, the first information is used to indicate that the first session requires the support of a first capability. For the first session, this can mean that only the access network device serving the first session needs to support the first capability, or it can mean that both the access network device serving the first session and core network elements (including but not limited to session management network elements) need to support the first capability. Based on this, optionally, one specific implementation of step 402 is as follows: if both the session management network element and the first access network device support the first capability, the session management network element sends a first parameter to the first access network device according to the first information.

[0147] In this method, the session management network element determines that the first session requires the support of the first capability based on the first information. If the first access network device serving the first session supports the first capability, the first access network element sends the first parameter associated with the first capability to the first access network device, thereby enabling the first access network device to know the relevant parameters of the first capability.

[0148] In addition, the session management network element sends the first parameter associated with the first capability to the first access network device only when the first access network device supports the first capability. If the first access network device does not support the first capability, the session management network element does not send the first parameter associated with the first capability to the first access network device. Compared with Figures 2 and 3, this avoids the signaling overhead caused by sending the first parameter associated with the first capability to the first access network device when the first access network device does not support the first capability.

[0149] Prior to step 402, optionally, the session management network element may determine whether the first access network device supports the first capability. The following describes several examples of how the session management network element determines whether the first access network device supports the first capability. It is understood that the numbering of the examples below (1, 2, 3, etc.) is for ease of description only and does not imply any limitation on the priority or importance of the examples.

[0150] Example 1: The session management network element determines whether there is stored indication information, which is used to indicate whether the first access network device supports or does not support the first capability.

[0151] For example, if the session management network element stores indication information that the first access network device supports the first capability, then it can be determined that the first access network device supports the first capability. Conversely, if the session management network element stores indication information that the first access network device does not support the first capability, then it can be determined that the first access network device does not support the first capability. If the session management network element does not store indication information regarding whether the first access network device supports or does not support the first capability, it can be understood that the session management network element has not yet learned whether the first access network device supports the first capability. In this case, the session management network element may query the second network element to inquire whether the first access network device supports the first capability.

[0152] One possible implementation is that the indication information indicating that the access network device supports the first capability is the association between the identifier of the first access network device and the indication information of the first capability. That is, if the session management network element stores the association between the identifier of the first access network device and the indication information of the first capability, it can be determined that the first access network device supports the first capability. If the association between the identifier of the first access network device and the indication information of the first capability is not stored, it can be determined that the first access network device does not support the first capability, or the second network element can be queried to determine whether the first access network device supports the first capability.

[0153] In one specific implementation, if the session management network element has queried the second network element about the capabilities supported by the first access network device, then the session management network element stores the profile information of the first access network device, which includes the capabilities supported by the first access network device. If the session management network element does not store the profile information of the first access network device, then it has not yet queried the second network element about the capabilities supported by the first access network device. If the session management network element stores the profile information of the first access network device, but the profile information does not contain information about the first access network device supporting the first capability, then it can be determined that the first access network device does not support the first capability.

[0154] One specific implementation of step 402 is as follows: when the association between the identifier of the first access network device and the indication information of the first capability is stored, the session management network element sends the first parameter to the first access network device according to the first information.

[0155] Another possible implementation is that the indication information indicating that the access network device supports the first capability is the association between the identifier of the first group to which the first access network device belongs and the indication information of the first capability. That is, if the session management network element stores the association between the identifier of the first group and the indication information of the first capability, it can be determined that the first access network device supports the first capability. If the association between the identifier of the first group and the indication information of the first capability is not stored, it can be determined that the first access network device does not support the first capability, or the second network element can be queried whether the first access network device supports the first capability, or the second network element can be queried whether the access network devices in the first group support the first capability. Access network devices within a group may simultaneously support the first capability, or simultaneously not support the first capability.

[0156] One specific implementation of step 402 is as follows: when the association between the identifier of the first group to which the first access network device belongs and the indication information of the first capability is stored, the session management network element sends the first parameter to the first access network device according to the first information.

[0157] The following are several examples of indications for any capability:

[0158] Example a) The indication information for any capability can be an indicator corresponding to a capability (or feature) in the prior art. For example, if the first capability is an MBS capability, the indication information for the first capability is an MBS Support indicator; for example, if the first capability is a PDU Set based QoS handling capability, the indication information for the first capability is a PDU Set based QoS handling support indication.

[0159] Example b) Any capability indication information includes the service name corresponding to the capability (or feature). For example, the service name corresponding to the quality of service processing capability (feature) based on PDU session sets is PDUsession_MBS service; for example, the service name corresponding to the MBS capability (feature) is PDUsession_PDUSet service.

[0160] Example c) The indication information for any capability includes a capability identifier or a feature identifier (Feature ID). For example, the identifier for a PDU Set based QoS handling capability (feature) is feature ID 1, and the identifier for an MBS capability (feature) is feature ID 2.

[0161] Example 2: The session management network element obtains the capabilities supported by the first access network device from the second network element, and determines whether the first capability is included in the obtained capabilities supported by the first access network; if it is included, it is determined that the first access network device supports the first capability; if it is not included, it is determined that the first access network device does not support the first capability.

[0162] The process by which the session management network element obtains the capabilities supported by the first access network device from the second network element can be referred to steps 502 and 503 below. Steps 502 and 503 can be presented as a separate embodiment, independent of Figure 4, or they can be integrated with Figure 4 as a unified embodiment. That is, the triggering reason for the session management network element to obtain the capabilities supported by the first access network device from the second network element can be the first information of the first session, or other reasons. After obtaining the capabilities supported by the first access network device, if the first access network device supports the first capability, the session management network element can send the first parameter associated with the first capability to the first access network device, or it can be used in other processes.

[0163] Figure 5 shows a flowchart of a communication method. The execution entities in Figure 5 (e.g., the first network element, the session management network element, the second network element, and the first access network device) can all be replaced by modules (e.g., chips, chip systems, or processors) in the execution entity, or logical nodes, logical modules, or software that implement all or part of the functions of the execution entity.

[0164] Figure 5 includes the following steps:

[0165] Optionally, in step 501: the first network element sends first information to the session management network element, and the session management network element receives the first information accordingly; the first information is used to indicate that the first session requires the support of a first capability.

[0166] The process is the same as step 401, and will not be described in detail here.

[0167] Step 502: The session management network element sends a first message to the second network element, the first message being used to obtain the capabilities supported by the first access network device (e.g., user plane capabilities supported by the first access network device); correspondingly, the second network element receives the first message.

[0168] For example, the first message includes an identifier for the first access network device; optionally, the first message also includes a type (i.e., access network device). For example, the first message is a Network Function Discovery Request (NF Discovery Request).

[0169] Optionally, the session management network element triggers the sending of a first message to the second network element based on the first information.

[0170] The session management network element can provide services for multiple sessions (including the first session) at the same time. The session management network element stores the identifier of the access network device associated with each session. The session management network element can determine the identifier of the first access network device serving the first session based on the identifier of the first session in the first information, and then carry the identifier of the first access network device in the first message sent to the second network element.

[0171] Optionally, before step 502, the session management network element may first determine whether it stores indication information indicating whether the first access network device supports or does not support the first capability. If not, step 502 is then executed. The session management network element may trigger the determination of whether it stores indication information indicating whether the first access network device supports or does not support the first capability based on the first information.

[0172] Optionally, the first message is a subscription message. If the capabilities supported by the first access network device change, the second network element can notify the session management network element of the changed capabilities supported by the first access network device based on this subscription.

[0173] Step 503: The second network element sends a first response to the session management network element, and the session management network element receives the first response from the second network element.

[0174] The first response is used to indicate the capabilities supported by the first access network device. For example, the first response includes an identifier of the first access network device and indication information for indicating the capabilities supported by the access network device. For ease of description, this indication information will be referred to as "RAN capability indication information" or "capability indication information". This name is only an example and should not be construed as limiting the name of the indication information.

[0175] The following are several examples of RAN capability indication information:

[0176] Example a) The RAN capability indication information is the indicator corresponding to the capability (or feature) in the prior art. For example, if the first access network device supports MBS capability, the RAN capability indication information includes the MBS Support indicator; for example, if the first access network device supports PDU Set based QoS handling capability, the RAN capability indication information includes the PDU Set based QoS handling support indication.

[0177] Example b) RAN capability indication information includes the service name corresponding to the capability (or feature). For example, the service name corresponding to the quality of service processing capability (feature) based on PDU session sets is PDUsession_MBS service; for example, the service name corresponding to the MBS capability (feature) is PDUsession_PDUSet service.

[0178] Example c) RAN capability indication information includes capability identifiers or feature identifiers (Feature IDs). For example, the identifier for a PDU Set based QoS handling capability (feature) is feature ID 1, and the identifier for an MBS capability (feature) is feature ID 2.

[0179] For example, the first response is a Network Function Discovery Response (NF Discovery Response). Optionally, the first response may include a RAN profile, which includes RAN capability indication information.

[0180] Optionally, if the first access network device does not support any corresponding capability, the first response is used to indicate that the capability supported by the first access network device is empty or a default value.

[0181] The second network element stores the association between the identifiers of each access network device and the indication information of the capabilities supported by the access network devices. After receiving the first message, the second network element can query the existing association based on the identifier of the first access network device in the first message, and thus find the indication information of the capabilities supported by the first access network device.

[0182] Optionally, in step 504: if the capabilities supported by the first access network device indicated in the first response include the first capability, the session management network element sends the first parameter to the first access network device based on the first information.

[0183] Optionally, step 505: The session management network element stores the association between the identifier of the first access network device and the indication information of the capabilities supported by the first access network device.

[0184] The session management network element stores indication information about the capabilities supported by the first access network device. This allows the session management network element to avoid having to query the second network element again which capabilities the first access network device supports when the first access network device provides services for other sessions. This reduces signaling overhead and also lowers the latency of session establishment / modification / switching processes.

[0185] Optionally, step 506: If the capabilities supported by the first access network device indicated in the first response do not include the first capability, the session management network element sends a first indication to the first network element. The first indication is used to indicate that the first information is not supported, or the first information is rejected, or the access network device serving the first session does not support the first capability, or the access network device serving the first session does not support the first information.

[0186] By sending a first instruction to the first network element, the first network element can be made aware that it cannot perform the first capability for the first session.

[0187] Example 3: The session management network element queries the second network element to see if the first access network device supports the first capability.

[0188] The process by which the session management network element queries the second network element whether the first access network device supports the first capability can be referred to steps 32 and 33 below. Steps 32 and 33 can be presented as a separate embodiment, independent of Figure 4, or they can be integrated with Figure 4 as a unified embodiment. That is, the triggering reason for the session management network element to query the second network element whether the first access network device supports the first capability can be the first information of the first session, or other reasons. After learning whether the first access network device supports the first capability, if the first access network device supports the first capability, the session management network element can send the first parameter associated with the first capability to the first access network device, or it can be used in other processes.

[0189] Optionally, in step 31: the first network element sends first information to the session management network element, and the session management network element receives the first information accordingly; the first information is used to indicate that the first session requires the support of a first capability.

[0190] The process is the same as step 401, and will not be described in detail here.

[0191] Step 32: The session management network element sends a message to the second network element, and the second network element receives the message accordingly; wherein, the message is used to query whether the first access network device supports the first capability.

[0192] The message includes the identifier of the first access network device and indication of its first capability; optionally, the message also includes the type (i.e., the access network device). For example, the message is a Network Function Discovery Request (NF Discovery Request).

[0193] Optionally, the session management network element triggers the sending of a message to the second network element based on the first information to query whether the first access network device supports the first capability.

[0194] The session management network element can provide services for multiple sessions (including the first session) at the same time. The session management network element stores the identifier of the access network device associated with each session. The session management network element can determine the identifier of the first access network device serving the first session based on the identifier of the first session in the first information, and then carry the identifier of the first access network device in the first message sent to the second network element.

[0195] Optionally, before step 32, the session management network element may first determine whether it stores indication information indicating whether the first access network device supports or does not support the first capability. If not, step 32 is then executed. The session management network element may trigger the determination of whether it stores indication information indicating whether the first access network device supports or does not support the first capability based on the first information.

[0196] Step 33: The second network element sends a response to the session management network element, and the session management network element receives the response from the second network element accordingly.

[0197] This response is used to indicate whether the first access network device supports the first capability or not. For example, the response includes an identifier of the first access network device and indication information indicating whether the first capability is supported or not.

[0198] For example, the indication information can be indicated by the value of at least one bit. For instance, when one bit is 0, it indicates that the first capability is not supported, and when one bit is 1, it indicates that the first capability is supported.

[0199] For example, when the first access network device supports the first capability, the response includes RAN capability indication information corresponding to the first capability; when the first access network device does not support the first capability, the response does not include RAN capability indication information corresponding to the first capability. The RAN capability indication information can be found in Example 2, and will not be elaborated upon here.

[0200] For example, this response is a network function discovery response.

[0201] The second network element stores the association between the identifiers of each access network device and the indication information of the capabilities supported by the access network devices. After receiving the message from step 32, the second network element can query the existing association based on the identifier of the first access network device in the message to find the capability information supported by the first access network device. Based on the indication information of the first capability carried in the message from step 32 and the queried indication information of the capabilities supported by the first access network device, the second network element can determine whether the first access network device supports the first capability and send a response to the session management network element to inform the session management network element whether the first access network device supports or does not support the first capability.

[0202] Optionally, in step 34: if the response in step 33 indicates that the first access network device supports the first capability, the session management network element sends the first parameter to the first access network device based on the first information.

[0203] Optionally, in step 35: if the response in step 33 indicates that the first access network device supports the first capability, the session management network element saves the indication information of the first capability supported by the first access network device.

[0204] For example, the session management network element stores the association between the identifier of the first access network device and the indication information of the first capability.

[0205] The session management network element stores indication information of the capabilities supported by the first access network device. This makes it easier for the session management network element to query the second network element again to see if the first access network device supports the first capability when the first access network device provides services for other sessions. This reduces signaling overhead and also lowers the latency of establishing, modifying, and switching access network devices.

[0206] Optionally, step 36: If the response indication in step 33 indicates that the first access network device does not support the first capability, the session management network element sends an indication to the first network element. This indication is used to indicate that the first information is not supported, or the first information is rejected, or the access network device serving the first session does not support the first capability, or the access network device serving the first session does not support the first information.

[0207] By sending this instruction to the first network element, the first network element can be informed that it is unable to perform the first capability for the first session.

[0208] Example 4: The session management network element obtains the capabilities supported by the access network device located in the first area from the second network element. The first access network device is located in the first area.

[0209] The process by which the session management network element obtains the capabilities supported by the access network devices located in the first area from the second network element can be referred to steps 42 and 43 below. Steps 42 and 43 can be presented as a separate embodiment, independent of Figure 4, or they can be integrated with Figure 4 as a unified embodiment. That is, the triggering reason for the session management network element to obtain the capabilities supported by the access network devices located in the first area from the second network element can be the first information of the first session, or other reasons. After learning of the capabilities supported by the first access network device, if the first access network device supports the first capability, the session management network element can send the first parameter associated with the first capability to the first access network device, or it can be used in other processes.

[0210] Optionally, in step 41: the first network element sends the first information to the session management network element, and the session management network element receives the first information accordingly.

[0211] The first information is used to indicate that the first session requires the support of the first capability.

[0212] The process is the same as step 401, and will not be described in detail here.

[0213] Step 42: The session management network element sends a second message to the second network element, the second message being used to obtain the capabilities supported by the access network equipment located in the first area; correspondingly, the second network element receives the second message.

[0214] For example, the first region includes the service area of ​​the session management network element. The second message includes information about the first region; for example, the second message includes the SMF Service Area. Optionally, the second message may also include RAN capability indication information corresponding to the features supported by the session management network element.

[0215] Optionally, the session management network element may trigger the sending of a second message to the second network element based on the first information.

[0216] Optionally, before step 42, the session management network element may first determine whether it stores indication information indicating whether the first access network device supports or does not support the first capability. If not, step 42 is then executed. The session management network element may trigger the determination of whether it stores indication information indicating whether the first access network device supports or does not support the first capability based on the first information.

[0217] Optionally, the second message is a subscription message. If the capabilities supported by the access network equipment located in the first area change, the second network element can notify the session management network element of the changed capabilities supported by the access network equipment based on this subscription. This eliminates the need for the session management network element to make another request, saving signaling overhead. It also allows the session management network element to be notified promptly after the change, enabling the session management network element to know the capabilities supported by the access network equipment in a timely manner.

[0218] Step 43: The second network element sends a second response to the session management network element, and the session management network element receives the second response from the second network element.

[0219] The second response is used to indicate the capabilities supported by each access network device located in the first area, including the capabilities supported by the first access network device.

[0220] For example, the second response includes the identifiers of each access network device located in the first area and indications of the capabilities supported by the access network devices (i.e., RAN capability indication information, which can be referred to in Example 2 and will not be repeated here).

[0221] The second network element stores the association between the identifier of the access network device and the indication information of the capabilities supported by the access network device, as well as the association between the identifier of the access network device and the area to which the access network device belongs. Upon receiving the second message, the second network element can determine the access network devices located within the first area based on the information of the first area carried in the second message and the stored information of the area to which the access network devices belong. Then, based on the identifiers of each access network device located within the first area, it can query the existing association between the identifiers of the access network devices and the indication information of the capabilities supported by the access network devices to find the indication information of the capabilities supported by the access network devices located within the first area. Subsequently, the second network element sends a second response to the session management network element to inform the session management network element of the capabilities supported by each access network device located within the first area.

[0222] If the second message includes RAN capability indication information corresponding to features supported by the session management network element, then the access network device indicated in the second response is: each access network device located in the first area that supports the capabilities indicated by the RAN capability indication information carried in the second message. For example, the second response includes: the identifiers of each access network device located in the first area that supports the capabilities indicated by the RAN capability indication information, and the RAN capability indication information corresponding to the capabilities supported by each access network device.

[0223] It should be noted that when a session management network element (SMI) supports multiple features, it can send multiple messages to the second network element to request these features. Each message contains RAN capability indication information corresponding to one feature. Alternatively, the SMI can send a single request message containing RAN capability indication information corresponding to multiple features supported by the SMI. For the latter, for example, if the SMI supports features 1, 2, and 3, and the corresponding RAN capability indication information is 1, 2, and 3, the second message sent by the SMI to the second network element includes: "RAN capability indication information 1 or 2 or 3," thereby allowing the second network element to return the identifiers of the access network devices supporting capabilities 1, 2, or 3, along with the RAN capability indication information corresponding to the capabilities supported by each access network device.

[0224] Optionally, in step 44: if the capabilities supported by the first access network device indicated by the second response include the first capability, the session management network element sends the first parameter to the first access network device based on the first information.

[0225] Optionally, step 45: The session management network element stores the association between the identifier of the first access network device and the indication information of the capabilities supported by the first access network device.

[0226] The session management network element stores indication information of the capabilities supported by the first access network device. It is not limited to the first capability. The session management network element can also store the capabilities supported by each access network device located in the first area. This makes it easier for the session management network element to query the second network element again which access network devices located in the first area or the first access network device support when they provide services for other sessions. This can reduce signaling overhead and reduce the latency of session establishment, session modification, and access network device handover processes.

[0227] Optionally, step 46: If the capabilities supported by the first access network device indicated in the second response do not include the first capability, the session management network element sends a second indication to the first network element. The second indication is used to indicate that the first information is not supported, or the first information is rejected, or the access network device serving the first session does not support the first capability, or the access network device serving the first session does not support the first information.

[0228] By sending a second instruction to the first network element, the first network element can be informed that it cannot perform the first capability on the first session.

[0229] Example 5: The session management network element obtains the capabilities supported by the access network devices belonging to the first group from the second network element. The first access network device belongs to the first group. It then determines whether the first capability is included in the obtained capabilities supported by the access network devices belonging to the first group. If it is included, the first access network device is determined to support the first capability; if it is not included, the first access network device is determined not to support the first capability.

[0230] The process by which the session management network element obtains the capabilities supported by the access network devices belonging to the first group from the second network element can be referred to steps 52 and 53 below. Steps 52 and 53 can be presented as a separate embodiment, independent of Figure 4, or they can be integrated with Figure 4 as a unified embodiment. That is, the triggering reason for the session management network element to obtain the capabilities supported by the access network devices belonging to the first group from the second network element can be the first information of the first session, or other reasons. After learning of the capabilities supported by the access network devices belonging to the first group, if the first access network device supports the first capability, the session management network element can send the first parameter associated with the first capability to the first access network device, or it can be used in other processes.

[0231] Optionally, in step 51: the first network element sends the first information to the session management network element, and the corresponding session management network element receives the first information.

[0232] The first information is used to indicate that the first session requires the support of the first capability.

[0233] The process is the same as step 401, and will not be described in detail here.

[0234] Step 52: The session management network element sends a third message to the second network element, and the second network element receives the third message accordingly; the third message is used to obtain the capabilities supported by the access network devices belonging to the first group.

[0235] For example, the third message includes the identifier of the first group.

[0236] Optionally, the session management network element may trigger the sending of a third message to the second network element based on the first information.

[0237] The session management network element can provide services for multiple sessions (including the first session) at the same time. The session management network element stores the identifier of the access network device associated with each session. Based on the identifier of the first session in the first information, the session management network element can determine the identifier of the first access network device serving the first session, and then determine the first group to which the first access network device belongs. The identifier of the first group is then carried in the message sent to the second network element.

[0238] Optionally, before step 52, the session management network element may first determine whether it stores indication information indicating whether the first access network device supports or does not support the first capability. If not, step 52 is then executed. The session management network element may trigger the determination of whether it stores indication information indicating whether the first access network device supports or does not support the first capability based on the first information.

[0239] Optionally, the third message is a subscription message. If the capabilities supported by the access network devices belonging to the first group change, the second network element can notify the session management network element of the changed capabilities supported by the access network devices based on this subscription.

[0240] Step 53: The second network element sends a third response to the session management network element. Correspondingly, the session management network element receives the third response from the second network element. The third response is used to indicate the capabilities supported by the access network devices belonging to the first group.

[0241] For example, the third response includes the identifier of the first group and RAN capability indication information. The RAN capability indication information can be found in Example 2, and will not be repeated here.

[0242] The second network element stores the association between the identifiers of each group and the indication information of the supported capabilities. After receiving the third message, the second network element can query the existing association based on the identifier of the first group in the third message, and then query the indication information of the capabilities supported by the first group.

[0243] Optionally, in step 54: if the third response indicates that the access network device belonging to the first group supports the first capability, the session management network element sends the first parameter to the first access network device based on the first information.

[0244] Optionally, in step 55: if the third response indicates that the access network device belonging to the first group supports the capability including the first capability, the session management network element saves the association between the identifier of the first access network device and the indication information of the first capability, and / or saves the association between the identifier of the first group and the indication information of the first capability.

[0245] The session management network element stores the indication information of the first access network device or the first group of devices that support the first capability. This makes it easier for the session management network element to serve other sessions without having to ask the second network element again whether the first access network device supports the first capability. This can reduce signaling overhead and also reduce the latency of establishing, modifying, and switching access network devices.

[0246] Optionally, in step 56: if the third response indicates that the capabilities supported by the access network devices belonging to the first group do not include the first capability, the session management network element sends a third indication to the first network element. The third indication is used to indicate that the first information is not supported, or the first information is rejected, or the access network device serving the first session does not support the first capability, or the access network device serving the first session does not support the first information.

[0247] By sending a third instruction to the first network element, the first network element can easily obtain information that it cannot perform the first capability on the first session.

[0248] Example 6: The session management network element queries the second network element to see if the access network devices belonging to the first group support the first capability.

[0249] The process by which the session management network element queries the second network element whether the access network devices belonging to the first group support the first capability can be referred to steps 62 and 63 below. Steps 62 and 63 can be presented as a separate embodiment, independent of Figure 4, or they can be integrated with Figure 4 as a unified embodiment. That is, the triggering reason for the session management network element to query the second network element whether the access network devices belonging to the first group support the first capability can be the first information of the first session, or other reasons. After learning whether the access network devices belonging to the first group support the first capability, if the first access network device supports the first capability, the session management network element can send the first parameter associated with the first capability to the first access network device, or it can be used in other processes.

[0250] Optionally, in step 61: the first network element sends first information to the session management network element, and the session management network element receives the first information accordingly; the first information is used to indicate that the first session requires the support of a first capability.

[0251] The process is the same as step 401, and will not be described in detail here.

[0252] Step 62: The session management network element sends a message to the second network element, and the second network element receives the message accordingly; wherein, the message is used to query whether the access network devices belonging to the first group support the first capability.

[0253] For example, the message includes the identifier of the first group and indications of the first capability.

[0254] Optionally, the session management network element triggers the sending of a message to the second network element based on the first information to query whether the access network devices belonging to the first group support the first capability.

[0255] The session management network element can provide services for multiple sessions (including the first session) at the same time. The session management network element stores the identifier of the access network device associated with each session. Based on the identifier of the first session in the first information, the session management network element can determine the identifier of the first access network device serving the first session, and then determine the first group to which the first access network device belongs. The identifier of the first group is then carried in the message sent to the second network element.

[0256] Optionally, before step 62, the session management network element may first determine whether it stores indication information indicating whether the first access network device supports or does not support the first capability. If not, step 62 is then executed. The session management network element may trigger the determination of whether it stores indication information indicating whether the first access network device supports or does not support the first capability based on the first information.

[0257] Step 63: The second network element sends a response to the session management network element, and the session management network element receives the response from the second network element accordingly.

[0258] This response is used to indicate whether access network devices belonging to the first group support the first capability or not. For example, the response includes an identifier of the first group and indication information indicating whether the first capability is supported or not.

[0259] For example, the indication information can be indicated by the value of at least one bit. For instance, when one bit is 0, it indicates that the first capability is not supported, and when one bit is 1, it indicates that the first capability is supported.

[0260] For example, when the access network devices belonging to the first group support the first capability, the response includes RAN capability indication information corresponding to the first capability; when the access network devices belonging to the first group do not support the first capability, the response does not include RAN capability indication information corresponding to the first capability. The RAN capability indication information can be found in Example 2, and will not be elaborated upon here.

[0261] The second network element stores the association between the identifiers of each group and the indication information of the supported capabilities. After receiving the message from step 62, the second network element can query the existing association based on the identifier of the first group in the message to find the indication information of the capabilities supported by the first group. Based on the indication information of the first capability carried in the message from step 62 and the queried indication information of the capabilities supported by the first group, the second network element can determine whether the first group supports the first capability and send a response to the session management network element to inform the session management network element whether the first group supports or does not support the first capability.

[0262] Optionally, in step 64: if the response in step 63 indicates that the access network device belonging to the first group supports the first capability, the session management network element sends the first parameter to the first access network device based on the first information.

[0263] Optionally, in step 65: if the response in step 63 indicates that the access network device belonging to the first group supports the first capability, the session management network element saves the association between the identifier of the first access network device and the indication information of the first capability, and / or saves the association between the identifier of the first group and the indication information of the first capability.

[0264] The session management network element stores the indication information of the first access network device or the first group of devices that support the first capability. This makes it easier for the session management network element to serve other sessions without having to ask the second network element again whether the first access network device supports the first capability. This can reduce signaling overhead and also reduce the latency of establishing, modifying, and switching access network devices.

[0265] Optionally, step 66: If the response indication in step 63 indicates that the access network device belonging to the first group does not support the first capability, the session management network element sends an indication to the first network element. This indication is used to indicate that the first information is not supported, or the first information is rejected, or the access network device serving the first session does not support the first capability, or the access network device serving the first session does not support the first information.

[0266] By sending this instruction to the first network element, the first network element can be informed that it is unable to perform the first capability for the first session.

[0267] The following is an example of how a second network element learns about the capabilities supported by access network devices (such as the first and second access network devices):

[0268] The access network device sends a fifth message to the second network element. Correspondingly, the second network element receives the fifth message from the access network device. The fifth message is used to request the access network device to register with the second network element. The fifth message includes: the identifier of the access network device and indication information for indicating the capabilities supported by the access network device (refer to the RAN capability indication information introduced in Example 2 above).

[0269] After learning of the capabilities supported by the access network device, the second network element can send a response to the session management network element based on the request from the session management network element. This response indicates the capabilities supported by the access network device. The process of the session management network element sending a request to the second network element and the second network element sending a response to the session management network element can be referred to Examples 2 to 5 above, and will not be elaborated further here. The second network element can also have other uses after learning of the capabilities supported by the access network device. In other words, the example of the second network element learning of the capabilities supported by the access network device can exist as a separate implementation, or it can be combined with Examples 2 to 5 above as a unified implementation.

[0270] When an access network device registers with a second network element, it sends an indication of the capabilities it supports to the second network element. The session management network element can then obtain the capabilities supported by the access network device from the second network element. This eliminates the need for the access network device to repeatedly report its supported capabilities to the session management network element in each session, thus avoiding signaling waste.

[0271] Based on the above description of the access network device reporting its supported capabilities during the registration process with the second network element, Figure 6 illustrates a flowchart of a communication method. The execution entities in Figure 6 (e.g., the first network element, session management network element, second network element, and first access network device, etc.) can all be replaced by modules (e.g., chips, chip systems, or processors) within these execution entities, or logical nodes, logical modules, or software that implement all or part of the functions of the execution entity.

[0272] Figure 6 includes the following steps:

[0273] Step 600: The first access network device sends a message to the second network element, and the second network element receives the message accordingly.

[0274] This message is used to request the first access network device to register with the second network element. The message includes the identifier of the first access network device and indication information for indicating the capabilities supported by the first access network device (refer to the RAN capability indication information introduced in Example 2 above).

[0275] This message is a Network Function Registration Request (NF register request) message. This message may include parameters already present in the NF register request. Optionally, this message may also include one or more of the following: type (i.e., RAN), identifier of the tracking area where the first access network device resides, and IP address of the first access network device.

[0276] Step 601: The session management network element establishes the first session for the terminal device.

[0277] For example, the first access network device sends a message to the session management network element, and the session management network element receives the message accordingly. This message requests the establishment of a first session for the terminal device. The message includes the identifier of the first access network device and the NAS-PDU. The NAS-PDU is the NAS message payload sent by the terminal device to the first access network device.

[0278] Before step 601, the first access network device receives a request message from the terminal device, which requests the establishment of a PDU session for the terminal device. The request message includes a NAS-PDU. Based on the request message from the terminal device, the first access network device triggers the sending of a message to the session management network element to request the establishment of a first session for the terminal device.

[0279] After receiving a message requesting the establishment of a first session for a terminal device, the session management network element can learn the association between the identifier of the first access network device, the identifier of the first session, and the identifier of the terminal device (or the UE IP address), and the session management network element can save this association.

[0280] Step 602: The first network element (e.g., the policy control network element) sends the first information to the session management network element, which is used to indicate that the first session requires the support of the first capability.

[0281] Step 602 can be referred to step 401, and will not be described in detail here.

[0282] Other processes may be included between steps 600, 601 and 602, and this application embodiment does not impose any limitations.

[0283] Step 603: The session management network element interacts with the second network element to learn whether the first access network device supports the first capability or not.

[0284] The specific process of step 603 can be referred to steps 502 and 503 in Example 2 above, or steps 32 and 33 in Example 3 above, or steps 42 and 43 in Example 4 above, or steps 52 and 53 in Example 5 above, or steps 62 and 63 in Example 6 above.

[0285] Alternatively, the session management network element can refer to Example 1 above to determine whether the first access network device supports the first capability or not.

[0286] Step 604: Depending on whether the first access network device supports the first capability or not, the session management network element performs the corresponding operation.

[0287] The specific process of step 604 can be referred to steps 504-506 in Example 2 above, or steps 34-36 in Example 3 above, or steps 44-46 in Example 4 above, or steps 54-56 in Example 5 above, or steps 64-65 in Example 6 above.

[0288] Based on the above description of the access network device reporting its supported capabilities during the registration process with the second network element, Figure 7 illustrates a flowchart of a communication method. The execution entities in Figure 7 (e.g., the first network element, session management network element, second network element, and first access network device, etc.) can all be replaced by modules (e.g., chips, chip systems, or processors) within these execution entities, or logical nodes, logical modules, or software that implement all or part of the functions of the execution entity. The differences between Figure 6 and Figure 7 are: Figure 6 shows the first network element sending the first information during the establishment of the first session; Figure 7 shows the first network element sending the first information after the establishment of the first session.

[0289] Steps 700 and 701 can be referred to steps 600 and 601, and will not be described in detail here.

[0290] Optionally, in step 702: AF sends a request message to NEF, which requests the enabling of a first feature for the first session (PDU session) of the terminal device. The first feature requires the support of a first capability. The message includes the IP address of the terminal device.

[0291] Optionally, the first feature / first capability is PDU Set based QoS handling.

[0292] Optionally, step 703: NEF interacts with BSF to obtain the identifier of the policy management element (PCF) corresponding to the first session.

[0293] For example, NEF authorizes the AF request and uses the IP address of the terminal device to request the PCF corresponding to the first session from BSF.

[0294] Optionally, step 704: NEF sends a policy authorization request to PCF, which is used by PCF to update the policy information of the first session, thereby activating the PDU Set based QoS handling requested by AF.

[0295] Step 705: The PCF (i.e., the first network element) sends the first information to the session management network element, which is used to indicate that the first session requires the support of the first capability.

[0296] Upon request from the NEF, the PCF updates the SM policy for the first session and sends the updated policy to the session management network element serving the first session. This first information is the SM policy update information. This first information can be used to instruct the first session to enable a first feature, which requires the support of a first capability.

[0297] The remaining details of step 705 can be found in step 401, and will not be repeated here.

[0298] Step 706: The session management network element interacts with the second network element to learn whether the first access network device supports the first capability or not.

[0299] The specific process of step 706 can be referred to steps 502 and 503 in Example 2 above, or steps 32 and 33 in Example 3 above, or steps 42 and 43 in Example 4 above, or steps 52 and 53 in Example 5 above, or steps 62 and 63 in Example 6 above.

[0300] Alternatively, the session management network element can refer to Example 1 above to determine whether the first access network device supports the first capability or not.

[0301] Step 707: Depending on whether the first access network device supports the first capability or not, the session management network element performs the corresponding operation.

[0302] The specific process of step 707 can be referred to steps 504-506 in Example 2 above, or steps 34-36 in Example 3 above, or steps 44-46 in Example 4 above, or steps 54-56 in Example 5 above, or steps 64-65 in Example 6 above.

[0303] The movement of a terminal device or other reasons may cause a switchover of the access network device serving the terminal device. If the access network device serving the terminal device switches from the first access network device to the second access network device, the access network device serving the first session also switches from the first access network device to the second access network device. If the first session requires the support of a first capability, and the second access network device supports the first capability, the session management network element can inform the second access network device of the first parameter associated with the first capability.

[0304] In one possible implementation, the second access network device sends fourth information to the session management network element. Correspondingly, the session management network element receives a fourth message from the second access network device, which requests a switch of the access network device serving the terminal device to the second access network device. The fourth message includes the identifier of the first session, the identifier of the terminal device, and the identifier of the second access network device, where the first session is the session of the terminal device. If the second access network device supports the first capability, the session management network element sends the first parameter to the second access network device based on the first information.

[0305] In one possible implementation, the session management network element triggers a determination of whether the second access network device supports the first capability based on the identifier of the first session in the fourth message and the first information. Alternatively, after receiving the first information, the session management network element saves the association between the identifier of the first session and the indication information of the first capability; after receiving the fourth message, the session management network element triggers a determination of whether the second access network device supports the first capability based on the identifier of the first session in the fourth message and the pre-saved association between the identifier of the first session and the indication information of the first capability.

[0306] Optionally, after step 401, the session management network element saves the content carried in the first information. The session management network element may also save the association between the identifier of the first session and the indication information of the first capability. Optionally, this association may also include the identifier of the terminal device associated with the first session (e.g., a temporary identifier). After receiving the first information, the session management network element can save the association between the identifier of the first session and the indication information of the first capability, regardless of whether the first access network device supports the first capability. Thus, when an access network device handover occurs, the session management network element can determine, based on the saved association, that the first session requires support for the first capability. The session management network element can then determine whether the handover access network device supports the first capability. If the handover access network device supports the first capability, the session management network element sends the parameters associated with the first session to the handover access network device. In the current technology, the session management network element only saves the association between the identifier of the first session and the indication information of the first capability after receiving indication information from the first access network device indicating that the first access network device supports the first capability. If the first access network device does not support the first capability, the association between the identifier of the first session and the indication information of the first capability is not saved. If this association is not saved, after the access network device is switched over, even if the switched access network device supports the first capability, the session management network element will need to wait to receive a second request from the first network element before determining whether the switched access network device supports the first capability; if no second request is received from the first network element, the session management network element will not determine whether the switched access network device supports the first capability. It can be seen that, compared with the prior art, the embodiments of this application can enable the first capability of the first session earlier.

[0307] After a switchover occurs in the access network equipment, the second access network equipment replaces the role of the first access network equipment. All the content related to the first access network equipment described earlier applies to the second access network equipment. For example, after the session management network element learns that the access network equipment serving the terminal device has switched to the second access network equipment, it determines whether the second access network equipment supports the first capability and performs corresponding operations based on whether it supports or does not support the first capability. The following, in conjunction with Figure 8, illustrates a flowchart of a communication method. The execution entities in Figure 8 (e.g., the first network element, the session management network element, the second network element, the second access network equipment, and the first access network equipment, etc.) can all be replaced by modules (e.g., chips, chip systems, or processors) within these execution entities, or logical nodes, logical modules, or software that implement all or part of the functions of the execution entity.

[0308] Step 800: The second access network device sends a message to the second network element, and the second network element receives the message accordingly.

[0309] This message is used to request the second access network device to register with the second network element. The message includes the identifier of the second access network device and indication information for indicating the capabilities supported by the second access network device (refer to the RAN capability indication information introduced in Example 2 above).

[0310] This message is a Network Function Registration Request (NF register request) message. This message may include parameters already present in the NF register request. Optionally, this message may also include one or more of the following: the type of network element (i.e., RAN), the identifier of the tracking area where the second access network device is located, and the IP address of the second access network device.

[0311] Step 801: Air interface handover occurs.

[0312] That is, the access network device serving the terminal device is switched from the first access network device to the second access network device.

[0313] Optionally, before step 801, the content described above can be performed, for example, Figure 4, Examples 1 to 6, Figure 6, Figure 7, etc.

[0314] Step 802: The second access network device sends a fourth message to the session management network element, and the session management network element receives the fourth message from the second access network device.

[0315] The fourth message is used to request the switching of the access network device serving the terminal device to the second access network device. The fourth message includes the identifier of the first session, the identifier of the terminal device (e.g., a temporary identifier), and the identifier of the second access network device; wherein, the first session is the session of the terminal device.

[0316] The fourth message can be a path switch request message.

[0317] Step 803: The session management network element interacts with the second network element to learn whether the second access network device supports the first capability or not.

[0318] Based on the context of the first session (including the association between the first information or the identifier of the first session and the indication information of the first capability), the session management network element triggers a determination of whether the second access network device supports the first capability or does not support the first capability.

[0319] The specific process of step 803 can be referred to steps 502 and 503 in Example 2 above, or steps 32 and 33 in Example 3 above, or steps 42 and 43 in Example 4 above, or steps 52 and 53 in Example 5 above, or steps 62 and 63 in Example 6 above; simply replace the first access network device in the previous example with the second access network device.

[0320] Alternatively, the session management network element can refer to Example 1 above to determine whether the second access network device supports the first capability or not.

[0321] Step 804: Depending on whether the second access network device supports the first capability or not, the session management network element performs the corresponding operation.

[0322] The specific process of step 804 can be referred to steps 504-506 in Example 2 above, or steps 34-36 in Example 3 above, or steps 44-46 in Example 4 above, or steps 54-56 in Example 5 above, or steps 64-65 in Example 6 above; simply replace the first access network device in the previous examples with the second access network device.

[0323] In the current technology, the AF (Agent Focus) sends a request message to the NEF (Network Provider), requesting PDU set-based QoS handling for the PDU session of the terminal device. This message includes the IP address of the terminal device. The NEF (Network Provider) authorizes the AF's request and, using the terminal device's IP address, requests the PCF (Policy Provider Function) corresponding to the PDU session from the BSF (Network Provider Function). The NEF sends a policy authorization request to the PCF, which updates the policy information of the PDU session, thereby activating the PDU set-based QoS handling requested by the AF. Based on the NEF's request, the PCF updates the SM (Session Management) policy of the PDU session and sends the updated policy to the session management network element serving the PDU session. The SMF (Session Management Function) sends the updated policy information, including QoS Profile information, to the RAN (Network RAN) through the AMF (Network Management Function). The RAN reports PDU set-based QoS handling support capability information to the SMF based on the QoS Profile. When the RAN supports PDU set-based QoS handling, the SMF performs subsequent configuration steps; when the RAN does not support PDU set-based QoS handling, the PCF notifies the NEF that policy authorization has been rejected via the Npcf_PolicyAuthorization_Create Response message, and the NEF rejects the AF request.

[0324] As can be seen, when the RAN does not support PDU Set-based QoS handling, the signaling interactions between the PCF, SMF, and RAN are ineffective, resulting in wasted signaling. The following introduces a communication method that can avoid this signaling waste.

[0325] The AF sends a sixth message to the NEF, and correspondingly, the NEF receives the sixth message from the AF; wherein, the sixth message is used to request the activation of a first feature for the first session, the first feature requiring support from a first capability; if the first access network device does not support the first capability, the NEF sends indication information to the AF; wherein, the first access network device serves the first session, and the indication information is used to indicate any of the following:

[0326] Refuse to enable the first feature for the first session; or,

[0327] The capabilities required for the first feature are not supported; or,

[0328] The access network device serving the first session does not support the capabilities required for the first feature; or,

[0329] The first feature is refused to be enabled for the first session, and the reason for refusing to enable the first feature for the first session is that the access network device serving the first session does not support the first capability.

[0330] In this method, if the first access network device does not support the first capability, the AF request is rejected, which can omit the signaling interaction between PCF, SMF, and RAN in the prior art and avoid signaling waste.

[0331] In one possible implementation, if the first access network device supports the first capability, the NEF sends a first message to the SMF, the first message indicating that the first session requires support for the first capability.

[0332] Optionally, the first information includes: the identifier of the first session and relevant parameters of the first capability. Taking PDU set based QoS handling as an example, the relevant parameters include, but are not limited to, at least one of the following: PDU set latency budget (PSDB), PDU set error rate (PSER), and PDU set comprehensive processing information (PSIHI). Further optionally, the first information also includes the identifier (temporary identifier) ​​and / or IP address of the terminal device, and the first session is a session of the terminal device.

[0333] The NEF can directly send the first information to the SMF, or the NEF can send a policy authorization request to the PCF, which will then update the policy information for the first session, thereby activating the first feature requested by the AF. Based on the NEF's request, the PCF updates the policy information for the first session and sends the updated policy, i.e., the first information, to the session management network element serving the first session.

[0334] After receiving the first information, the session management network element performs the same process as in the prior art. For example, the session management network element sends the first parameter to the first access network device according to the first information, and the first access network device receives the first parameter accordingly.

[0335] The first parameter is associated with the first capability. Optionally, the first parameter is determined based on relevant parameters of the first capability contained in the first information. The first parameter and the relevant parameters of the first capability contained in the first information may be partially the same, partially different, or completely identical. Further details are omitted here.

[0336] It should be noted that after receiving the first parameter, the first access network device can perform corresponding functions for the first session based on the first parameter. After receiving the first parameter, the first access network device does not need to send indication information to the session management network element to indicate that the first access network device supports the first capability, which can save signaling.

[0337] Optionally, after receiving the first information, the session management network element sends the second parameter to the user plane network element; or, after sending the first parameter to the first access network device, the session management network element sends the second parameter to the user plane network element. The second parameter is associated with the first capability. The second parameter is determined based on the relevant parameters of the first capability contained in the first information. The second parameter and the relevant parameters of the first capability contained in the first information may be partially the same, partially different, or completely identical.

[0338] In the current technology, after receiving the indication information from the first access network device that supports the first capability, the session management network element sends the second parameter to the user plane network element. In the embodiments of this application, the session management network element can send the second parameter to the user plane network element without waiting for the response from the first access network device, which can enable the first capability of the first session to be enabled earlier.

[0339] Figure 9 shows a flowchart of a communication method. The execution entities in Figure 9 can all be replaced by modules (e.g., chips, chip systems, or processors) within the execution entity, or logical nodes, logical modules, or software that implement all or part of the functions of the execution entity.

[0340] Step 900: The first access network device sends a message to the network storage element (NRF), and the network storage element receives the message accordingly.

[0341] This message is used to request the first access network device to register with the NRF. The message includes the identifier of the first access network device and indication information indicating the capabilities supported by the first access network device (refer to the RAN capability indication information described in Example 2 above).

[0342] This message is a Network Function Registration Request (NF register request) message. This message may include parameters already present in the NF register request. Optionally, this message may also include one or more of the following: the type of network element (i.e., RAN), the identifier of the tracking area where the first access network device is located, and the IP address of the first access network device.

[0343] Step 901: The session management network element establishes the first session for the terminal device.

[0344] For example, the first access network device sends a message to the Session Management Network (SMF), and the SMF receives the message accordingly. This message requests the establishment of a first session for the terminal device. The message includes the identifier of the first access network device and the NAS-PDU. The NAS-PDU is sent by the terminal device to the first access network device.

[0345] Before step 901, the first access network device receives a request message from the terminal device, which requests the establishment of a PDU session for the terminal device. The request message includes a NAS-PDU. Based on the request message from the terminal device, the first access network device triggers the sending of a message to the session management network element to request the establishment of a first session for the terminal device.

[0346] After receiving a message requesting the establishment of a first session for a terminal device, the session management network element can learn the association between the identifier of the first access network device, the identifier of the first session, and the identifier of the terminal device (or the UE IP address), and the session management network element can save this association.

[0347] Step 902: The session management network element sends a message to the BSF / UDM / NRF, which includes the identifier of the terminal device, the IP address of the terminal device, and the identifier of the first access network device.

[0348] After receiving the message, BSF / UDM / NRF can save the association between the terminal device's identifier and / or IP address and the identifier of the first access network device.

[0349] Step 903: AF sends the sixth message to NEF, and NEF receives the sixth message from AF accordingly.

[0350] The sixth message is used to request the activation of a first feature for the first session, the first feature requiring support from a first capability. The sixth message includes the IP address and / or identifier of the terminal device, and the first session is the session of the terminal device.

[0351] The sixth message is an AF session creation request with QoS (Nnef_AFsessionWithQoS_Create request). For example, if the first capability or feature is PDU Set based QoS handling, the sixth message also includes: PDU Set QoS parameters.

[0352] Step 904: Based on the IP address and / or identifier of the terminal device in the sixth message, the NEF requests the identifier of the access network device serving the first session from the BSF / UDM / NRF, i.e., the identifier of the first access network device.

[0353] For example, the NEF sends a request message to the BSF / UDM / NRF, which includes the IP address and / or identifier of the terminal device. This request message is used to obtain the identifier of the access network device serving the terminal device. Based on the association between the identifier and / or IP address of the terminal device stored in step 902 and the identifier of the first access network device, the BSF / UDM / NRF locates the identifier of the first access network device. The BSF / UDM / NRF then sends the identifier of the first access network device to the NEF.

[0354] Step 905: NEF interacts with NRF to determine whether the first access network device supports or does not support the first capability based on the identifier of the first access network device.

[0355] The process by which the NEF learns whether the first access network device supports or does not support the first capability is similar to the process by which the session management element learns whether the first access network device supports or does not support the first capability, as described earlier.

[0356] For example, the specific process of step 905 can be referred to steps 502 and 503 in Example 2 above, or steps 32 and 33 in Example 3 above. The second network element in steps 502 and 503, and steps 32 and 33 is the NRF, and the session management network element can be replaced by the NEF.

[0357] Alternatively, NEF can determine whether the first access network device supports or does not support the first capability by determining whether there is stored indication information that indicates whether the first access network device supports or does not support the first capability. For details, please refer to the Session Management Network Element in Example 1 above for determining whether there is stored indication information that the first access network device supports or does not support the first capability.

[0358] Step 906: If the first access network device does not support the first capability, the NEF sends an indication message to the AF; the indication message is used to indicate any of the following:

[0359] Refuse to enable the first feature for the first session; or,

[0360] The capabilities required for the first feature are not supported; or,

[0361] The access network device serving the first session does not support the capabilities required for the first feature; or,

[0362] The first feature is refused to be enabled for the first session, and the reason for refusing to enable the first feature for the first session is that the access network device serving the first session does not support the first capability.

[0363] Step 907: If the first access network device supports the first capability, the NEF sends first information to the SMF, the first information being used to indicate that the first session requires support for the first capability.

[0364] Optionally, the first information includes: an identifier for the first session and relevant parameters of the first capability. Further optionally, the first information also includes an identifier (temporary identifier) ​​and / or IP address of the terminal device, wherein the first session is a session of the terminal device.

[0365] In existing technologies, when an AF requests the enabling of a certain feature for a session, if the RAN serving that session does not support the corresponding capability, the following interaction between network elements is performed: AF→NEF→BSF→PCF→SMF→RAN→SMF→PCF→NEF→Reject AF request. In this embodiment, when an AF requests the enabling of a certain feature for a session, if the RAN serving that session does not support the corresponding capability, the following interaction between network elements is performed: AF→NEF→BSF→NEF→Reject AF request. This omits the intermediate process of BSF→PCF→SMF→RAN→SMF→PCF, saving signaling overhead.

[0366] It is understood that, in order to achieve the functions in the above embodiments, the Session Management Network Element (SMF), the Second Network Element (NRF), the First Access Network Device, and the NEF include corresponding hardware structures and / or software modules for performing each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0367] Figures 10 and 11 are schematic diagrams of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of the Session Management Network Element (SMF), the Second Network Element (NRF), the First Access Network Device, and the NEF in the above method embodiments, and thus can also achieve the beneficial effects of the above method embodiments.

[0368] As shown in Figure 10, the communication device 1000 includes a processing unit 1010 and a transceiver unit 1020.

[0369] For example, the communication device 1000 is used to implement the functions of the Session Management Network Element (SMF), the Second Network Element (NRF), the First Access Network Device, and the NEF in the method embodiments shown in Figures 4 to 9. The transceiver unit 1020 can execute the receiving and transmitting actions performed by the Session Management Network Element (SMF), the Second Network Element (NRF), the First Access Network Device, and the NEF in the method embodiments. The processing unit 1010 can execute other actions besides the transmitting and receiving actions performed by the Session Management Network Element (SMF), the Second Network Element (NRF), the First Access Network Device, and the NEF in the method embodiments.

[0370] For example, when the communication device 1000 is used to implement the function of the session management network element in the method embodiment shown in FIG4, the transceiver unit 1020 is used to receive first information and send first parameters. The processing unit 1010 is used to determine that the first access network device supports the first capability.

[0371] A more detailed description of the processing unit 1010 and the transceiver unit 1020 can be obtained directly from the relevant descriptions in the method embodiments shown in Figures 4 to 9, and will not be repeated here. The processing unit 1010 can be implemented by a processor, and the transceiver unit 1020 can be implemented by a transceiver.

[0372] As shown in Figure 11, the communication device 1100 includes a processor 1110 and an interface circuit 1120. The processor 1110 and the interface circuit 1120 are coupled to each other. It is understood that the interface circuit 1120 can be a transceiver or an input / output interface. Optionally, the communication device 1100 may also include a memory 1130 for storing instructions executed by the processor 1110, or storing input data required by the processor 1110 to execute instructions, or storing data generated after the processor 1110 executes instructions. Sometimes, the interface circuit 1120 can also be understood as part of the processor 1110, in which case the communication device 1100 includes the processor 1110.

[0373] When the communication device 1100 is used to implement the methods shown in Figures 4 to 9, the processor 1110 is used to implement the functions of the processing unit 1010, and the interface circuit 1120 is used to implement the functions of the transceiver unit 1020.

[0374] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information from a network device, which can be understood as the information being first received by other modules (such as an RF module or antenna) in the terminal device, and then sent to the terminal device chip by these modules. The terminal device chip sends information to a network device, which can be understood as the information being first sent to other modules (such as an RF module or antenna) in the terminal device, and then sent to the network device by these modules.

[0375] When the aforementioned communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from the terminal device, which can be understood as the information being first received by other modules (such as radio frequency modules or antennas) in the network device, and then sent to the network device chip by these modules. The network device chip sends information to the terminal device, which can be understood as the information being sent down to other modules (such as radio frequency modules or antennas) in the network device, and then sent to the terminal device by these modules. Here, the network device module can be the baseband chip of the network device, or a DU (Digital Unit) or other modules. The DU here can be a DU under the Open Radio Access Network (O-RAN) architecture.

[0376] In this application, entity A sends information to entity B, either directly or indirectly through other entities. Similarly, entity B receives information from entity A, either directly or indirectly through other entities. Entities A and B can be network devices or terminal devices, or modules within network devices or terminal devices. The sending and receiving of information can be between network devices and terminal devices, between two network devices (e.g., CU and DU), or between different modules within a single device (e.g., a terminal device chip and other modules within the terminal device, or a network device chip and other modules within the network device).

[0377] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0378] This application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, enables the computer to perform the aforementioned communication method. Alternatively, the computer program includes instructions for implementing the aforementioned communication.

[0379] This application also provides a computer program product, including: computer program code, which, when run on a computer, enables the computer to execute the communication method provided above.

[0380] This application also provides a communication system, which includes at least two of the following: a first access network device that performs the above-described communication method, a second network element, a first network element, a session management network element, and a NEF.

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

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

[0383] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0384] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A or B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. Expressions such as "at least one of the following" or "one or more of them" refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c, or one or more of a, b, or c, means: a, b, c, a and b, a and c, b and c, or a and b and c. Each of a, b, and c can be single or multiple.

[0385] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority, or importance of the multiple objects. Furthermore, such names do not indicate differences in the content, sending / receiving end, sending order, size, application scenario, priority, or importance of the two pieces of information. Additionally, the numbering of steps in the various embodiments described in this application is only to distinguish different steps and is not used to limit the order of steps.

Claims

1. A communication method characterized by comprising: Applied to session management network elements, including: Receive first information from a first network element, the first information being used to indicate that a first session requires the support of a first capability, and the session management network element serving the first session; If the first access network device supports the first capability, a first parameter is sent to the first access network device based on the first information. The first parameter is associated with the first capability, and the first access network device serves the first session.

2. The method of claim 1, wherein, The first capability includes one or more of the following: Based on the protocol data unit set, it has the following service quality processing capabilities, multicast and broadcast session capabilities, access network device positioning capabilities, access network device perception capabilities, access network device timing capabilities, and access network device general computing capabilities.

3. The method of claim 1 or 2, wherein, When the first access network device supports the first capability, sending the first parameter to the first access network device based on the first information includes: If the association between the identifier of the first access network device and the indication information of the first capability is stored, then the first parameter is sent to the first access network device according to the first information; or, If the association between the identifier of the first group to which the first access network device belongs and the indication information of the first capability is stored, the first parameter is sent to the first access network device according to the first information.

4. The method of claim 1 or 2, wherein, When the first access network device supports the first capability, sending the first parameter to the first access network device based on the first information includes: Send a first message to the second network element, the first message being used to obtain the capabilities supported by the first access network device; Receive a first response from the second network element, the first response being used to indicate the capabilities supported by the first access network device; If the capabilities supported by the first access network device indicated by the first response include the first capability, the first parameter is sent to the first access network device based on the first information.

5. The method of claim 4, wherein, The method further includes: If the capabilities supported by the first access network device indicated in the first response do not include the first capability, a first indication is sent to the first network element. The first indication is used to indicate that the access network device serving the first session does not support the first capability or does not support the first capability.

6. The method of claim 1 or 2, wherein, When the first access network device supports the first capability, sending the first parameter to the first access network device based on the first information includes: Send a second message to the second network element, the second message being used to obtain the capabilities supported by the access network equipment located in the first area; Receive a second response from the second network element, the second response being used to indicate the capabilities supported by the access network device located within the first area, the first access network device being located within the first area; If the capabilities supported by the first access network device indicated by the second response include the first capability, the first parameter is sent to the first access network device based on the first information.

7. The method of claim 6, wherein, The first area includes the service area of ​​the session management network element.

8. The method of claim 6 or 7, wherein, The method further includes: If the capabilities supported by the first access network device in the second response indication do not include the first capability, a second indication is sent to the first network element, the second indication being used to indicate that the access network device serving the first session does not support the first capability or does not support the first capability.

9. The method of claim 1 or 2, wherein, When the first access network device supports the first capability, sending the first parameter to the first access network device based on the first information includes: Send a third message to the second network element, the third message being used to obtain the capabilities supported by the access network devices belonging to the first group, the first access network devices belonging to the first group; Receive a third response from the second network element, the third response being used to indicate the capabilities supported by the access network devices belonging to the first group; If the capabilities supported by the access network devices belonging to the first group indicated by the third response include the first capability, the first parameter is sent to the first access network device based on the first information.

10. The method of any one of claims 1-9, wherein, After receiving the first information from the first network element, the method further includes: Save the association between the identifier of the first session and the indication information of the first capability.

11. The method of any one of claims 1-10, wherein, The method further includes: A fourth message is received from a second access network device. The fourth message is used to request the access network device serving the terminal device to be switched to the second access network device. The fourth message includes the identifier of the first session and the identifier of the terminal device. The first session is the session of the terminal device. If the second access network device supports the first capability, the first parameter is sent to the second access network device based on the first information.

12. The method of claim 11, wherein, The method further includes: Based on the identifier of the first session and the first information in the fourth message, a determination is triggered to determine whether the second access network device supports the first capability.

13. A method of communication, comprising: Applied to a second network element, the method includes: A fifth message is received from a first access network device, the fifth message being used to request the first access network device to register with the second network element, the fifth message including indication information, the indication information being used to indicate the capabilities supported by the first access network device; Based on the request from the session management network element, a response is sent to the session management network element, the response indicating the capabilities supported by the first access network device.

14. The method of claim 13, wherein, The capabilities supported by the first access network device include one or more of the following: Based on the protocol data unit set, it has the following service quality processing capabilities, multicast and broadcast session capabilities, access network device positioning capabilities, access network device perception capabilities, access network device timing capabilities, and access network device general computing capabilities.

15. The method of claim 13 or 14, wherein, The request based on the session management network element, sending a response to the session management network element, includes: Receive a first message from the session management network element, the first message being used to obtain the capabilities supported by the first access network device; Based on the first message, a first response is sent to the session management network element, the first response being used to indicate the capabilities supported by the first access network device.

16. The method of claim 13 or 14, wherein, The request based on the session management network element, sending a response to the session management network element, includes: Receive a second message from the session management network element, the second message being used to obtain the capabilities supported by the access network devices located in the first area; Based on the second message, a second response is sent to the session management network element. The second response is used to indicate the capabilities supported by the access network device located in the first area.

17. The method of claim 16, wherein, The first area includes the service area of ​​the session management network element.

18. The method of claim 13 or 14, wherein, The request based on the session management network element, sending a response to the session management network element, includes: Receive a third message from the session management network element, the third message being used to obtain the capabilities supported by the access network devices belonging to the first group, the first access network devices belonging to the first group; Based on the third message, a third response is sent to the session management network element, the third response being used to indicate the capabilities supported by the access network devices belonging to the first group.

19. A communications device, characterized by Includes modules for performing the method as described in any one of claims 1-12 or any one of claims 13-18.

20. A communications device, characterized by Includes a processor, which is coupled to a memory; The memory is used to store computer programs or instructions; The processor is configured to execute some or all of the computer programs or instructions in the memory, and when the some or all of the computer programs or instructions are executed, to implement the method as described in any one of claims 1-12 or any one of claims 13-18.

21. A communications device, characterized by Including processor and memory; The memory is used to store computer programs or instructions; The processor is configured to execute some or all of the computer programs or instructions in the memory, and when the some or all of the computer programs or instructions are executed, to implement the method as described in any one of claims 1-12 or any one of claims 13-18.

22. A chip system, characterized by Includes a processor and interface circuitry, wherein the processor is coupled to a memory; The memory is used to store computer programs or instructions; The processor is configured to execute some or all of the computer programs or instructions in the memory, and when the some or all of the computer programs or instructions are executed, to implement the method as described in any one of claims 1-12 or any one of claims 13-18.

23. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-12 or any one of claims 13-18.

24. A computer program product, characterised in that, The computer program product includes: computer instructions that, when executed on a computer, cause the method as described in any one of claims 1-12 or any one of claims 13-18 to be implemented.

Images