Communication method, apparatus, and system

Abstract

The present application is applied to the technical field of communications, and provides a communication method, apparatus, and system. The communication method provided in the present application enables mutually isolated routing information to be provided for different local data networks. The communication method comprises: a first network element receiving a first policy, the first policy being used to indicate information allowing a service flow to be routed to at least one local data network; and the first network element sending information corresponding to a second network element to the second network element, wherein the second network element is used to manage edge deployment information in a first local data network, and the information corresponding to the second network element is determined on the basis of the first policy and is used to determine whether the service flow is allowed to be routed to the first local data network.

Description

Communication method, apparatus and system

[0001] The present application claims priority to the Chinese patent application No. 202411099048.2, filed on August 9, 2024, and entitled "Communication method, apparatus and system", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

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

[0003] In the current mobile edge computing (MEC) scenario, a policy control function (PCF) network element or a session management function (SMF) sends an offloading policy to all regions (for example, all provinces / cities / parks) managed by the network element. However, this offloading policy configuration method does not consider the isolation and deployment flexibility requirements of the policy, which may result in that the local applications of different regions are all open to terminals or all refuse terminal access, and cannot flexibly meet the needs of operators or users. SUMMARY

[0004] Embodiments of the present application provide a communication method, apparatus and system, which can provide mutually isolated offloading policies for different local data networks.

[0005] To achieve the above-mentioned purpose, embodiments of the present application adopt the following technical solutions:

[0006] In a first aspect, a communication method is provided, which can be executed by a first network element, or can also be executed by a module (such as a processor, a chip, or a chip system, etc.) applied to the first network element. Hereinafter, the first network element is taken as an example to execute the communication method, which includes: the first network element receives a first policy; the first policy is used to indicate information of allowing a traffic flow to be routed to at least one local data network. The first network element sends information corresponding to a second network element to the second network element; wherein the second network element is used to manage edge deployment information in a first local data network, and the information corresponding to the second network element is determined according to the first policy, and the information corresponding to the second network element is used to determine whether to allow the traffic flow to be routed to the first local data network.

[0007] Based on the communication method provided in the embodiments of the present application, after receiving the first policy, the first network element can determine information for determining whether to allow the traffic flow to be routed to the first local data network according to the first policy, in other words, the first network element can provide targeted routing information (or also referred to as offloading information) for the local data network. Compared with the current network element that does not distinguish offloading policies based on local data networks, but directly provides offloading policies to each local data network below for policy configuration, the communication method provided in the embodiments of the present application can provide mutually isolated routing information for different local data networks, thereby improving the flexibility of policy deployment and more flexibly meeting the needs of the network or the user.

[0008] With reference to the first aspect, in a possible design, the information corresponding to the second network element includes at least one of the following information that allows the traffic flow to be routed to the first local data network: a fully qualified domain name (FQDN), an internet protocol (IP) segment, a service area, a data network access identifier (DNAI), or an application identity (APP ID).

[0009] The present solution provides various forms of routing information, which can be suitable for different application scenarios and improves the flexibility of policy configuration.

[0010] With reference to the first aspect, in a possible design, the information corresponding to the second network element includes a first parameter and a second parameter that allow the traffic flow to be routed to the first local data network, the first parameter is a FQDN or an IP segment, and the second parameter is a service area, a DNAI, or an APP ID.

[0011] The present solution provides a new form of routing information. Through this new form, the first network element can plan different first parameters and / or second parameters for different local data networks to provide different routing information for different local data networks. For example, the first network element can plan the same IP segment for different local data networks, but provide different routing information for different local data networks by planning different service areas.

[0012] With reference to the first aspect, in a possible design, the information corresponding to the second network element is determined according to the first policy and configuration information of a network supported by the second network element.

[0013] The present solution provides a determination manner of routing information, which can avoid using information not supported by the second network element as the routing information corresponding to the first local data network.

[0014] In a possible design of the first aspect, the configuration information of the network supported by the second network element includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0015] The scheme provides a plurality of possible configuration information of the network supported by the second network element.

[0016] In a possible design of the first aspect, the information that allows the traffic flow to be routed to the at least one local data network includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0017] The scheme provides a plurality of forms of routing information, which can be suitable for different application scenarios and improves the flexibility of policy configuration. For example, the network element that provides the first policy can configure information such as a service area, a DNAI, or an APP ID, which does not change frequently, thereby reducing the configuration work.

[0018] In a possible design of the first aspect, the information corresponding to the third network element that manages a second local data network of the at least one local data network is different from the information corresponding to the second network element, the information corresponding to the third network element is determined according to the first policy, and the information corresponding to the third network element is used to determine whether to allow the traffic flow to be routed to the second local data network.

[0019] Based on the scheme, the first network element can determine different routing information for the second network element and the third network element, to ensure that the second network element and the third network element do not conflict when managing local applications, and to avoid problems such as misaccess of a terminal device to a local application caused by the same offloading policy configured for different local data networks.

[0020] In a possible design of the first aspect, the information corresponding to the third network element that manages a second local data network of the at least one local data network is different from the information corresponding to the second network element, the information corresponding to the third network element is determined according to the first policy, and the information corresponding to the third network element is used to determine whether to allow the traffic flow to be routed to the second local data network.

[0021] Based on the communication method provided in the embodiments of the present application, the second network element managing the first local data network can send the first information to the first network element to authorize the first information. If the first information is successfully authorized, it indicates that the first information can be used to determine whether to allow the traffic flow to be routed to the first local data network. Alternatively, the first network element can provide the second network element with the routing information (i.e., the information used to determine whether to allow the traffic flow to be routed to the first local data network) of the first local data network. Therefore, in the communication method provided in the embodiments of the present application, the second network element can have more rights to autonomously configure the routing information, and the first network element can authorize the first information to indicate whether the first information can be used as the routing information of the first local data network, or the first network element can directly provide the routing information of the first local data network, i.e., the first network element can provide mutually isolated routing information for different local data networks, thereby improving the flexibility of policy deployment and meeting the requirements of the network or the user more flexibly.

[0022] With reference to the second aspect, in a possible design, the information allowing the traffic flow to be routed to the at least one local data network includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0023] The present solution provides various forms of routing information, which can be suitable for different application scenarios and improve the flexibility of policy configuration.

[0024] With reference to the second aspect, in a possible design, the information allowing the traffic flow to be routed to the at least one local data network includes a first parameter and a second parameter, the first parameter is an FQDN or an IP segment, and the second parameter is a service area, a DNAI, or an APP ID.

[0025] The present solution provides a new form of routing information, and through the new form, different routing information can be planned by planning different first parameters and / or second parameters.

[0026] With reference to the second aspect, in a possible design, the information corresponding to the second network element includes at least one of the following information allowing the traffic flow to be routed to the first local data network: an FQDN, an IP segment, a service area, a DNAI, or an APP ID; or the information corresponding to the second network element includes identification information, and the identification information is used to identify at least one of the following information allowing the traffic flow to be routed to the first local data network: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0027] The present solution provides a new form of routing information, which can be suitable for different application scenarios and improve the flexibility of policy configuration. For example, when the information corresponding to the second network element includes identification information, the identification information can be transmitted between network elements to transmit the routing information, thereby reducing the signaling overhead.

[0028] With reference to the second aspect above, in a possible design of the method, the first network element further sends the first information to a fourth network element; and the first network element receives the authorization result or the information corresponding to the second network element from the fourth network element.

[0029] The solution provides another way: the fourth network element authorizes the first information or determines the information corresponding to the second network element.

[0030] With reference to the second aspect above, in a possible design of the method, the authorization result or the information corresponding to the second network element is determined according to the first information, first identification information supported by the second network element, and at least one of the following: FQDN, IP segment, service area, or DNAI; wherein the first identification information is used to identify at least one of the following: FQDN, IP segment, service area, DNAI, or APP ID.

[0031] With reference to the second aspect above, in a possible design of the method, the first message is used to request establishment of the session.

[0032] The solution can be executed in a session establishment process, and can reuse messages in the session establishment process, thereby reducing signaling overhead.

[0033] With reference to the second aspect above, in a possible design of the method, the first message further includes first indication information; and the first indication information is used to indicate authorization of the first information.

[0034] Based on the solution, the indication information can be used to indicate that the first network element needs to authorize the first information, thereby avoiding a case where the first network element does not know what to do after receiving the first information.

[0035] With reference to the second aspect above, in a possible design of the method, the information corresponding to a third network element that manages a second local data network of the at least one local data network is different from the information corresponding to the second network element, and the information corresponding to the third network element is used to determine whether to allow a service flow to be routed to the second local data network.

[0036] Based on the solution, the first network element can determine different routing information for the second network element and the third network element, so as to ensure that policies do not conflict when the second network element and the third network element manage local applications, and to avoid problems such as misaccess of a terminal device to a local application caused by configuration of the same offloading policy for different local data networks.

[0037] In a third aspect, a communication method is provided, which can be performed by a second network element or a module (e.g., a processor, a chip, or a chip system) applied to the second network element. The method includes: obtaining, by the second network element, information corresponding to the second network element, wherein the second network element is configured to manage edge deployment information in a first local data network, and the information corresponding to the second network element includes at least one of the following information that allows a service flow to be routed to the first local data network: a service area, a DNAI, or an APP ID; or the information corresponding to the second network element includes at least one identifier, and the at least one identifier is configured to identify the at least one of the following information that allows the service flow to be routed to the first local data network: the service area, the DNAI, or the APP ID. The second network element configures a filtering rule of the service flow according to the information corresponding to the second network element, and the filtering rule is configured to determine whether the service flow is allowed to be routed to the first local data network.

[0038] According to the communication method provided in the embodiments of the present application, new forms of routing information can be provided for the second network element, which can be applicable to different application scenarios and improve the flexibility of configuration. For example, if the form of the routing information is the service area, the DNAI, or the APP ID, the network element providing the routing information can configure the service area / DNAI / APP ID without configuring the IP segment / FQDN. The service area / DNAI / APP ID in the area usually does not need to be changed frequently, and therefore, the network element providing the first policy can configure the DNAI / APP ID, which can greatly reduce the configuration work. For another example, if the form of the routing information is the identifier, the network element providing the routing information can deliver the identifier to configure the routing information for the local data network, which can reduce the signaling overhead.

[0039] In combination with the third aspect, in a possible design, the information corresponding to the second network element further includes an FQDN and / or an IP segment that allows the service flow to be routed to the first local data network.

[0040] In combination with the third aspect, in a possible design, the information corresponding to the second network element includes a first parameter and a second parameter that allow the service flow to be routed to the first local data network, the first parameter is an FQDN or an IP segment, and the second parameter is a service area, a DNAI, or an APP ID.

[0041] The present solution provides a new form of routing information, and through the new form, different first parameters and / or second parameters can be planned for different local data networks to provide different routing information for different local data networks. For example, the same IP segment can be planned for different local data networks, but different service areas are planned to provide different routing information for different local data networks.

[0042] With reference to the third aspect above, in a possible design, the method further includes: the second network element sending, to the fifth network element, the filtering rule of the service flow and the tunnel information; and the tunnel information includes at least one of the tunnel information of the anchor user plane function network element, the tunnel information of the user plane function network element corresponding to the first local data network, or the tunnel information of the access network.

[0043] Based on this scheme, the second network element can send the filtering rule and the tunnel information to the fifth network element, so that the fifth network element can split the service flow based on the filtering rule.

[0044] With reference to the third aspect above, in a possible design, the second network element obtaining the information corresponding to the second network element includes: the second network element sending a first message to the first network element, where the first message includes the first information; the first information includes information that allows the service flow to be routed to the at least one local data network or at least one identifier, and each identifier in the at least one identifier is used to identify information that allows the service flow to be routed to one of the at least one local data network. The second network element receives the authorization result and / or the information corresponding to the second network element from the first network element, where the authorization result indicates authorization success or failure. In a case where the second network element receives the authorization result and the authorization result indicates authorization success, the second network element determines the first information as the information corresponding to the second network element.

[0045] Based on this scheme, the second network element can send the first information to the first network element to authorize the first information. If the first information is authorized successfully, it indicates that the first information can be used to determine whether the service flow is allowed to be routed to the first local data network. Alternatively, the first network element can provide the routing information (i.e., information used to determine whether the service flow is allowed to be routed to the first local data network) of the first local data network to the second network element. Therefore, in this scheme, the second network element can have more rights to autonomously configure the routing information, and the first network element can authorize the first information to indicate whether the first information can be used as the routing information of the first local data network, or the first network element can directly provide the routing information of the first local data network, i.e., the first network element can provide mutually isolated routing information for different local data networks, thereby improving the flexibility of policy deployment and meeting the needs of the network or users more flexibly.

[0046] With reference to the third aspect above, in a possible design, the first message is used to request to establish a session.

[0047] This scheme can be performed in a session establishment process, and can reuse messages in the session establishment process, thereby reducing signaling overhead.

[0048] With reference to the third aspect, in a possible design, the information allowing the traffic flow to be routed to the at least one local data network includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0049] The solution provides various forms of routing information, which can be applicable to different application scenarios, and improves flexibility of policy configuration.

[0050] With reference to the third aspect, in a possible design, the first message further includes first indication information, where the first indication information is used to indicate authorization on the first information.

[0051] Based on the solution, the indication information can be used to indicate that the first network element needs to authorize the first information, so that the first network element can know what to do after receiving the first information.

[0052] In a fourth aspect, a communication method is provided, which can be performed by a second network element, or can also be performed by a module (for example, a processor, a chip, or a chip system) applied to the second network element. The following takes the second network element as an example to describe the communication method, which includes the following steps: the second network element sends a first message to a first network element, where the first message includes first information; the first information includes information allowing traffic flow to be routed to at least one local data network or at least one identifier, each identifier in the at least one identifier is used to identify information allowing traffic flow to be routed to one of the at least one local data network; the second network element receives an authorization result from the first network element and / or second network element corresponding information, where the authorization result indicates authorization success or failure, and the second network element corresponding information is used to determine whether to allow traffic flow to be routed to a first local data network managed by the second network element; and in a case where the second network element receives the authorization result and the authorization result indicates authorization success, the second network element determines the first information as the second network element corresponding information.

[0053] Based on the solution, the second network element can send the first information to the first network element to authorize the first information. If the first information is authorized successfully, it indicates that the first information can be used to determine whether to allow traffic flow to be routed to the first local data network. Alternatively, the first network element can provide routing information (that is, information used to determine whether to allow traffic flow to be routed to the first local data network) of the first local data network to the second network element. Therefore, in the solution, the second network element can have more autonomous rights to configure routing information, and the first network element can authorize the first information to indicate whether the first information can be used as routing information of the first local data network, or the first network element can directly provide the routing information of the first local data network, that is, the first network element can provide mutually isolated routing information for different local data networks, thereby improving flexibility of policy deployment and meeting network or user requirements more flexibly.

[0054] In a possible design of the fourth aspect, the information corresponding to the second network element comprises at least one of the following information that allows the traffic flow to be routed to the first local data network: FQDN, IP segment, service area, DNAI, or APP ID.

[0055] The scheme provides various forms of routing information, which can be applied to different application scenarios, and improves the flexibility of policy configuration.

[0056] In a possible design of the fourth aspect, the information corresponding to the second network element comprises a first parameter and a second parameter that allow the traffic flow to be routed to the first local data network, the first parameter is FQDN or IP segment, and the second parameter is service area, DNAI, or APP ID.

[0057] The scheme provides a new form of routing information, and by planning different first parameters and / or second parameters, different routing information can be planned.

[0058] In a possible design of the fourth aspect, the information that allows the traffic flow to be routed to at least one local data network comprises at least one of the following: FQDN, IP segment, service area, DNAI, or APP ID.

[0059] The scheme provides various forms of routing information, which can be applied to different application scenarios, and improves the flexibility of policy configuration.

[0060] In a possible design of the fourth aspect, the first message is used to request establishment of a session.

[0061] The scheme can be performed in a session establishment process, and can reuse messages in the session establishment process, thereby reducing signaling overhead.

[0062] In a possible design of the fourth aspect, the first message further comprises first indication information, and the first indication information is used to indicate authorization of the first information.

[0063] Based on the scheme, the indication information can be used to indicate that the first network element needs to authorize the first information, thereby avoiding the case that after the first network element receives the first information, the first network element does not know what to do.

[0064] In a fifth aspect, a communication method is provided, which can be performed by the fourth network element or by a module (e.g., a processor, a chip, or a chip system) applied to the fourth network element. The method includes: sending, by the fourth network element, a first policy to the first network element, where the first policy is used to indicate the following at least one information of the at least one local data network to which the traffic flow is allowed to be routed: a FQDN, an IP segment, a service area, a DNAI, or an APP ID. The first policy is used to determine information corresponding to the second network element, and the information corresponding to the second network element is used to determine whether the traffic flow is allowed to be routed to the first local data network managed by the second network element.

[0065] Based on the communication method provided in the embodiments of the present application, after the fourth network element sends the first policy to the first network element, the first network element can determine the information used to determine whether the traffic flow is allowed to be routed to the first local data network according to the first policy, in other words, the first network element can provide the targeted routing information (or referred to as the offloading information) for the local data network. Compared with the current network element that does not distinguish the offloading policy based on the local data network, but directly provides the offloading policy to each local data network below, the communication method provided in the embodiments of the present application can provide the isolated routing information for different local data networks, thereby improving the flexibility of policy deployment and meeting the needs of the network or the user more flexibly.

[0066] In a sixth aspect, a communication method is provided, which can be performed by the fourth network element or by a module (e.g., a processor, a chip, or a chip system) applied to the fourth network element. The method includes: receiving, by the fourth network element, a second message from the first network element, where the second message includes first information; the first information includes information of at least one local data network to which the traffic flow is allowed to be routed or at least one identifier, and each identifier in the at least one identifier is used to identify the information of one local data network in the at least one local data network to which the traffic flow is allowed to be routed. The fourth network element sends an authorization result or information corresponding to the second network element to the first network element, where the authorization result indicates that the authorization is successful or failed, and the information corresponding to the second network element is used to determine whether the traffic flow is allowed to be routed to the first local data network managed by the second network element.

[0067] Based on the communication method provided in the embodiments of the present application, the fourth network element can authorize the first information, and if the first information is successfully authorized, it indicates that the first information can be used to determine whether to allow the traffic flow to be routed to the first local data network. Alternatively, the first network element can directly provide the routing information of the first local data network (i.e., the information used to determine whether to allow the traffic flow to be routed to the first local data network). Therefore, in the communication method provided in the embodiments of the present application, the fourth network element can provide mutually isolated routing information for different local data networks, thereby improving the flexibility of policy deployment and meeting the requirements of the network or the user more flexibly.

[0068] With reference to the fifth aspect or the sixth aspect, in a possible design, the information corresponding to the second network element includes at least one of the following information that allows the traffic flow to be routed to the first local data network: FQDN, IP segment, service area, DNAI, or APP ID.

[0069] The present solution provides various forms of routing information, which can be suitable for different application scenarios and improves the flexibility of policy configuration.

[0070] With reference to the fifth aspect or the sixth aspect, in a possible design, the information corresponding to the second network element includes a first parameter and a second parameter that allow the traffic flow to be routed to the first local data network, the first parameter is FQDN or an IP segment, and the second parameter is a service area, DNAI, or APP ID.

[0071] The present solution provides a new form of routing information, and through this new form, different routing information can be planned by planning different first parameters and / or second parameters.

[0072] The seventh aspect provides a communication apparatus for implementing the method implemented by the first network element in the first aspect.

[0073] The communication apparatus includes modules, units, or means corresponding to the above method, which can be implemented by hardware, software, or by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0074] With reference to the above seventh aspect, in a possible design of the communication apparatus, the communication apparatus includes a transceiver and a processing module; the transceiver is configured to receive the first policy; the first policy is used to indicate information about whether to allow a service flow to be routed to at least one local data network; and the processing module is configured to determine information about the second network element according to the first policy. The transceiver is further configured to send the information about the second network element to the second network element; the second network element is configured to manage edge deployment information in the first local data network, and the information about the second network element is used to determine whether to allow the service flow to be routed to the first local data network.

[0075] With reference to the above seventh aspect, in a possible design of the communication apparatus, the information about the second network element includes at least one of the following information about whether to allow the service flow to be routed to the first local data network: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0076] With reference to the above seventh aspect, in a possible design of the communication apparatus, the information about the second network element includes a first parameter and a second parameter about whether to allow the service flow to be routed to the first local data network; the first parameter is an FQDN or an IP segment; and the second parameter is a service area, a DNAI, or an APP ID.

[0077] With reference to the above seventh aspect, in a possible design of the communication apparatus, the information about the second network element is determined according to the first policy and at least one of the following information supported by the second network element: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0078] With reference to the above seventh aspect, in a possible design of the communication apparatus, the information about whether to allow the service flow to be routed to at least one local data network includes at least one of the following information: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0079] With reference to the above seventh aspect, in a possible design of the communication apparatus, information about a third network element that manages a second local data network in the at least one local data network is different from the information about the second network element; and the processing module is further configured to determine information about the third network element according to the first policy, where the information about the third network element is used to determine whether to allow the service flow to be routed to the second local data network.

[0080] An eighth aspect provides a communication apparatus for implementing the method implemented by the first network element in the second aspect.

[0081] The communication apparatus includes modules, units, or means corresponding to the above method, which can be implemented by hardware, software, or by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0082] With reference to the eighth aspect above, in a possible design, the communication apparatus includes a transceiver module; the transceiver module is configured to receive a first message from a second network element, where the first message includes first information, and the second network element is configured to manage edge deployment information in a first local data network, and the first information includes information that allows a service flow to be routed to at least one local data network or at least one identifier that identifies the information that allows the service flow to be routed to the at least one local data network; and the transceiver module is further configured to send, to the second network element, an authorization result and / or information corresponding to the second network element, where the authorization result indicates authorization success or failure, and the information corresponding to the second network element is used to determine whether the service flow is allowed to be routed to the first local data network.

[0083] With reference to the eighth aspect above, in a possible design, the information that allows the service flow to be routed to the at least one local data network includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0084] With reference to the eighth aspect above, in a possible design, the information that allows the service flow to be routed to the at least one local data network includes a first parameter and a second parameter, the first parameter is an FQDN or an IP segment, and the second parameter is a service area, a DNAI, or an APP ID.

[0085] With reference to the eighth aspect above, in a possible design, the information corresponding to the second network element includes at least one of the following information that allows the service flow to be routed to the first local data network: an FQDN, an IP segment, a service area, a DNAI, or an APP ID; or the information corresponding to the second network element includes identifier information that identifies at least one of the following information that allows the service flow to be routed to the first local data network: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0086] With reference to the eighth aspect above, in a possible design, the communication apparatus further includes a processing module; the processing module is configured to authorize the first information to obtain the authorization result; or the processing module is configured to determine the information corresponding to the second network element.

[0087] With reference to the eighth aspect above, in a possible design, the transceiver module is further configured to send the first information to a fourth network element; and the transceiver module is further configured to receive an authorization result or the information corresponding to the second network element from the fourth network element.

[0088] With reference to the eighth aspect above, in a possible design, the authorization result or the information corresponding to the second network element is determined according to the first information, the first identification information supported by the second network element, and at least one of the following: FQDN, IP segment, service area, or DNAI; wherein the first identification information is used to identify at least one of the following: FQDN, IP segment, service area, DNAI, or APP ID.

[0089] With reference to the eighth aspect above, in a possible design, the first message is used to request establishment of a session.

[0090] With reference to the eighth aspect above, in a possible design, the first message further includes first indication information; the first indication information is used to indicate authorization of the first information.

[0091] With reference to the eighth aspect above, in a possible design, the information corresponding to a third network element that manages the second local data network of the at least one local data network is different from the information corresponding to the second network element, and the information corresponding to the third network element is used to determine whether to allow a service flow to be routed to the second local data network.

[0092] The ninth aspect provides a communication apparatus for implementing the method implemented by the second network element in the third aspect above.

[0093] The communication apparatus includes modules, units, or means corresponding to the above-described method, which can be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0094] With reference to the ninth aspect above, in a possible design, the communication apparatus includes a transceiver module and a processing module; wherein the transceiver module or the processing module is configured to obtain information corresponding to the communication apparatus; wherein the communication apparatus is configured to manage edge deployment information in a first local data network, and the information corresponding to the communication apparatus includes at least one of the following: service area, DNAI, or APP ID, which are used to allow a service flow to be routed to the first local data network; or the information corresponding to the communication apparatus includes at least one identification information, and the at least one identification information is used to identify at least one of the following: service area, DNAI, or APP ID, which are used to allow a service flow to be routed to the first local data network. The processing module is configured to configure a filtering rule of the service flow according to the information corresponding to the communication apparatus, and the filtering rule is used to determine whether to allow the service flow to be routed to the first local data network.

[0095] With reference to the ninth aspect above, in a possible design, the information corresponding to the communication apparatus further includes FQDN and / or IP segment, which are used to allow a service flow to be routed to the first local data network.

[0096] With reference to the ninth aspect above, in a possible design of the ninth aspect, the information corresponding to the communication device includes the first parameter and the second parameter allowing the traffic flow to be routed to the first local data network, the first parameter being an FQDN or an IP segment, and the second parameter being a service area, a DNAI, or an APP ID.

[0097] With reference to the ninth aspect above, in a possible design of the ninth aspect, the transceiver is further configured to send, to the fifth network element, the filtering rule of the traffic flow and the tunnel information; and the tunnel information includes at least one of the following: tunnel information of the anchor user plane function network element, tunnel information of the user plane function network element corresponding to the first local data network, or tunnel information of the access network.

[0098] With reference to the ninth aspect above, in a possible design of the ninth aspect, the transceiver or the processing module obtains the information corresponding to the second network element, including: the transceiver sends, to the first network element, a first message, and the first message includes the first information; the first information includes information allowing the traffic flow to be routed to at least one local data network or at least one identifier, each identifier in the at least one identifier being used to identify information allowing the traffic flow to be routed to one of the at least one local data network; the transceiver receives, from the first network element, an authorization result and / or the information corresponding to the communication device, the authorization result indicating authorization success or failure; and in a case where the transceiver receives the authorization result and the authorization result indicates authorization success, the processing module determines the first information as the information corresponding to the communication device.

[0099] With reference to the ninth aspect above, in a possible design of the ninth aspect, the first message is used to request establishment of a session.

[0100] With reference to the ninth aspect above, in a possible design of the ninth aspect, the information allowing the traffic flow to be routed to the at least one local data network includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0101] With reference to the ninth aspect above, in a possible design of the ninth aspect, the first message further includes first indication information, and the first indication information is used to indicate authorization of the first information.

[0102] The tenth aspect provides a communication device for implementing the method implemented by the second network element in the fourth aspect.

[0103] The communication device includes modules, units, or means corresponding to the method, which can be implemented by hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions.

[0104] In a possible design of the tenth aspect, the communication device includes a transceiver module and a processing module; the transceiver module is configured to send a first message to the first network element, where the first message includes first information; the first information includes information that allows a service flow to be routed to at least one local data network or at least one identifier, each of the at least one identifier is used to identify information that allows a service flow to be routed to one of the at least one local data network; the transceiver module is further configured to receive an authorization result and / or information corresponding to the communication device from the first network element, where the authorization result indicates authorization success or failure, and the information corresponding to the communication device is used to determine whether a service flow is allowed to be routed to a first local data network managed by the communication device; and the processing module is configured to determine the first information as information corresponding to the second network element, in a case where the transceiver module receives the authorization result and the authorization result indicates authorization success.

[0105] In a possible design of the tenth aspect, the information corresponding to the communication device includes at least one of the following information that allows a service flow to be routed to the first local data network: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0106] In a possible design of the tenth aspect, the information corresponding to the communication device includes a first parameter and a second parameter that allow a service flow to be routed to the first local data network, the first parameter is an FQDN or an IP segment, and the second parameter is a service area, a DNAI, or an APP ID.

[0107] In a possible design of the tenth aspect, the information that allows a service flow to be routed to the at least one local data network includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID.

[0108] In a possible design of the tenth aspect, the first message is used to request establishment of a session.

[0109] In a possible design of the tenth aspect, the first message further includes first indication information, where the first indication information is used to indicate authorization of the first information.

[0110] An eleventh aspect provides a communication device for implementing the method implemented by the fourth network element in the fifth aspect.

[0111] The communication device includes modules, units, or means corresponding to the method, which can be implemented by hardware, software, or by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the above functions.

[0112] With reference to the eleventh aspect above, in a possible design, the communication apparatus includes a transceiver module; and the transceiver module is configured to send the first policy to the first network element, where the first policy is used to indicate the following at least one information of the at least one local data network to which the traffic flow is allowed to be routed: FQDN, IP segment, service area, DNAI or APP ID. The first policy is used to determine the information corresponding to the second network element, and the information corresponding to the second network element is used to determine whether the traffic flow is allowed to be routed to the first local data network managed by the second network element.

[0113] The twelfth aspect provides a communication apparatus for implementing the method implemented by the fourth network element in the sixth aspect above.

[0114] The communication apparatus includes modules, units or means corresponding to the above method, which can be implemented by hardware, software or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions.

[0115] With reference to the twelfth aspect above, in a possible design, the communication apparatus includes a transceiver module; and the transceiver module is configured to receive a second message from the first network element, where the second message includes the first information; the first information includes the information of the at least one local data network to which the traffic flow is allowed to be routed or at least one identifier, and each identifier in the at least one identifier is used to identify the information of one of the at least one local data network to which the traffic flow is allowed to be routed. The processing module is configured to authorize the first information to obtain an authorization result; or the processing module is configured to determine the information corresponding to the second network element. The transceiver module is further configured to send the authorization result or the information corresponding to the second network element to the first network element, where the authorization result indicates authorization success or failure, and the information corresponding to the second network element is used to determine whether the traffic flow is allowed to be routed to the first local data network managed by the second network element.

[0116] With reference to the eleventh aspect or the twelfth aspect above, in a possible design, the information corresponding to the second network element includes the following at least one information of the first local data network to which the traffic flow is allowed to be routed: FQDN, IP segment, service area, DNAI or APP ID.

[0117] With reference to the eleventh aspect or the twelfth aspect above, in a possible design, the information corresponding to the second network element includes a first parameter and a second parameter of the first local data network to which the traffic flow is allowed to be routed, the first parameter is FQDN or IP segment, and the second parameter is service area, DNAI or APP ID.

[0118] In a thirteenth aspect, a communication apparatus is provided, which comprises a processor, configured to execute the instructions stored in a memory, and when the instructions are executed by the processor, the communication apparatus performs the method in any one of the aspects above. The communication apparatus can be the first network element or a module (for example, a chip) applied to the first network element in the first aspect to the second aspect or any possible design of the first aspect to the second aspect. Alternatively, the communication apparatus can be the second network element or a module (for example, a chip) applied to the second network element in the third aspect to the fourth aspect or any possible design of the third aspect to the fourth aspect. Alternatively, the communication apparatus can be the fourth network element or a module (for example, a chip) applied to the fourth network element in the fifth aspect to the sixth aspect or any possible design of the fifth aspect to the sixth aspect.

[0119] In a possible design of the communication apparatus, the communication apparatus further comprises a memory, configured to store the computer program or instructions. Optionally, the processor and the memory are integrated together, or the processor and the memory are separately arranged.

[0120] In a possible design of the communication apparatus, the memory is coupled with the processor and is outside the communication apparatus.

[0121] In a fourteenth aspect, a communication apparatus is provided, which comprises a processor and an interface circuit, configured to communicate with a module outside the communication apparatus; and the processor is configured to perform the method in any one of the aspects above by means of a logic circuit, or by running a computer program or instructions. The communication apparatus can be the first network element or a module (for example, a chip) applied to the first network element in the first aspect to the second aspect or any possible design of the first aspect to the second aspect. Alternatively, the communication apparatus can be the second network element or a module (for example, a chip) applied to the second network element in the third aspect to the fourth aspect or any possible design of the third aspect to the fourth aspect. Alternatively, the communication apparatus can be the fourth network element or a module (for example, a chip) applied to the fourth network element in the fifth aspect to the sixth aspect or any possible design of the fifth aspect to the sixth aspect.

[0122] Alternatively, the interface circuit can be a code / data read-write interface circuit, configured to receive computer execution instructions (the computer execution instructions are stored in a memory, and can be directly read from the memory or can pass through other devices) and transmit the computer execution instructions to the processor, so that the processor runs the computer execution instructions to perform the method in any one of the aspects above.

[0123] In a possible design of the communication apparatus, the communication apparatus further comprises a memory, configured to store the computer program or instructions. Optionally, the processor and the memory are integrated together, or the processor and the memory are separately arranged.

[0124] In a possible design, the memory is coupled with the processor and is outside the communication apparatus.

[0125] In some possible designs, the communication apparatus can be a chip or a chip system.

[0126] In a fifteenth aspect, the present application provides a computer readable storage medium, which stores instructions. When the instructions are run on a computer, the computer can execute the method in the first aspect to the sixth aspect or any possible design of the first aspect to the sixth aspect.

[0127] In a sixteenth aspect, the present application provides a computer program product containing instructions. When the instructions are run on a computer, the computer can execute the method in the first aspect to the sixth aspect or any possible design of the first aspect to the sixth aspect.

[0128] In a seventeenth aspect, a communication apparatus (for example, the communication apparatus can be a chip or a chip system) is provided. The communication apparatus includes a processor, which is configured to implement the functions in the first aspect to the sixth aspect or any possible design of the first aspect to the sixth aspect. In a possible design, the communication apparatus further includes a memory, which is configured to store necessary program instructions and data. When the communication apparatus is a chip system, the communication apparatus can be composed of a chip or can include a chip and other discrete devices.

[0129] In an eighteenth aspect, a communication system is provided. The communication system includes a first network element and a second network element. In a possible design, the first network element is configured to implement the method in the first aspect or any possible design of the first aspect, and the second network element is configured to receive information corresponding to the second network element. Optionally, the communication system further includes a fourth network element. The fourth network element is configured to implement the method in the fifth aspect or any possible design of the fifth aspect.

[0130] In another possible design, the first network element is configured to implement the method in the second aspect or any possible design of the second aspect, and the second network element is configured to implement the method in the fourth aspect or any possible design of the fourth aspect. Optionally, the communication system further includes a fourth network element. The fourth network element is configured to implement the method in the sixth aspect or any possible design of the sixth aspect.

[0131] In yet another possible design, the second network element is configured to implement the method in the third aspect or any possible design of the third aspect, and the first network element is configured to send the first policy or information corresponding to the second network element to the second network element. Optionally, the communication system further includes a fourth network element. The fourth network element is configured to send the first policy to the first network element.

[0132] The technical effects brought by any one of the design manners of the seventh aspect to the eighteenth aspect can refer to the technical effects brought by the different design manners of the first aspect to the sixth aspect, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0133] FIG. 1 is a schematic diagram of an architecture of a communication system provided by an embodiment of the present application;

[0134] FIG. 2 is a schematic diagram of an interaction of a communication method provided by an embodiment of the present application;

[0135] FIG. 3 is a schematic diagram of a first network element distributing routing information to different I-SMF network elements provided by an embodiment of the present application;

[0136] FIG. 4 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0137] FIG. 5 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0138] FIG. 6 is a schematic diagram of an interaction of another communication method provided by an embodiment of the present application;

[0139] FIG. 7 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0140] FIG. 8 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0141] FIG. 9 is a schematic diagram of an interaction of still another communication method provided by an embodiment of the present application;

[0142] FIG. 10 is a schematic diagram of a flow of a communication method provided by an embodiment of the present application;

[0143] FIG. 11 is a schematic diagram of a structure of a communication apparatus provided by an embodiment of the present application;

[0144] FIG. 12 is a schematic diagram of a structure of another communication apparatus provided by an embodiment of the present application;

[0145] FIG. 13 is a schematic diagram of a structure of a chip system provided by an embodiment of the present application. DETAILED DESCRIPTION

[0146] In order to facilitate understanding of the technical solutions of the embodiments of the present application, first, a brief introduction of the related technologies of the present application is given as follows.

[0147] 1. Offloading policy in MEC:

[0148] For some services with low latency and large bandwidth requirements, such as virtual reality (VR), cloud gaming, or industrial automation, deploying application services at the edge of the network can provide better service experience to users. Such application services deployed at the edge of the data network can be referred to as edge application services (EAS). The edge data network where the EAS is deployed can also be referred to as a local data network (L-DN) / (local area data network, LADN). Hereinafter, L-DN is used as an abbreviation for local data network. In actual applications, the abbreviation for local data network can also be LADN.

[0149] MEC is a network architecture that can provide edge application services for terminal devices. In the current MEC, edge deployment information (EDI) in the local data network is managed by an intermediate session management (I-SMF) network element. The edge deployment information can refer to existing standards, for example, the edge deployment information can include at least one of the following information: IP segment, FQDN, service area, DNAI or APP ID, etc. which will not be repeated here. The I-SMF network element can also manage and control edge applications (EAS) in the local data network.

[0150] In MEC, the PCF / SMF network element can provide an offload policy to the I-SMF network element. The offload policy is used to determine whether a service flow can be offloaded (or understood as routed) to the corresponding local data network. Based on the offload policy, the service flow that cannot be routed to the local data network can be routed to the central data network.

[0151] In this article, the offload policy can also be referred to as offload information, routing policy, or routing information, etc.

[0152] Currently, the offload policy includes IP segment / FQDN. Taking the offload policy including FQDN as an example, if the FQDN of the service flow matches the FQDN included in the offload policy, that is, the FQDN of the service flow is one of the FQDN included in the offload policy, the service flow can be routed to the local data network. If the FQDN of the service flow does not match the FQDN included in the offload policy, that is, there is no FQDN of the service flow in the FQDN included in the offload policy, the service flow cannot be routed to the local data network. Taking the offload policy including IP segment as an example, if the IP address of the service flow matches the IP segment included in the offload policy, that is, the IP address of the service flow is contained in any IP segment included in the offload policy, the service flow can be routed to the local data network. If the IP address of the service flow does not match the IP segment included in the offload policy, that is, the IP address of the service flow is not contained in any IP segment included in the offload policy, the service flow cannot be routed to the local data network, but can be routed to the central data network. Generally, the area managed by the PCF / SMF network element is large (for example, the PCF / SMF network element manages multiple provinces / cities / parks), and there are likely to be multiple local data networks in the area managed by the PCF / SMF network element. Currently, the PCF / SMF network element provides the same offload policy to each I-SMF network element in the managed area. In other words, the PCF / SMF network element configures the same offload policy for different local data networks in the area managed by the PCF / SMF network element. This configuration method has the following problems: when the terminal device moves in different areas, because the local data networks in different areas configure the same offload policy, it may cause different local applications in different areas to all open or all reject the terminal device access, and cannot flexibly meet the needs of operators or users. For example, assuming that the area managed by the PCF has park A and park B, the terminal device is trusted for park A, and the operator authorizes the terminal device to access the local application deployed in park A. The local application is also deployed in park B, but the operator does not authorize the terminal device to access the local application deployed in park B. The PCF network element determines the offload policy based on the authorization information provided by the operator and provides the offload policy to different I-SMF network elements managing park A and park B. Because park A and park B are configured with the same offload policy, when the terminal device is located in park B, the network can still route the service flow of the terminal device to the local application deployed in park B based on the configured offload policy, but this cannot meet the needs of the operator who originally wants to control whether the terminal device can access the local application deployed in different parks by whether the terminal device is authorized.

[0153] It can be seen that the current offloading policy configuration mode does not consider the isolation and deployment flexibility requirements of the policy. Based on this problem, the communication method provided in the embodiments of the present application can configure a targeted offloading policy for a local data network (for example, different offloading policies are configured for different local data networks), realize the isolation of the offloading policy, and improve the configuration flexibility of the offloading policy.

[0154] In the description of the embodiments of the present application, unless otherwise specified, " / " represents that the objects before and after the " / " are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. In addition, in the description of the present application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or the like means any combination of the items, including any combination of single item or multiple items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the same items or similar items with basically the same functions and effects are distinguished by using "first", "second", etc. The skilled in the art can understand that "first", "second", etc. do not limit the quantity and execution order, and "first", "second", etc. also do not limit the difference. At the same time, in the embodiments of the present application, "exemplary" or "for example" is used to represent as an example, illustration or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, "exemplary" or "for example" is used to present the relevant concept in a specific manner, and to facilitate understanding.

[0155] In the embodiments of the present application, the indication can include direct indication and indirect indication, and can also include explicit indication and implicit indication. The information indicated by certain information is referred to as to-be-indicated information. In the implementation process, there are many ways to indicate the to-be-indicated information, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or an index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an association relationship. The to-be-indicated information can also be indicated only by a part of the to-be-indicated information, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, a protocol), thereby reducing the indication overhead to a certain extent. Meanwhile, a common part of each information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separately indicating the same information.

[0156] It should be understood that the to-be-indicated information can be sent as a whole or can be divided into multiple sub-information and sent separately, and the sending period and / or sending occasion of the sub-information can be the same or different. The specific sending method is not limited in the embodiments of the present application. The sending period and / or sending occasion of the sub-information can be pre-defined, for example, pre-defined according to a protocol, or configured by the sending end device by sending configuration information to the receiving end device.

[0157] In the embodiments of the present application, the pre-definition, pre-definition, pre-configuration, pre-configuration or local configuration can be implemented by pre-saving corresponding codes, tables or other information indicating methods in the device, for example, can be burned in the device when the device is manufactured, or configured when the device accesses the network for the first time, and the specific implementation method is not limited in the embodiments of the present application. The storage can be stored in one or more memories. The one or more memories can be separately set, or integrated in the encoder or decoder, processor, or communication device. The one or more memories can be part of the separately set, and part of the integrated in the decoder, processor, or communication device. The type of the memory can be any form of storage medium, and the present application is not limited thereto.

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

[0159] In the embodiments of the present application, "sending information to (for example, the first network element) can be understood as that the destination of the information is the first network element. It can include directly or indirectly sending information to the first network element. "Receiving information from (for example, the first network element) can be understood as that the source of the information is the first network element, and it can include directly or indirectly receiving information from the first network element. The information between the source and the destination of the information sending can be processed as necessary, for example, format change, etc., but the destination can understand the valid information from the source. Similar expressions in the embodiments of the present application can be similarly understood, and will not be repeated here.

[0160] The technical solutions provided by the present application can be used in various communication systems, for example, long term evolution (LTE) system, 4th generation (4G) mobile communication system, 5th generation (5G) mobile communication system and its evolution system, non-terrestrial network (NTN) system, vehicle to everything (V2X) system, LTE and new radio (NR) hybrid networking system, or device-to-device (D2D) system, machine to machine (M2M) communication system, internet of things (IoT), and future communication systems. In addition, the term "system" can be replaced by "network".

[0161] It should be noted that the network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0162] It should be noted that the network element appearing in the present document is only a possible example name. If the actual name used by the network element in the subsequent communication network is different from the name appearing in the present document, it does not affect the application of the communication method provided by the embodiments of the present application.

[0163] Take the application example applied to the 5G system as an example, Fig. 1 is a possible, non-limiting architecture of a communication system to which embodiments of the application are applicable. The communication system to which embodiments of the application are applicable includes a terminal device, a core network (CN) and an access network (AN). Logically, the core network can be divided into two parts, the user plane and the control plane, the control plane is responsible for the management of the mobile network, and the user plane is responsible for the transmission of service data.

[0164] As shown in Fig. 1, in the communication system, the core network user plane function (UPF) network element, together with the access network device (AN in Fig. 1) and the terminal device, forms the user plane network element of the 5G system (5GS). The core network control plane mainly includes the following network elements: core access and mobility management function (AMF) network element, session management function (SMF) network element, network exposure function (NEF) network element, network function repository function (NRF), policy control function (PCF) network element, unified data management (UDM) network element, edge application service discovery function (EASDF) network element. The functions of these network elements can refer to the existing standards and will not be described here.

[0165] As shown in Fig. 1, the communication system can also include an EAS. The EAS can be deployed in a local data network. Optionally, the EAS can be controlled by an operator or a third party. For example, the entity providing the EAS can be a server. For example, in the MEC scenario, the EAS can be provided by an edge computing server, or in other words, the EAS can be deployed on an edge computing server. The server providing the EAS can also be referred to as an EAS server.

[0166] As shown in Fig. 1, the communication system can also include a second network element. The second network element can be used to manage the edge deployment information of the local data network.

[0167] Optionally, the second network element can be a newly defined network element. Alternatively, the second network element can also be an existing network element. For example, the second network element can be an I-SMF network element. As shown in FIG. 1, the second network element can be an I-SMF network element connected with the AMF network element and the SMF network element.

[0168] As shown in FIG. 1, in the UPF network element in the communication system, a local UPF network element can be included. The local UPF network element is a user plane function network element connected with the EAS. When the application that the terminal device wants to access has deployed the EAS in the L-DN, or the network provides the EAS for the terminal device, the local UPF network element can be used to provide the connection for the terminal device.

[0169] It can be understood that the local UPF network element is an exemplary name provided by the embodiments of the present application for the user plane function network element connected with the EAS. If the name actually used by the user plane function network element connected with the EAS in the communication system is not the local UPF network element, it does not affect the application of the communication method provided by the embodiments of the present application. For example, the local UPF network element can also be referred to as a local PDU session anchor UPF (which can be referred to as L-PSA UPF for short) network element.

[0170] As shown in FIG. 1, in the UPF network element in the communication system, a remote UPF network element can be included. The remote UPF network element is a user plane function network element connected with the central DN.

[0171] It can be understood that the remote UPF network element is an exemplary name provided by the embodiments of the present application for the user plane function network element connected with the central DN. If the name actually used by the user plane function network element connected with the central DN in the communication system is not the remote UPF network element, it does not affect the application of the communication method provided by the embodiments of the present application. For example, the remote UPF network element can also be referred to as a central PDU session anchor (PSA) UPF (which can be referred to as C-PSA UPF for short) network element.

[0172] Optionally, when the terminal device is located in an area not managed by the session management network element, an I-SMF network element can be inserted to find the session management network element supporting the session.

[0173] As shown in FIG. 1, in the UPF network element in the communication system, an uplink classifier / branching point UPF (ULCL / BP UPF) network element can be included (FIG. 1 shows the ULCL / BP UPF network element as UPF (ULCL / BP)). The ULCL / BP UPF network element can be connected to the L-PSA UPF network element and the remote UPF network element at the same time.

[0174] In some possible architectures, the second network element can also manage a local user plane function network element and / or an edge application service. For example, the second network element in FIG. 1 can manage the L-UPF network element and / or the EAS.

[0175] It should be noted that FIG. 1 only exemplarily shows some examples of network elements or entities in the communication system, and the communication system can also include some network elements or entities that are not shown in FIG. 1, which are not limited herein. For example, the communication system can also include an application function (AF) network element.

[0176] As shown in FIG. 1, the terminal device accesses the network through the AN device, and the terminal device communicates with the AMF network element through an N1 interface (N1 for short); the AN device communicates with the AMF network element through an N2 interface (N2 for short); the AN device communicates with the ULCL / BP UPF network element through an N3 interface (N3 for short); an entity providing the EAS can communicate with the L-UPF network element through an N6 interface (N6 for short); the second network element can communicate with the UPF network element through an N4 interface (N4 for short), for example, can communicate with the ULCL / BP UPF network element through the N4 interface, and can also communicate with the L-UPF network element through the N4 interface; the SMF network element can communicate with the remote UPF network element through the N4 interface; and the remote UPF network element can communicate with the central data network through the N6 interface.

[0177] In addition, the core network control plane network elements shown in FIG. 1 interact using service interfaces. For example, the service interface provided by the AMF network element to the outside is Namf; the service interface provided by the SMF network element to the outside is Nsmf; the service interface provided by the second network element to the outside is Nsmf; the service interface provided by the NEF network element to the outside is Nnef; the service interface provided by the NRF network element to the outside is Nnrf; the service interface provided by the PCF network element to the outside is Npcf; the service interface provided by the UDM network element to the outside is Nudm; and the service interface provided by the EASDF network element to the outside is Nasdf. The related function description and interface description can refer to the existing standards, and will not be described herein.

[0178] All or part of the functions of the network element or device in the embodiments of the present application can also be implemented by software functions running on hardware, or by virtualized functions instantiated on a platform (such as a cloud platform). The network element in the embodiments of the present application can also be a logical node, a logical module or software that can implement all or part of the functions of the network element.

[0179] The access network device, which can also be referred to as an AN entity or an access node, constitutes part of a communication system and is used to help terminal devices access the network. In a possible scenario, the access network device can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a wireless fidelity (WiFi) system, etc. The access network device can be a macro base station, a micro base station or an indoor station, a relay node or a donor node, or a wireless controller in a cloud radio access network (C-RAN) scenario. Optionally, the access network device can also be a server, a wearable device, a vehicle or a vehicle-mounted device, etc. For example, the access network device in V2X technology can be a road side unit (RSU).

[0180] In another possible scenario, multiple access network devices cooperate to assist terminal devices to access, and different access network devices respectively implement part of the functions of a base station. For example, the access network device can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU), etc. The CU and the DU can be separately arranged, or can be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a radio frequency remote unit (RRU), an active antenna processing unit (AAU) or a remote radio head (RRH).

[0181] In different systems, the CU (or CU-CP and CU-UP), DU or RU can also have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN), the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. For the convenience of description, the CU, CU-CP, CU-UP, DU and RU are taken as examples for description in the embodiments of the present application. Any one of the CU (or CU-CP, CU-UP), DU and RU in the embodiments of the present application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0182] The terminal device can also be referred to as a terminal, a user equipment (UE), a mobile station, a mobile terminal, etc. The terminal device can be widely applied to various scenarios, such as D2D, V2X communication, machine-type communication (MTC), Internet of Things, virtual reality (VR), augmented reality (AR), industrial control, self driving, remote medical, smart grid, smart furniture, smart office, smart wear, smart transportation or smart city, etc. The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, a vehicle, a drone, a helicopter, an airplane, a ship, a robot, a mechanical arm, a smart home device, etc. The embodiments of the present application do not limit the device form of the terminal device.

[0183] The communication method provided by the embodiments of the present application will be described below in combination with the architecture of the communication system shown in FIG. 1.

[0184] It can be understood that in the following embodiments of the present application, the names of various network elements, the names of messages exchanged between various network elements, the names of various parameters, or the names of various information, etc. are only examples, and in other embodiments, they can also be other names, and the method provided by the present application does not specifically limit this.

[0185] It can be understood that in the following embodiments of the present application, each item of information / parameter can include one or more specific values. The information / parameter (s) can be used to indicate that the item of information / parameter has one or more specific values. Taking DNAI as an example, DNAI (s) can indicate that there is one or more DNAI.

[0186] It can be understood that, in the following embodiments of the present application, the values included in each item of information / parameter can also be referred to as the range of each item of information / parameter. Taking FQDN as an example, FQDN(s) can also be referred to as the range of FQDN.

[0187] It can be understood that, in the embodiments of the present application, each network element or entity can perform part or all of the steps in the embodiments of the present application, and these steps or operations are only examples, and the embodiments of the present application can also perform other operations or variations of various operations. In addition, each step can be performed in a different order from that presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application are performed.

[0188] As shown in FIG. 2, a communication method provided by the embodiments of the present application is shown. In FIG. 2, the first network element and the second network element are taken as an example to illustrate the execution subject of the flowchart, but the present application does not limit the execution subject of the flowchart. For example, the first network element in FIG. 2 can also be a module applied to the first network element, such as a chip, a chip system, or a processor, and can also be a logical node, a logical module, or software that can realize all or part of the functions of the first network element. The second network element in FIG. 2 can also be a module applied to the second network element, such as a chip, a chip system, or a processor, and can also be a logical node, a logical module, or software that can realize all or part of the functions of the second network element.

[0189] Referring to FIG. 2, the communication method includes steps S201-S203:

[0190] S201, the first network element receives a first policy from a fourth network element (FIG. 2 illustrates the fourth network element as a third network element); the first policy is used to indicate information allowing a service flow to be routed to at least one local data network.

[0191] The embodiments of the present application do not limit the first network element, and the first network element can be an SMF network element, for example.

[0192] The at least one local data network corresponding to the information indicated by the first policy can be at least one local data network in the area managed by the first network element (which can also be referred to as the area of the service). The information indicated by the first policy can also be understood as information allowing a service flow to be routed to an EAS in at least one local data network, or information allowing a service flow to be routed to an EAS in the area managed by the first network element.

[0193] The following will be expanded to introduce S201.

[0194] In S201, the first policy is an exemplary name provided by the embodiments of the present application, and in actual application, other names can also be used, for example, the first policy can also be referred to as an offloading policy, a routing policy, a local offloading policy, a local offloading control policy, etc., and the embodiments of the present application do not limit the name of the first policy.

[0195] The first policy can also be understood as a policy of offloading a service flow to a local data network. Alternatively, the first policy is a split policy configured by a network element providing the first policy for at least one local data network in a managed area.

[0196] The first policy is used to indicate information of allowing a service flow to be routed to at least one local data network. Optionally, the first policy can indicate at least one of the following information: an FQDN, an IP segment, a service area, a data network access identifier (DNAI) or an application identity (APP ID).

[0197] The embodiments of the present application do not limit the form of the information of allowing a service flow to be routed to at least one local data network indicated by the first policy. Exemplarily, the form of the information of allowing a service flow to be routed to at least one local data network indicated by the first policy can be any of the following:

[0198] (1) an IP segment / FQDN. In other words, the first policy can indicate an IP segment / FQDN of allowing a service flow to be routed to at least one local data network.

[0199] For example, the first policy can indicate FQDN1, FQDN2 and FQDN3. For another example, the first policy can indicate IP segment1, IP segment2 and IP segment3. If the first policy indicates an IP segment, the first policy can indicate a start IP address-end IP address of the IP segment.

[0200] If the first policy indicates the information in the form of (1), the network element providing the first policy can plan the first policy based on an applied IP segment / FQDN.

[0201] (2) a service area / DNAI / APP ID. In other words, the first policy can indicate a service area / DNAI / APP ID of allowing a service flow to be routed to at least one local data network. The DNAI can also be replaced by a DNAI prefix.

[0202] For example, the first policy can indicate service area 1, service area 2, and service area 3. For another example, the first policy can indicate DNAI1, DNAI2, and DNAI3. For another example, the first policy can indicate APP ID1, APP ID2, and APP ID3.

[0203] If the first policy indicates information in the form shown in (1), the network element providing the first policy can plan the first policy based on the service area, the APP ID, or the DNAI of the application accessed by the network element. Since the service area / DNAI / APP ID is not frequently updated, the network element providing the first policy does not need to frequently update the first policy.

[0204] (3), IP segment / FQDN, and service area / DNAI / APP ID. In other words, the first policy can indicate the first parameter and the second parameter allowing the traffic flow to be routed to at least one local data network, wherein the first parameter is IP segment / FQDN, and the second parameter is service area / DNAI.

[0205] For example, the first policy can indicate FQDN1, FQDN2, FQDN3, service area 1, service area 2, and service area 3. For another example, the first policy can indicate IP segment 1, IP segment 2, IP segment 3, DNAI1, DNAI2, and DNAI3. For another example, the first policy can indicate FQDN1, FQDN2, FQDN3, DNAI1, DNAI2, and DNAI3. For another example, the first policy can indicate IP segment 1, IP segment 2, IP segment 3, service area 1, service area 2, and service area 3.

[0206] If the first policy indicates information in the form shown in (3), the network element providing the first policy can plan the first policy based on the first parameter and / or the second parameter, based on which, when a certain parameter planned for an application overlaps (for example, IP segment / FQDN), different first policies can be planned by planning different another parameter. For example, the network element providing the first policy configures the first policy for an application in a certain area, and the first policy includes IP segment 1, IP segment 2, IP segment 3, service area 1, service area 2, and service area 3. When the network element configures the first policy for an application in another area, the network element can configure the same IP segment: IP segment 1, IP segment 2, and IP segment 3, and different service areas: service area 4, service area 5, and service area 6, so that the network element can configure different first policies for applications in different areas by configuring different service areas when the IP segments overlap.

[0207] The present solution provides multiple forms of the information indicated by the first policy, and the first network element can provide corresponding policies for the local data network based on different forms of the information indicated by the first policy, facilitating management. For example, if the form of the information indicated by the first policy is as described in (1) above, the first network element can provide different routing information for different local data networks by planning different IP segments / FQDNs for different local data networks. For another example, if the form of the information indicated by the first policy is as described in (2) above, the first network element can provide different routing information for different local data networks by planning different service areas / DNAIs / APP IDs for different local data networks. For another example, if the form of the information indicated by the first policy is as described in (3) above, the first network element can provide different routing information for different local data networks by planning different first parameters and / or second parameters for different local data networks. For example, the first network element can plan the same IP segment for different local data networks, but provide different routing information for different local data networks by planning different service areas.

[0208] For the information indicated by the first policy to allow the traffic flow to be routed to the at least one local data network, in one possible implementation, the first policy can include the information to allow the traffic flow to be routed to the at least one local data network. For example, the first policy can include the information in the form described in (1), (2), or (3) above. In this implementation, the first network element can directly determine the information included in the first policy as the information to allow the traffic flow to be routed to the at least one local data network.

[0209] In another possible implementation, the first policy can include at least one identification information. The identification information corresponds to the preconfigured local offloading information on the first network element, and the first network element can determine, as the information to allow the traffic flow to be routed to the at least one local data network, the local offloading information corresponding to the identification information in the preconfigured local offloading information. That is, the identification information can identify (or be understood as indicating) the local offloading information, and the first network element can determine, as the information to allow the traffic flow to be routed to the at least one local data network, the local offloading information identified by the identification information.

[0210] In the present solution, the local offloading information is an exemplary name provided by the embodiments of the present application, and in actual applications, can be other names, such as offloading information, routing information, local routing information, etc., which are not limited by the embodiments of the present application.

[0211] Based on the present solution, the information to allow the traffic flow to be routed to the at least one local data network can be identified by the identification information, and therefore, the network elements can provide routing information for the local data network by transmitting the identification information, which can reduce the overhead.

[0212] Exemplarily, in the implementation, the identification information included in the first policy can be referred to as a local offloading identity (LOID). That is, the first policy includes LOID(s) (indicating at least one LOID), and the LOID(s) corresponds to the preconfigured local offloading information on the first network element.

[0213] The following describes an embodiment of the method shown in FIG. 2 by taking the identification information as an example of the LOID. Of course, the identification information can also have other names, and the embodiments of the present application do not limit this.

[0214] In addition, in another embodiment of the method introduced below, the LOID can also correspond to the preconfigured local offloading information on the second network element, which will be described below, and will not be expanded here.

[0215] Optionally, the LOID can correspond to the information in the form of (1), (2), or (3) shown above, which is preconfigured on the first network element.

[0216] In the implementation in which the first policy includes LOID(s), the first network element can determine, based on the LOID(s) included in the first policy and the preconfigured first mapping relationship, information corresponding to the LOID(s) included in the first policy in the first mapping relationship as information allowing the service flow to be routed to the at least one local data network. The first mapping relationship includes a correspondence between the LOID(s) and the information allowing the service flow to be routed to the at least one local data network.

[0217] Exemplarily, assuming that the LOID is used to identify the information in the form of (1) shown above, the first policy includes LOID1, and the first mapping relationship preconfigured by the first network element includes LOID1 and the corresponding IP segment 1 / FQDN1.

[0218] Exemplarily, assuming that the LOID is used to identify the information in the form of (2) shown above, the first policy includes LOID1, and the first mapping relationship preconfigured by the first network element includes LOID1 and the corresponding service area 1 / DNAI1 / APP ID1.

[0219] Exemplarily, assuming that the LOID is used to identify the information in the form of (3) shown above, and taking the information in the form of (3) shown above including the IP segment and the service area as an example, the first policy includes LOID1, and the first mapping relationship preconfigured by the first network element includes LOID1 and the corresponding IP segment 1 and service area 1.

[0220] It can be understood that the above example of the LOID is taken as an example of the first policy including one LOID, and in actual application, the LOID can be multiple. Any item of information (for example, an IP segment, a DNAI, a service area, and the like) in the local offloading information preconfigured by the first network element can also include multiple values (or can also be one value, and the embodiments of the present application do not limit this). In other words, the local offloading information preconfigured by the first network element can include at least one of an IP segment (s), an FQDN (s), a DNAI (s), a service area (s), and an APP ID (s).

[0221] Optionally, one LOID can correspond to multiple values of the local offloading information preconfigured by the first network element. For example, assuming that the LOID is used to identify the information in the form shown in (1) above, the first policy includes LOID1, and in the first mapping relationship preconfigured by the first network element, LOID1 can correspond to IP segment 1 and IP segment 2.

[0222] In S201, the first network element can receive the first policy from the fourth network element. Exemplarily, the fourth network element can be a policy control function network element, or can also be another network element that can generate a policy.

[0223] For the first network element receiving the first policy from the fourth network element, optionally, the fourth network element can send the first policy to the first network element based on a message from the first network element. Or, the fourth network element can actively send the first policy to the first network element. The following are introduced respectively.

[0224] Implementation I: The first network element sends a certain message to the fourth network element. After receiving the message, the fourth network element sends the first policy to the first network element based on the trigger of the message.

[0225] Optionally, in implementation I, the message sent by the first network element to the fourth network element can include indication information indicating that the first policy is sent. The fourth network element sends the first policy to the first network element based on the received indication information. Exemplarily, the indication information can be referred to as a local offloading control indication (local offloading indication).

[0226] Or, the message sent by the first network element to the fourth network element can be a request message requesting to send the first policy.

[0227] The embodiments of the present application do not limit the message sent by the first network element to the fourth network element in implementation I. For example, the first network element can send a session management (SM) control policy request (SM policy control create) message to the fourth network element.

[0228] In the embodiments of the present application, the message sent by the network element can also be referred to as a service invoked by the network element. For example, the first network element sends the SM control policy request message, which can also be referred to as the first network element invoking the SM control policy request service.

[0229] Optionally, the implementation one can be applied in a PDU session establishment process.

[0230] Optionally, in the implementation one, the first network element sending the message to the fourth network element can be triggered by a certain message from the second network element, and the message can carry indication information indicating sending of the first policy. For example, the message can carry a local offloading control indication. Alternatively, the message can be a request message requesting sending of the first policy.

[0231] For example, the second network element can send a PDU session establishment request to the first network element, where the PDU session establishment request carries a local offloading control indication. After receiving the local offloading control indication, the first network element sends an SM control policy request to the fourth network element, where the SM control policy request carries the local offloading control indication.

[0232] Optionally, in the implementation one, after the second network element sends the information indicating sending of the first policy to the first network element, the first network element can obtain session management (SM) subscription data. If the subscription data includes authorization information authorizing the first network element to obtain the first policy, the first network element can send a message to the fourth network element to trigger the fourth network element to return the first policy. For example, the first network element can obtain the subscription data from a unified data management network element, and if the subscription data includes the authorized local offloading control indication, the first network element can send a message to the fourth network element.

[0233] Optionally, the subscription data obtained by the first network element can also include the first policy. In this case, the first network element can not need to send a message to the fourth network element to trigger the fourth network element to return the first policy.

[0234] Implementation two: The fourth network element actively sends the first policy to the first network element.

[0235] In the implementation two, the fourth network element can send the first policy to the first network element in a case where the fourth network element receives the first policy from another network element.

[0236] Optionally, when the other network element sends the first policy to the fourth network element, the other network element can also send indication information indicating that the information sent by the other network element is the first policy. Based on the indication information, the fourth network element can determine that the received information is the first policy, and then send the first policy to the first network element. For example, the indication information can be referred to as a local offloading control indication.

[0237] In the second implementation, the other network element sending the first policy to the fourth network element, and the message carrying the first policy sent by the other network element to the fourth network element are not limited. For example, an application function (AF) network element can send an AF traffic influence request message to the fourth network element, where the first policy and a local offload control indication are carried in the AF traffic influence request message, and the local offload control indication is used to indicate that the AF traffic influence request message carries the first policy.

[0238] In the second implementation, the fourth network element sending the first policy to the first network element is not limited. For example, the fourth network element can send the first policy to the first network element through an SM policy control_update notify message.

[0239] Optionally, in the second implementation, the first policy sent by the other network element to the fourth network element can include information allowing the traffic flow to be sent to at least one local data network. For example, the first policy can include information in the form of (1), (2), or (3) described above.

[0240] Optionally, in the second implementation, the fourth network element can send the received first policy to the first network element when the received first policy is different from the historical first policy previously sent to the first network element. It can also be understood that the fourth network element updates the historical first policy based on the received first policy, and sends the updated first policy to the first network element.

[0241] In addition, optionally, the first network element can also be preconfigured with the first policy, without receiving the first policy from the fourth network element. That is, in S202, "the first network element receives the first policy" can be replaced with "the first network element obtains the first policy". For example, the first network element can be preconfigured with information in the form of (1), (2), or (3) described above.

[0242] In S202, the first network element determines information corresponding to the second network element according to the first policy. The information corresponding to the second network element is used to determine whether to allow the traffic flow to be routed to the first local data network.

[0243] The following describes S202 in detail.

[0244] In the embodiments of the present application, the local data network in the area managed by the second network element is referred to as the first local data network. The second network element is used to manage the edge deployment information in the first local data network. For example, the second network element can be an I-SMF network element corresponding to the first local data network. The second network element is not limited in the embodiments of the present application.

[0245] Optionally, the second network element can also manage the EAS in the first local data network.

[0246] The first local data network can be one of the local data networks in the area managed by the first network element. That is, the area managed by the first network element includes the area managed by the second network element.

[0247] Optionally, in the area managed by the first network element, in addition to the area managed by the second network element, there can also be other areas. For example, in the area managed by the first network element, in addition to the area managed by the second network element, there can also be an area managed by a third network element. The local data network in the area managed by the third network element can be referred to as a second local data network. That is, the at least one local data network in the area managed by the first network element also includes the second local data network. The third network element can manage the edge deployment information in the second local data network.

[0248] After the first network element obtains the first policy, the first network element can determine the information corresponding to the second network element according to the first policy and the information supported by the second network element.

[0249] The information corresponding to the second network element includes information allowing the traffic flow to be routed to the first local data network. It can also be understood that the information corresponding to the second network element includes information allowing the traffic flow to be routed to the EAS in the area managed by the second network element (or the information corresponding to the second network element includes information allowing the traffic flow to be routed to the EAS managed by the second network element).

[0250] Optionally, the information corresponding to the second network element can include at least one of the following information allowing the traffic flow to be routed to the first local data network: FQDN, IP segment, service area, DNAI, or APP ID.

[0251] Exemplarily, the form of the information corresponding to the second network element can refer to the forms shown in (1), (2), or (3) in the introduction of S201 above.

[0252] Optionally, the information supported by the second network element can include configuration information of the network supported by the second network element. Exemplarily, the configuration information of the network supported by the second network element can include at least one of the following information: FQDN, IP segment, service area, DNAI, or APP ID.

[0253] In a possible implementation, the information corresponding to the second network element can be the same information as the information allowing the traffic flow to be routed to the at least one local data network indicated by the first policy. That is, the information corresponding to the second network element is both the information in the information allowing the traffic flow to be routed to the at least one local data network and the information in the information supported by the second network element.

[0254] For example, in the case of the first policy indicating that the traffic flow is allowed to be routed to the IP segment / FQDN of the at least one local data network, the first network element can determine, according to the IP segment / FQDN supported by the second network element, the IP segment / FQDN in the IP segment / FQDN indicated by the first policy that is the same as the IP segment / FQDN supported by the second network element as the information corresponding to the second network element. Similarly, if the first policy indicates the information in the form of (2) shown in the introduction of S201 above, the first network element can determine, according to the information supported by the second network element, the service area / DNAI / APP ID corresponding to the second network element. If the first policy indicates the information in the form of (3) shown in the introduction of S201 above, the first network element can determine, according to the information supported by the second network element, the IP segment / FQDN and the service area / DNAI corresponding to the second network element.

[0255] Optionally, the information supported by the second network element can be determined according to a second mapping relationship. The second mapping relationship includes the mapping relationship between the identification information of each network element in the at least one network element and the information supported by each network element, wherein the at least one network element includes the second network element.

[0256] Optionally, the first network element can pre-configure the second mapping relationship. For example, the first network element can configure, on the managed area, the mapping relationship between the identification information of each network element (such as the I-SMF network element) managing the edge deployment information in the local data network and the information supported by each network element.

[0257] Alternatively, the second mapping relationship can be configured by other network elements. For example, the NRF network element can configure the second mapping relationship. The first network element can send a request message carrying the identification information of the second network element to other network elements, and the request message is used to request to query the information supported by the second network element. After receiving the request message, the other network elements find the information supported by the second network element according to the identification information of the second network element, and feed back the information supported by the second network element to the first network element.

[0258] S203, the first network element sends the information corresponding to the second network element to the second network element.

[0259] Based on the communication method provided in the embodiments of the present application, after the first network element receives the first policy, the information for determining whether to allow the traffic flow to be routed to the first local data network can be determined according to the first policy, in other words, the first network element can provide the targeted routing information (or also called offloading information) for the local data network. Compared with the current situation that the PCF / SMF network element does not distinguish the offloading policy based on the local data network, but directly provides the offloading policy to the policy configuration method of each local data network below, the communication method provided in the embodiments of the present application can provide the isolated routing information for different local data networks, thereby improving the flexibility of policy deployment, and can more flexibly meet the needs of the network or the user.

[0260] The following will be expanded to introduce S203.

[0261] After the first network element determines the information corresponding to the second network element, the information corresponding to the second network element is sent to the second network element. After the second network element receives the information corresponding to the second network element, the filtering rule of the traffic flow can be generated and configured according to the information corresponding to the second network element. The filtering rule of the traffic flow is used to determine whether to allow the traffic flow to be routed to the EAS in the first local data network. If the traffic flow matches the filtering rule, the traffic flow can be routed to the EAS in the first local data network. If the traffic flow does not match the filtering rule, the traffic flow cannot be routed to the EAS in the first local data network.

[0262] Optionally, when the second network element configures the filtering rule of the traffic flow according to the information corresponding to the second network element, if there are multiple EASs on the area managed by the second network element, the second network element can configure different traffic flow filtering rules for different EASs, or can also configure the same traffic flow filtering rule.

[0263] Among them, the filtering rule of the traffic flow can include the information of allowing to be routed to the EAS in the first local data network. The network element (for example, the fifth network element below) configuring the filtering rule of the traffic flow can determine whether the traffic flow matches the filtering rule according to the information of the traffic flow and the information included in the filtering rule of the traffic flow, and then decide whether to allow the traffic flow to be routed to the EAS in the first local data network.

[0264] For example, assuming that the first EAS is deployed in the first local data network, and the filtering rule of the service flow includes information allowing routing to the first EAS, if the information of the service flow is included in the information allowing routing of the service flow to the first EAS, it can be considered that the service flow matches the filtering rule, and the service flow can be routed to the first EAS. If the information of the service flow is not the information allowing routing of the service flow to the first local data network, it can be considered that the service flow does not match the filtering rule, and the service flow cannot be routed to the first EAS. For another example, if other EASs, such as a second EAS, are also deployed in the first local data network, the filtering rule of the service flow can also include information allowing routing to the second EAS.

[0265] In the embodiments of the present application, the information allowing routing to the first local data network included in the filtering rule of the service flow can be an IP segment or an FQDN.

[0266] For example, assuming that the filtering rule includes an FQDN, if the FQDN of the service flow is included in the FQDN included in the filtering rule, the service flow matches the filtering rule, and the service flow can be routed to the first local data network.

[0267] For another example, assuming that the filtering rule includes an IP segment, if the IP address of the service flow is included in the IP segment included in the filtering rule, the service flow matches the filtering rule, and the service flow can be routed to the first local data network.

[0268] The embodiments of the present application do not limit the specific implementation of the second network element configuring the filtering rule of the service flow according to the information corresponding to the second network element.

[0269] Optionally, for the second network element generating the filtering rule of the service flow according to the information corresponding to the second network element, if the information corresponding to the second network element is in the form shown in (1) in the introduction of S201 above, the second network element can directly generate the filtering rule of the service flow according to the information corresponding to the second network element.

[0270] If the information corresponding to the second network element is in the form shown in (2) in the introduction of S201 above, the second network element can determine the IP segment / FQDN associated with the information corresponding to the second network element in the edge deployment information according to the association between the service area / DNAI / APP ID and the IP segment / FQDN in the managed edge deployment information, and generate the filtering rule of the service flow according to the associated IP segment / FQDN.

[0271] For example, assuming that the information corresponding to the second network element includes service area 1 and service area 2, the second network element can determine, based on the association relationship between the service area and the IP segment in the edge deployment information of the first local data network, that service area 1 is associated with IP segment 1 and service area 2 is associated with IP segment 2, and then the second network element can determine that IP segment 1 and IP segment 2 are IP segments that allow the traffic flow to be routed to at least one local data network, and generate a filtering rule for the traffic flow, which includes IP segment 1 and IP segment 2 that allow the traffic flow to be routed to the first local data network.

[0272] If the information corresponding to the second network element is in the form shown in (3) in the introduction of S201 above, i.e., including the first parameter (IP segment / FQDN) and the second parameter (service area / DNAI / APP ID), the second network element can determine the IP segment / FQDN associated with the second parameter in the edge deployment information according to the association relationship between the service area / DNAI / APP ID and the IP segment / FQDN in the managed edge deployment information, and generate a filtering rule for the traffic flow according to the first parameter in the information corresponding to the second network element and the IP segment / FQDN associated with the second parameter.

[0273] Optionally, the traffic flow that cannot be routed to the first local data network can be routed to the central data network.

[0274] Optionally, the first network element can also send tunnel information of a user plane function network element connected to the central data network to the second network element. The tunnel information can include tunnel endpoint identifier and other information. For example, the first network element can send tunnel information of a C-PSA UPF network element to the second network element.

[0275] Optionally, after receiving the information corresponding to the second network element, the second network element can select an EASDF network element according to the information corresponding to the second network element.

[0276] Optionally, the second network element configures the traffic flow filtering rule, including: the second network element sends the filtering rule to the fifth network element, so that the fifth network element can split the traffic flow based on the filtering rule, and split the traffic flow that is allowed to be sent to the first local data network and the traffic flow that is not allowed to be sent to the first local data network.

[0277] The fifth network element can be a user plane function network element connected to the central data network and the first local data network. For example, the fifth network element can be a ULCL / BP network element.

[0278] Optionally, the second network element can also send the tunnel information to the fifth network element. The tunnel information can include at least one of the following information: tunnel information of a user plane function network element connected to the central data network, tunnel information of a user plane function network element connected to the first local data network, or tunnel information of an access network (the tunnel information of the access network is the tunnel information provided by the access network device to the user function network element, which can also be referred to as AN tunnel information). For example, the user plane function network element connected to the central data network can be a C-PAS UPF network element. The user plane function network element connected to the first local data network can be an L-UPF network element.

[0279] In the case of an uplink service flow, if the fifth network element determines, according to the filtering rule, that the service flow matches the filtering rule, the fifth network element can send the service flow to the user plane function network element connected to the first local data network. If the fifth network element determines, according to the filtering rule, that the service flow does not match the filtering rule, the fifth network element can send the service flow to the user plane function network element connected to the central network.

[0280] In the case of a downlink service flow, if the fifth network element determines, according to the filtering rule, that the service flow matches the filtering rule, the fifth network element can send the service flow to the access network. If the fifth network element determines, according to the filtering rule, that the service flow does not match the filtering rule, the fifth network element can send the service flow to the central data network.

[0281] Optionally, the second network element can select the fifth network element.

[0282] Optionally, the filtering rule and the tunnel information of the service flow sent by the second network element to the fifth network element can be carried in an N4 message.

[0283] Optionally, in the case where, in addition to the first local data network, there is another local data network in the area managed by the first network element, the first network element can also determine corresponding routing information for the other local data network. In the following, a certain local data network in the other local data network is referred to as a second local data network, and a network element managing the edge deployment information in the second local data network is referred to as a third network element. This scheme is introduced below.

[0284] After receiving the first policy, the first network element can also determine information corresponding to the third network element according to the first policy. The information corresponding to the third network element is used to determine whether to allow the service flow to be routed to the second local data network. The information corresponding to the third network element can be different from the information corresponding to the second network element, or it can be the same.

[0285] The specific implementation of the first network element determining the information corresponding to the third network element can refer to the introduction of S202 above.

[0286] The first network element can also send information corresponding to the third network element to the third network element. After receiving the information corresponding to the third network element, the third network element can configure the filtering rule of the service flow according to the information corresponding to the third network element. The specific implementation of the third network element configuring the filtering rule of the service flow according to the information corresponding to the third network element can refer to the description of S203 above.

[0287] For example, it is assumed that the first network element is an SMF network element, the second network element is an I-SMF1 network element, the third network element is an I-SMF2 network element, the fourth network element is a PCF network element, the L-UPF1 network element and the L-UPF2 network element are connected with the first local data network, and the L-UPF3 network element and the L-UPF4 network element are connected with the second local data network. As shown in FIG. 3, the PCF network element can send the first policy to the SMF network element. After receiving the first policy, the SMF network element determines the information corresponding to the I-SMF1 network element and the information corresponding to the I-SMF2 network element according to the first policy. The information corresponding to the I-SMF1 network element and the information corresponding to the I-SMF2 network element can be the same or different. The SMF network element sends the information corresponding to the I-SMF1 network element to the I-SMF1 network element and sends the information corresponding to the I-SMF2 network element to the I-SMF2 network element. After receiving the information corresponding to the I-SMF1 network element, the I-SMF1 network element determines the filtering rule 1 sent to the L-UPF1 network element and the filtering rule 2 sent to the L-UPF2 network element according to the information corresponding to the I-SMF1 network element. The filtering rule 1 and the filtering rule 2 can be the same or different. After receiving the information corresponding to the I-SMF2 network element, the I-SMF2 network element determines the filtering rule 3 sent to the L-UPF3 network element and the filtering rule 4 sent to the L-UPF4 network element according to the information corresponding to the I-SMF2 network element. The filtering rule 3 and the filtering rule 4 can be the same or different.

[0288] In addition, as shown in FIG. 3, if the terminal device is located in the area managed by the I-SMF1 network element, the L-UPF1 network element / L-UPF2 network element can determine whether the service flow sent by the terminal device can be routed to the first local data network based on the configured filtering rule. If the terminal device is located in the area managed by the I-SMF2 network element, the L-UPF3 network element / L-UPF4 network element can determine whether the service flow sent by the terminal device can be routed to the second local data network based on the configured filtering rule.

[0289] It is assumed that in the PDU session establishment scenario, the first network element sends the information corresponding to the second network element to the second network element, the first network element is an SMF network element, the second network element is an I-SMF network element, the fourth network element is a PCF network element, the fifth network element is a ULCL / BP UPF network element, and the terminal device is a UE. As shown in FIG. 4, one possible process can include the following steps:

[0290] S401, the UE registers to the core network. In the registration process, the AMF network element obtains the subscription data of the UE, and the subscription data of the UE includes a local offloading control indication.

[0291] S402, the UE initiates establishment of a PDU session, and sends a PDU session establishment request message to the AMF network element.

[0292] S403, the AMF network element selects an I-SMF network element. For example, the AMF network element can select an I-SMF(s) network element supporting a local session break out capability according to the local offloading control indication, the UE location, the data network name (DNN) / single network slice selection assistance information (S-NSSAI), the service area of the I-SMF, and the like. The I-SMF(s) network element means at least one I-SMF network element, that is, the AMF network element can select one I-SMF network element supporting the local session break out capability, or the AMF network element can select multiple I-SMF network elements supporting the local session break out capability, and the embodiments of the present application do not limit this.

[0293] FIG. 4 takes one I-SMF network element as an example for illustration, and it can be understood that in actual application, if the AMF network element selects multiple I-SMF network elements, the multiple I-SMF network elements can all execute the steps in the process shown in FIG. 4. The process shown in FIG. 4 is described below taking the AMF network element selecting one I-SMF network element as an example.

[0294] S404, the AMF network element sends a PDU session establishment SM context request message to the I-SMF network element, where the local offloading control indication is carried.

[0295] S405, the I-SMF network element selects an L-UPF network element.

[0296] S406, the I-SMF network element sends a PDU session establishment request message to the SMF network element, where the local offloading control indication is carried.

[0297] S407, the SMF network element obtains the subscription data from the UDM network element. Optionally, the subscription data can contain an authorized local offloading control indication.

[0298] After S407, the process can include S408a-S410a, or in the case where the SMF network element is preconfigured with the correspondence between the local offloading information and the LOID(s), the process can include S408b-S410b.

[0299] After S407, S408a-S410a include:

[0300] S408a, when the SMF network element receives the local offload control indication or determines that the SM subscription contains the authorization of the local offload control indication, sends an SM control policy request message to the PCF network element, wherein the local offload control indication is carried.

[0301] S409a, the PCF network element sends an SM control policy response message to the SMF network element, wherein the first policy is included. The information included in the first policy can be in the form of (1), (2) or (3) in the introduction of "information allowing traffic flow to be routed to at least one local data network" in S201.

[0302] For ease of introduction, if "the above (1), (2) or (3)" appears in this paper, it refers to (1), (2) or (3) in the introduction of "information allowing traffic flow to be routed to at least one local data network" in S201 without special instructions.

[0303] S410a, the SMF network element determines the information corresponding to the I-SMF network element according to the information supported by the I-SMF(s) network element and the information included in the first policy.

[0304] Among them, the information supported by the I-SMF network element can be in the form of (1), (2) or (3) in the introduction of S201. The information corresponding to the I-SMF network element can also be in the form of (1), (2) or (3) in the introduction of S201. For example, when the AMF network element selects multiple I-SMFs, the SMF network element can determine the information corresponding to each I-SMF network element according to the information supported by the I-SMF(s) network element and the information included in the first policy.

[0305] Among them, the information supported by the I-SMF network element can be pre-configured by the SMF network element, or obtained by the SMF network element from the NRF network element.

[0306] S410a can refer to the introduction of S201 above.

[0307] After S407, S408b-S410b include:

[0308] S408b, the SMF network element pre-configures the correspondence between the local offload information and the LOID(s), wherein the local offload information can be in the form of (1), (2) or (3) in the introduction of S201.

[0309] S409b, the SMF network element sends an SM control policy request message to the PCF network element, wherein the local offloading control indication is carried. After the PCF network element receives the SM control policy request message, the PCF network element sends an SM control policy response message to the SMF network element, wherein at least one LOID (i.e., the first policy) is included.

[0310] S410b, the SMF network element determines the local offloading information corresponding to the at least one LOID returned by the PCF network element according to the pre-configured correspondence between the local offloading information and the LOID(s). The SMF network element determines the information corresponding to the I-SMF network element according to the information supported by the I-SMF network element and the local offloading information corresponding to the at least one LOID returned by the PCF network element. The information corresponding to the I-SMF network element can be in the form of (1), (2) or (3) introduced above in the introduction of S201.

[0311] S410b can refer to the introduction of S202 above.

[0312] After S408a-S410a or S408b-S410b, the flow includes the following steps:

[0313] S411, the SMF network element sends the information corresponding to the I-SMF network element and the tunnel information of the PSA UPF network element to the I-SMF network element.

[0314] Optionally, the I-SMF network element can select the EASDF network element after receiving the information corresponding to the I-SMF network element and the tunnel information of the PSA UPF network element.

[0315] S412, the I-SMF network element generates a filtering rule of the service flow according to the information corresponding to the I-SMF network element.

[0316] S412 can refer to the introduction of S203 above.

[0317] S413, the I-SMF network element selects the ULCL / BP UPF network element and sends an N4 message to the ULCL / BP UPF network element. The N4 message includes the tunnel information of the PSA UPF, the tunnel information of the LUPF and the filtering rule.

[0318] S414, the I-SMF network element sends an N1 and an N2 message to the AMF network element. The N2 message carries the tunnel information of the PSA UPF network element and the tunnel information of the LUPF network element, and the N1 message includes the IP address of the EASDF network element. The AMF network element provides the N2 message to the RAN and provides the N1 message to the UE. The N1 message sent by the AMF network element to the UE can be carried in a PDU session establishment response message.

[0319] S415, the RAN sends an N2 message to the AMF network element, including AN tunnel information. The AMF network element sends a PDU session SM context update message to the I-SMF(s) network element, including AN tunnel information.

[0320] S416, the I-SMF network element sends an N4 message to the ULCL / BP UPF network element, including AN tunnel information and ULCL / BP UPF tunnel information and filtering rules.

[0321] S417, the ULCL / BP UPF network element filters traffic flows according to the filtering rules and decides whether to offload the traffic flows to the L-DN or the central data network.

[0322] S417 can refer to the description of S203 above.

[0323] It can be understood that the flow shown in FIG. 4 is only a logical schematic flow provided for the purpose of understanding the embodiments of the present application, and does not represent the actual timing of the embodiments of the present application. The embodiments of the present application do not limit the timing between different steps in FIG. 4. For example, in FIG. 4, S408b is after S407, which does not mean that S407 is completed first and then S408b is completed. S408b and S407 can be independent processes.

[0324] Suppose in the AF traffic influence scenario, the first network element sends information corresponding to the second network element to the second network element, the first network element is the SMF network element, the second network element is the I-SMF network element, the fourth network element is the PCF network element, the fifth network element is the ULCL / BP UPF network element, and the terminal device is the UE. As shown in FIG. 5, a possible flow can include the following steps:

[0325] S501, the AF network element sends an AF traffic influence request message to the PCF network element, including local offload control indication and first policy. The information included in the first policy can be in the form of (1), (2) or (3) described above in S201.

[0326] S501 can refer to the description of S202 above.

[0327] S502, the PCF network element sends an SM policy control update notification message to the SMF network element, including the first policy.

[0328] S501 can refer to the description of S202 above.

[0329] The steps after S502 are the same as S410a-S417.

[0330] Fig. 5 takes an I-SMF network element as an example for illustration. It can be understood that in actual application, if the area managed by the SMF corresponds to multiple I-SMF network elements, the multiple I-SMF network elements can all perform the steps in the flow shown in Fig. 5.

[0331] It can be understood that the flow shown in Fig. 5 is only a logical flow provided for the convenience of understanding the embodiments of the present application, and does not represent the actual timing of the embodiments of the present application. The embodiments of the present application do not limit the timing between different steps in Fig. 5.

[0332] In addition, the embodiments of the present application also provide another communication method. Fig. 6 takes the first network element and the second network element as an example for illustration of the execution subject of the flow, but the present application does not limit the execution subject of the flow. For example, the first network element in Fig. 6 can also be a module applied to the first network element, such as a chip, a chip system, or a processor, and can also be a logical node, a logical module or software that can realize all or part of the functions of the first network element. The second network element in Fig. 6 can also be a module applied to the second network element, such as a chip, a chip system, or a processor, and can also be a logical node, a logical module or software that can realize all or part of the functions of the second network element.

[0333] As shown in Fig. 6, the method comprises the following steps:

[0334] S601, the fourth network element sends a first policy to the first network element. Correspondingly, the first network element receives the first policy from the fourth network element.

[0335] The first policy indicates information allowing the traffic flow to be routed to at least one local data network. Specifically, the first policy can include local offloading information, which can be in the form shown in (1), (2) or (3) in the introduction of S201 above, or the local offloading information can include identification information (such as LOID), which is used to identify the information in the form shown in (1), (2) or (3) in the introduction of S201 above.

[0336] For example, the local offloading information can include IP segment(s) / FQDN(s). Or, the local offloading information can include service area(s) / DNAI(s) / APP ID(s). Or, the local offloading information can include a first parameter and a second parameter, wherein the first parameter includes IP segment(s) / FQDN(s), and the second parameter includes service area(s) / DNAI(s) / APP ID(s). Or, the local offloading information can include LOID(s).

[0337] Additionally, the first network element can also pre-configure the first policy (or in other words, the first network element can pre-configure the local offload information). In this case, the first network element can send the pre-configured local offload information to the second network element.

[0338] S601 can refer to the above description of S201.

[0339] S602, the first network element sends the local offload information to the second network element, including the form shown in (1), (2) or (3), or the identification information (e.g. LOID). In other words, the first network element forwards the first policy from the fourth network element to the second network element.

[0340] Additionally, the first network element can also pre-configure the first policy without receiving the first policy from the fourth network element. That is, in S501, "the first network element receives the first policy" can be replaced by "the first network element obtains the first policy". For example, the first network element can pre-configure the information in the form shown in (1), (2) or (3) in the above description of S201, or can pre-configure LOID(s).

[0341] S603, the second network element determines the filtering rule of the service flow according to the local offload information and the managed edge deployment information.

[0342] Based on the communication method provided in the embodiments of the present application, new forms of routing information can be provided for the second network element, which can be applicable to different application scenarios and improve the flexibility of configuration. For example, if the first policy provided by the fourth network element includes information in the form as shown in (2) in the introduction of S201 above, the fourth network element can configure the service area / DNAI / APP ID without configuring the IP segment / FQDN, and in this case, the second network element can still configure the filtering rule based on the IP segment / FQDN according to the correspondence between the DNAI / APP ID and the IP segment / FQDN in the edge deployment information, to realize the routing of the service flow. Generally, the IP address / FQDN used in an area (such as a park or a factory) can change frequently, and if the fourth network element configures the IP segment / FQDN and configures the policy based on the configured IP segment / FQDN, the fourth network element needs to frequently change the configured IP segment / FQDN, while the DNAI / APP ID used in the area generally does not need to be changed frequently. Therefore, the fourth network element configuring the service area / DNAI / APP ID can greatly reduce the configuration work. Moreover, if the IP address / FQDN of the application in the area is updated, the second network element managing the area can configure a new filtering rule to realize the routing of the service flow without the participation of the fourth network element, which can reduce the operation work. For another example, if the information included in the first policy is in the form of identification information (such as LOID), the transmission of the identification information between the fourth network element and the second network element can configure the routing information for the local data network, which can reduce the signaling overhead.

[0343] The following will be introduced in detail.

[0344] The filtering rule of the service flow includes the IP segment(s) / FQDN(s) of the EAS in the first local data network to which the service flow is allowed to be routed.

[0345] Optionally, the edge deployment information managed by the second network element can also be referred to as the information supported by the second network element.

[0346] For the second network element to determine the filtering rule of the service flow, specifically, when the local offloading information includes the FQDN(s) / IP segment(s), the second network element determines the intersection (i.e., the coinciding information) of the FQDN(s) / IP segment(s) of the EAS in the edge deployment information and the FQDN(s) / IP segment(s) included in the local offloading information, and determines the intersection as the IP segment(s) / FQDN(s) of the EAS in the first local data network to which the service flow is allowed to be routed.

[0347] When the local offload information includes service area(s) / DNAI(s) / APP ID(s), the second network element determines the service area(s) / DNAI(s) / APP ID(s) of the EAS in the edge deployment information, the intersection of the service area(s) / DNAI(s) / APP ID(s) included in the local offload information, and the IP segment(s) / FQDN(s) associated with the intersection information in the edge deployment information as the IP segment(s) / FQDN(s) allowed to route to the EAS in the first local data network.

[0348] When the local offload information includes the first parameter and the second parameter, the second network element determines the FQDN(s) / IP segment(s) of the EAS in the edge deployment information, the intersection of the first parameter included in the local offload information, and the IP segment(s) / FQDN(s) allowed to route to the EAS in the first local data network. The second network element also determines the service area(s) / DNAI(s) / APP ID(s) of the EAS in the edge deployment information, the intersection of the service area(s) / DNAI(s) / APP ID(s) included in the local offload information, and the IP segment(s) / FQDN(s) associated with the intersection information in the edge deployment information as the IP segment(s) / FQDN(s) allowed to route to the EAS in the first local data network.

[0349] When the local offload information includes LOID(s), the second network element determines the information in the form of (1), (2) or (3) corresponding to the received LOID(s) according to the mapping relationship between the LOID(s) included in the local offload information and the information in the form of (1), (2) or (3) shown in the above description of S201, and determines the IP segment(s) / FQDN(s) allowed to route to the EAS in the first local data network according to the determined information in the form of (1), (2) or (3) and the edge deployment information. The second network element determines the IP segment(s) / FQDN(s) allowed to route to the EAS in the first local data network according to the information in the form of (1), (2) or (3) shown in the above description of S201 and the edge deployment information, which can be referred to the above description of the second network element determining the IP segment(s) / FQDN(s) allowed to route to the EAS in the first local data network when the local offload information includes different information.

[0350] Optionally, the second network element can send the filtering rule of the service flow to the fifth network element. The fifth network element can determine whether to allow the service flow to route to the first local data network according to the filtering rule of the service flow, which can be referred to the above description of S203.

[0351] Optionally, the second network element can also send the tunnel information to the fifth network element. For details, refer to the description of the tunnel information in S203 above.

[0352] Optionally, the second network element can select the fifth network element.

[0353] Optionally, the filter rule and the tunnel information sent by the second network element to the fifth network element can be carried in an N4 message.

[0354] Optionally, the embodiments of S601-S603 above can be applied in a PDU session establishment process.

[0355] Suppose in a PDU session establishment scenario, the first network element sends the local offload information to the second network element, the first network element is an SMF network element, the second network element is an I-SMF network element, the fourth network element is a PCF network element, the fifth network element is a ULCL / BP UPF network element, and the terminal device is a UE. As shown in FIG. 7, a possible flow can include the following steps:

[0356] S701-S708: S701-S708 are the same as S401-S408a in FIG. 4, and will not be expanded here.

[0357] FIG. 7 takes an I-SMF network element as an example for illustration, and it can be understood that in actual application, if the AMF network element selects multiple I-SMF network elements, the multiple I-SMF network elements can all perform the steps in the flow shown in FIG. 7. The following takes an AMF network element selecting one I-SMF network element as an example to illustrate the flow shown in FIG. 7.

[0358] S709, the PCF network element sends an SM control policy response message to the SMF network element, which contains the first policy. The local offload information included in the first policy can be in any one of the following four forms: (1) IP segment / FQDN; (2) service area / DNAI / APP ID; (3) a first parameter (IP segment / FQDN) and a second parameter (service area / DNAI / APP ID); and (4) LOID.

[0359] S709 can refer to the description of S601 above.

[0360] S710, the SMF network element sends the local offload information included in the first policy to the I-SMF network element, and also sends the tunnel information of the PSA UPF network element.

[0361] Optionally, the I-SMF network element can select the EASDF network element after receiving the local offload information and the tunnel information of the PSA UPF network element.

[0362] S711, the I-SMF network element determines the filtering rule (including the IP segment(s) / FQDN(s) allowed to be routed to the EAS in the first local data network) of the service flow according to the edge deployment information and the received local offloading information.

[0363] S711 can refer to the description of S603.

[0364] The steps after S711 are the same as S413-S417 in FIG. 4, which will not be expanded here.

[0365] It can be understood that the flow shown in FIG. 7 is only a logical schematic flow provided for the purpose of understanding the embodiments of the present application, and does not represent the actual timing of the embodiments of the present application. The embodiments of the present application do not limit the timing between different steps in FIG. 7.

[0366] Suppose in the AF traffic influence scenario, the first network element sends the local offloading information to the second network element, the first network element is the SMF network element, the second network element is the I-SMF network element, the fourth network element is the PCF network element, the fifth network element is the ULCL / BP UPF network element, and the terminal device is the UE. As shown in FIG. 8, a possible flow can include the following steps:

[0367] S801, the AF network element sends an AF traffic influence request message to the PCF network element, including a local offloading control indication and a first policy. The first policy includes local offloading information, which can be in any of the following four forms: (1) IP segment / FQDN; (2) service area / DNAI / APP ID; (3) first parameter (IP segment / FQDN) and second parameter (service area / DNAI / APP ID); (4) LOID.

[0368] S802, the PCF network element sends an SM policy control update notification message to the SMF network element, including the first policy.

[0369] S801-S802 can refer to the description of S601.

[0370] FIG. 8 takes an I-SMF network element as an example, and it can be understood that in actual application, if the AMF network element selects multiple I-SMF network elements, the multiple I-SMF network elements can all execute the steps in the flow shown in FIG. 4. The following takes an AMF network element selecting an I-SMF network element as an example to describe the flow shown in FIG. 8.

[0371] S803, the SMF network element sends the local offloading information included in the first policy to the I-SMF network element, and also sends the tunnel information of the PSA UPF network element.

[0372] S804, the I-SMF network element determines the filtering rule of the service flow (including the IP segment(s) / FQDN(s) allowed to be routed to the EAS in the first local data network) according to the edge deployment information and the received local offloading information.

[0373] S804 can refer to the description of S603.

[0374] The steps after S804 are the same as S413-S417 in FIG. 4, which will not be expanded here.

[0375] It can be understood that the flow shown in FIG. 8 is only a logical schematic flow provided for the purpose of understanding the embodiments of the present application, and does not represent the actual timing of the embodiments of the present application. The embodiments of the present application do not limit the timing between different steps in FIG. 8.

[0376] In addition, the embodiments of the present application also provide another communication method. The method is schematically shown in FIG. 9, taking the first network element and the second network element as the execution subject of the schematic flow, but the present application does not limit the execution subject of the schematic flow. For example, the first network element in FIG. 9 can also be a module applied to the first network element, such as a chip, a chip system, or a processor, and can also be a logical node, a logical module or software that can realize all or part of the function of the first network element. The second network element in FIG. 9 can also be a module applied to the second network element, such as a chip, a chip system, or a processor, and can also be a logical node, a logical module or software that can realize all or part of the function of the second network element.

[0377] As shown in FIG. 9, the method comprises the following steps:

[0378] S901, the second network element sends a first message to the first network element, and correspondingly, the first network element receives the first message from the second network element. The second network element is used to manage the edge deployment information in the first local data network. For example, the second network element can be an I-SMF network element corresponding to the first local data network. For details, refer to the description of the second network element in S201.

[0379] Optionally, the second network element can also manage the EAS in the first local data network.

[0380] The following describes S901.

[0381] S901 can have the following three implementations:

[0382] (a) The first message includes first information, and the first information includes information allowing the service flow to be routed to at least one local data network. For example, the first information can be in the form of (1), (2) or (3) as described above in the introduction of S201.

[0383] (b) The first message includes first information, and the first information includes at least one identification information, and the at least one identification information is used to identify information allowing the traffic flow to be routed to the at least one local data network.

[0384] In an implementation of (b), the identification information included in the first information can correspond to the preconfigured local offloading information on the second network element. For example, the first information can include at least one LOID, and the LOID can correspond to the information preconfigured on the second network element, such as the information in the form of (1), (2) or (3) as described above in the introduction of S201. For details, refer to the introduction of the at least one identification information included in the first policy in S201 above.

[0385] (c) The first message includes first indication information, and the first indication information is used to indicate authorization of the first information. For example, the first indication information can be referred to as local offloading authorization indication information.

[0386] In an implementation of (c), the first message can not include the first information.

[0387] Optionally, in the implementation of (a) and (b), the first message can further include the first indication information.

[0388] Optionally, in the implementation of (a) and (b), the first network element and the second network element can be pre-agreed that when the first message received by the first network element includes the first information, the first network element needs to authorize the first information.

[0389] Optionally, the first message can be a newly defined request message used to request authorization of the first information.

[0390] Optionally, the first message can be an existing message. For example, the first message can be a PDU session establishment request message.

[0391] In S901, the first information is an exemplary name provided by the embodiments of the present application, and can also be referred to as offloading information, routing information, local offloading information, local routing information, etc. The name of the embodiments of the present application is not limited.

[0392] The first information can be preconfigured by the second network element. The first information can also be understood as information locally configured by the second network element and expected to be used to determine information allowing the traffic flow to be routed to the first local data network.

[0393] Optionally, if there is a second local data network on the area managed by the first network element, the third network element is configured to manage edge deployment information in the second local data network, and the third network element is preconfigured with second information, the second information including information allowing traffic flow to be routed to at least one local data network or at least one identifier, and the second information can be the same as or different from the first information.

[0394] The information allowing traffic flow to be routed to at least one local data network included in the first information can refer to the description of the information allowing traffic flow to be routed to at least one local data network in S201 above.

[0395] In addition, optionally, the second network element can also select a user plane network element connected to the first local data network according to the first information. For example, the second network element can select an L-UPF network element corresponding to the first local data network according to the first information.

[0396] In a possible case, after S901, S9011 can be included:

[0397] The first network element or the fourth network element authorizes the first information to obtain an authorization result.

[0398] In the embodiments of the present application, the authorization of the first information can also be understood as determining whether the first information can be used as information for determining whether to allow traffic flow to be routed to the first local data network (or referred to as information corresponding to the second network element), or whether the first information can be used as information allowing traffic flow to be routed to the first local data network. If it is determined that the first information can be used as the information corresponding to the second network element, the authorization of the first information is successful. If it is determined that the first information cannot be used as the information corresponding to the second network element, the authorization of the first information fails.

[0399] In the implementation of the first network element authorizing the first information, the first network element authorizes the first information after receiving the first message to obtain an authorization result. Further, the first network element can feed back the authorization result of the first information to the second network element.

[0400] The first message can include the first information or can not include the first information.

[0401] The embodiments of the present application do not limit the implementation of the first network element authorizing the first information. In a possible implementation, the first network element can authorize the first information according to the first information and information supported by the second network element. If the first information is included in the information supported by the second network element, the first network element can determine that the authorization of the first information is successful. If the first information is not included in the information supported by the second network element, the first network element can determine that the authorization of the first information fails.

[0402] In another possible implementation, the first network element can authorize the first information according to the second network element. For example, the first network element can be preconfigured with a list of network elements. If the first network element determines that the second network element is in the list, the first network element can determine that the authorization of the first information is successful. If the first information is not included in the list, the first network element can determine that the authorization of the first information is failed.

[0403] The information supported by the second network element can include first identification information supported by the second network element, and at least one of the following information supported by the second network element: an IP segment, an FQDN, a service area, a DNAI, or an APP ID. The first identification information supported by the second network element can identify at least one of the following information supported by the second network element: an IP segment, an FQDN, a service area, a DNAI, or an APP ID. For example, the first identification information supported by the second network element can be referred to as a LOID.

[0404] For example, if the first information includes an IP segment 1, an IP segment 2, and an IP segment 3, and the first network element determines that the second network element supports the IP segment 1, the first network element determines that the authorization of the first information is failed.

[0405] For another example, if the first information includes a LOID 1 and a LOID 2, and the first network element determines that the second network element supports the LOID 1 and the LOID 2, the first network element determines that the authorization of the first information is successful.

[0406] For another example, if the first information includes an IP segment 1, an IP segment 2, and a DNAI 1 and a DNAI 2, and the first network element determines that the second network element supports the IP segment 3 and the DNAI 1 and the DNAI 2, the first network element determines that the authorization of the first information is failed.

[0407] Optionally, the information supported by the second network element can be determined according to a second mapping relationship. The second mapping relationship includes mapping relationships between identification information of each network element of at least one network element and information supported by each network element, where the at least one network element includes the second network element.

[0408] Optionally, the first network element can be preconfigured with the second mapping relationship. Alternatively, the second mapping relationship can be configured by another network element. For example, the NRF network element can configure the second mapping relationship. The first network element can send a request message carrying identification information of the second network element to the other network element, where the request message requests to query information supported by the second network element. After receiving the request message, the other network element determines the information supported by the second network element according to the identification information of the second network element, and feeds back the information supported by the second network element to the first network element.

[0409] In the implementation of the fourth network element authorizing the first information, after the first network element receives the first message, the first network element can send a second message to the fourth network element. After the fourth network element receives the second message, the fourth network element can authorize the first information to obtain an authorization result. Further, the fourth network element can feed back the authorization result of the first information to the first network element.

[0410] The second message can include the first information or can not include the first information.

[0411] Embodiments of the present application do not limit the implementation of the fourth network element authorizing the first information. In one possible implementation, the fourth network element can determine the authorization result of the first information according to the information supported by the second network element. In another possible implementation, the fourth network element can authorize the first information according to the second network element. For details, refer to the above description of the first network element determining the authorization result of the first information.

[0412] Optionally, the second message can be a newly defined request message for requesting authorization of the first information.

[0413] Optionally, the second message can be an existing message. For example, the second message can be an SM policy control creation request message.

[0414] Optionally, the second message can further include second indication information, and the second indication information is used to indicate authorization of the first information. For example, the second indication information can be referred to as local offloading authorization indication information.

[0415] Optionally, the first network element and the fourth network element can be previously agreed that when the second message received by the fourth network element includes the first information, the fourth network element needs to authorize the first information.

[0416] In another possible case, after S901, S9012 can be included:

[0417] The first network element or the fourth network element determines information corresponding to the second network element.

[0418] The information corresponding to the second network element can also be understood as the information authorized by the first network element or the fourth network element.

[0419] In one possible implementation of S9012, the first network element or the fourth network element can determine the information corresponding to the second network element as the first information in the case of determining that the authorization of the first information is successful.

[0420] In another possible implementation, the first network element or the fourth network element can determine the information corresponding to the second network element in the case of determining that the authorization of the first information fails.

[0421] In S9012, the first network element or the fourth network element authorizes the first information. For details, refer to the description of S9011 above.

[0422] In another possible implementation, the first network element or the fourth network element can not authorize the first information, but directly determine the information corresponding to the second network element.

[0423] The embodiments of the present application do not limit the implementation of the first network element or the fourth network element to determine the information corresponding to the second network element. For example, the first network element or the fourth network element can determine, as the information corresponding to the second network element, the information in the first information that is the same as the information supported by the second network element. In other words, the information corresponding to the second network element is the intersection of the first information and the information supported by the second network element. At this time, the information corresponding to the second network element can also be understood as the part of the first information that is successfully authorized. For another example, the first network element or the fourth network element can directly determine, as the information corresponding to the second network element, the information supported by the second network element. For another example, the first network element or the fourth network element can determine, as the information corresponding to the second network element, the pre-configured local offloading information.

[0424] In S9012, if the fourth network element determines the information corresponding to the second network element, the first network element can send a second message to the fourth network element after receiving the first message. The fourth network element determines the information corresponding to the second network element after receiving the second message. Further, the fourth network element can feed back the information corresponding to the second network element to the first network element.

[0425] For various cases of the second message, refer to the description above.

[0426] In S902, the first network element sends an authorization result and / or the information corresponding to the second network element to the second network element. The authorization result indicates authorization success or failure, and the information corresponding to the second network element is used to determine whether to allow the service flow to be routed to the first local data network.

[0427] Based on the communication method provided in the embodiments of the present application, the second network element managing the first local data network can send the first information to the first network element for authorization. If the first information is successfully authorized, it means that the first information can be used as the routing information of the first local data network, and the first information can be used to determine whether to allow the traffic flow to be routed to the first local data network. Alternatively, the first network element can provide the second network element with the routing information of the first local data network (i.e. the information used to determine whether to allow the traffic flow to be routed to the first local data network). Therefore, in the communication method provided in the embodiments of the present application, the second network element can have more rights to autonomously configure the routing information, and the first network element can authorize the first information to indicate that the first information is the routing information of the local data network, or the first network element can directly provide the routing information of the local data network, i.e. the first network element can provide mutually isolated routing information for different local data networks, thereby improving the flexibility of policy deployment and meeting the needs of the network or users more flexibly.

[0428] The following describes S902 in detail.

[0429] In S902, based on whether the first network element or the fourth network element performs S9011 or S9012, the first network element can send at least one of the authorization result or the second network element to the second network element.

[0430] For example, if S901 is implemented by (a), the first network element can send the information corresponding to the second network element to the second network element, such as the information in the form of (1), (2) or (3) described in the introduction of S201 above. Optionally, the first network element can also send the authorization result to the second network element.

[0431] If S901 is implemented by (b), the first network element can send the information corresponding to the second network element to the second network element, and the information corresponding to the second network element includes LOID(s). Optionally, the first network element can also send the authorization result to the second network element.

[0432] If S901 is implemented by (c), the first network element can send the information corresponding to the second network element to the second network element, and the information corresponding to the second network element includes LOID(s). Alternatively, the first network element can send the authorization result to the second network element.

[0433] If the second network element receives the authorization result, and the authorization result indicates that the authorization is successful, the second network element can determine the filtering rule of the traffic flow according to the first information. The specific implementation of the second network element determining the filtering rule of the traffic flow according to the first information can refer to the introduction of S203 above, which is not expanded here.

[0434] If the second network element receives the information corresponding to the second network element, the second network element can determine the filtering rule of the service flow according to the information corresponding to the second network element. Optionally, the second network element can determine the intersection of the information corresponding to the second network element and the managed edge deployment information, and then determine the filtering rule of the service flow according to the intersection information.

[0435] The specific implementation of the second network element determining the filtering rule of the service flow can refer to the description of S203 above, and will not be expanded here.

[0436] Optionally, the second network element can also select a user plane network element connected to the first local data network according to the information corresponding to the second network element. For example, the second network element can select an L-UPF network element corresponding to the first local data network according to the information corresponding to the second network element.

[0437] Optionally, the second network element can send the filtering rule of the service flow to the fifth network element. The fifth network element can determine whether the service flow can be routed to the first local data network according to the filtering rule of the service flow. The specific implementation can refer to the description of S203 above, and will not be expanded here.

[0438] Assuming that in a session establishment scenario, the first network element sends the first message to the second network element, the first network element is an SMF network element, the second network element is an I-SMF network element, the fourth network element is a PCF network element, the fifth network element is a ULCL / BP UPF network element, and the terminal device is a UE, as shown in FIG. 10, a possible process can include the following steps:

[0439] S1001, the UE registers to the core network. In the registration process, the AMF network element obtains the subscription data of the UE, and the subscription data of the UE includes a local offload control indication.

[0440] S1002, the UE initiates establishment of a PDU session, and sends a PDU session establishment request message to the AMF network element.

[0441] S1003, the AMF network element selects an I-SMF(s) network element. For example, the AMF network element can select an I-SMF(s) network element according to information such as UE location, DNN / S-NSSAI, and service area of the I-SMF.

[0442] FIG. 10 takes an I-SMF network element as an example, and it can be understood that in actual application, if the AMF network element selects multiple I-SMF network elements, the multiple I-SMF network elements can all execute the steps in the process shown in FIG. 10. The following takes the AMF network element selecting one I-SMF network element as an example to describe the process shown in FIG. 10.

[0443] S1004, the AMF network element sends a PDU session establishment SM context request message to the I-SMF network element, wherein the local offloading control indication is carried.

[0444] S1005, the I-SMF network element preconfigures first information, and the form of the first information can be (1), (2), or (3) or LOID as introduced above for S201.

[0445] S1005 can refer to the introduction of S901 above.

[0446] S1006 (optional), the I-SMF network element selects an L-UPF network element.

[0447] S1007, the I-SMF network element sends a PDU session establishment request message to the SMF network element, wherein the local offloading authorization control indication and the first information are carried.

[0448] S1007 can refer to the introduction of S901 above.

[0449] After S1007, the flow can include S1008a-S1009a, or the flow can include S1008b-S1009b.

[0450] S1008a-S1009a includes:

[0451] S1008a, the SMF network element sends an SM policy control creation request message to the PCF network element, wherein the local offloading authorization control indication and the first information are carried.

[0452] S1009a, the PCF network element sends an SM policy control creation response message to the SMF network element, wherein the authorization result is included, the authorization result indicates success / failure, or the information corresponding to the I-SMF network element is included, the information corresponding to the I-SMF network element includes information allowing the traffic flow to be routed to the first local data network, and the form can be (1), (2), or (3) as introduced above for S201.

[0453] S1008a-S1009a can refer to the introduction of S9011 and S9012 above.

[0454] S1008b-S1009b includes:

[0455] S1008b, the SMF network element preconfigures local offloading information, wherein the information supported by the I-SMF network element is included.

[0456] Optionally, the local offloading information preconfigured by the SMF network element can further include information supported by the I-SMF network element. The information supported by the I-SMF network element can be different from or the same as the information supported by other I-SMF network elements.

[0457] S1009b, the SMF network element authorizes the first information according to the information supported by the I-SMF network element, or determines the information corresponding to the I-SMF network element.

[0458] After S1008a-S1009a or S1008b-S1009b, the flow includes the following steps:

[0459] S1010, the SMF network element sends a PDU session creation response message to the I-SMF network element, including the authorization result or the information corresponding to the I-SMF network element, and the tunnel information of the PSA UPF network element.

[0460] S1011, (optional), the I-SMF network element selects an L-UPF network element according to the information corresponding to the I-SMF network element.

[0461] S1011 can be executed without S706.

[0462] Optionally, the I-SMF network element can select an EASDF network element after receiving the information corresponding to the I-SMF network element and the tunnel information of the PSA UPF network element.

[0463] The steps after S1011 are the same as S312-S317.

[0464] It can be understood that the flow shown in FIG. 10 is only a logical schematic flow provided for the purpose of facilitating understanding of the embodiments of the present application, and does not represent the actual timing of the embodiments of the present application. The embodiments of the present application do not limit the timing between different steps in FIG. 10. For example, in FIG. 10, S1008b is after S1007, which does not mean that S1007 is completed first and then S1008b is completed. S1008b and S1007 can be independent processes.

[0465] The above various method embodiments can be independently applied or combined.

[0466] The above mainly introduces the scheme provided by the embodiments of the present application from the perspective of interaction between various network elements. Correspondingly, the embodiments of the present application also provide a communication device for implementing the above various methods. The communication device can be various network elements (such as a first network element, a second network element, and a fourth network element) in the above method embodiments, or a device containing the above various network elements, or a component that can be used for the above various network elements.

[0467] It should be noted that the communication apparatus includes hardware structure and / or software module corresponding to each function in order to realize the above functions. Those skilled in the art should clearly understand that, in combination with the units and algorithm steps of each example described in the embodiments disclosed in the present document, the present application can be realized in the form of hardware or a combination of hardware and computer software. Whether a certain function is realized in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0468] The embodiments of the present application can divide the functional modules of the communication apparatus according to the method embodiments described above, for example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The integrated module can be realized in the form of hardware or software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, and is only a logical functional division. There can be another division manner in actual implementation.

[0469] FIG. 11 shows a structural schematic diagram of a communication apparatus 1100. The communication apparatus 1100 includes a transceiver module 1101 and a processing module 1102. The transceiver module 1101, which can also be referred to as a transceiver unit 1101, is used to realize the receiving and / or transmitting functions. The processing module 1102, which can also be referred to as a processing unit 1102, is used to realize the processing functions.

[0470] Optionally, the communication apparatus 1100 can also include a storage module 1103.

[0471] Wherein, all relevant contents of each step involved in the above method embodiments can be cited to the function description of the corresponding functional module, which will not be repeated here.

[0472] Optionally, in the communication apparatus shown in FIG. 11, the names of each module can also be different from those shown in the figure, for example, the transceiver module can also be referred to as a communication module or a communication unit.

[0473] The various units in FIG. 11, if implemented in the form of software function modules and sold or used as independent products, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application essentially or in other words the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to perform all or part of the steps of the methods described in the various embodiments of the present application. The storage medium storing the computer software product includes a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0474] In the embodiments of the present application, the communication device 1100 is presented in the form of dividing various function modules in an integrated manner. The "module" here can refer to an application-specific integrated circuit (ASIC), a circuit, a processor and a memory executing one or more software or firmware programs, an integrated logic circuit, and / or other devices that can provide the above functions.

[0475] In a simple embodiment, those skilled in the art can conceive that the communication device 1100 can take the form of the communication device 1200 shown in FIG. 12.

[0476] As shown in FIG. 12, the communication device 1200 includes one or more processors 1201, a communication line 1202, and at least one communication interface (only exemplary to include a communication interface 1204 and a processor 1201 is described as an example), and optionally further includes a memory 1203.

[0477] The processor 1201 can be a general central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of programs of the present application.

[0478] The communication line 1202 can include a channel for connecting between different components.

[0479] The communication interface 1204 can be a transceiver module for communicating with other devices or communication networks, such as an Ethernet, a RAN, a terminal, a wireless local area network (WLAN), and the like. For example, the transceiver module can be a transceiver, a transceiver module, or the like. Alternatively, the communication interface 1204 can also be a transceiver circuit or an input / output interface within the processor 1201, for realizing signal input and signal output of the processor.

[0480] The memory 1203 can be a device having a storage function. For example, the memory 1203 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this. The memory 1203 can exist independently and be connected to the processor via the communication line 1202. The memory 1203 can also be integrated with the processor.

[0481] The memory 1203 is configured to store computer-executable instructions for implementing the solutions of the present application, and the processor 1201 is configured to control execution of the computer-executable instructions. The processor 1201 is configured to execute the computer-executable instructions stored in the memory 1203, so as to implement the communication method provided in the embodiments of the present application.

[0482] Alternatively, in the embodiments of the present application, the processor 1201 can execute the functions related to processing in the communication method provided in the embodiments of the present application, and the communication interface 1204 is responsible for communication with other devices or communication networks, which is not limited in the embodiments of the present application.

[0483] Alternatively, in the embodiments of the present application, the computer-executable instructions can also be referred to as application program codes, which are not limited in the embodiments of the present application.

[0484] In a specific implementation, as an embodiment, the processor 1201 can include one or more CPUs, such as CPU0 and CPU1 in FIG. 12.

[0485] In a particular implementation, as an example, the communication apparatus 1200 can include multiple processors, such as the processor 1201 and the processor 1207 in FIG. 12. Each of these processors can be a single-core processor or a multi-core processor. The processor herein can include, but is not limited to, at least one of the following: a CPU, a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), an artificial intelligence processor, and various other computing devices running software, each of which can include one or more cores for executing software instructions to perform calculations or processing.

[0486] In a particular implementation, as an example, the communication apparatus 1200 can further include an output device 1205 and an input device 1206. The output device 1205 communicates with the processor 1201 and can display information in various ways. For example, the output device 1205 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, a projector, or the like. The input device 1206 communicates with the processor 1201 and can receive user input in various ways. For example, the input device 1206 can be a mouse, a keyboard, a touch screen device, a sensor device, or the like.

[0487] The communication apparatus 1200 described above can also be referred to as a communication device, which can be a general-purpose device or a special-purpose device. For example, the communication apparatus 1200 can be the first network element, the second network element, the fourth network element, or a device having a similar structure as in FIG. 12. The embodiments of the present application do not limit the type of the communication apparatus 1200.

[0488] In addition, the constituent structure shown in FIG. 12 does not limit the communication apparatus, and the communication apparatus 1200 can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0489] Optionally, the functions / implementation procedures of the transceiver module 1101 and the processing module 1102 in FIG. 11 can be implemented by invoking the computer-executed instructions stored in the memory 1203 by the processor 1201 in the communication apparatus 1200 shown in FIG. 12. Alternatively, the functions / implementation procedures of the processing module 1102 in FIG. 11 can be implemented by invoking the computer-executed instructions stored in the memory 1203 by the processor 1201 in the communication apparatus 1200 shown in FIG. 12, and the functions / implementation procedures of the transceiver module 1101 in FIG. 11 can be implemented by the communication interface 1204 in the communication apparatus 1200 shown in FIG. 12.

[0490] It should be understood that one or more of the above modules or units can be implemented in software, hardware or a combination of both. When any of the above modules or units is implemented in software, the software exists in the form of computer program instructions and is stored in a memory, and a processor can be used to execute the program instructions and implement the above method procedures. The processor can be built in a SoC or an ASIC, or be a separate semiconductor chip. The processor further includes a core for executing software instructions to perform operations or processing, and can further include necessary hardware accelerators, such as an FPGA, a programmable logic device (PLD), or a logic circuit for implementing special logic operations.

[0491] When any of the above modules or units is implemented in hardware, the hardware can be any one or any combination of a CPU, a microprocessor, a DSP chip, an MCU, an artificial intelligence processor, an ASIC, a SoC, an FPGA, a PLD, a special digital circuit, a hardware accelerator, or a non-integrated discrete device, which can execute necessary software or be independent of software to perform the above method procedures.

[0492] Optionally, the embodiments of the present application also provide a communication apparatus (for example, the communication apparatus can be a chip or a chip system), which comprises a processor configured to implement the method in any of the above method embodiments. In a possible design, the communication apparatus further comprises a memory. The memory is configured to store necessary program instructions and data, and the processor can invoke the program instructions stored in the memory to instruct the communication apparatus to perform the method in any of the above method embodiments. Of course, the memory can also not be in the communication apparatus. When the communication apparatus is a chip system, the communication apparatus can be composed of a chip, or can include a chip and other discrete devices, and the embodiments of the present application do not make a specific limitation in this regard.

[0493] For example, FIG. 13 shows a structural schematic diagram of a chip system. As shown in FIG. 13, the chip system includes a processor module, a storage module, a power module and a radio frequency / antenna module.

[0494] Among them, the processor module is used for various calculations, in which the CPU is responsible for executing various instructions, including the instructions of application programs, operating systems and other software; the graphic processing unit (GPU) is mainly responsible for graphic processing, but the CPU can also process some graphic tasks, such as rendering of application program interfaces; the modem is used for modulating or demodulating signals, so that digital signals can be transmitted in space.

[0495] In the storage module, the RAM is a temporary storage space, used for temporarily storing data in use, for example, if the chip system is in a mobile phone, the RAN can store opened web pages, messages of chat applications, game states, etc. The ROM is a read-only storage space, for example, if the chip system is in a mobile phone, the ROM can store system files, pre-installed application programs and firmware.

[0496] The power module is used to provide voltage and current to other modules to maintain the normal operation of the chip.

[0497] The radio frequency / antenna module is used to amplify signals and radiate them into space, or receive wireless signals in space.

[0498] Optionally, the embodiment of the present application further provides a computer readable storage medium, which stores computer programs or instructions, and when the computer programs or instructions are run on a communication device, the communication device can execute the method described in any of the method embodiments or any implementation manner thereof.

[0499] Optionally, the embodiment of the present application further provides a computer program product, which stores computer programs or instructions, and when the computer programs or instructions are run on a communication device, the communication device can execute the method described in any of the method embodiments or any implementation manner thereof.

[0500] Optionally, the embodiment of the present application further provides a communication system, which includes the first network element described in the method embodiment and the second network element described in the method embodiment. Optionally, the communication system can further include the fourth network element described in the method embodiment. Optionally, the communication system can further include the third network element described in the method embodiment.

[0501] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the flow or function according to the embodiments of this application is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0502] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0503] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of the application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Thus, if such modifications and modifications fall within the scope of the claims and their equivalents, this application is also intended to include such modifications and modifications.

Claims

A communication method characterized by comprising: The method comprises: The first network element receives a first policy, the first policy being used to indicate information of allowing a service flow to be routed to at least one local data network; The first network element sends information corresponding to a second network element to the second network element, wherein the second network element is used to manage edge deployment information in a first local data network, the information corresponding to the second network element is determined according to the first policy, and the information corresponding to the second network element is used to determine whether the service flow is allowed to be routed to the first local data network. The method of claim 1, wherein The information corresponding to the second network element comprises at least one of the following: a fully qualified domain name (FQDN), an Internet Protocol (IP) segment, a service area, a data network access identifier (DNAI) or an application identifier (APP ID). The method according to claim 1 or 2, characterized in that The information corresponding to the second network element is determined according to the first policy and configuration information of a network supported by the second network element. The method according to claim 3, characterized in that The configuration information of the network supported by the second network element comprises at least one of the following: the FQDN, the IP segment, the service area, the DNAI or the APP ID. The method according to any one of claims 1 to 4, characterized in that Information corresponding to a third network element that manages a second local data network of the at least one local data network is different from the information corresponding to the second network element, the information corresponding to the third network element is determined according to the first policy, and the information corresponding to the third network element is used to determine whether the service flow is allowed to be routed to the second local data network. The second local data network is different from the first local data network. A communication method characterized by comprising: The method comprises: The first network element receives a first message from a second network element, the first message comprising first information; wherein the second network element is used to manage edge deployment information in a first local data network, and the first information comprises information of allowing a service flow to be routed to at least one local data network or at least one identifier information used to identify the information of allowing the service flow to be routed to the at least one local data network; The first network element sends at least one of the following to the second network element: an authorization result or information corresponding to the second network element; wherein the authorization result indicates that authorization is successful or failed, and the information corresponding to the second network element is used to determine whether the service flow is allowed to be routed to the first local data network. The method according to claim 6, characterized in that The information of allowing the service flow to be routed to at least one local data network comprises at least one of the following: a fully qualified domain name (FQDN), an Internet Protocol (IP) segment, a service area, a data network access identifier (DNAI) or an application identifier (APP ID). The method according to any one of claims 6 or 7, characterized in that The information corresponding to the second network element comprises at least one of the following: the FQDN, the IP segment, the service area, the DNAI or the APP ID, which allows the service flow to be routed to the first local data network. Or, the information corresponding to the second network element comprises identifier information used to identify at least one of the following: the FQDN, the IP segment, the service area, the DNAI or the APP ID, which allows the service flow to be routed to the first local data network. The method according to any one of claims 6-8, characterized in that The method further comprises: The first network element sends the first information to a fourth network element; The first network element receives the authorization result or the information corresponding to the second network element from the fourth network element. The method according to any one of claims 6-9, characterized in that The authorization result or the information corresponding to the second network element is determined according to the first information, first identification information supported by the second network element, and at least one of the following: a fully qualified domain name (FQDN), an Internet Protocol (IP) segment, a service area, or a data network access identifier (DNAI); wherein the first identification information is used to identify at least one of the following: the FQDN, the IP segment, the service area, the DNAI, or an application ID (APP ID). The method according to any one of claims 6-10, characterized in that The first message further includes first indication information; the first indication information is used to indicate authorization of the first information. The method according to any one of claims 6-11, characterized in that The information corresponding to a third network element that manages a second local data network in the at least one local data network is different from the information corresponding to the second network element, and the information corresponding to the third network element is used to determine whether to allow the service flow to be routed to the second local data network. The second local data network is different from the first local data network. A communication method characterized by comprising: The method comprises: The second network element obtains the information corresponding to the second network element, wherein the second network element is used to manage edge deployment information in a first local data network, and the information corresponding to the second network element includes at least one of the following information that allows a service flow to be routed to the first local data network: a service area, a data network access identifier (DNAI), or an application identifier (APP ID); or the information corresponding to the second network element includes at least one identification information, wherein the identification information is used to identify at least one of the following information that allows a service flow to be routed to the first local data network: a service area, a DNAI, or an APP ID; The second network element configures a filtering rule of a service flow according to the information corresponding to the second network element, and the filtering rule is used to determine whether to allow the service flow to be routed to the first local data network. The method of claim 13, wherein The information corresponding to the second network element further includes a fully qualified domain name (FQDN) and / or an Internet Protocol (IP) segment that allows the service flow to be routed to the first local data network. The method according to claim 13 or 14, characterized in that The method further comprises: The second network element sends the filtering rule of the service flow and tunnel information to a fifth network element; wherein the tunnel information includes at least one of the following: tunnel information of an anchor user plane function network element, tunnel information of a user plane function network element corresponding to the first local data network, or tunnel information of an access network. The method according to any one of claims 13-15, characterized in that The second network element obtains the information corresponding to the second network element, comprising: The second network element sends a first message to a first network element, and the first message includes first information; the first information includes information that allows a service flow to be routed to at least one local data network or at least one identification information, and each identification information in the at least one identification information is used to identify information that allows a service flow to be routed to one of the at least one local data network; The second network element receives an authorization result and / or the information corresponding to the second network element from the first network element, and the authorization result indicates authorization success or failure; In a case where the second network element receives the authorization result and the authorization result indicates that the authorization is successful, the second network element determines the first information as the information corresponding to the second network element. The method of claim 16, wherein The first message further includes first indication information, and the first indication information is used to indicate authorization of the first information. A communication method characterized by comprising: The method comprises: The second network element sends a first message to a first network element, and the first message includes first information; the first information includes information allowing a service flow to be routed to at least one local data network or at least one identifier; each identifier in the at least one identifier is used to identify information allowing the service flow to be routed to one local data network in the at least one local data network; The second network element receives an authorization result and / or information corresponding to the second network element from the first network element; the authorization result indicates that the authorization is successful or failed; and the information corresponding to the second network element is used to determine whether the service flow is allowed to be routed to a first local data network managed by the second network element. In a case where the second network element receives the authorization result and the authorization result indicates that the authorization is successful, the second network element determines the first information as the information corresponding to the second network element. The method of claim 18, wherein The information corresponding to the second network element includes at least one of the following information allowing the service flow to be routed to the first local data network: a fully qualified domain name (FQDN), an Internet Protocol (IP) segment, a service area, a data network access identifier (DNAI), or an application identifier (APP ID). The method according to claim 18 or 19, characterized in that The information allowing the service flow to be routed to at least one local data network includes at least one of the following: an FQDN, an IP segment, a service area, a DNAI, or an APP ID. The method according to any one of claims 18-20, characterized in that The first message further includes first indication information, and the first indication information is used to indicate authorization of the first information. A communication method characterized by comprising: The method comprises: The fourth network element receives a second message from a first network element, and the second message includes first information; the first information includes information allowing a service flow to be routed to at least one local data network or at least one identifier; each identifier in the at least one identifier is used to identify information allowing the service flow to be routed to one local data network in the at least one local data network; The fourth network element sends an authorization result or information corresponding to a second network element to the first network element; the authorization result indicates that the authorization is successful or failed; and the information corresponding to the second network element is used to determine whether the service flow is allowed to be routed to a first local data network managed by the second network element. The method of claim 22, wherein The information corresponding to the second network element includes at least one of the following information allowing the service flow to be routed to the first local data network: a fully qualified domain name (FQDN), an Internet Protocol (IP) segment, a service area, a data network access identifier (DNAI), or an application identifier (APP ID). A communication device, characterized by The communication apparatus includes modules or units for implementing the method in any of claims 1-23. A chip characterized by The chip includes a processor configured to run a computer program, so that a device including the chip performs the method in any of claims 1-23. A communication device, characterized by The communication device comprises a processor and an interface circuit for communicating with devices other than the communication device, the processor being configured to execute instructions stored in a memory; when the instructions are executed by the processor, the communication device is caused to perform the method of any one of claims 1-23. The apparatus of claim 26, wherein The communication device is a chip or a chip system. A computer-readable storage medium, characterized by An instruction is stored on the computer, when the instruction is executed by the computer, the method of any one of claims 1-23 is executed. A computer program product, characterized in that The computer program product comprises instructions, when the instructions are executed by the computer, the method of any one of claims 1-23 is executed. A communication system characterized by The communication system comprises a first network element and a second network element; wherein the first network element is configured to implement the method of any one of claims 1-5, and the second network element is configured to receive information corresponding to the second network element; or the first network element is configured to implement the method of any one of claims 6-12, and the second network element is configured to implement the method of any one of claims 18-21; or the first network element is configured to send the first policy or information corresponding to the second network element to the second network element, and the second network element is configured to implement the method of any one of claims 13-17.

Images