WO2023098624A1

WO2023098624A1 - Communication method and apparatus, and readable storage medium

Info

Publication number: WO2023098624A1
Application number: PCT/CN2022/134714
Authority: WO
Inventors: 陈泽昊; 李永翠; 倪慧
Original assignee: 华为技术有限公司
Priority date: 2021-12-01
Filing date: 2022-11-28
Publication date: 2023-06-08
Also published as: CN114363173A; CN114363173B

Abstract

A communication method and apparatus, and a readable storage medium. The method comprises: a SMF obtains a UE-specific ECS provider identifier, then determines ECS configuration information according to the UE-specific ECS provider identifier, the ECS configuration information comprising the UE-specific ECS provider identifier and the address of an ECS corresponding to the UE-specific ECS provider identifier. Using the present application can reduce the signaling overhead of an ECS configuration in a network.

Description

Communication method, device and readable storage medium

This application claims the priority of the Chinese patent application with the application number 202111456378.9 and the application title "communication method, device and readable storage medium" filed with the China Patent Office on December 01, 2021, the entire contents of which are incorporated herein by reference. Applying.

technical field

The present application relates to the technical field of communication, and in particular to a communication method, device and readable storage medium.

Background technique

In the 4th generation mobile communication technology (4G) and previous traditional mobile network architecture and deployment, user plane devices basically follow the tree topology deployment. Uplink user packets pass through the base station and the backhaul network, and finally access the data network through the centrally deployed anchor gateways. These anchor gateways are generally deployed at higher positions in the network, such as the central computer room in a large area. This topology is relatively simple, and it is convenient for operators to perform centralized service control and message processing at the anchor point.

However, with the explosive growth of mobile service traffic, it becomes increasingly difficult for this deployment method to support the fast-growing mobile service traffic model. On the one hand, in a network with centralized deployment of anchor gateways, the increased traffic is finally concentrated at the gateway and the core computer room, which puts forward higher and higher requirements for the backhaul network bandwidth, the throughput of the computer room, and the specifications of the gateway; on the other hand, , the long-distance backhaul network and complex transmission environment from the access point to the anchor gateway also lead to a large delay and jitter in the transmission of user packets. Based on the above background, the industry has proposed the concept of edge computing (EC). By moving the user plane function (UPF) network elements and service processing capabilities down to the edge of the network, EC realizes the local processing of distributed service traffic and avoids excessive concentration of traffic, thereby greatly reducing the impact on the core equipment room and The specification requirements of the centralized gateway. At the same time, the distance of the backhaul network is shortened, and the end-to-end (E2E) delay and jitter of user packets are reduced, making it possible to deploy ultra-low-latency services.

Based on the edge computing architecture and process specified in 3GPP (3rd generation partnership project, 3rd generation partnership project) TS 23.558, user equipment (user equipment, UE) can obtain edge usage through edge configuration server (edge configuration server, ECS). The edge enabler server (Edge Enabler Server, EES) information, and then through the EES to obtain the edge application server (edge application server, EAS) information, so as to access the EAS to obtain the required services. The configuration of ECS is worth considering.

Contents of the invention

Embodiments of the present application provide a communication method, device, and readable storage medium, which can reduce signaling overhead for configuring ECSs in a network.

The following introduces the present application from different aspects, and it should be understood that the implementation manners and beneficial effects of the following different aspects can refer to each other.

In the first aspect, the present application provides a communication method, the method includes: a session management function entity (session management function, SMF) accesses receiving the UE-specific first ECS provider identifier and/or UE-specific first application identifier with a mobility management function entity (access and mobility management function, AMF), and the UE-specific first application identifier is used to determine A UE-specific first ECS provider identifier; the SMF determines first ECS configuration information according to the received first ECS provider identifier or the first application identifier, and the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS (such as a full domain name, Internet protocol address, or uniform resource locator, etc.), the first ECS corresponds to the first ECS provider identifier; the SMF sends the first ECS configuration information to the UE. Optionally, the first ECS configuration information further includes an identifier of the first ECS. Optionally, the first ECS configuration information is used by the UE to determine the ECS.

In this application, the UE-specific first ECS provider ID can be understood as the ECS Provider ID that the UE may use, or the ECS Provider ID commonly used by the UE, or the ECS Provider ID available to the UE, or the ECS provider ID determined for the UE, Or correspond to the ECS provider ID of the UE, or the ECS provider ID supported by the UE, etc. In other words, a UE-specific ECS provider ID is an ECS provider ID that is associated or bound to this UE. For example, the ECS provider ID (ECS provider ID) related to the application program downloaded or installed in the UE, or the ECS provider ID related to the application program commonly used in the UE, or the ECS provider ID related to the application program signed by the UE, etc. wait.

Exemplarily, the UE-specific first ECS Provider ID can be understood as a set of ECS Provider IDs corresponding to the deployer or manager of all or part of the applications available to the UE, or the set of ECS Provider IDs that may be accessed by all or part of the applications available to the UE. A collection of ECS Provider IDs corresponding to ECS. The "available applications" may refer to applications installed by the UE, or applications installed by the UE and cloud storage applications, or applications registered or subscribed by the UE, and the like.

Exemplarily, the UE-specific first ECS provider identifier can be understood as the UE's use of the application (including but not limited to the frequency of use of the application, the duration of use, the download rate of the application, or other parameters that characterize the use of the application by the UE) one or more of them) determined.

Understandably, in this application, the UE-specific ECS provider ID, the ECS Provider ID that the UE may use, the ECS Provider ID commonly used by the UE, the ECS Provider ID available to the UE, the ECS provider ID determined for the UE, and the ECS provider ID corresponding to the UE ECS provider ID, ECS provider ID supported by UE, etc. can be used interchangeably.

It should be understood that because a UE usually downloads/installs multiple applications, which may be related to one or more different ECS provider IDs, the UE-specific first ECS provider ID is one or more ECS provider ID. It should also be understood that the first ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs.

In the same way as the UE-specific ECS provider ID, the UE-specific application ID in this application can be understood as an application ID that may be used by the UE, or an application ID commonly used by the UE, or an application ID available to the UE, or as an The application identifier determined by the UE, or the application identifier corresponding to the UE, and so on. For example, an identifier of an application program downloaded or installed in the UE, or an identifier of an application program commonly used in the UE, or an identifier of an application program subscribed to by the UE, and so on.

Exemplarily, the UE-specific application identifier can be understood as a set of identifiers of all or part of the applications that the UE can use. The "available applications" may refer to applications installed by the UE, or applications installed by the UE and cloud storage applications, or applications registered or subscribed by the UE, and the like.

Exemplarily, the UE-specific application identifier can be understood as one of the following parameters according to the UE's use of the application (including but not limited to the frequency of use of the application, the duration of use, the download rate of the application, or other parameters that characterize the use of the application by the UE). item or items) determined.

It can be understood that in this application, UE-specific application identifiers, application identifiers that may be used by the UE, application identifiers commonly used by the UE, application identifiers available to the UE, application identifiers determined for the UE, and application identifiers corresponding to the UE The program identification and the like can be used interchangeably.

The 5G core network does not perceive the services that the UE needs to access or may access, so the ECS configuration information initially sent by the SMF network element to the UE includes the ECS Provider ID corresponding to the ECS that the UE will not use, resulting in redundant signaling consume. Therefore, in this solution, the UE reports the UE-specific ECS Provider ID/AppID to the network side (specifically, SMF or AMF), and the SMF then sends the UE-specific ECS configuration information corresponding to the UE-specific ECS Provider ID (that is, the first ECS configuration information ), which can reduce redundant cells in the ECS configuration information.

With reference to the first aspect, in a possible implementation manner, the UE-specific first ECS provider identifier may be carried in the session establishment request message or the session modification request message, and the UE-specific first application identifier may also carry In the session establishment request message or session modification request message. The above first ECS configuration information may be carried in the session establishment acceptance message or the session modification response message.

This solution carries the ECS provider ID/application program ID and ECS configuration information by multiplexing the session establishment process or session modification process, without designing new processes and signaling.

With reference to the first aspect, in a possible implementation manner, the SMF determines the first ECS configuration information according to the received first application identifier, including: the SMF acquires the correspondence between the application identifier and the ECS provider identifier; The SMF determines the first ECS provider ID corresponding to the first application program ID according to the corresponding relationship; the SMF determines the first ECS configuration information according to the first ECS provider ID.

With reference to the first aspect, in a possible implementation manner, after the SMF sends the first ECS configuration information to the UE, the method further includes: when the first ECS changes, the SMF sends the second ECS configuration information to the UE, The second ECS configuration information includes the first ECS provider identifier and the changed address of the first ECS. Wherein, the first ECS may change due to reasons such as UE movement, load balancing, and ECS downtime.

With reference to the first aspect, in a possible implementation manner, the first ECS provider ID is one or more ECS provider IDs. After the SMF sends the first ECS configuration information to the UE, the method further includes: if the second ECS corresponding to the second ECS provider identifier changes and the second ECS provider identifier belongs to the first ECS provider identifier, the SMF Send the second ECS provider identifier and the changed address of the second ECS to the UE.

Optionally, although the second ECS corresponding to the second ECS provider ID changes, if the second ECS Provider ID does not belong to the first ECS Provider ID, that is, the first ECS Provider ID does not include the second ECS Provider ID, Then the SMF determines that there is no need to update, and does not perform the update operation.

This solution sends the updated ECS configuration information to the UE when the ECS corresponding to the UE-specific ECS Provider ID needs to be updated, and does not update when the changed ECS is not the ECS corresponding to the UE-specific ECS Provider ID, thereby avoiding unnecessary The update signaling of ECS configuration information reduces the signaling overhead in the network.

With reference to the first aspect, in a possible implementation manner, after the SMF sends the first ECS configuration information to the UE, the method further includes: the SMF receives a first message from the UE, and the first message is used to indicate to update the UE-specific The first ECS provider ID or the UE-specific first application program ID (AppID); the SMF updates the first ECS provider ID according to the first message to obtain the UE-specific third ECS provider ID; the SMF sends The UE sends third ECS configuration information, where the third ECS configuration information includes the third ECS provider identifier and the address of the third ECS, and the third ECS corresponds to the third ECS provider identifier.

Optionally, the first message above indicates the newly added ECS Provider ID or AppID, and/or the deleted ECS Provider ID or AppID, and/or the updated ECS Provider ID or AppID. Here, the updated ECS Provider ID is one or more ECS Provider IDs, and the updated AppID is one or more AppIDs.

In this solution, when the UE-specific application identification (i.e. the above-mentioned first application identification) or ECS Provider ID (i.e. the first ECS provider ID) changes, for example, the UE installs or uninstalls an application, the UE reports relevant information, In order for the SMF to update the UE-specific ECS Provider ID and send the updated ECS configuration information to the UE.

In a second aspect, the present application provides a communication method, the method includes: a terminal device (UE) sends the UE-specific first ECS provider identifier and/or UE-specific first application identifier to the SMF or AMF, the first UE-specific An application identifier is used to determine a UE-specific first ECS provider identifier; the UE receives first ECS configuration information from the SMF, and the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS (for example, full domain name, Internet Protocol address, or Uniform Resource Locator, etc.), the first ECS corresponds to the first ECS provider identifier. Optionally, the first ECS configuration information further includes an identifier of the first ECS.

For the UE-specific first ECS provider identifier, reference may be made to the description of the first aspect, and details are not repeated here. It should be understood that the implementation manners of various aspects in the present application may refer to each other.

With reference to the second aspect, in a possible implementation manner, before the terminal device (UE) sends the UE-specific first ECS provider identifier or UE-specific first application identifier to the SMF or AMF, the method further includes: The UE determines the UE-specific first ECS provider identifier and/or the UE-specific first application identifier according to the application installed in the UE and/or the use of the application by the UE.

With reference to the second aspect, in a possible implementation manner, the first ECS configuration information is used by the UE to determine the ECS. Specifically, the UE determines the ECS used for EES discovery according to the first ECS configuration information. The UE may also send an EES discovery request to the ECS for EES discovery. Wherein, the ECS used for EES discovery is one of the first ECSs, and EES discovery may also be called service provisioning (Service Provisioning or Provision). Optionally, the ECS used for EES discovery may not be the ECS in the first ECS.

With reference to the second aspect, in a possible implementation manner, the UE-specific first ECS provider identifier may be carried in the session establishment request message or the session modification request message, and the UE-specific first application identifier may also carry In the session establishment request message or session modification request message. The above first ECS configuration information may be carried in the session establishment acceptance message or the session modification response message.

With reference to the second aspect, in a possible implementation manner, after the UE receives the first ECS configuration information from the SMF, the method further includes: the UE receives second ECS configuration information from the SMF, and the second ECS configuration information includes the first ECS configuration information. The ECS provider ID and the changed address of the first ECS. Wherein, the first ECS may change due to reasons such as UE movement, load balancing, and ECS downtime.

With reference to the second aspect, in a possible implementation manner, after the UE receives the first ECS configuration information from the SMF, the method further includes: the UE receives the second ECS provider identifier and the changed address of the second ECS from the SMF, The second ECS provider ID belongs to the first ECS provider ID.

With reference to the second aspect, in a possible implementation manner, after the UE receives the first ECS configuration information from the SMF, the method further includes: the UE sends a first message to the SMF, where the first message is used to indicate to update the UE-specific first ECS configuration information. An ECS provider identifier or a UE-specific first application identifier (AppID); the UE receives third ECS configuration information from the SMF, the third ECS configuration information includes the third ECS provider identifier and the address of the third ECS, the The third ECS provider identifier is obtained by updating the UE-specific first ECS provider identifier, and the third ECS corresponds to the third ECS provider identifier.

Optionally, for the specific content of the above first message, refer to the description of the first aspect, and details are not repeated here.

In a third aspect, the present application provides a communication method, the method includes: AMF receives a UE-specific first ECS provider identifier or a UE-specific first application identifier from a UE during a registration procedure; In the modification process, the UE-specific first ECS provider identifier or the UE-specific first application identifier is sent to the SMF, and the first application identifier is used to determine the UE-specific first ECS provider identifier. Here, for the UE-specific first ECS provider identifier, reference may be made to the description of the first aspect, and details are not repeated here.

In a fourth aspect, the present application provides a communication method, which includes: the SMF receives a UE-specific first ECS provider identifier from a network data analysis function (network data analysis function, NWDAF) NWDAF or AMF; The ECS provider ID sends the first ECS configuration information to the UE, the first ECS configuration information includes the first ECS provider ID and the address of the first ECS, and the first ECS corresponds to the first ECS provider ID; the SMF sends The UE sends the first ECS configuration information.

Here, for the UE-specific first ECS provider identifier, reference may be made to the description of the first aspect, and details are not repeated here. This solution obtains UE-specific ECS Provider ID from NWDAF or AMF through SMF, and SMF sends UE-specific ECS configuration information corresponding to the UE-specific ECS Provider ID (that is, the first ECS configuration information), which can reduce redundant ECS configuration information. cell.

With reference to the fourth aspect, in a possible implementation manner, the SMF sending the first ECS configuration information to the UE according to the first ECS provider identifier includes: the SMF determines the first ECS configuration information according to the first ECS provider identifier, and Send the first ECS configuration information to the UE.

With reference to the fourth aspect, in a possible implementation manner, the foregoing first ECS configuration information may be carried in a session establishment acceptance message or a session modification response message.

With reference to the fourth aspect, in a possible implementation manner, before the SMF receives the UE-specific first ECS provider identifier from the NWDAF, the method further includes: the SMF sends a first request message to the NWDAF, and the first request message is used for Obtain the UE-specific ECS provider ID. Optionally, the first request message includes the identifier of the UE.

Optionally, the foregoing first request message may specifically be a subscription message. When the UE-specific first ECS provider identifier changes, the NWDAF may also send a notification message to the SMF to notify the UE-specific first ECS provider identifier of the change.

Optionally, the above first request message further includes one or more of the following: data network name (data network name, DNN), single network slice selection assistance information (single network slice selection assistance information, S-NSSAI). Wherein, the DNN and/or the S-NSSAI are used to determine the UE-specific first ECS provider identifier. Specifically, the role of the DNN and/or S-NSSAI is to indicate that the ECS corresponding to the ECS Provider ID commonly used by the UE is an ECS that needs to support the DNN and S-NSSAI.

In this solution, the SMF subscribes to the NWDAF for the UE-specific ECS provider ID, so that the SMF can obtain the UE-specific ECS provider ID. In addition, when the subsequent NWDAF finds that the UE-specific ECS provider ID has changed, the NWDAF can further send the updated UE-specific ECS provider ID to the SMF, so that the SMF can send the updated UE-specific ECS provider ID to the SMF based on the updated UE-specific ECS provider ID. The UE updates the ECS configuration information.

With reference to the fourth aspect, in a possible implementation manner, when the above-mentioned first ECS changes, the update of the configuration information of the first ECS may refer to the description of the first aspect, and details are not repeated here.

With reference to the fourth aspect, in a possible implementation manner, the first ECS provider ID is one or more ECS provider IDs. After the SMF sends the first ECS configuration information to the UE, the method further includes: if the second ECS corresponding to the second ECS provider identifier changes and the second ECS provider identifier belongs to the first ECS provider identifier, the SMF Send the second ECS provider identifier and the changed address of the second ECS to the UE.

With reference to the fourth aspect, in a possible implementation manner, after the SMF sends the first ECS configuration information to the UE, the method further includes: the SMF receives from the NWDAF or AMF a fourth ECS provider identifier update for the first ECS Provider ID: The SMF sends fourth ECS configuration information to the UE according to the fourth ECS provider ID, the fourth ECS configuration information includes the fourth ECS provider ID and the address of the fourth ECS, and the fourth ECS is related to the fourth ECS The four ECS provider IDs correspond.

In this solution, the SMF sends updated ECS configuration information to the UE when the ECS corresponding to the UE-specific ECS Provider ID needs to be updated, thereby avoiding unnecessary updating signaling of ECS configuration information and reducing signaling overhead in the network.

With reference to the fourth aspect, in a possible implementation manner, after the SMF sends the first ECS configuration information to the UE, the method further includes: the SMF receives a second message from the UE, and the second message includes the fifth ECS provider identifier or a second application identifier, where the second application identifier is used to determine a fifth ECS provider identifier, and the fifth ECS provider identifier does not belong to the first ECS provider identifier; the SMF sends the fifth ECS provider identifier to the UE Identifies the address of the corresponding ECS. This solution provides a solution in which the UE uses an unused ECS.

In a fifth aspect, the present application provides a communication method, the method comprising: the UE receives first ECS configuration information from the SMF, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first The ECS corresponds to the first ECS provider identifier.

With reference to the fifth aspect, in a possible implementation manner, the first ECS configuration information is used by the UE to determine the ECS. Specifically, the UE determines the ECS used for EES discovery according to the first ECS configuration information. The UE may also send an EES discovery request to the ECS for EES discovery. It should be understood that for the UE-specific first ECS provider identifier, reference may be made to descriptions in other aspects.

With reference to the fifth aspect, in a possible implementation manner, after the UE receives the first ECS configuration information from the SMF, the method further includes: the UE receives second ECS configuration information from the SMF, and the second ECS configuration information includes the first ECS configuration information. The ECS provider ID and the changed address of the first ECS. Wherein, the first ECS may change due to reasons such as UE movement, load balancing, and ECS downtime.

With reference to the fifth aspect, in a possible implementation manner, the first ECS provider ID is one or more ECS provider IDs. After the UE receives the first ECS configuration information from the SMF, the method further includes: the UE receives the second ECS provider identifier and the changed address of the second ECS from the SMF, and the second ECS provider identifier belongs to the first ECS provider ID, the second ECS corresponds to the second ECS provider ID.

With reference to the fifth aspect, in a possible implementation manner, after the UE receives the first ECS configuration information from the SMF, the method further includes: the UE receives fourth ECS configuration information from the SMF, and the fourth ECS configuration information includes the fourth ECS configuration information. The provider ID and the address of the fourth ECS. The fourth ECS provider ID is obtained by updating the first ECS provider ID. The fourth ECS corresponds to the fourth ECS provider ID.

With reference to the fifth aspect, in a possible implementation manner, after the UE receives the first ECS configuration information from the SMF, the method further includes: the UE sends a second message to the SMF, where the second message includes the fifth ECS provider identifier or A second application identifier, where the second application identifier is used to determine a fifth ECS provider identifier, and the fifth ECS provider identifier does not belong to the first ECS provider identifier; the UE receives the fifth ECS provider identifier from the SMF The address of the corresponding ECS.

In a sixth aspect, the present application provides a communication method, which includes: NWDAF acquires a UE-specific first ECS provider identifier; NWDAF sends the first ECS provider identifier to SMF or AMF.

Here, for the UE-specific ECS provider identifier, reference may be made to descriptions in other aspects.

With reference to the sixth aspect, in a possible implementation manner, before the NWDAF obtains the UE-specific first ECS provider identifier, the method further includes: the NWDAF receives a first request message from the SMF, and the first request message is used to obtain the UE A specific ECS provider ID. Optionally, the first request message includes the identifier of the UE.

Optionally, for the specific implementation of the above first request message, refer to the description of the fourth aspect, and details are not repeated here.

With reference to the sixth aspect, in a possible implementation manner, before the NWDAF obtains the UE-specific first ECS provider identifier, the method further includes: the NWDAF receives a first request message from the AMF, and the first request message is used to obtain the UE A specific ECS provider ID. Optionally, the first request message includes the identifier of the UE.

Optionally, the foregoing first request message may specifically be a subscription message. When the UE-specific first ECS provider identifier changes, the NWDAF may also send a notification message to the AMF to notify the UE-specific first ECS provider identifier of the change.

Optionally, the above first request message further includes allowed NSSI (allowed NSSI). Specifically, the role of allowing NSSAI is to indicate that the ECS corresponding to the UE-specific ECS Provider ID is an ECS that supports this allowed NSSAI.

With reference to the sixth aspect, in a possible implementation manner, the NWDAF acquires the UE-specific first ECS provider identifier, including: NWDAF requests one or more AFs to subscribe to the UE's usage of the application program; NWDAF obtains from one or more AFs An AF receives the UE's use of the application program; the NWDAF determines the UE-specific first ECS provider identifier according to the UE's use of the application program. Here, the UE's use of the application program includes one or more of the following: use frequency, average use duration, use times, application download rate, and the like.

This solution determines the UE-specific ECS provider ID based on the UE's use of the application program, so that the SMF only sends the ECS configuration information corresponding to the commonly used ECS provider ID to the UE, thereby reducing the number of information elements in the ECS configuration information.

With reference to the sixth aspect, in a possible implementation manner, after the NWDAF sends the first ECS provider identifier to the SMF or AMF, the method further includes: the NWDAF receives the UE-to-application request from one or more AFs If the use situation changes, determine the updated fourth ECS provider ID for the first ECS provider ID; the NWDAF sends the fourth ECS provider ID to the SMF or AMF.

In a seventh aspect, the present application provides a communication method, which includes: AMF sends a first request message to NWDAF, where the first request message is used to obtain a UE-specific ECS provider identifier; AMF receives the UE-specific first ECS provider identifier from NWDAF. The ECS provider identifier; the AMF sends the UE-specific first ECS provider identifier to the SMF. Here, for the UE-specific ECS provider identifier, reference may be made to descriptions in other aspects, which will not be repeated here.

Optionally, the first request message includes the identifier of the UE.

Optionally, the foregoing first request message may specifically be a subscription message. When the UE-specific first ECS provider identifier changes, the AMF may also receive a notification message sent by the NWDAF, where the notification message is used to notify the UE-specific first ECS provider identifier of the change.

Optionally, the foregoing first request message further includes allowing NSSAI. Specifically, the function of allowing NSSAI is to indicate that the ECS corresponding to the common ECS Provider ID of the UE needs to support the ECS that allows NSSAI.

With reference to the seventh aspect, in a possible implementation manner, the above-mentioned update of the first ECS provider identifier may refer to descriptions in other aspects, and details are not repeated here.

In an eighth aspect, the present application provides a communication method, the method comprising: the SMF obtains a UE-specific first ECS provider identifier from the AF or AMF; the SMF sends the first ECS configuration information to the UE according to the first ECS provider identifier , the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS corresponds to the first ECS provider identifier.

For the UE-specific ECS provider identifier, reference may be made to descriptions in other aspects, and details are not described here.

In this solution, the AF analyzes the UE-specific ECS Provider ID and sends it to the SMF (via AMF), and the SMF sends the UE the configuration information of the ECS corresponding to the ECS Provider ID commonly used by the UE (that is, the first ECS configuration information), which can reduce the ECS configuration information redundant cells.

With reference to the eighth aspect, in a possible implementation manner, the SMF sending the first ECS configuration information to the UE according to the first ECS provider identifier includes: the SMF determines the first ECS configuration information according to the first ECS provider identifier, and Send the first ECS configuration information to the UE.

With reference to the eighth aspect, in a possible implementation manner, the foregoing first ECS configuration information may be carried in a session establishment acceptance message or a session modification response message.

With reference to the eighth aspect, in a possible implementation manner, when the above-mentioned first ECS changes, the update of the configuration information of the first ECS may refer to the description in the first aspect, and details are not repeated here.

With reference to the eighth aspect, in a possible implementation manner, the first ECS provider ID is one or more ECS provider IDs. After the SMF sends the first ECS configuration information to the UE, the method further includes: if the second ECS corresponding to the second ECS provider identifier changes and the second ECS provider identifier belongs to the first ECS provider identifier, the SMF Send the second ECS provider identifier and the changed address of the second ECS to the UE.

With reference to the eighth aspect, in a possible implementation manner, after the SMF sends the first ECS configuration information to the UE, the method further includes: the SMF receives from the AF or AMF a fourth ECS provider identity update update for the first ECS Provider ID: SMF sends the fourth ECS configuration information to the UE according to the fourth ECS provider ID, the fourth ECS configuration information includes the fourth ECS provider ID and the address of the fourth ECS, the fourth ECS is related to the Corresponding to the fourth ECS provider identifier.

With reference to the eighth aspect, in a possible implementation manner, after the SMF sends the first ECS configuration information to the UE, the method further includes: the SMF receives a second message from the UE, and the second message includes the fifth ECS provider identifier or a second application identifier, where the second application identifier is used to determine a fifth ECS provider identifier, and the fifth ECS provider identifier does not belong to the first ECS provider identifier; the SMF sends the fifth ECS provider identifier to the UE Identifies the address of the corresponding ECS. This solution provides a solution in which the UE uses an unused ECS.

In a ninth aspect, the present application provides a communication method, the method comprising: an application function entity (application function, AF) determines a UE-specific first ECS provider identifier according to the usage of the application program by the UE; the AF sends the SMF or AMF Send the first ECS provider identifier.

Here, for the UE-specific ECS provider identifier, reference may be made to descriptions in other aspects, which will not be repeated here.

With reference to the ninth aspect, in a possible implementation manner, after the AF sends the first ECS provider identifier to the SMF or AMF, the method further includes: the AF sends an update message for the first ECS provider identifier to the SMF or AMF The fourth ECS provider ID.

In a tenth aspect, the present application provides a communication method, which includes: AMF obtains a UE-specific first ECS provider identifier from an AF; AMF sends the UE-specific first ECS provider identifier to an SMF. Here, for the UE-specific ECS provider identifier, reference may be made to descriptions in other aspects, which will not be repeated here.

With reference to the tenth aspect, in a possible implementation manner, after the AMF sends the UE-specific first ECS provider identifier to the SMF, the method further includes: the AMF receives a fourth update update of the first ECS provider identifier from the AF. The ECS provider identifier; the AMF sends the fourth ECS provider identifier to the SMF.

In an eleventh aspect, the present application provides a communication device, which may be any one of SMF, UE, AMF, NWDAF, and AF, or a chip therein. The communication device includes a unit and/or module for performing any one of the first aspect to the eleventh aspect above, or the communication method provided by any possible implementation of any one of the aspects, such as a transceiver unit And/or the processing unit, the transceiver unit is used to send and receive various information or signaling, so the beneficial effects (or advantages) of the communication method provided by any of the above aspects can also be realized.

In a twelfth aspect, the present application provides a communication device, where the communication device may include a processor and a transceiver. Wherein, the transceiver is used to send and receive various information or signaling, the computer program includes program instructions, and when the processor executes the program instructions, the communication device is made to execute any one of the above first aspect to the above tenth aspect, Or the communication method described in any possible implementation of any aspect. Wherein, the transceiver may be a radio frequency module in the communication device, or a combination of a radio frequency module and an antenna, or an input and output interface of a chip or a circuit. Optionally, the communication device further includes a memory, where the memory is used to store computer programs.

In a thirteenth aspect, the present application provides a readable storage medium, on which program instructions are stored, and when it is run on a computer, the computer executes any one of the above-mentioned first aspect to the above-mentioned tenth aspect , or the communication method described in any possible implementation of any aspect.

In the fourteenth aspect, the present application provides a program product containing instructions. When the instructions are executed, the communication method described in any possible implementation manner of any one of the first aspect to the tenth aspect above is executed. .

In a fifteenth aspect, the present application provides an apparatus, which may be implemented in the form of a chip or in the form of equipment, and the apparatus includes a processor. The processor is used to read and execute the program stored in the memory, so as to implement one or more of any one of the above-mentioned first aspect to the above-mentioned tenth aspect, or, in any possible implementation manner of any one of them One or more of the provided communication methods. Optionally, the device further includes a memory, and the memory is connected to the processor through a circuit. Further optionally, the device further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive information and/or signaling that needs to be processed, and the processor obtains the information and/or signaling from the communication interface, processes the information and/or signaling, and outputs the information and/or signaling through the communication interface process result. The communication interface may be an input-output interface.

Optionally, the above-mentioned processor and memory may be physically independent units, or the memory may also be integrated with the processor.

In a sixteenth aspect, the present application provides a communication system, which includes the communication devices described in the first aspect to the third aspect above, or the communication devices described in the fourth aspect to the seventh aspect above, or the communication device described in the eighth aspect above Aspect to the communication device described in the tenth aspect above.

Implementing the embodiment of the present application can not only reduce redundant information elements in the ECS configuration information, but also reduce the signaling overhead of the ECS configuration in the network.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings that need to be used in the description of the embodiments.

Figure 1 is a schematic diagram of SA WG2 non-roaming network architecture;

Figure 2 is a schematic diagram of the architecture of the interaction between NWDAF network elements and other network elements;

Figure 3 is a schematic diagram of the SA WG6 edge computing network architecture;

FIG. 4 is a schematic diagram of changes in the ECS available to the UE during the UE's movement;

FIG. 5 is a first schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 6 is a second schematic flowchart of the communication method provided by the embodiment of the present application;

FIG. 7 is a third schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 8 is a fourth schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 9 is a fifth schematic flowchart of the communication method provided by the embodiment of the present application;

FIG. 10 is a sixth schematic flowchart of a communication method provided by an embodiment of the present application;

FIG. 11 is a seventh schematic flow chart of the communication method provided by the embodiment of the present application;

Fig. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of a communication device 1000 provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

In the description of the present application, unless otherwise specified, "/" means "or", for example, A/B may mean A or B. The "and/or" in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist at the same time, and B exists alone These three situations. In addition, "at least one" means one or more, and "plurality" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (unit) of a, b, or c may represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, c can be single or multiple.

In the description of this application, words such as "first" and "second" are only used to distinguish different objects, and do not limit the number and execution order, and words such as "first" and "second" do not limit It must be different. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally It also includes other steps or units inherent to these processes, methods, products, or devices.

In this application, words such as "exemplary" or "for example" are used to mean an example, illustration or description. Any embodiment or design described in this application as "exemplary", "for example" or "such as" is not to be construed as preferred or advantageous over other embodiments or designs. Rather, use of words such as "exemplary," "for example," or "such as" is intended to present related concepts in a specific manner.

It should be understood that in this application, "when", "if" and "if" all mean that the device will make corresponding processing under certain objective circumstances, it is not a time limit, and it is not required that the device must The act of judgment does not mean that there are other limitations.

"Simultaneously" in this application can be understood as at the same time point, within a certain period of time, or within the same period, which can be specifically understood in conjunction with the context.

In this application, an element expressed in the singular is intended to mean "one or more" rather than "one and only one", unless otherwise specified.

Additionally, the terms "system" and "network" are often used herein interchangeably. The terms "network element" and "entity" may also be used interchangeably herein, for example, "session management function entity" and "session management function network element" may represent the same device.

It can be understood that, in each embodiment of the present application, "A corresponds to B" means that there is a corresponding relationship between A and B, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.

The following briefly introduces the network architecture of this application. It should be understood that the network architecture described in the present application is for more clearly illustrating the technical solutions of the embodiments of the present application, and does not constitute a limitation to the technical solutions provided by the embodiments of the present application.

The terminal equipment in this application may also be referred to as terminal, user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), etc., which may be a user-side device for An entity that receives or transmits signals, such as a mobile phone; it can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as aircraft, balloons, and satellites) superior). UEs include handheld devices, vehicle-mounted devices, wearable devices, or computing devices with wireless communication capabilities. Exemplarily, the UE may be a mobile phone, a tablet computer, or a computer with a wireless transceiver function. The terminal device can also be a virtual reality (virtual reality, VR) terminal device, an augmented reality (augmented reality, AR) terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a smart Wireless terminals in power grids, wireless terminals in smart cities, wireless terminals in smart homes, etc. In the embodiment of the present application, the device for realizing the function of the terminal may be a terminal; it may also be a device capable of supporting the terminal to realize the function, such as a chip system, or a communication module, or a modem, etc., and the device may be installed in the terminal . In the embodiment of the present application, the system-on-a-chip may be composed of chips, or may include chips and other discrete devices. In the technical solution provided by the present application, the technical solution provided by the present application is described by taking the device for realizing the terminal function as the terminal and taking the terminal as the UE as an example. The embodiment of the present application does not limit the specific technology and specific device form adopted by the terminal device.

Optionally, the UE can also be used as a base station. For example, UE can act as a scheduling entity between UEs in vehicle-to-everything (V2X), device-to-device (D2D) or peer-to-peer (P2P), etc. Provides a sidelink signal.

Optionally, the UE may also serve as a relay node. For example, the UE can act as a relay device (relay), or access an integrated access and backhaul (IAB) node, to provide wireless backhaul services for terminal devices.

For ease of description, the terminal equipment shown below will use UE as an example to illustrate the technical solution provided by this application.

The technical solution provided by this application can be applied to various communication systems, such as: long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), Internet of things (internet of things, IoT) system, narrow band-internet of things (NB-IoT), wireless fidelity (Wi-Fi), fifth generation (5th generation, 5G) communication system or new radio (new radio, NR) and other communication systems in the future, such as the sixth generation mobile communication system.

For example, the technical solutions provided by this application can be applied to the framework formulated by the 3GPP Service & System Aspects Working Group 2 (SA WG2), and can also be applied to the network data analysis function (network data analysis function, NWDAF) network elements interact with other network elements. Referring to Figure 1, Figure 1 is a schematic diagram of the SA WG2 non-roaming network architecture. As shown in Figure 1, the network architecture may include but not limited to the following: Network Slice-Specific Authentication and Authorization Function (NSSAAF), Network Slice Selection Function (NSSF), Policy Control function (policy control function, PCF), unified data management (unified data management, UDM), application function (application function, AF), authentication server function (authentication server function, AUSF), access and mobility management function (access and mobility management function (AMF), session management function (session management function, SMF), user plane function (user plane function, UPF), user equipment (user equipment, UE), (wireless) access network ((radio) access network, (R)AN), and data network (data network, DN), etc.

Among them, the AMF is mainly responsible for the mobility management in the mobile network, such as user location update, user registration network, user handover and so on. SMF is mainly responsible for session management in the mobile network, such as session establishment, modification, and release. Specific functions such as assigning Internet Protocol (Internet Protocol, IP) addresses to users, selecting UPF that provides message forwarding functions, etc. The purpose of the interaction between AF and the core network is to provide services, such as supporting the following functions: impact on service routing, exposure of access network capabilities, and interaction with policy decision-making network elements for policy control, etc. The application server (Application Service, AS) network element can be deployed together with the AF network element, interacts with the UPF network element, and is responsible for sending, receiving and processing uplink and downlink messages on the user plane.

It should also be understood that the functions or roles of each network element shown in FIG. 1 may refer to related protocols or standards, and will not be described in this application. It should also be understood that N1, N2, N3, N4, N5, N6, N7, N8, N10, N11, N12, N13, N14, N15, N22, N58, N59, etc. shown in FIG. 1 are all interface serial numbers. For example, the meaning of the above-mentioned interface serial number can refer to the meaning defined in the 3GPP standard agreement, and the present application does not limit the meaning of the above-mentioned interface serial number.

Referring to FIG. 2, FIG. 2 is a schematic diagram of the architecture of the interaction between the NWDAF network element and other network elements. As shown in 2(a) of Figure 2, it shows the architecture used for data collection, that is, the architecture used when NWDAF network elements call services of other 5G core network elements to collect input information required for network analysis. As shown in 2(b) of FIG. 2 , it shows the architecture used when the data is open, that is, the architecture where the NWDAF network element sends the analysis data to the network element that subscribes or requests the analysis data by providing the NWDAF service. Among them, NWDAF represents the network analysis logic function managed by the operator. NWDAF network elements provide slice-level network data analysis for other network elements, and provide network analysis information (ie, load level information) at the network slice instance level, without knowing the current subscribers using the slice. "Any NF" shown in Figure 2 means any network function element, and "Nnf" and "Nnwdaf" mean the name of the service interface. For details, please refer to the relevant description in the 3GPP standard protocol, which will not be explained here.

The above content briefly describes the network architecture of the present application. In order to better understand the technical solutions provided by the embodiments of the present application, the application scenarios of the embodiments of the present application will be introduced below. The technical solutions provided by the embodiments of the present application can be applied to edge computing scenarios.

The 3GPP standard agreement TS 23.558 defines the service and system aspect working group 6 (SA WG6) edge computing network architecture. Specifically, refer to Figure 3, which is a schematic diagram of the SA WG6 edge computing network architecture. As shown in Figure 3, UE includes two functional components: application client (application client, AC) and edge enabler client (edge enabler client, EEC), edge application server (edge application server, EAS) and edge enabler server (Edge Enabler Server, EES) is deployed in the local edge data network (Edge Data Network, EDN). The edge configuration server (ECS) provides EES-related configuration information, including information about the EDN where EES is deployed, and can be used for EES discovery. Among them, the EEC is used to provide support functions required by the AC, including but not limited to: EAS discovery, obtaining and providing configuration information for traffic exchange between the AC and the EAS, and the like. ECS is used to provide the support functions required by EEC to access EES, including but not limited to: provide EEC with edge configuration information (such as EES Uniform Resource Identifier (Uniform Resource Identifier, URI), service area, etc.), and support EES to Information about registration to ECS and other functions. EES is used to provide the supporting functions required by EAS and EEC, including but not limited to: providing EAS configuration information to EEC, supporting EAS to register relevant information with EES, and supporting application context migration and other functions. EAS is an application server deployed in the EDN to provide edge computing (edge computing, EC) services.

It should be understood that EDGE-1, EDGE-2, EDGE-3, EDGE-4, EDGE-5, EDGE-6, EDGE-7, EDGE-8, and EDGE-9 shown in FIG. 3 are all interfaces. For example, the meaning of the above interface may refer to the meaning defined in the 3GPP standard agreement, which is not limited in the present application.

It should be understood that some of the network elements or functions in Figure 3 correspond to the SA WG2 non-roaming network architecture, where the AC and EEC in Figure 3 correspond to the UE in the aforementioned Figure 1, and the ECS, EES, and EAS can correspond to the aforementioned Figure 1 AF network element or AS network element in 1.

According to the architecture and process specified in 3GPP TS 23.558, UE can obtain EES information through ECS, and then obtain EAS information through EES, so as to access EAS to obtain required services. Therefore, in order to obtain the required services through the edge computing network, the UE first needs to access the ECS. In order to access the ECS, the UE needs to obtain ECS configuration information (ECS configuration information). Wherein, the ECS configuration information may also be referred to as ECS address information, or ECS address configuration information, etc., which is not limited in this embodiment of the present application. The ECS configuration information includes the following information of one or more ECSs: (1) The address of the ECS, which can be the full qualified domain name (full qualified domain name, FQDN), Internet protocol (internet protocol, IP) address or uniform resource locator of the ECS One or more of (uniform resource locator, URL), the information provided to the UE can be used to access the ECS. (2) ECS Provider ID (ECS Provider ID), which can be used to characterize the deployer of this ECS, where ECS can be deployed by an operator or a third party, and this information can indicate the business capability or function of ECS, for example, UE wants to access A The EAS deployed by the company can be realized by first connecting to the ECS deployed by company A, and the ECS corresponding to other ECS Provider IDs may not be able to connect to the EAS deployed by company A. It should be noted that accessing the EAS deployed by Company A does not necessarily require accessing the ECS corresponding to Company A's ECS Provider ID first. On the contrary, accessing the ECS corresponding to the ECS Provider ID of non-Company A may also be possible. The EAS deployed by the company depends on the deployment of the edge server. (3) ECS identifier (Identifier, ID), which is the unique identifier of ECS.

It should be noted that the content of the above ECS configuration information is described based on the progress of the current standard. With the development of technology and the update of standards, the content of the ECS configuration information may also change. The content of the ECS configuration information in the technical solution provided by this application can also be changed accordingly. It can also be said that in the technical solution provided by the present application, the content of the ECS configuration information may be consistent with current standards or future standards, and the embodiment of the present application does not limit the specific content of the ECS configuration information.

Regarding how the UE obtains the ECS configuration information, the TS 23.558 standard stipulates that the UE can obtain the ECS configuration information in one of the following ways: (1) pre-configuration; (2) configuration by the edge-aware AC; (3) configuration by the user; ( 4) Issued by the 5G Core Network (5G Core Network, 5GC); (5) Deduced through the PLMN identifier (Identifier, ID). The embodiment of the present application focuses on the method (4), and the relevant content of the method (4) is stipulated in the standard TS 23.548. For details, please refer to the description of the corresponding standard.

The standard TS 23.548 stipulates that SMF network elements can obtain ECS configuration information through local configuration or from UDM network elements. The UE then sends indication information to the SMF network element through the protocol data unit (protocol data unit, PDU) session establishment or modification process, used to indicate that it (whether) has the ability to use ECS (for example, (whether) has EEC) or whether Hope to use ECS. The SMF network element sends ECS configuration information (of all ECSs that the SMF network element can perceive) to the UE according to the indication information. Because the ECS provider can deploy one or more ECSs in different locations in the PLMN, and because the deployment locations are different, edge service platforms in different locations can be managed. An ECS has a service range, and a UE can access this ECS only when it is within the service range of an ECS. Therefore, when the UE moves, the available ECS list of the UE may change, so after the SMF network element initially sends the ECS configuration information to the UE, it may also need to send the updated ECS configuration information to the UE (the SMF network element can perceive the UE location, and can also obtain the service range of each ECS (here refers to the ECS perceived by the SMF network element), so the SMF network element can determine whether to update the list of ECS available to the UE). Of course, the SMF network element may also send updated ECS configuration information to the UE for other reasons, such as local policy update, UE subscription information update, and so on.

It should be noted that the service scope of the ECS can also be expressed as the space availability condition, space condition, location condition, etc. of the ECS, and this application does not limit its name. The service range of the ECS can be understood as: (1) the range that can/can provide services for the UE; (2) the range that is most suitable for serving the UE or the best range for serving the UE. It can be understood that the service range of a certain ECS includes the UE, and it can be understood that the ECS can/can provide services for the UE at the current location, or the ECS is the most suitable ECS for serving the UE at the current location. Among them, the meaning of the ECS most suitable for serving the UE at the current location can be interpreted as, among all ECSs that can provide services for the current location of the UE, one or more of the following conditions are met: the closest to the current location of the UE, The load is the lowest, the user plane path with the UE is the shortest, and the delay is the lowest. It should be noted that the above conditions are only for illustrating that the ECS has the best service effect for the UE, and the conditions for judging the most suitable ECS for serving the UE at the current location may not be limited to the conditions listed above.

Because the 5GC does not perceive the services that the UE needs to access or may access, the ECS configuration information initially sent by the SMF network element to the UE includes the ECS Provider ID corresponding to some ECS that the UE may not use. When the SMF network element detects that the ECS corresponding to any ECS Provider ID needs to be updated, it must send the updated ECS configuration information to the UE.

Although the network will provide a variety of services to the UE, and multiple ECS providers (ie operators and/or third parties) will deploy multiple ECSs, in fact the UE may only use some of the services, that is to say The services that may be used by the UE are limited. For example, although there are tens of thousands of different applications in the application store, a smartphone usually only has dozens of different applications installed, which means that the UE can only use the resources of this small number of installed applications. Business (without considering the installation/uninstallation of applications), that is, the UE may only use the ECS corresponding to some ECS Provider IDs. Based on this, when the UE moves (or other reasons such as load balancing, here only the UE moves as an example), the ECS configuration information is updated, even if the update does not involve the ECS that the UE may use, the SMF network element still sends the update to the UE. ECS configuration information, which will result in waste of signaling. In addition, the ECS configuration information initially sent by the SMF network element to the UE includes some ECS Provider IDs corresponding to the ECS that the UE may not use. This also results in some redundant information elements being included in the ECS configuration information. To better understand this issue, an example is given below.

For example, refer to FIG. 4 . FIG. 4 is a schematic diagram of changes in ECS available to the UE during the movement of the UE. Among them, it is assumed that there are three ECS deployers A, B, and C in the network (such as PLMN) (that is, ECS Provider, for the convenience of description, the corresponding ECS Provider IDs are represented by A, B, and C respectively). Each ECS Provider deploys two ECS instances in different locations (for ease of illustration, the ECS IDs are represented as A1, A2, B1, B2, C1, and C2). In Figure 4, the solid straight line 100, the solid straight line 200, and the solid straight line 300 respectively indicate the boundaries where different ECS providers need to be switched to ECS instances. For example, when the UE is above the solid line 100, use A1 when using the ECS provided by company A; when the UE is below the solid line 100, use A2 when using the ECS provided by company A. When the UE is on the left side of the solid straight line 200, B1 should be used when using the ECS provided by company B; when the UE is on the right side of the solid straight line 200, B2 should be used when using the ECS provided by company B. When the UE is above the solid line 300, C1 should be used when using the ECS provided by C company; when the UE is below the solid line 300, C2 should be used when using the ECS provided by C company.

It is assumed that the UE may only use the ECS provided by company A, and it is assumed that the UE moves in the direction shown by the dotted line in FIG. 4 .

According to the standard, the ECS configuration information sent by the network side (such as SMF network element) to the UE is: {{A, A1, A1's IP address}, {B, B1, B1's IP address}, {C, C1, C1 IP address}}.

When the UE moves through the solid line 100, the network side (such as the SMF network element) sends the updated ECS configuration information to the UE: {{A, A2, A2's IP address}, {B, B1, B1's IP address}, {C, C1, IP address of C1}}.

When the UE continues to move through the solid line 300, the network side (such as the SMF network element) sends the updated ECS configuration information to the UE: {{A, A2, A2's IP address}, {B, B1, B1's IP address} , {C, C2, IP address of C2}}.

When the UE continues to move through the solid straight line 200, the network side (such as the SMF network element) sends updated ECS configuration information to the UE: {{A, A2, A2's IP address}, {B, B2, B2's IP address} , {C, C2, IP address of C2}}.

It should be understood that the content of the above ECS configuration information is only an example, and in actual implementation, the content of the ECS configuration information may change as the standard changes, and be consistent with the standard.

Because the UE may only use the ECS provided by company A, the last two updates in the three updates of the ECS configuration information are unnecessary, and the ECS information related to company B and company C in the ECS configuration information is also unnecessary .

Therefore, the embodiment of the present application provides a communication method, which can not only reduce redundant cells in the ECS configuration information, but also reduce unnecessary updating of the ECS configuration information, thereby reducing signaling overhead in the network.

The technical solutions provided by the present application will be described in detail below in conjunction with more drawings.

The technical solutions provided by the present application are described through multiple embodiments, and specifically refer to the description of each embodiment below. The parts that are the same or similar among the various embodiments or implementations may refer to each other. In the various embodiments in this application, and the various implementation methods/implementation methods/implementation methods in each embodiment, if there is no special description and logical conflict, different embodiments, and each implementation method/implementation method in each embodiment The terms and/or descriptions between implementation methods/implementation methods are consistent and can be referred to each other. Different embodiments, and the technical features in each implementation manner/implementation method/implementation method in each embodiment are based on their inherent Logical relationships can be combined to form new embodiments, implementation modes, implementation methods, or implementation methods. The following embodiments of the present application are not intended to limit the protection scope of the present application.

Each embodiment will be described in detail below.

In this application, "session management function entity", "session management function network element" and "SMF" can be used interchangeably, and the three can represent the same device. Similarly, "access and mobility management functional entity", "access and mobility management functional network element" and "AMF" can also be used interchangeably to indicate the same device. "Network data analysis function entity", "network data analysis function network element" and "NWDAF" can also be used interchangeably to represent the same device. "Application Function Entity", "Application Function Network Element" and "AF" can also be used interchangeably to represent the same device. The terminal device in this application may be UE. It should be understood that with the development of communication technologies, the names of network elements may also change, which is not limited in this application.

Embodiment one

Referring to FIG. 5 , FIG. 5 is a first schematic flowchart of a communication method provided by an embodiment of the present application. As shown in Figure 5, the communication method includes but is not limited to the following steps:

S101. The SMF obtains a first UE-specific edge configuration server (edge configuration server, ECS) provider identifier.

Optionally, the SMF may acquire the UE-specific first ECS provider identifier locally, for example, the UE-specific first ECS provider identifier is pre-stored in the SMF. Alternatively, the SMF can also obtain the UE-specific first ECS provider ID from other network elements, for example: the SMF receives the UE-specific first ECS provider ID sent by the UE, or the SMF receives the UE-specific first ECS provider ID sent by the AMF. or the SMF receives the UE-specific first ECS provider identifier sent by the NWDAF, or the SMF receives the UE-specific first ECS provider identifier sent by the AF. Specifically, the manner in which the SMF obtains the UE-specific first ECS provider identifier (from other network elements) may refer to the description of the following embodiments, and details are not repeated here. In another possible implementation, the SMF determines the first ECS provider identifier according to information received from other network elements, for example, the SMF determines the UE-specific first ECS provider identifier according to the application identifier (Application ID, AppID) received from the UE. Provider ID.

In this application, the ECS provider ID (ECS provider ID) can be used to identify the ECS or the ECS service, or the provider of the edge service platform/environment, or the deployment party, or the management party, etc. The ECS provider ID may also be called the ECS manager ID or other names, which are not limited in this application.

In this application, the UE-specific first ECS provider ID can be understood as: the ECS provider ID that the UE may use, or the ECS provider ID commonly used by the UE, or the ECS provider ID determined for the UE, or the ECS provider ID corresponding to the UE etc. In other words, a UE-specific ECS provider ID is an ECS provider ID that is associated or bound to this UE. For example, the ECS provider ID (ECS provider ID) related to the application program downloaded or installed in the UE, or the ECS provider ID related to the application program commonly used in the UE, or the ECS provider ID related to the application program signed by the UE, etc. wait. The meaning of "UE-specific ECS provider ID" mentioned below will not be described in detail.

Exemplarily, "UE-specific first ECS Provider ID" can be understood as a collection of ECS Provider IDs corresponding to the deployer or manager of all or part of the applications available to the UE, or all or part of the applications available to the UE may receive A set of ECS Provider IDs corresponding to the imported ECS. The "available applications" may refer to the applications installed by the UE, or the applications installed by the UE and cloud storage applications, or the applications registered on the UE, or the applications determined by the UE according to usage conditions, etc.

Exemplarily, the "UE-specific first ECS provider identifier" can be understood as according to the usage of the application by the UE (including but not limited to the frequency of use of the application, the duration of use, the download rate of the application, or other characteristics of the usage of the application by the UE) One or more of the parameters of ) determine the ECS provider ID.

S102. The SMF sends first ECS configuration information to the UE, where the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS corresponds to the first ECS provider identifier.

S103. The UE receives the first ECS configuration information.

Optionally, after obtaining the first ECS provider identifier, the SMF may determine the first ECS configuration information according to the first ECS provider identifier, and send the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information. Wherein, the first ECS configuration information includes the first ECS provider identifier and related information of the first ECS, such as the address of the first ECS, the identifier of the first ECS, and the like. The address here may include one or more of the following: Fully Quantified Domain Name (FQDN), Internet Protocol (IP) address, and Uniform Resource Locator (URL). The first ECS corresponds to the first ECS provider ID (or the first ECS is provided by the provider/deployer identified by the first ECS provider ID), and the service scope (or space) of the first ECS availability) may include the current location of the UE.

Optionally, when the SMF perceives that the ECS configuration information of the UE needs to be updated (for example, the ECS corresponding to the first ECS provider identifier changes, or the first ECS changes, or the UE-specific ECS provider identifier changes, etc.) , the SMF sends the updated ECS configuration information to the UE. For a specific update process, refer to the description of the following embodiments, which will not be repeated here.

It should be understood that the content contained in the ECS configuration information in this application is only an example, and in practical applications, the name and content of the ECS configuration information may be consistent with existing standards or future standards.

The ECS configuration information sent by the SMF in the embodiment of the present application to the UE includes the UE-specific ECS provider ID and the ECS address corresponding to these ECS provider IDs, so that the UE can obtain the required ECS configuration information, thereby supporting edge computing , to reduce the end-to-end delay and jitter of user packets; and the ECS configuration information does not need to include ECS information that is irrelevant to the UE or impossible to use by the UE, so redundant information elements in the ECS configuration information can be reduced. In addition, the SMF sends updated ECS configuration information to the UE only when the ECS corresponding to the UE-specific ECS Provider ID needs to be updated, thereby reducing unnecessary signaling for updating the ECS configuration information, that is, reducing signaling overhead in the network.

The foregoing embodiment 1 briefly describes the communication method provided by the present application, and the following embodiments 2 to 7 respectively describe the technical solutions provided by the present application in detail. It should be understood that the contents in the various embodiments of the present application may refer to each other, such as explanation of terms, specific messages, and so on. In addition, the methods and steps in the various embodiments can be combined with each other.

Embodiment 2 and Embodiment 3 of this application mainly introduce that the UE reports to the network side the ECS Provider ID corresponding to the ECS that may be used. When the ECS corresponding to these ECS Provider IDs is updated, the network side issues an update of the ECS configuration information; and when When the ECS Provider ID corresponding to the ECS that may be used/commonly used by the UE is updated, the UE updates the ECS Provider ID to the SMF. Embodiments 4 to 7 of this application mainly introduce that the network side analyzes the ECS Provider ID corresponding to the ECS commonly used by the UE and sends it to the SMF. When these ECS are updated, the SMF issues an update of the ECS configuration information; When the ECS Provider ID is updated, the network side sends the updated ECS Provider ID to the SMF.

Embodiment two

Referring to FIG. 6, FIG. 6 is a second schematic flowchart of the communication method provided by the embodiment of the present application. Exemplarily, the communication method provided by the embodiment of the present application may be applied to the network architecture shown in the aforementioned FIG. 1 or FIG. 3 . As shown in Figure 6, the communication method includes one or more of the following steps:

S201. The UE sends the UE-specific first ECS provider identifier and/or the UE-specific first application identifier to the SMF. Correspondingly, the SMF receives the UE-specific first ECS provider identifier and/or the UE-specific first application identifier.

Optionally, the UE obtains a UE-specific first ECS provider ID. In one implementation, when the UE downloads an application, the UE can perceive/acquire the ECS provider ID related to the application (that is, the first ECS provider ID logo). In other words, here the UE-specific first ECS provider identifier may refer to an ECS provider identifier related to an application that has been downloaded or installed in the UE. That is to say, when the UE downloads/installs an application, the ECS or ECS provider ID related to the application may be used by the UE. It should be understood that because a UE usually downloads/installs multiple applications, which may be related to one or more different ECS provider IDs, the UE-specific first ECS provider ID is one or more ECS provider ID. It should also be understood that the first ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs.

In another implementation, the UE can determine the ECS provider ID related to the application program frequently used by the UE (that is, the first an ECS provider ID). In other words, the UE-specific first ECS provider ID here may refer to an application-related ECS provider ID whose usage frequency is greater than the first threshold, and/or the number of times of usage is greater than the second threshold, and/or the usage duration is greater than the third threshold. . Wherein, the UE-specific first ECS provider identifier is one or more ECS provider IDs. Alternatively, the first ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs.

After acquiring the UE-specific first ECS provider identifier, the UE may send the UE-specific first ECS provider identifier to the SMF. Correspondingly, the SMF receives the first ECS provider identifier sent by the UE. Wherein, the UE-specific first ECS provider identifier may be carried in a session establishment request (PDU Session Establishment Request) message or a session modification request message, for example, the UE sends the PDU Session Establishment Request message to the AMF during the session establishment process, Then AMF forwards it to SMF through Nsmf_PDUSession_CreateSMContext Request message. Of course, the UE-specific first ECS provider identifier may also be carried in other messages, signaling or procedures, and the embodiment of the present application does not limit the method and procedure for the UE to report the ECS provider identifier.

Optionally, the UE acquires a UE-specific first application identifier. In an implementation manner, when the UE downloads the application program, the UE can perceive/obtain the identifier of the application program (that is, the first application program identifier). It can be understood that when the UE downloads an application, the UE may not only perceive/acquire the identifier of the application (that is, the first application identifier), but also perceive/obtain the ECS provider ID related to the application (that is, the first application identifier). ECS provider ID); in this case, the UE can determine whether to send the application program ID or the ECS provider ID to the network, which is not limited by the embodiment of this application. In another implementation, when the UE downloads the application, if the UE (due to UE capabilities and other reasons) cannot perceive/obtain the ECS provider ID (ie, the first ECS provider ID) related to the application, the UE can Perceive/obtain the identifier of the application program (that is, the identifier of the first application program). In other words, here the UE-specific first application identifier may refer to an identifier of an application program that has been downloaded or installed in the UE. That is to say, when the UE downloads/installs a certain application program, the application program may be used by the UE. Therefore, the UE-specific first application identifier is one or more application identifiers (application ID, AppID). It should be understood that the first application identifier can also be understood as a set or list, including one or more AppIDs.

In yet another implementation, the UE may determine the identity of the application that the UE frequently uses (that is, the first application logo). In other words, the UE-specific first application identifier here may refer to an identifier of an application whose use frequency is greater than the first threshold, and/or the number of uses is greater than the second threshold, and/or the use duration is greater than the third threshold. Wherein, the UE-specific first application identifier is one or more AppIDs. It should be understood that the first application identifier can also be understood as a set or list, including one or more AppIDs.

It should be noted that the first application identifier in this application can be used to identify a UE-specific application, such as AppID, EAS ID, EES ID, etc. This application does not limit the specific identification. In the following, the application identifier is AppID as an example, but it can be understood that the AppID mentioned in this application can also be replaced with other information elements that can identify the application, such as EAS ID.

After acquiring the UE-specific first application identifier, the UE may send the UE-specific first application identifier to the SMF. Correspondingly, the SMF receives the first application identifier sent by the UE. Wherein, the first application identifier may be used to determine a UE-specific first ECS provider identifier. The UE-specific first application identifier can be carried in the session establishment request message or the session modification request message. For example, in the session establishment process, the UE sends the PDU Session Establishment Request message to the AMF, and then the AMF forwards it to the AMF through the Nsmf_PDUSession_CreateSMContext Request message. SMF. Of course, the UE-specific first application identifier may also be carried in other messages, signaling or procedures, and the embodiment of the present application does not limit the method and procedure for the UE to report the application identifier.

In this application, information sent from UE to SMF or from SMF to UE can be forwarded by other network elements (such as AMF), and it is not necessarily that UE sends directly to SMF or SMF directly sends to UE. For ease of understanding, this application does not show the forwarding operation in the same flow. For example, the UE sends the UE-specific first ECS provider identifier to the SMF. In practical applications, the UE sends the UE-specific first ECS provider identifier to the The AMF forwards the first ECS provider identifier to the SMF.

S202. The SMF determines first ECS configuration information according to the first ECS provider ID or the first application program ID. The first ECS configuration information includes the first ECS provider ID and the address of the first ECS. The first ECS Corresponding to the first ECS provider ID.

S203. The SMF sends the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information.

Optionally, before step S202 (specifically, before step S201), the SMF may acquire the correspondence between the application identifier and the ECS provider identifier. After the SMF receives the UE-specific first application identifier, the SMF may determine the first ECS provider identifier corresponding to the first application identifier according to the corresponding relationship. In other words, if the UE identifies the first UE-specific application to the SMF, the SMF also obtains the correspondence between the AppID and the ECS provider ID.

Specifically, there are multiple ways for the SMF to obtain the corresponding relationship between the application ID and the ECS provider ID. For example, in one implementation, the SMF can obtain the correspondence between the application ID and the ECS provider ID locally, that is, before step S202 (specifically, before step S201), SMF has already configured locally related information, such as the correspondence between AppID and ECS provider ID.

In another implementation, before step S202 (specifically before step S201), the AF sends the correspondence between the application ID and the ECS provider ID to the SMF; correspondingly, the SMF receives the application ID sent by the AF The corresponding relationship with the ECS provider ID. It should be understood that, for a certain AF, the corresponding relationship sent to the SMF should be the corresponding relationship between the identifier of the application managed by the AF and the identifier of the ECS provider. Each AF in the network can send to the SMF the corresponding relationship between the application ID it manages and the ECS provider ID. Wherein, the corresponding relationship can be sent through the application function influence (AF influence) process, refer to the description of the 3GPP TS 23.502 standard for details, and will not be described here. Of course, the corresponding relationship may also be sent through other processes/methods, which is not limited in this embodiment of the present application. It should be noted that the AF here may be an ECS (Edge Configuration Server), or other network elements that manage the deployment of the ECS, which is not limited here.

In yet another implementation, before step S202 (specifically before step S201), the SMF obtains the correspondence between the application identifier and the ECS provider identifier from the UDM or unified data repository (unified data repository, UDR) network element relation. For example, in the session establishment/modification process, the SMF obtains the above corresponding relationship from the UDM/UDR network element through the Nudm_SDM_Get or Nudr_DM_Query message. For another example, in the registration process, the AMF obtains the above corresponding relationship from the UDM network element through the Nudm_SDM_Get message, and in the session establishment/modification process, the AMF sends the above corresponding relationship to the SMF through the Nsmf_PDUSessionSMContext Request message. Of course, the corresponding relationship may also be sent through other processes/methods, which is not limited in this embodiment of the present application.

Optionally, after the SMF receives the UE-specific first application identifier, the SMF may send the first application identifier to the AF (or other network elements, such as PCF, UDM, etc.) to request that the first application identifier correspond to and receive the first ECS Provider ID corresponding to the first application identifier from the AF (or other network elements, such as PCF, UDM, etc.) network element.

Optionally, after the SMF obtains the UE-specific first ECS Provider ID (the acquisition method may be by receiving the UE-specific first ECS Provider ID from the UE, or by receiving the UE-specific first AppID sent by the UE to determine the first ECS Provider ID). An ECS Provider ID, or the first ECS Provider ID configured locally by the SMF, etc.), the SMF can determine the first ECS configuration information according to the first ECS Provider ID. After determining the first ECS configuration information, the SMF may send the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information. The first ECS configuration information may be used by the UE to determine the ECS. Specifically, the UE may determine the ECS used for EES discovery according to the first ECS configuration information. The UE may also send an EES discovery request to the ECS for EES discovery. Wherein, the ECS used for EES discovery is one of the first ECSs, and EES discovery may also be called service provisioning (Service Provisioning or Provision). Optionally, the ECS used for EES discovery may not be the ECS in the first ECS.

The first configuration information may be carried in a session establishment acceptance message or a session modification response message. For example, the above-mentioned first ECS Provider ID or the above-mentioned first application program identifier is carried in the session establishment request message, and correspondingly, the first ECS configuration information is carried in the session establishment acceptance message. A specific implementation is that the UE sends the first ECS Provider ID or the first application program ID to the AMF through the PDU Session Establishment Request message, and then the AMF forwards the first ECS Provider ID or the first application program ID to the SMF through the Nsmf_PDUSession_CreateSMContext Request message; A piece of ECS configuration information is sent to the AMF, and then the AMF sends the first ECS configuration information to the UE through a NAS message. For another example, the above-mentioned first ECS Provider ID or the above-mentioned first application program identifier is carried in the session modification request message, and correspondingly, the first ECS configuration information is carried in the session modification response message. A specific implementation method is that the UE sends the first ECS Provider ID or the first application program identifier to the AMF through the PDU Session Modification Request message, and then the AMF forwards it to the SMF through the Nsmf_PDUSession_UpdateSMContext Request message; the SMF passes the Nsmf_PDUSession_UpdateSMContext Response A piece of ECS configuration information is sent to the AMF, and then the AMF sends the first ECS configuration information to the UE through a NAS message. Of course, the first ECS configuration information may also be carried in other messages, signaling or procedures, which is not limited in this embodiment of the present application.

Wherein, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, such as one or more of a fully qualified domain name (FQDN), an IP address, and a URL. Optionally, the configuration information of the first ECS also includes the identifier of the first ECS, that is, the ECS ID. The first ECS corresponds to the first ECS provider identifier, or the first ECS is provided by the provider/deployer identified by the first ECS provider identifier. In addition, the first ECS configuration information may also include the space availability of the first ECS. The spatial validity includes one or a set of location information, and the location information may be a geographic location (such as latitude and longitude, landmarks, etc.) or a topological location (such as TA, cell, etc.). For example, the spatial availability may be the service range of the ECS, that is, when the location of the UE corresponds to the location identified by the spatial availability, the ECS may serve the UE. For another example, the space availability may be the ideal service range of the ECS, that is, when the location of the UE corresponds to the location identified by the space availability, the ECS may provide a better service for the UE, such as a shorter path, Lower latency, or smaller load, etc. When the location of the UE does not correspond to the location of the space availability identifier, the ECS may or may not be able to provide services for the UE. For another example, the spatial availability may be the best service range of the ECS, that is, when the location of the UE corresponds to the location identified by the spatial availability, the ECS is the most suitable ECS to provide services for the UE. At this time, there may be Other ECSs can also provide services for the UE, but this ECS is the most suitable for providing services for the UE among all the ECSs that meet the needs of the UE (for example, among these ECSs, the ECS can provide the shortest path for the UE, the lowest delay , or minimum load, etc.). It can be understood that when an ECS serves a UE, the UE is not necessarily located in the location of the space validity identifier corresponding to the ECS. For example, the location of the UE is not included in the ideal service range of any ECS that meets the needs of the UE, but There is an ECS that can serve the UE. At this time, the ECS serves the UE, but the UE is not located in the location of the space availability identifier corresponding to the ECS.

It should be noted that the space validity is used to identify the location information of the service situation of the ECS, and it can also be replaced with other names or information elements, such as service range, effective area, and optimal service range.

The SMF may determine the first ECS from the ECS corresponding to the UE-specific first ECS provider ID according to the UE location and the spatial availability of the ECS. Alternatively, the SMF may determine the first ECS from the ECS corresponding to the UE-specific first ECS provider ID according to the load balancing policy or local policy. Here, the first ECS may be one or more ECSs.

Optionally, the SMF may also directly use the ECS corresponding to the UE-specific first ECS provider ID as the first ECS.

Optionally, the above step S201 to the above step S203 can be understood as an initial sending process of the ECS configuration information. In some cases (such as UE mobility, load balancing, etc.), if the SMF determines that the ECS configuration information corresponding to the UE-specific AppID/ECS provider ID (that is, the first ECS configuration information above) needs to be updated, then perform the update of the ECS configuration information process. It should be understood that the updating process of ECS configuration information (such as the following step S204) can be implemented together with the aforementioned initial sending process (ie, step S201 to step S203), or can be implemented separately, which is not limited in this embodiment of the present application. It should also be understood that the updating process of the ECS configuration information is generally later than the initial sending process in time.

Specifically, after the above step S203, the communication method further includes the following steps:

S204. When the first ECS changes, the SMF sends second ECS configuration information to the UE, where the second ECS configuration information includes the first ECS provider identifier and the changed address of the first ECS. Correspondingly, the UE receives the second ECS configuration information.

Optionally, due to reasons such as UE movement, load balancing, and ECS downtime, the ECS serving the UE may change. When the SMF determines that the changed ECS is one or more ECSs in the above-mentioned first ECS, that is to say, when the above-mentioned first ECS changes (that is, when an ECS in the first ECS changes), the SMF determines that the ECS updated to the UE ECS configuration information (that is, second ECS configuration information), and send the second ECS configuration information to the UE. Correspondingly, the UE receives the second ECS configuration information. Optionally, the second ECS configuration information may be sent through a session modification process. Exemplarily, after the SMF determines new ECS configuration information (that is, the second ECS configuration information), it initiates a session modification process, that is, carries the second ECS configuration information Sent in Session Modification Request message or Session Modification Response message. Of course, the second ECS configuration information may also be carried in other signaling, messages, or processes, which is not limited in this embodiment of the present application.

Wherein, the second ECS configuration information includes the first ECS provider identifier and the changed address of the first ECS (for example, FQDN, or IP address, or URL, etc.). The changed first ECS also corresponds to the first ECS provider identifier. It should be understood that the changed first ECS refers to (one or more) ECSs that the current UE can use/allow to use in the ECS corresponding to the first ECS provider ID. Here, "the ECS available to the current UE" can be understood as an ECS whose service range/spatial availability includes the current location of the UE. Understandably, if the service range/spatial availability here is the range most suitable for serving the UE or the best range for serving the UE, then the "ECS available to the current UE" may be the service range/spatial availability including the UE's current The location ECS may also be an ECS whose service range/spatial availability does not include the current location of the UE. For example, if the current location of the UE is not within the range of the most suitable/best service of any ECS, but there is an ECS that can serve the UE, this ECS can still be the "ECS available to the current UE". "ECS allowed to be used by the current UE" can be understood as the ECS allocated by the SMF to the UE. These ECS can be all or part of the ECS currently available to the UE. The allocation method of the SMF can be determined based on the load balancing strategy or other strategies. This application The examples are not limiting. It should also be understood that if the reason for the change of the first ECS is caused by the movement of the UE, the changed service range/spatial availability of the first ECS may include the position of the UE after the move; of course, the changed service range of the first ECS The /spatial availability may also not include the location of the UE after moving (if the service range/spatial availability is the best range to serve the UE). If the reason for the change of the first ECS is load balancing, or ECS downtime, etc., the changed first ECS is the ECS allocated by the SMF to the UE in the ECS corresponding to the UE-specific first ECS provider ID.

For example, assume that 10 ECS instances from ECS 1 to ECS 10 are deployed in the network. The correspondence between these 10 ECS instances and ECS provider IDs is shown in Table 1 below. Among them, the first ECS is 5 ECSs from ECS 1 to ECS 5. Due to UE movement or other reasons, it is assumed that the changed ECSs include ECS 2 and ECS 6-ECS 8. Since ECS provider ID 2 corresponds to ECS 2, ECS 9, and ECS10, then the first ECS after the change is ECS 1, ECS3-ECS 5, and ECS 9 and/or ECS 10; it should be understood that ECS 9 specifically Or ECS 10, or ECS 9 and ECS 10 can be determined by SMF. In one implementation, the second ECS configuration information may include address information related to ECS 1, ECS 3-ECS 5, ECS 9 and/or ECS 10, ECS Provider ID, and optionally, the ECS ID and space valid One or more of the components such as sex. In another implementation, the second ECS configuration information may only include address information related to ECS 9 and/or ECS 10, ECS Provider ID, and optionally, one of components such as ECS ID and space validity or more. In the latter implementation, optionally, the first indication information may also be sent to indicate that ECS9 and/or ECS 10 are the updated ECS, or indicate that the address of ECS 9 and/or ECS 10 is the address of the updated ECS , or in other words, to indicate that the second ECS configuration information only includes the ECS Provider ID corresponding to the changed ECS, that is, the ECS corresponding to the ECS Provider ID not included in the second ECS configuration information can still provide services for the UE.

Table 1

ECS提供者标识ECS Provider ID	ECSECS
ECS Provider ID 1 ECS Provider ID 1	ECS 1 ECS 1
ECS Provider ID 2 ECS Provider ID 2	ECS 2、ECS 9、ECS 10 ECS 2, ECS 9, ECS 10
ECS Provider ID 3 ECS Provider ID 3	ECS 3、ECS 4、ECS 5 ECS 3, ECS 4, ECS 5
ECS Provider ID 4 ECS Provider ID 4	ECS 6 ECS 6
ECS Provider ID 5 ECS Provider ID 5	ECS 7 ECS 7
ECS Provider ID 6 ECS Provider ID 6	ECS 8 ECS 8

Optionally, if the SMF determines that none of the changed ECSs belong to the first ECS, the SMF determines that the ECS configuration information does not need to be updated. That is to say, when the changed ECS is not the ECS corresponding to the UE-specific first ECS provider ID, the SMF does not need to send signaling/messages to update the ECS configuration information to the UE, thereby reducing unnecessary ECS configuration information. Updates and signaling overhead in the network.

In an optional embodiment, when the ECS in the network changes due to reasons such as UE movement, load balancing, or ECS downtime, the SMF may determine whether to update the ECS configuration information according to the above-mentioned first ECS provider identifier. Specifically, the first ECS provider ID is one or more ECS provider IDs. If the ECS (recorded as the second ECS) corresponding to an ECS Provider ID (recorded as the second ECS Provider ID) changes, SMF judges whether the second ECS Provider ID belongs to the first ECS Provider ID, in other words, the second ECS Provider ID Whether the first ECS Provider ID includes the second ECS Provider ID. If the second ECS Provider ID belongs to the first ECS Provider ID, that is, the first ECS Provider ID includes the second ECS Provider ID, the SMF sends the updated ECS configuration information to the UE. Optionally, if the second ECS Provider ID does not belong to the first ECS Provider ID, that is, the first ECS Provider ID does not include the second ECS Provider ID, then the SMF determines that no update is required, and does not perform the update operation. Wherein, the updated ECS configuration information may include the second ECS Provider ID and the changed address of the second ECS. At this time, the updated ECS configuration information may also include first indication information for indicating that the second ECS The ECS corresponding to the Provider ID has been updated. Alternatively, the updated ECS configuration information includes the first ECS Provider ID, the changed address of the second ECS, and the unchanged address of the first ECS. That is to say, the updated ECS configuration information may only include the updated ECS Provider ID and the address of the changed ECS, or may include all UE-specific ECS Provider IDs, the changed address of the ECS, and the unchanged The address of the ECS.

In other words, when the ECS in the network changes due to UE movement, load balancing, or ECS downtime, etc., if there are ECS Provider IDs that may be used by the UE in all ECS Provider IDs corresponding to all ECSs that have changed (ie One or more ECS provider IDs in the first ECS provider ID above), the SMF determines that the ECS configuration information needs to be updated. Otherwise, there is no need to update, that is, all ECS Provider IDs corresponding to all ECSs that have changed do not have an ECS Provider ID that may be used by the UE (that is, the above-mentioned first ECS provider ID), and no update is required. When the SMF determines that the ECS configuration information needs to be updated to the UE, the SMF determines the new ECS configuration information (including the first ECS provider ID, the address of the changed ECS, and the address of the first ECS that has not changed), and initiates session modification Process: Through the session modification process, the SMF can send new ECS configuration information to the UE.

Optionally, when the UE-specific ECS Provider ID/AppID is updated, the UE can notify the SMF. Therefore, after step S203, the communication method further includes one or more of the following steps:

S205. The UE sends a first message to the SMF, where the first message is used to indicate to update the UE-specific first ECS provider identifier or UE-specific first application identifier. Correspondingly, the SMF receives the first message.

S206. The SMF updates the first ECS provider identifier according to the first message to obtain a UE-specific third ECS provider identifier.

Optionally, when the application identification (i.e. the above-mentioned first application identification) or ECS Provider ID (i.e. the first ECS provider ID) that may be used by the UE changes, for example, if the UE installs or uninstalls an application, the UE Send the first message to the SMF. The first message is used to indicate to update the UE-specific first ECS provider identifier or UE-specific first application identifier. Exemplarily, when the UE installs/uninstalls an application, the UE may obtain the ECS provider ID related to the application or the identification of the application. Therefore, the first message may include: (1) a newly added ECS Provider ID or AppID, or a deleted ECS Provider ID or AppID. Alternatively, the first message may include: (2) the updated ECS Provider ID or AppID, that is, replace the above-mentioned first ECS provider ID with the ECS Provider ID included in the first message, or use the AppID included in the first message The corresponding ECS Provider ID replaces the first ECS provider ID above. Here, the updated ECS Provider ID is one or more ECS Provider IDs, and the updated AppID is one or more AppIDs.

Optionally, the first message above may also include second indication information, which is used to indicate whether the ECS Provider ID included in the first message is a newly added ECS Provider ID or a deleted ECS Provider ID, or is used to indicate that the first ECS Provider ID Whether the AppID included in the first message is a newly added AppID or a deleted AppID, or used to indicate that the ECS Provider ID/AppID included in the first message is an updated ECS Provider ID/AppID.

Wherein, the above-mentioned first message may be a session modification request message, and may also be other signaling and messages, which are not limited in this embodiment of the present application. As a possible implementation, in the session modification process, the UE sends the above-mentioned ECS Provider ID or application identifier to the AMF through the PDU Session Modification Request message, and then the AMF sends the above-mentioned ECS Provider ID or application identifier to the SMF through the Nsmf_PDUSession_UpdateSMContext message.

Optionally, after receiving the first message, the SMF may update the first ECS provider ID to obtain the UE-specific third ECS Provider according to the indication of the first message and/or the above-mentioned first ECS provider ID ID. In other words, after receiving the newly added/deleted/updated ECS Provider ID or AppID of the UE, the SMF updates the UE-specific first ECS Provider ID accordingly.

Specifically, for the above case (1), that is, if the first message includes the newly added or deleted ECS Provider ID, the SMF adds or deletes the ECS Provider ID included in the first message in the first ECS provider ID above, and obtains UE A specific third ECS Provider ID (also called the ECS Provider ID that the UE may use after updating, or the new ECS Provider ID that the UE may use). In other words, the third ECS provider ID is one or more ECS provider IDs, the first ECS provider ID is one or more ECS provider IDs; the difference between the third ECS provider ID and the first ECS provider ID is the first message Included ECS Provider ID, that is, the third ECS Provider ID is based on the first ECS Provider ID, adding the newly added ECS Provider ID (if any) in the first message, and removing the deleted ECS Provider ID in the first message (If there is). In this case, if the first message contains the second indication information, the SMF can judge whether the ECS Provider ID is added or deleted according to the second indication information; if the first message does not contain the second indication information, the SMF You can judge whether the ECS Provider ID is new or deleted based on your own logic. For example, if the ECS Provider ID is included in the first ECS Provider ID, it will be judged as a deleted ECS Provider ID. If the ECS Provider ID is not included in the In the first ECS Provider ID, it is judged as a newly added ECS Provider ID. If the first message contains multiple ECS Provider IDs, and the first message contains the second indication information corresponding to some of the ECS Provider IDs in these ECS Provider IDs, then for this part of the ECS Provider IDs that contain the corresponding second indication information ID, SMF can judge whether it is added or deleted according to the second indication information. For the part of ECS Provider ID that does not contain the corresponding second indication information, SMF can judge whether it is added or deleted according to its own logic.

For the above case (2), that is, if the first message includes the updated ECS Provider ID, the SMF determines the ECS Provider ID included in the first message as the UE-specific third ECS Provider ID; the third ECS Provider ID One or more ECS provider IDs. After receiving the first message, the SMF may judge whether it belongs to the situation (1) or the situation (2) according to the second indication information or its own logic. Specifically, if the second indication information is included, if the second indication information indicates a newly added/deleted ECS provider ID, the SMF judges that it belongs to the case (1), and if the second indication information indicates an updated ECS provider ID, Then SMF judges that it belongs to the case (2). If the second indication information is not included, the SMF shall have internal logic indicating whether the ECS provider ID contained in the first message belongs to case (1) or case (2). This logic can be pre-configured through the SMF or obtained from other network elements (such as PCF network elements).

If the first message includes the deleted AppID, the SMF determines the ECS Provider ID corresponding to the AppID included in the first message according to the correspondence between the AppID and the ECS Provider ID. The SMF deletes the ECS Provider ID corresponding to the AppID from the first ECS provider ID, and obtains the UE-specific third ECS Provider ID. If the first message includes the newly added AppID, the SMF determines the ECS Provider ID corresponding to the AppID included in the first message according to the correspondence between the AppID and the ECS Provider ID. If the ECS Provider ID corresponding to the AppID does not belong to the above-mentioned first ECS provider ID, the SMF adds the ECS Provider ID corresponding to the AppID to the first ECS provider ID to obtain the UE-specific third ECS Provider ID. If the ECS Provider ID corresponding to the AppID belongs to the above-mentioned first ECS provider ID, the SMF determines the first ECS provider ID as the third ECS Provider ID. That is to say, the UE reports the update of the AppID, but the update of the AppID does not necessarily lead to a change of the UE-specific first ECS Provider ID. For example, the UE installs a new application, but this new application can reuse the ECS of the existing application. In this case, the SMF may not update the UE-specific first ECS Provider ID. If the first message includes the updated AppID, the SMF determines the ECS Provider ID corresponding to the updated AppID according to the correspondence between the AppID and the ECS Provider ID. If the ECS Provider ID corresponding to the updated AppID belongs to the first ECS provider ID mentioned above, it means that the update of the AppID does not lead to the change of the UE-specific first ECS Provider ID, and the SMF will not update the first ECS provider ID. Then, at this time, the first ECS provider ID is the same as the third ECS provider ID. If the ECS Provider ID corresponding to the updated AppID does not all belong to the above-mentioned first ECS provider ID, it means that the update of the AppID has caused the change of the UE-specific first ECS Provider ID, then the SMF will assign the ECS Provider ID corresponding to the updated AppID Determined as the UE-specific third ECS Provider ID.

It should be understood that the above steps S205 - S206 are not related to the above step S204 in terms of time and logic, and their execution order is not limited.

In an optional embodiment, if the above-mentioned first message includes the deleted ECS Provider ID/AppID, the following step S207 may not be performed, that is, the SMF determines the UE-specific third ECS provider identifier according to the first message After that, the updated ECS configuration information is not sent to the UE. That is to say, if the above-mentioned first message includes the deleted ECS Provider ID/AppID, the SMF can only update its own locally stored UE-specific ECS Provider ID without updating the ECS configuration information.

In another optional embodiment, the UE installs or uninstalls a certain application program, but the UE itself can judge that this installation/uninstallation behavior will not lead to a change in the ECS Provider ID (for example, a newly installed application can reuse the ID of an installed application. ECS, or the ECS used by the uninstalled application will also be used by other non-uninstalled applications). In this case, the UE will not send the first message to the SMF, that is, in this case, step S205 and step S206 will not be performed, and there will be no subsequent step S207 and so on.

S207. The SMF sends third ECS configuration information to the UE, where the third ECS configuration information includes the third ECS provider identifier and the address of the third ECS, and the third ECS corresponds to the third ECS provider identifier. Correspondingly, the UE receives the third ECS configuration information.

Optionally, after the SMF determines the UE-specific third ECS provider ID (that is, the updated ECS Provider ID that may be used by the UE), it can determine the third ECS configuration information according to the third ECS provider ID. The SMF sends the third ECS configuration information to the UE, and correspondingly, the UE receives the third ECS configuration information. The UE may also determine the ECS used for EES discovery according to the third ECS configuration information. Wherein, the ECS used for EES discovery may be one of the third ECS. The third ECS configuration information may be carried in the session modification response message, or in other messages, signaling or procedures, which is not limited in this embodiment of the present application. Exemplarily, in the session modification process, the SMF sends the third ECS configuration information to the AMF through the Nsmf_PDUSession_UpdateSMContext Response message, and then the AMF sends the third ECS configuration information to the UE through the NAS message.

Wherein, the above-mentioned third ECS configuration information includes the third ECS provider identifier (that is, the ECS provider ID that UE may use after updating) and the address of the third ECS, such as one or more of FQDN, IP address, and URL . Optionally, the configuration information of the third ECS also includes an identifier of the third ECS, that is, an ECS ID. The third ECS corresponds to the third ECS provider identifier, or the third ECS is provided by the provider/deployer identified by the third ECS provider identifier. In addition, the space availability of the third ECS may include the current location of the UE; it can be understood that when the space availability refers to the best range for serving the UE, as mentioned above, the space availability of the third ECS It is also possible not to include the UE's current location. That is to say, the SMF may determine the ECS whose service range (or space validity) includes the current location of the UE in the ECS corresponding to the ECS provider ID that may be used by the UE after the update is the third ECS. Alternatively, the SMF may determine the third ECS from the ECS corresponding to the ECS provider ID that may be used by the UE after the update according to the load balancing policy or local policy. Here, the third ECS may be one or more ECSs. It should be understood that the third ECS configuration information may be understood as the updated ECS configuration information of the aforementioned first ECS configuration information. The third ECS is not completely the same as or completely different from the foregoing first ECS, which is not limited in this embodiment of the present application.

Optionally, the SMF may also directly use the ECS corresponding to the UE-specific third ECS provider ID as the third ECS.

It should be understood that the content contained in the ECS configuration information in the embodiment of the present application is only an example, and in practical applications, the name and content of the ECS configuration information may be consistent with existing standards or future standards.

In the embodiment of the present application, the UE sends the UE-specific ECS Provider ID/AppID to the network side (specifically, the SMF), and the SMF sends the UE-specific ECS configuration information corresponding to the UE-specific ECS Provider ID (ie, the first ECS configuration information), and Instead of sending all the ECS configuration information corresponding to the ECS Provider ID to the UE, redundant information elements in the ECS configuration information can be reduced. In addition, the SMF in the embodiment of the present application sends the updated ECS configuration information to the UE when the ECS corresponding to the UE-specific ECS Provider ID needs to be updated, thereby avoiding unnecessary update signaling of the ECS configuration information and reducing network traffic. Signaling overhead.

Embodiment three

Referring to FIG. 7, FIG. 7 is a third schematic flowchart of a communication method provided by an embodiment of the present application. Exemplarily, the communication method provided by the embodiment of the present application may be applied to the network architecture shown in the aforementioned FIG. 1 or FIG. 3 . As shown in Figure 7, the communication method includes one or more of the following steps:

S301. The UE sends the UE-specific first ECS provider identifier and/or the UE-specific first application identifier to the AMF. Correspondingly, the AMF receives the UE-specific first ECS provider identifier and/or the UE-specific first application identifier.

Optionally, the UE acquires the UE-specific first ECS provider identifier, and for the acquisition method, refer to the corresponding description in the foregoing embodiment shown in FIG. 6 , which will not be repeated here. After acquiring the UE-specific first ECS provider identifier, the UE may send the UE-specific first ECS provider identifier to the AMF. For example, the UE-specific first ECS provider identifier is sent through a registration process. Specifically, the UE may send the first ECS Provider ID to the AMF through a NAS message during the initial registration process. Correspondingly, the AMF receives the first ECS provider identifier sent by the UE. Wherein, the UE-specific first ECS provider identifier may be carried in the registration request message, and of course the UE-specific first ECS provider identifier may also be carried in other messages, signaling or procedures, and this embodiment of the present application does not limit.

Optionally, the UE acquires the UE-specific first application identifier, and for specific implementation, refer to the corresponding description in the foregoing embodiment shown in FIG. 6 , which will not be repeated here. After acquiring the UE-specific first application identifier, the UE may send the UE-specific first application identifier to the AMF. For example, the UE-specific first application identifier is sent through a registration process. Correspondingly, the AMF receives the first application identifier sent by the UE. Wherein, the first application identifier may be used to determine a UE-specific first ECS provider identifier. The UE-specific first application identifier may be carried in the registration request message. Specifically, the UE may send the first application identifier to the AMF through a NAS message during the initial registration process. Of course, the UE-specific first application identifier may also be carried in other messages, signaling or procedures, which is not limited in this embodiment of the present application.

S302. The AMF sends the UE-specific first ECS provider identifier and/or the UE-specific first application identifier to the SMF. Correspondingly, the SMF receives the UE-specific first ECS provider identifier and/or the UE-specific first application identifier.

Optionally, if step S301 and step S302 are implemented through different processes, for example, step S301 is implemented in the registration process, and step S302 is implemented in the session establishment or session modification process, then the AMF receives the UE-specific first ECS provider identifier and/or After the UE-specific first application ID is identified, the ECS Provider ID and/or AppID can be cached, and then the UE-specific first ECS provider ID and/or UE-specific first application ID can be passed through the session establishment process or the session modification process. The identity is sent to SMF. Correspondingly, the SMF receives the UE-specific first ECS provider identifier and/or the UE-specific first application identifier. Exemplarily, when the AMF receives the PDU session establishment or modification request, the UE-specific first ECS provider identifier or the UE-specific first application identifier is carried in the N11 interface message and sent to the SMF, such as the Nsmf_PDUSession_CreateSMContext Request message.

S303. The SMF determines first ECS configuration information according to the first ECS provider ID or the first application program ID. The first ECS configuration information includes the first ECS provider ID and the address of the first ECS. The first ECS Corresponding to the first ECS provider ID.

S304. The SMF sends the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information.

For the implementation of step S303-step S304 in the embodiment of the present application, reference may be made to the implementation of step S202-step S203 in the embodiment shown in FIG.

Optionally, after the above step S304, the communication method further includes the following steps:

S305. When the first ECS changes, the SMF sends second ECS configuration information to the UE, where the second ECS configuration information includes the first ECS provider identifier and the changed address of the first ECS. Correspondingly, the UE receives the second ECS configuration information.

For the implementation of step S305 in this embodiment of the present application, reference may be made to the implementation of step S204 in the aforementioned embodiment shown in FIG.

Optionally, after step S304, the communication method further includes one or more of the following steps:

S306. The UE sends a first message to the SMF, where the first message is used to indicate to update the UE-specific first ECS provider identifier or UE-specific first application identifier. Correspondingly, the SMF receives the first message.

S307. The SMF updates the first ECS provider identifier according to the first message to obtain a UE-specific third ECS provider identifier.

S308. The SMF sends third ECS configuration information to the UE, where the third ECS configuration information includes the third ECS provider identifier and the address of the third ECS, and the third ECS corresponds to the third ECS provider identifier. Correspondingly, the UE receives the third ECS configuration information.

For the implementation of step S306-step S308 in the embodiment of the present application, reference may be made to the implementation of step S205-step S207 in the aforementioned embodiment shown in FIG.

The embodiment of this application provides that the UE sends the UE-specific ECS Provider ID/AppID to the AMF, and the AMF then sends the UE-specific ECS Provider ID/AppID to the SMF, and the SMF sends the UE-specific ECS Provider ID corresponding to the ECS configuration information (that is, the first ECS configuration information), instead of sending all the ECS configuration information corresponding to the ECS Provider ID to the UE, the redundant information elements in the ECS configuration information can be reduced. In addition, the SMF in the embodiment of the present application sends the updated ECS configuration information to the UE when the ECS corresponding to the UE-specific ECS Provider ID needs to be updated, thereby avoiding unnecessary update signaling of the ECS configuration information and reducing network traffic. Signaling overhead.

Embodiment Four

Referring to FIG. 8 , FIG. 8 is a fourth schematic flowchart of a communication method provided by an embodiment of the present application. Exemplarily, the communication method provided by the embodiment of the present application may be applied to the network architecture shown in FIG. 2 above. As shown in Figure 8, the communication method includes one or more of the following steps:

S401. The SMF sends a first request message to the NWDAF, where the first request message is used to acquire a UE-specific ECS provider identifier. Correspondingly, the NWDAF receives the first request message.

Optionally, the SMF sends a first request message to the NWDAF for obtaining the UE-specific ECS provider identifier. Specifically, the first request message carries the identifier of the UE. Exemplarily, the SMF may periodically send a first request message to the NWDAF, to periodically obtain the UE-specific ECS provider identifier.

Exemplarily, the UE-specific ECS provider identifier may be one of the parameters according to the UE's use of the application (including but not limited to the frequency of use of the application, the duration of use, the download rate of the application, or other parameters that characterize the use of the application by the UE). item or items) determined.

It should be noted that the identifier of UE in this application may identify a certain UE, such as UE ID, or identify a group of UEs, such as UE group ID, etc.; the identifier of UE may be an internal identifier , such as a user permanent identifier (Subscription permanent identifier, SUPI), etc., or an external identifier, such as a general public subscription identifier (generic public subscription identifier, GPSI) and the like.

Further, the first request message above can be understood as a subscription message, and step S401 can also be described as: the SMF sends the first subscription message to the NWDAF for subscribing to the UE-specific ECS provider identifier. The first subscription message includes the identifier of the UE. It should be understood that, if the first request message is a subscription message, when the ECS provider ID commonly used by the UE changes, the NWDAF may send a notification message to the SMF, including the updated ECS provider ID commonly used by the UE.

Optionally, the above first request message may also include one or more of the following: data network name (data network name, DNN), single network slice selection assistance information (single network slice selection assistance information, S-NSSAI). Among them, the role of DNN and/or S-NSSAI is to indicate that the ECS corresponding to the common ECS Provider ID of the UE requested or subscribed by the SMF is the ECS that needs to support this DNN and/or S-NSSAI.

S402. The NWDAF sends a second subscription message to one or more AFs, where the second subscription message is used for subscribing the use of the application by the UE. Specifically, the second subscription message includes the identifier of the UE. Correspondingly, one or more AFs receive the second subscription message.

S403. One or more AFs send a second notification message to the NWDAF, where the second notification message includes the usage of the application by the UE. Correspondingly, the NWDAF receives the second notification message.

Optionally, after receiving the first request message, the NWDAF may send a second subscription message to one or more AFs, where the second subscription message is used for subscribing the usage of the application by the UE. The second subscription message may include the identifier of the UE (such as UE ID, UE group ID, SUPI, or GPSI, etc.). It should be understood that NWDAF can send the same subscription message to multiple AFs, and can also send different subscription messages to multiple AFs (including sending the same subscription message to some AFs and sending different subscription messages to other AFs; It also includes the case of sending different subscription messages to each AF, etc.), the embodiment of the present application is not limited, as long as the NWDAF can obtain the usage status of the UE for the application program through the subscription message. The different subscription messages may refer to different UE identities and/or subscribed content. Each AF can perceive/acquire the UE's usage of the AF-related application program. Specifically, the AF can perceive the UE's usage of the application server (application service, AS). The AS here can be EAS or ECS, etc., here not limited. The above-mentioned one or more AFs may respectively send their own second notification messages to the NWDAF, and each of the second notification messages includes the UE's use of the application program (related to the AF).

Wherein, the UE's use of the application program includes but is not limited to one or more of the following: the average use time of the UE for the application program, the frequency of the UE's use of the application program, the number of times the UE uses the application program, and the UE's use of the application program. App download rate, etc.

It should be understood that after the NWDAF subscribes to the AF about the UE's usage of the application, if the UE's usage of the application is updated, the AF may notify the NWDAF of the latest UE's usage of the application.

It should be noted that the above-mentioned second subscription message can also be expressed as a second request message. After receiving the second request message, the AF sends the UE's usage status of the application program to the NWDAF through a response message. When the usage status changes, AF may or may not send updated usage to NWDAF. If the NWDAF obtains the application status of the UE from multiple AFs, it may send a second subscription message to some of the AFs, and send a second request message to some of the AFs.

Optionally, the second subscription message may further include an application identifier, and the second subscription message is specifically used for subscribing the use of the application identified by the application identifier by the UE. Correspondingly, what is included in the second notification message is also the usage status of the application identified by the application identifier by the UE. For example, in the embodiment of the present application, the AppID is carried in the second subscription message to filter the use of certain application programs by the UE, which can reduce complexity, and can also reduce information elements in the notification message, thereby saving overhead.

Optionally, the above-mentioned second notification message may be a notification corresponding to the above-mentioned second subscription message, or may be a notification sent by the AF to the NWDAF after subscription. For example, the second notification message may be a notification returned for the initial subscription (that is, the second subscription message), or may be a notification sent because the usage of the application by the UE changes after subscription.

It should be understood that, no matter whether the NWDAF receives the first request message from the SMF, the NWDAF can subscribe to the AF about the UE's use of the application program. That is to say, the present application does not limit that the NWDAF needs to subscribe the UE-specific ECS provider identifier to the AF after receiving the first request message from the SMF.

It should also be understood that the execution sequence of the above step S402 - step S403 and the above step S401 is not limited. For example, step S402-step S403 may be performed after step S401, or before step S401, or may be performed simultaneously/parallel with step S401.

S404. The NWDAF determines the UE-specific identifier of the first ECS provider according to the application status of the UE in the second notification message.

S405. The NWDAF sends the UE-specific first ECS provider identifier to the SMF. Correspondingly, the SMF receives the first ECS provider identifier.

Optionally, the NWDAF determines the UE-specific first ECS provider identifier according to the usage of the application by the UE in the second notification message (such as usage duration, usage frequency, usage times, etc.). In an implementation manner, NWDAF may determine the ECS Provider ID corresponding to the application whose frequency of use exceeds the first threshold, and/or the average duration of use exceeds the second threshold, and/or the number of times of use exceeds the third threshold as the UE-specific first threshold. An ECS provider ID. An application corresponds to an ECS provider ID, and an ECS provider ID corresponds to one or more applications. It should be understood that the UE-specific first ECS provider identifier is one or more ECS provider IDs. It should also be understood that the first ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs. Wherein, the first threshold and the second threshold can be set according to actual conditions. Exemplarily, the first threshold is 1 time/day, or 10 times/day, etc.; the second threshold is 30 minutes/day, or 1 hour/month, etc.; the third threshold is 10 times, or 1 time, etc.

In another implementation, NWDAF can sort the applications according to the frequency of use, and/or the average duration of use, and/or the number of uses in descending order, and sort the top n (n is a positive integer) applications The corresponding ECS Provider ID is determined as the UE-specific first ECS provider identifier.

It should be understood that if NWDAF subscribes to multiple AFs for the UE's usage of applications, NWDAF can determine the UE-specific first ECS provider ID based on the UE's usage of applications in multiple notification messages returned by multiple AFs . Specifically, the NWDAF can determine the overall usage of each application by the UE according to the usage of several applications by the UE obtained from multiple AFs, and then determine the UE-specific first ECS provider identifier according to the overall usage. Alternatively, NWDAF can first determine the UE’s commonly used ECS provider ID corresponding to the usage provided by each AF according to the UE’s application usage obtained from each AF, and then determine the UE’s final common ECS provider ID based on these IDs . For example, NWDAF obtains from AF1 that UE uses application 1 (corresponding to ECS Provider ID 1) at a frequency of 60 minutes/day, and uses application 2 (corresponding to ECS Provider ID 2) at a frequency of 1 minute/day. NWDAF obtains from AF2 that UE uses application 3 (corresponding to ECS Provider ID 3) at a frequency of 90 minutes/day, and uses application 2 (corresponding to ECS Provider ID 2) at a frequency of 1 minute/day. Therefore, NWDAF determines that the UE uses application 1 at a frequency of 60 minutes/day, application 2 at a frequency of 1 minute/day, and application 3 at a frequency of 90 minutes/day, and judges that the ECS Provider ID commonly used by UE is ECS Provider ID 1 and ECS Provider ID 3. For another example, NWDAF obtains from AF1 that UE uses application 1 (corresponding to ECS Provider ID 1) at a frequency of 60 minutes/day, and uses application 2 (corresponding to ECS Provider ID 2) at a frequency of 1 minute/day, and thus Determine that the ECS Provider ID commonly used by the UE is ECS Provider ID 1. NWDAF obtains from AF2 that the UE uses App 3 (corresponding to ECS Provider ID 3) at a frequency of 90 minutes/day, and uses App 2 (corresponding to ECS Provider ID 2) at a frequency of 1 minute/day, and thus determines that the UE frequently uses The ECS Provider ID is ECS Provider ID 3. The commonly used ECS Provider IDs obtained by NWDAF from AF1 and AF2 are ECS Provider ID 1 and ECS Provider ID 3. It should be noted that, in the latter implementation above, the common ECS Provider ID of the UE determined by the NWDAF may be the union of all common ECS Provider IDs received from each AF, or a subset of the union .

Optionally, after determining the UE-specific first ECS provider identifier, the NWDAF sends the UE-specific first ECS provider identifier to the SMF. The UE-specific first ECS provider identifier may be carried in a first notification message, and the first notification message may be a notification corresponding to the above-mentioned first request message.

S406. The SMF determines first ECS configuration information according to the first ECS provider identifier, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS and the first ECS provider ID corresponds.

S407, the SMF sends the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information.

For the implementation of step S406-step S407 in the embodiment of the present application, reference may be made to the corresponding description in step S202-step S203 in the aforementioned embodiment shown in FIG.

The content contained in the ECS configuration information in the embodiment of the present application is only an example. In practical applications, the name and content of the ECS configuration information may be consistent with existing standards or future standards.

Optionally, the above step S401 to the above step S407 can be understood as an initial sending process of ECS configuration information, which can be implemented through a session establishment or session modification process.

In some cases (such as UE mobility, load balancing, etc.), if the SMF determines that the ECS configuration information corresponding to the ECS provider ID commonly used by the UE (ie the first ECS configuration information above) needs to be updated, the SMF updates the ECS configuration information to the UE. In an implementation manner, when the first ECS changes, the SMF sends second ECS configuration information to the UE, where the second ECS configuration information includes the first ECS provider identifier and the changed address of the first ECS. Correspondingly, the UE receives the second ECS configuration information. For details, refer to the implementation manner of step S204 in the embodiment shown in FIG. 6 (that is, Embodiment 2), and details are not described here.

After the initial sending process (such as after step S407), as time goes by, the UE's use of the application program may change, which may cause the UE-specific first ECS Provider ID to be updated. Therefore, the communication method in the embodiment of the present application may also include one or more of the following steps:

S408. The NWDAF determines a fourth ECS provider ID to be updated for the first ECS provider ID according to the change of the UE's use of the application program received from one or more AFs.

S409. The NWDAF sends the fourth ECS provider identifier to the SMF. Correspondingly, the SMF receives the fourth ECS provider identifier.

Optionally, because NWDAF subscribed to the AF for the UE's usage of the application to the AF in the above step S402, when the AF perceives/obtains that the UE's usage of the application is updated or changed, the AF will send the UE's usage of the application to the NWDAF. Changes in Application Usage. When the AF judges the changes in the frequency of use/average use time/number of uses, etc., it is determined that notification is required, which belongs to the logic and subscription details between NWDAF and AF, and is not limited by the embodiment of this application. In a possible example, when the frequency of use of an application program by the UE decreases from no less than 1 hour/week to less than 0.5 hours/week, or the frequency of use increases from less than 0.5 hours/week to no less than 0.5 hours/week At 1 hour/week, the frequency of use is deemed to have changed and AF needs to notify NWDAF.

The NWDAF determines the fourth ECS provider ID to be updated for the first ECS provider ID according to the change of the UE's use of the application program received from the AF. For example, the frequency of use of a certain application by the UE increases or decreases. It should be understood that the installation/uninstallation of application programs can be understood as a special case of increasing/decreasing the frequency of use. Wherein, the ID of the fourth ECS provider may be the same as or different from the ID of the first ECS provider. That is to say, it is possible that the change of the UE's usage of the application program does not lead to the update of the ECS Provider ID commonly used by the UE.

Optionally, after the NWDAF determines the fourth ECS provider identifier, it may send the fourth ECS provider identifier to the SMF. If the first request message in step S401 is a subscription message, when the fourth ECS provider ID is different from the first ECS provider ID, the fourth ECS provider ID is carried in the notification message and sent to the SMF. On the contrary, if the first request message in the above step S401 is a subscription message, when the fourth ECS provider ID is the same as the first ECS provider ID, the NWDAF does not need to notify the SMF. If the SMF requests the NWDAF for a UE-specific ECS provider ID, whether the fourth ECS provider ID is the same as or different from the first ECS provider ID, NWDAF can send the fourth ECS provider ID in the response message to SMF.

S410. The SMF determines fourth ECS configuration information according to the fourth ECS provider identifier, the fourth ECS configuration information includes the fourth ECS provider identifier and the address of the fourth ECS, and the fourth ECS and the fourth ECS provider ID corresponds.

S411. The SMF sends the fourth ECS configuration information to the UE. Correspondingly, the UE receives the fourth ECS configuration information.

Optionally, after the SMF obtains the fourth ECS provider identifier, it may determine the fourth ECS configuration information according to the fourth ECS provider identifier. The SMF sends the fourth ECS configuration information to the UE, for example, the SMF initiates a session modification process, and sends the fourth ECS configuration information to the UE in this process. Correspondingly, the UE receives the fourth ECS configuration information. The UE may determine the ECS used for EES discovery according to the fourth ECS configuration information. The ECS used for EES discovery may be one of the fourth ECSs. The fourth ECS configuration information may be carried in the session modification request message, or in other messages, signaling or procedures, which is not limited in this embodiment of the present application.

Wherein, the fourth ECS configuration information includes the fourth ECS provider identifier (that is, the ECS provider ID commonly used by the UE after updating) and the address of the fourth ECS, such as one or more of FQDN, IP address, and URL. Optionally, the configuration information of the fourth ECS also includes the identification of the fourth ECS, that is, the ECS ID. The fourth ECS corresponds to the fourth ECS provider identifier, or in other words, the fourth ECS is provided by the provider/deployer identified by the fourth ECS provider identifier. In addition, the spatial availability of the fourth ECS may include the current location of the UE. That is to say, the SMF may determine the ECS whose spatial validity includes the current location of the UE in the ECS corresponding to the ECS provider ID commonly used by the UE after the update (that is, the fourth ECS provider ID) as the fourth ECS. Of course, the space availability of the fourth ECS may not include the current location of the UE (if the space availability here is the best range for serving the UE). Alternatively, the SMF may determine the fourth ECS from the ECS corresponding to the ECS provider ID commonly used by the UE after the update (that is, the fourth ECS provider ID) according to the load balancing strategy or the local strategy. Here, the fourth ECS may be one or more ECSs. It should be understood that the fourth ECS configuration information may be understood as the updated ECS configuration information of the aforementioned first ECS configuration information. The fourth ECS is not completely the same as or completely different from the foregoing first ECS, which is not limited in this embodiment of the present application.

Understandably, the above step S408-step S411 can be understood as an update process of ECS configuration information, and the update process can be implemented together with the aforementioned initial sending process (that is, step S401 to step S407), or it can be implemented separately, which is not covered in this embodiment of the present application. limit. It should also be understood that the updating process of the ECS configuration information is generally later than the initial sending process in time.

Optionally, after the above step S407, the UE may use an "infrequently used ECS", that is to say, the UE may temporarily use a certain infrequently used ECS. For example, a user downloads and installs a ticket-buying application, but only uses it once a year (going home to buy a ticket during the Chinese New Year), and the ticket-buying application is a "very useful" application, so the SMF may not send the ECS configuration corresponding to this application to the UE information (assuming that the ECS Provider ID corresponding to the application does not correspond to any application commonly used by the UE). When the user uses the ticket purchase application (infrequent use does not mean never use), since the UE does not know which ECS should be used, or it may need to use a different ECS instance since the last use, the UE needs to request the purchase ticket from the 5GC. ECS corresponding to the ticket application.

"Very useful ECS" can be understood as the ECS Provider ID corresponding to this ECS does not belong to the UE-specific first ECS Provider ID. Specifically, this ECS is not an ECS frequently used by the UE, or the use of this ECS by the UE does not meet the conditions for being identified as a commonly used ECS. For example, the frequency of use of the application program corresponding to the ECS by the UE does not exceed the first threshold, and/or the average use time does not exceed the second threshold, and/or the number of times of use does not exceed the third threshold. Then, the communication method in this embodiment of the application may also include one or more of the following steps:

S412. The UE sends a second message to the SMF, where the second message includes a fifth ECS provider identifier or a second application identifier, where the second application identifier is used to determine a fifth ECS provider identifier, and the fifth ECS provider The ID does not belong to the first ECS provider ID. Correspondingly, the SMF receives the second message.

S413. The SMF sends the address of the ECS corresponding to the fifth ECS provider identifier to the UE. Correspondingly, the UE receives the address of the ECS.

Optionally, when the UE perceives that an unused ECS needs to be used, the UE may send the second message to the SMF. The second message includes the ECS Provider ID (denoted as the fifth ECS provider ID) corresponding to the unused ECS. In a possible implementation, when the UE needs to use a certain ECS, the ECS cannot be obtained from the last received ECS configuration information (maybe the first ECS configuration information, or the fourth ECS configuration information, etc.) The address of the ECS, so the UE determines that the ECS is a non-used ECS. That is to say, the fifth ECS provider ID does not belong to the first ECS provider ID or the fourth ECS provider ID.

Or, when the UE perceives that an unused application needs to be used, the UE may send the second message to the SMF. The second message includes the AppID of the non-used application (denoted as the second application identifier). In a possible implementation, when the UE uses an unused application, if the UE cannot perceive/obtain the ECS Provider ID related to the unused application, the UE can perceive or acquire the identity of the unused application (that is, the second application identification). It should be understood that the second application identifier is used to determine the fifth ECS provider identifier. That is to say, the second application identifier corresponds to the fifth ECS provider identifier.

Wherein, the above-mentioned second message may be a session modification request message, or other messages, which are not limited by this embodiment of the present application.

Optionally, after the SMF receives the second message, if the second message includes the fifth ECS provider identifier, the SMF may send to the UE the address of the ECS corresponding to the fifth ECS provider identifier (such as the FQDN /IP address/URL, etc.). If the second message includes the second application ID (that is, the non-used AppID), the SMF will assign the ECS provider ID corresponding to the second application ID to the corresponding ECS provider ID according to the correspondence between the application ID and the ECS provider ID. Determined as the fifth ECS provider ID. The SMF then sends the address of the ECS corresponding to the fifth ECS provider identifier (such as FQDN/IP address/URL, etc.) to the UE. Optionally, for the manner in which the SMF obtains the correspondence between the application ID and the ECS provider ID, reference may be made to the corresponding description in the aforementioned embodiment shown in FIG. 6 (i.e. Embodiment 2), which will not be repeated here.

Wherein, the address of the ECS corresponding to the fifth ECS provider identifier may be carried in the session modification response message or in other messages, which is not limited in this embodiment of the present application.

Optionally, the ECS Provider ID received or determined by the SMF through the above step S412 will not be added to the common ECS Provider ID of the UE, nor will it send ECS configuration information to the UE. That is to say, when the UE uses "unused ECS", SMF will not update the ECS Provider ID commonly used by the UE, nor will it send updated ECS configuration information to the UE.

It should be noted that when the UE needs to use an unused ECS, it may not obtain the address of the fifth ECS from the SMF or receive the second message. One possible situation is that the UE has previously configured or received the ECS configuration information corresponding to the fifth ECS Provider ID, and this ECS can still serve the current location of the UE. At this time, the UE can use the previous ECS, regardless of whether the ECS is is the most suitable ECS to serve the UE at this time. It can be understood that the situation listed above is just an example, and there may be other situations. In these situations, when the UE needs to use an unused ECS, it does not obtain the address of the fifth ECS from the SMF or receive the second message.

It should be understood that the process of the UE using the "unused ECS" (that is, the above step S412 and step S413) may not be related to the initial sending process and updating process of the aforementioned ECS configuration information in terms of time and logic.

In the embodiment of this application, the UE-specific ECS Provider ID is obtained from NWDAF through SMF, and the SMF sends the configuration information of the ECS corresponding to the UE-specific ECS Provider ID (that is, the first ECS configuration information) to the UE, instead of corresponding to all ECS Provider IDs. The ECS configuration information sent to the UE can reduce redundant information elements in the ECS configuration information. In addition, the SMF in the embodiment of the present application sends updated ECS configuration information to the UE when the ECS corresponding to the UE-specific ECS Provider ID needs to be updated, thereby avoiding unnecessary update signaling of the ECS configuration information and reducing signaling in the network. order overhead.

Embodiment five

Referring to FIG. 9, FIG. 9 is a fifth schematic flowchart of the communication method provided by the embodiment of the present application. Exemplarily, the communication method provided by the embodiment of the present application may be applied to the network architecture shown in FIG. 2 above. As shown in Figure 9, the communication method includes but is not limited to the following steps:

S501. The AMF sends a first request message to the NWDAF, where the first request message is used to obtain a UE-specific ECS provider identifier. Correspondingly, the NWDAF receives the first request message.

Optionally, the above-mentioned first request message includes the identifier of the UE, and optionally also includes allowing NSSAI. When the first request message includes the identifier of the UE, the first request message may be used to acquire a UE-specific ECS provider identifier. Exemplarily, the UE-specific ECS provider identifier may be one of the parameters according to the UE's use of the application (including but not limited to the frequency of use of the application, the duration of use, the download rate of the application, or other parameters that characterize the use of the application by the UE). item or items) determined. It should be understood that, for the meaning of the identifier of the UE, reference may be made to the corresponding description in the foregoing fourth embodiment, and details are not described here. When the first request message includes the allowed NSSAI, the first request message may be used to obtain the ECS provider identifier corresponding to the ECS that supports the allowed NSSAI. When the above-mentioned first request message includes the identifier of the UE and the allowed NSSAI, the first request message may be used to obtain the ECS provider identifier corresponding to the ECS that supports the allowed NSSAI among the UE-specific ECS provider identifiers. It should be understood that the NSSAI is information subscribed by the UE, and the NSSAI subscribed by different UEs may be different. The allowed NSSAI is a parameter in the NSSAI set, indicating the NSSAI that the UE is allowed to use. Therefore, the allowed NSSAI is associated with the UE.

Further, the first request message above can be understood as a subscription message, and the first request message is used for subscribing to a UE-specific ECS provider ID, or for subscribing to an ECS provider ID corresponding to an ECS that supports the NSSAI. It should be understood that if the first request message is a subscription message, when the ECS provider ID subscribed by the AMF changes, the NWDAF may notify the AMF of the latest ECS provider ID.

As an example, a possible implementation of this step is that in the registration process, the AMF sends the first request message to the NWDAF through the Nnwdaf_AnalyticsSubscription Subscribe message or sends the first request message to the NWDAF through the Nnwdaf_AnalyticsInfo Request message. In another example, step S501 can also be implemented in a PDU session establishment/modification process, or a service request (service request) process. It can be understood that the above is only an example of implementing step S501, and the present application does not limit specific implementation procedures, messages or signaling.

S502. The NWDAF sends a second subscription message to one or more AFs, where the second subscription message is used to request the use of the application by the UE. Specifically, the second subscription message includes the identifier of the UE. Correspondingly, one or more AFs receive the second subscription message.

S503. One or more AFs send a second notification message to the NWDAF, where the second notification message includes usage of the application by the UE. Correspondingly, the NWDAF receives the second notification message.

For the implementation of step S502-step S503 in the embodiment of the present application, reference may be made to the implementation of step S402-step S403 in the embodiment shown in FIG.

Optionally, the second subscription message may also include NSSAI, such as the NSSAI subscribed by the UE or the allowed NSSAI, etc., and the second subscription message is specifically used for subscribing the usage of the application program supporting the NSSAI by the UE. Correspondingly, what is included in the second notification message is also the use of the application program supporting the NSSAI by the UE.

S504. The NWDAF determines the UE-specific identifier of the first ECS provider according to the application status of the UE in the second notification message.

S505. The NWDAF sends the UE-specific identifier of the first ECS provider to the AMF. Correspondingly, the AMF receives the first ECS provider identifier.

For the implementation of step S504 in this embodiment of the present application, reference may be made to the implementation of step S404 in the aforementioned embodiment shown in FIG.

Optionally, the above step S501-step S505 can be performed in the registration process, or the PDU session establishment/modification process, or the service request (service request) process.

S506. The AMF sends the first ECS provider identifier to the SMF. Correspondingly, the SMF receives the first ECS provider identifier.

Optionally, the AMF may send the first ECS provider identifier to the SMF through a session establishment process or a session modification process. Exemplarily, the first ECS provider identifier sent by the AMF to the SMF is carried in the N11 interface message, such as the Nsmf_PDUSession_CreateSMContext Request message. Certainly, the first ECS provider identifier sent by the AMF to the SMF may also be carried in other messages, signaling or procedures, which is not limited by this embodiment of the present application.

S507. The SMF determines the first ECS configuration information according to the first ECS provider identifier, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS and the first ECS provider ID corresponds.

S508. The SMF sends the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information.

For the implementation of step S507-step S508 in the embodiment of the present application, reference may be made to the implementation of step S406-step S407 in the aforementioned embodiment shown in FIG.

The content contained in the ECS configuration information in the embodiment of the present application is only an example. In practical applications, the content of the ECS configuration information may be consistent with existing standards or future standards.

Optionally, the above steps S506-S508 may be performed in a session establishment or session modification process.

Optionally, after step S508, the communication method in this embodiment of the present application may further include one or more of the following steps:

S509. The NWDAF determines the fourth ECS provider ID updated for the first ECS provider ID according to the change of the UE's use of the application program received from one or more AFs.

S510. The NWDAF sends the fourth ECS provider identifier to the AMF. Correspondingly, the AMF receives the fourth ECS provider identifier.

For the implementation of step S509-step S510 in the embodiment of the present application, reference may be made to the implementation of step S408-step S409 in the embodiment shown in FIG.

S511. The AMF sends the fourth ECS provider identifier to the SMF. Correspondingly, the SMF receives the fourth ECS provider identifier.

Optionally, the AMF may send the fourth ECS provider identifier to the SMF through a session establishment process or a session modification process. Exemplarily, the fourth ECS provider identifier sent by the AMF to the SMF is carried in the N11 interface message. Of course, the fourth ECS provider identifier sent by the AMF to the SMF may also be carried in other messages, signaling or procedures, which is not limited by this embodiment of the present application.

S512. The SMF determines fourth ECS configuration information according to the fourth ECS provider identifier, the fourth ECS configuration information includes the fourth ECS provider identifier and the address of the fourth ECS, and the fourth ECS is related to the fourth ECS provider. ID corresponds.

S513. The SMF sends the fourth ECS configuration information to the UE. Correspondingly, the UE receives the fourth ECS configuration information.

For the implementation of step S512-step S513 in the embodiment of the present application, reference may be made to the implementation of step S410-step S411 in the embodiment shown in FIG.

S514. The UE sends a second message to the SMF, where the second message includes a fifth ECS provider identifier or a second application identifier, where the second application identifier is used to determine a fifth ECS provider identifier, and the fifth ECS provider The ID does not belong to the first ECS provider ID. Correspondingly, the SMF receives the second message.

S515. The SMF sends the address of the ECS corresponding to the fifth ECS provider identifier to the UE. Correspondingly, the UE receives the address of the ECS.

For the implementation of step S514-step S515 in the embodiment of the present application, reference may be made to the implementation of step S412-step S413 in the embodiment shown in FIG.

In the embodiment of this application, the AMF subscribes/acquires the UE-specific ECS Provider ID from the NWDAF, and sends it to the SMF, and the SMF sends the UE-specific ECS configuration information corresponding to the UE-specific ECS Provider ID (that is, the first ECS configuration information), and Instead of sending all the ECS configuration information corresponding to the ECS Provider ID to the UE, redundant information elements in the ECS configuration information can be reduced. In addition, the SMF in the embodiment of the present application sends updated ECS configuration information to the UE when the ECS corresponding to the UE-specific ECS Provider ID needs to be updated, thereby avoiding unnecessary update signaling of the ECS configuration information and reducing signaling in the network. order overhead.

Embodiment six

Referring to FIG. 10 , FIG. 10 is a sixth schematic flowchart of a communication method provided by an embodiment of the present application. Exemplarily, the communication method provided by the embodiment of the present application may be applied to the network architecture shown in the aforementioned FIG. 1 or FIG. 3 . As shown in Figure 10, the communication method includes one or more of the following steps:

S601. The AF determines a UE-specific first ECS provider identifier according to the use of the application by the UE.

S602. The AF sends the first ECS provider identifier to the SMF. Correspondingly, the SMF receives the first ECS provider identifier.

Optionally, the AF may perceive/acquire the usage status of the UE's AF-related applications (such as usage frequency, average usage duration, usage times, application download rate, etc.). The AF may determine at least one UE-specific ECS provider identifier according to the usage of the AF-related application program by the UE. Specifically, the manner in which the AF determines the UE-specific ECS provider ID according to the usage of the application by the UE can refer to the above-mentioned embodiment shown in Figure 8 (that is, the fourth embodiment) in which NWDAF determines the UE The manner of identifying a specific ECS provider is not described here. The AF can send at least one ECS provider identifier specific to the UE to the SMF through the AF influence process, and the SMF receives the at least one ECS provider identifier accordingly. The SMF may determine the first ECS provider identifier according to the received at least one ECS provider identifier. For example, the SMF obtains the first ECS provider identifier after merging the same ECS provider identifier among the received at least one ECS provider identifier. The first ECS provider identifier includes all or part of the received at least one ECS provider identifier. Wherein, the first ECS provider ID can be one or more ECS provider IDs; or the first ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs.

Because the first ECS provider ID is all or part of at least one UE-specific ECS provider ID received by the SMF from the AF, it can also be understood that the AF determines the UE-specific The ID of the first ECS provider, and sends the ID of the first ECS provider to the SMF.

Optionally, the AF here may be EAS, EES or ECS, or any other AF that can associate or manage one or more applications or application platforms.

It should be understood that because an AF may only associate or manage some applications in the network, the SMF can actually obtain the ECS Provider ID commonly used by the UE from one or more AFs. If the SMF obtains the ECS Provider ID commonly used by UE from multiple AFs, then the SMF may not be able to obtain all the commonly used ECS Provider IDs from a single AF, and the ECS Provider ID commonly used by the UE sent to the SMF by different AFs may also be different. The SMF can filter out the first ECS provider ID from the received UE common ECS Provider ID. The screening strategy of the SMF may depend on specific circumstances, which is not limited in this embodiment of the present application. One possible implementation is that if the number of different ECS Provider IDs received is large (for example, more than 10), the SMF will determine the first 10 of them as the first ECS provider ID according to the usage frequency from high to low . Of course, the SMF can also directly use the received UE common ECS Provider ID as the first ECS provider ID without screening.

S603. The SMF determines first ECS configuration information according to the first ECS provider identifier, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS is related to the first ECS provider. ID corresponds.

S604. The SMF sends the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information.

For the implementation of step S603-step S604 in the embodiment of the present application, reference may be made to the implementation of step S202-step S203 in the aforementioned embodiment shown in FIG.

Optionally, the above step S603 and step S604 may be implemented through a session establishment process or a session modification process. The above step S401 to the above step S407 can be understood as an initial sending process of the ECS configuration information.

In some cases (such as UE mobility, load balancing, etc.), if the SMF determines that the ECS configuration information corresponding to the UE-specific ECS provider ID (ie, the first ECS configuration information above) needs to be updated, the SMF updates the ECS configuration information to the UE. In an implementation manner, when the first ECS changes, the SMF sends second ECS configuration information to the UE, where the second ECS configuration information includes the first ECS provider identifier and the changed address of the first ECS. Correspondingly, the UE receives the second ECS configuration information. For details, refer to the implementation manner of step S204 in the embodiment shown in FIG. 6 (that is, Embodiment 2), and details are not described here.

After the initial sending process (such as after step S604), as time goes by, the UE's usage of the application may change, which may cause the UE's commonly used ECS Provider ID to be updated. Therefore, the communication method in the embodiment of the present application may also include one or more of the following steps:

S605. The AF sends to the SMF a fourth ECS provider ID updated with respect to the first ECS provider ID. Correspondingly, the SMF receives the fourth ECS provider identifier.

Optionally, when the AF perceives/obtains that the usage of the UE related to itself is updated or changed, the AF determines the updated UE-specific At least one ECS provider ID. The AF may send the updated UE-specific at least one ECS provider identifier to the SMF. The SMF may determine a fourth ECS provider identifier updated with respect to the first ECS provider identifier according to the received at least one UE-specific ECS provider identifier after the update. For example, the SMF obtains the fourth ECS provider identifier after combining the received ECS provider identifiers with the same ECS provider identifier. The fourth ECS provider identifier is all or part of the received updated UE-specific at least one ECS provider identifier. Wherein, the fourth ECS provider ID can be one or more ECS provider IDs; or the fourth ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs.

Because the fourth ECS provider ID is all or part of at least one UE-specific ECS provider ID after the update, it can also be understood that: AF determines the first ECS provider ID according to the change of the UE's usage of the application program. The provider identifies the updated fourth ECS provider ID, and sends the fourth ECS provider ID to the SMF.

It should be understood that because an AF may only associate or manage some applications in the network, in fact any AF can send the updated UE-specific ECS Provider ID to the SMF.

S606. The SMF determines fourth ECS configuration information according to the fourth ECS provider identifier, the fourth ECS configuration information includes the fourth ECS provider identifier and the address of the fourth ECS, and the fourth ECS and the fourth ECS provider ID corresponds.

S607, the SMF sends the fourth ECS configuration information to the UE. Correspondingly, the UE receives the fourth ECS configuration information.

For the implementation of step S606-step S607 in the embodiment of the present application, reference may be made to the implementation of step S410-step S411 in the embodiment shown in FIG.

Optionally, after the above step S604, the UE may use the "unused ECS". For the process of using the "unused ECS" by the UE, refer to step S412-step S413 in the embodiment shown in FIG. 8 above, which will not be repeated here.

In the embodiment of this application, the AF analyzes the ECS Provider ID commonly used by the UE and sends it to the SMF. The SMF sends the configuration information of the ECS corresponding to the ECS Provider ID commonly used by the UE to the UE (that is, the first ECS configuration information), instead of sending all ECS Provider IDs to the UE. The configuration information of the ECS corresponding to the ID is sent to the UE, which can reduce redundant information elements in the ECS configuration information. In addition, the SMF in the embodiment of the present application sends updated ECS configuration information to the UE when the ECS corresponding to the ECS Provider ID commonly used by the UE needs to be updated, thereby avoiding unnecessary update signaling of ECS configuration information and reducing signaling in the network. order overhead.

Embodiment seven

Referring to FIG. 11 , FIG. 11 is a seventh schematic flowchart of the communication method provided by the embodiment of the present application. Exemplarily, the communication method provided by the embodiment of the present application may be applied to the network architecture shown in the aforementioned FIG. 1 or FIG. 3 . As shown in Figure 11, the communication method includes one or more of the following steps:

S701. The AF determines at least one UE-specific ECS provider identifier according to the usage of the application program by the UE.

S702. The AF sends at least one ECS provider identifier specific to the UE to the AMF. Correspondingly, the AMF receives at least one ECS provider identifier specific to the UE.

S703. The AMF determines a UE-specific first ECS provider identifier according to the UE-specific at least one ECS provider identifier, where the first ECS provider identifier includes all or part of the at least one ECS provider identifier.

S704. The AMF sends the first ECS provider identifier to the SMF. Correspondingly, the SMF receives the first ECS provider identifier.

Optionally, the AF may perceive/obtain the UE's usage of the AF-related application (such as usage frequency, average usage duration, usage times, application download rate, etc.). The AF may determine at least one UE-specific ECS provider identifier according to the usage of the AF-related application program by the UE. Specifically, the manner in which the AF determines the UE-specific ECS provider ID according to the usage of the application by the UE can refer to the above-mentioned embodiment shown in Figure 8 (that is, the fourth embodiment) in which NWDAF determines the UE The manner of identifying a specific ECS provider is not described here. The AF may send at least one ECS provider identifier specific to the UE to the AMF through the AF influence process, and correspondingly, the AMF receives the at least one ECS provider identifier. The AMF may determine the first ECS provider identifier according to the received at least one ECS provider identifier. For example, the AMF obtains the first ECS provider identifier after merging the same ECS provider identifier among the received at least one ECS provider identifier. The first ECS provider identifier includes all or part of the received at least one ECS provider identifier. The AMF then sends the first ECS provider identifier to the SMF.

Wherein, the first ECS provider ID can be one or more ECS provider IDs; or the first ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs.

It should be understood that since an AF may only associate or manage some applications in the network, the AMF can actually obtain the ECS Provider ID commonly used by the UE from one or more AFs. If the AMF obtains the ECS Provider ID commonly used by the UE from multiple AFs, then the AMF may not be able to obtain all the commonly used ECS Provider IDs from a single AF, and the ECS Provider ID commonly used by the UE sent to the AMF by different AFs may also be different. The AMF can filter out the first ECS provider ID from the received UE common ECS Provider ID. The screening strategy for AMF may depend on specific circumstances, which is not limited in this embodiment of the present application. Of course, the AMF can also directly use the received UE common ECS Provider ID as the first ECS provider ID without screening. That is to say, AMF uses the union of ECS Provider IDs sent by all AFs received as the first ECS provider ID.

S705. The SMF determines first ECS configuration information according to the first ECS provider identifier, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS is related to the first ECS provider. ID corresponds.

S706. The SMF sends the first ECS configuration information to the UE. Correspondingly, the UE receives the first ECS configuration information.

For the implementation of step S705-step S706 in the embodiment of the present application, reference may be made to the implementation of step S202-step S203 in the aforementioned embodiment shown in FIG.

Optionally, the above step S705 and step S706 may be implemented through a session establishment process or a session modification process. The above step S701 to the above step S706 can be understood as the initial sending process of the ECS configuration information.

After the initial sending process (such as after step S706), as time goes by, the UE's use of the application program may change, which may cause the UE-specific ECS Provider ID to be updated. Therefore, the communication method in the embodiment of the present application may also include one or more of the following steps:

S707, the AF sends the updated UE-specific at least one ECS provider identifier to the AMF. Correspondingly, the AMF receives the updated UE-specific at least one ECS provider identifier.

S708. The AMF determines a fourth ECS provider identity updated for the first ECS provider identity according to the updated UE-specific at least one ECS provider identity, and the fourth ECS provider identity is at least one ECS provider identity specific to the updated UE. All or part of an ECS provider ID.

S709. The AMF sends the fourth ECS provider identifier to the SMF. Correspondingly, the SMF receives the fourth ECS provider identifier.

Optionally, when the AF perceives/obtains that the usage of the UE related to itself is updated or changed, the AF determines the updated UE-specific At least one ECS provider ID. The AF may send the updated UE-specific at least one ECS provider identifier to the AMF. The AMF may determine a fourth ECS provider identifier updated with respect to the first ECS provider identifier according to the received at least one UE-specific ECS provider identifier after the update. For example, the AMF obtains the fourth ECS provider identifier after combining the received ECS provider identifiers with the same ECS provider identifier. The fourth ECS provider identifier is all or part of the received updated UE-specific at least one ECS provider identifier. The AMF then sends the fourth ECS provider identifier to the SMF.

Wherein, the fourth ECS provider ID can be one or more ECS provider IDs; or the fourth ECS provider ID can also be understood as a set or list, including one or more ECS provider IDs.

It should be understood that because an AF may only associate or manage some applications in the network, in fact any AF can send the updated UE-specific ECS Provider ID to the AMF.

S710, the SMF determines fourth ECS configuration information according to the fourth ECS provider identifier, the fourth ECS configuration information includes the fourth ECS provider identifier and the address of the fourth ECS, and the fourth ECS is related to the fourth ECS provider ID corresponds.

S711. The SMF sends the fourth ECS configuration information to the UE. Correspondingly, the UE receives the fourth ECS configuration information.

For the implementation of step S710-step S711 in the embodiment of the present application, reference may be made to the implementation of step S410-step S411 in the embodiment shown in FIG.

Optionally, after the above step S706, the UE may use the "unused ECS". For the process of using the "unused ECS" by the UE, refer to step S412-step S413 in the embodiment shown in FIG. 8 above, which will not be repeated here.

In the embodiment of this application, the AF analyzes the ECS Provider ID commonly used by the UE and sends it to the AMF. The AMF sends all or part of the received ECS Provider ID commonly used by the UE to the SMF, and the SMF sends the received part of the ECS Provider ID to the UE. The corresponding ECS configuration information (that is, the first ECS configuration information), instead of sending all the ECS configuration information corresponding to the ECS Provider ID to the UE, can reduce redundant information elements in the ECS configuration information. In addition, the SMF in the embodiment of the present application sends updated ECS configuration information to the UE when the ECS corresponding to the ECS Provider ID commonly used by the UE needs to be updated, thereby avoiding unnecessary update signaling of ECS configuration information and reducing signaling in the network. order overhead.

The above content elaborates the method of the present application in detail. In order to better implement the above solutions of the embodiments of the present application, the embodiments of the present application also provide corresponding devices or equipment.

In the embodiment of the present application, the functional modules of each network element of the present application can be divided according to the above method example, and the functional modules of the above network element can also be divided according to the above method example. For example, each functional module can be divided corresponding to each function, or can be Two or more functions are integrated in one processing module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation. The communication device according to the embodiment of the present application will be described in detail below with reference to FIG. 12 to FIG. 13 .

In the case of using an integrated unit, refer to FIG. 12 , which is a schematic structural diagram of a communication device provided by an embodiment of the present application. As shown in FIG. 12 , the communication device includes: a transceiver unit 11 and a processing unit 12 .

In some embodiments of the present application, the communication device may be an SMF or a chip or a circuit that may be disposed in the SMF. That is, the communication device can be used to perform the steps or functions performed by the SMF in the method embodiments above.

Wherein, the processing unit 12 is configured to obtain a UE-specific first ECS provider identifier; the transceiver unit 11 is configured to send first ECS configuration information to the UE, wherein the first ECS configuration information includes the first ECS provider identifier and The address of the first ECS, where the first ECS corresponds to the first ECS provider identifier.

It should be understood that the communication device in this design can correspondingly execute the aforementioned first embodiment, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operation of the SMF in the aforementioned first embodiment, and its technical effect can be found in the aforementioned implementation For the sake of brevity, the technical effect in Example 1 will not be repeated here.

In one design, the transceiver unit 11 is configured to receive a UE-specific first ECS provider identifier and/or a UE-specific first application identifier from the UE or AMF, and the UE-specific first application identifier is used to determine the UE A specific first ECS provider identifier; a processing unit 12 configured to determine first ECS configuration information according to the first ECS provider identifier or the first application identifier, the first ECS configuration information including the first ECS provider identifier An identifier and an address of the first ECS, where the first ECS corresponds to the first ECS provider identifier; the transceiving unit 11 is further configured to send the first ECS configuration information to the UE.

Optionally, the above-mentioned transceiving unit 11 is further configured to send second ECS configuration information to the UE when the first ECS changes, and the second ECS configuration information includes the first ECS provider identifier and the changed first ECS configuration information. The address of the ECS.

Optionally, the transceiving unit 11 is further configured to send the second ECS to the UE when the second ECS corresponding to the second ECS provider ID changes and the second ECS provider ID belongs to the first ECS provider ID. The ECS provider ID and the changed address of the second ECS.

Optionally, the above-mentioned transceiving unit 11 is further configured to receive a first message, where the first message is used to indicate to update the UE-specific first ECS provider identifier or UE-specific first application identifier; the above-mentioned processing unit 12 is also configured to: is used to update the first ECS provider ID according to the first message to obtain a UE-specific third ECS provider ID; the transceiver unit 11 is further configured to send third ECS configuration information to the UE, the third The ECS configuration information includes the third ECS provider identifier and the address of the third ECS, and the third ECS corresponds to the third ECS provider identifier. Correspondingly, the UE receives the third ECS configuration information.

It should be understood that the communication device in this design can correspondingly execute the foregoing

embodiment

2 or 3, and the above-mentioned operations or functions of each unit in the communication device are to realize the corresponding operations of the SMF in the foregoing

embodiment

2 or 3 respectively, and its technical For the effect, refer to the technical effect in the foregoing embodiment two or three, and for the sake of brevity, details are not repeated here.

In one design, the transceiver unit 11 is configured to receive a UE-specific first ECS provider identifier from the NWDAF or AMF or AF; the processing unit 12 is configured to determine the first ECS configuration information according to the first ECS provider identifier, the The first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS corresponds to the first ECS provider identifier; the transceiver unit 11 is also configured to send the first ECS configuration to the UE information.

Optionally, the above-mentioned transceiving unit 11 is further configured to send a first request message to the NWDAF, where the first request message is used to acquire a UE-specific ECS provider identifier. Wherein, the first request message may include the identifier of the UE.

Optionally, the above-mentioned transceiving unit 11 is further configured to receive a fourth ECS provider ID updated for the first ECS provider ID from the AF or NWDAF or AMF; the above-mentioned processing unit 12 is also configured to provide The provider identifier determines the fourth ECS configuration information, the fourth ECS configuration information includes the fourth ECS provider identifier and the address of the fourth ECS, and the fourth ECS corresponds to the fourth ECS provider identifier; the transceiver unit 11 also It is used to send the fourth ECS configuration information to the UE.

Optionally, the above-mentioned transceiving unit 11 is further configured to receive a second message from the UE, where the second message includes a fifth ECS provider identifier or a second application identifier, and the second application identifier is used to determine whether the fifth ECS provider The provider identifier, the fifth ECS provider identifier does not belong to the first ECS provider identifier; the transceiving unit 11 is further configured to send the address of the ECS corresponding to the fifth ECS provider identifier to the UE.

It should be understood that the communication device in this design can correspondingly execute the foregoing embodiments 4 to 7, and the above-mentioned operations or functions of each unit in the communication device are to realize the corresponding operations of the SMF in the foregoing embodiments 4 to 7, and its technical effect can be found in For the sake of brevity, the technical effects in the aforementioned embodiments 4 to 7 will not be repeated here.

Reusing FIG. 12 , in other embodiments of the present application, the communication device may be the terminal device (such as UE, etc.) shown above or a chip in the terminal device. That is, the communication device may be used to perform the steps or functions performed by the UE in the above method embodiments.

Wherein, the transceiver unit 11 is configured to receive first ECS configuration information, wherein the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS corresponds to the first ECS provider identifier .

Optionally, the processing unit 12 is configured to determine an ECS for EES discovery according to the first ECS configuration information.

Optionally, the above-mentioned processing unit 12 is further configured to determine the UE-specific first ECS provider identifier and/or the UE-specific first application according to the application installed in the UE and/or the usage of the application by the UE. Program ID.

Optionally, the above-mentioned transceiver unit 11 is further configured to send a UE-specific first ECS provider identifier and/or a UE-specific first application identifier to the SMF or AMF, where the first application identifier is used to determine the UE-specific The first ECS provider ID.

Optionally, the transceiving unit 11 is further configured to receive second ECS configuration information from the SMF, where the second ECS configuration information includes the first ECS provider identifier and the changed address of the first ECS.

Optionally, the above-mentioned transceiving unit 11 is further configured to receive the second ECS provider ID and the changed address of the second ECS from the SMF, the second ECS provider ID belongs to the first ECS provider ID, and the second ECS provider ID belongs to the first ECS provider ID. The second ECS corresponding to the second ECS provider identifier changes.

Optionally, the above-mentioned transceiver unit 11 is further configured to send a first message to the SMF, where the first message is used to indicate to update the UE-specific first ECS provider identifier or UE-specific first application identifier; the above-mentioned transceiver unit 11 , is also used to receive third ECS configuration information from the SMF, the third ECS configuration information includes the third ECS provider identifier and the address of the third ECS, the third ECS provider identifier is the first ECS specific to the UE The provider ID is updated, and the third ECS corresponds to the third ECS provider ID.

Optionally, the above-mentioned transceiving unit 11 is further configured to receive fourth ECS configuration information from the SMF, the fourth ECS configuration information including the fourth ECS provider ID updated for the first ECS provider ID and the address of the fourth ECS , the fourth ECS corresponds to the fourth ECS provider identifier.

Optionally, the above-mentioned transceiver unit 11 is further configured to send a second message to the SMF, where the second message includes the fifth ECS provider identifier or the second application identifier, and the second application identifier is used to determine whether the fifth ECS provider The provider identifier, the fifth ECS provider identifier does not belong to the first ECS provider identifier; the transceiving unit 11 is further configured to receive the address of the ECS corresponding to the fifth ECS provider identifier.

It should be understood that the communication device can correspondingly execute the aforementioned embodiments 1 to 7, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of the UE in the aforementioned embodiments 1 to 7, and the technical effects thereof can be referred to the aforementioned embodiments 1 to 7. For the sake of brevity, the technical effects of No. 7 will not be repeated here.

Reusing FIG. 12 , in some other embodiments of the present application, the communication device may be the AMF shown above or a chip in the AMF, or the like. That is, the communication device may be used to execute the steps or functions executed by the AMF in the above method embodiments.

One design, the transceiver unit 11 is configured to receive the UE-specific first ECS provider identifier and/or the UE-specific first application identifier from the UE; the transceiver unit 11 is also configured to send the first ECS provider identifier to the SMF The provider identifier and/or the UE-specific first application identifier, where the first application identifier is used to determine the UE-specific first ECS provider identifier.

It should be understood that the communication device can correspondingly execute the aforementioned third embodiment, and the above-mentioned operations or functions of each unit in the communication device are to realize the corresponding operation of the AMF in the aforementioned third embodiment, and its technical effect can be referred to in the aforementioned third embodiment For the sake of brevity, the technical effects will not be repeated here.

In one design, the transceiver unit 11 is configured to send a first request message to the NWDAF, where the first request message is used to obtain a UE-specific ECS provider identifier; the transceiver unit 11 is also configured to receive the UE-specific first ECS provider identifier from the NWDAF. An ECS provider identifier; the transceiving unit 11 is also configured to send the first ECS provider identifier to the SMF.

Optionally, the above-mentioned first request message includes the identifier of the UE and/or allowed NSSAI.

It should be understood that the communication device can correspondingly execute the foregoing fifth embodiment, and the above-mentioned operations or functions of each unit in the communication device are to realize the corresponding operation of the AMF in the foregoing embodiment 5, and its technical effect can be referred to in the foregoing embodiment 5. For the sake of brevity, the technical effects will not be repeated here.

In one design, the transceiver unit 11 is configured to receive at least one UE-specific ECS provider identifier from the AF; the processing unit 12 is configured to determine a UE-specific first ECS provider according to the UE-specific at least one ECS provider identifier An identifier, the first ECS provider identifier includes all or part of the at least one ECS provider identifier; the transceiving unit 11 is further configured to send the first ECS provider identifier to the SMF.

Optionally, the above-mentioned transceiving unit 11 is further configured to send a fourth ECS provider ID updated to the first ECS provider ID to the AMF or SMF.

It should be understood that the communication device can correspondingly execute the foregoing seventh embodiment, and the above-mentioned operations or functions of each unit in the communication device are to realize the corresponding operation of the AMF in the foregoing embodiment 7, and its technical effect can be referred to in the foregoing embodiment 7. For the sake of brevity, the technical effects will not be repeated here.

Reusing FIG. 12 , in still other embodiments of the present application, the communication device may be the NWDAF shown above or a chip in the NWDAF, or the like. That is, the communication device may be used to perform the steps or functions performed by the NWDAF in the above method embodiments.

Wherein, the processing unit 12 is configured to obtain a UE-specific first ECS provider identifier; the transceiving unit 11 is configured to send the first ECS provider identifier to the SMF or AMF.

Optionally, the transceiving unit 11 is further configured to receive a first request message from the SMF, where the first request message is used to acquire a UE-specific ECS provider identifier. Wherein, the first request message may include the identifier of the UE.

Optionally, the transceiving unit 11 is further configured to receive a first request message from the AMF, where the first request message is used to obtain a UE-specific ECS provider identifier. The first request message includes the identifier of the UE and/or allowed NSSAI.

Optionally, the above-mentioned transceiving unit 11 is further configured to request one or more AFs to subscribe to the UE's usage of the application; the transceiving unit 11 is also configured to receive the UE's usage of the application from one or more AFs The above-mentioned processing unit 12 is configured to determine the UE-specific first ECS provider identifier according to the usage of the application program by the UE.

Optionally, the above-mentioned processing unit 12 is further configured to determine a fourth ECS provider identifier updated for the first ECS provider identifier according to the change of the UE's usage of the application program received from one or more AFs; The above-mentioned transceiving unit is further configured to send the fourth ECS provider identifier to the SMF or AMF.

It should be understood that the communication device can correspondingly execute the foregoing

embodiments

4 and 5, and the above-mentioned operations or functions of each unit in the communication device are to realize the corresponding operations of the NWDAF in the foregoing

embodiments

4 and 5 respectively, and its technical effect can be referred to the foregoing embodiments For the sake of brevity, the technical effects in Examples 4 and 5 will not be repeated here.

Reusing FIG. 12 , in still other embodiments of the present application, the communication device may be the AF shown above or a chip in the AF, or the like. That is, the communication device can be used to execute the steps or functions executed by the AF in the method embodiments above.

Wherein, the processing unit 12 is configured to determine the UE-specific first ECS provider ID according to the usage of the application program by the UE; the transceiving unit 11 is configured to send the first ECS provider ID to the AMF or SMF.

It should be understood that the communication device can correspondingly execute the

aforementioned embodiments

6 and 7, and the above-mentioned operations or functions of each unit in the communication device are to realize the corresponding operations of AF in the

aforementioned embodiments

6 and 7 respectively. For the technical effects, refer to the aforementioned embodiments For the sake of brevity, the technical effects in Examples 6 and 7 will not be repeated here.

In a possible implementation, in the communication device shown in FIG. 12 , the processing unit 12 may be one or more processors, the transceiver unit 11 may be a transceiver, or the transceiver unit 11 may also be a sending unit and a receiving unit , the sending unit may be a transmitter, and the receiving unit may be a receiver, and the sending unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiment of the present application, the processor and the transceiver may be coupled, and the connection manner of the processor and the transceiver is not limited in the embodiment of the present application.

Referring to FIG. 13 , FIG. 13 is a schematic structural diagram of a communication device 1000 provided by an embodiment of the present application. As shown in FIG. 13 , the communication device 1000 provided in the embodiment of the present application may be used to implement the method described in the above method embodiment, and reference may be made to the description in the above method embodiment. The communication device 1000 may be any network element among the foregoing SMF, UE, AMF, NWDAF, and AF.

The communication device 1000 includes one or more processors 1001 . The processor 1001 may be a general purpose processor or a special purpose processor or the like. For example, it may be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processor can be used to control devices (such as UE, SMF or NWDAF, etc.), execute software programs, and process data of software programs. The device may include a transceiver unit for inputting (receiving) and outputting (sending) signals. For example, the device may be a chip, and the transceiver unit may be an input and/or output circuit of the chip, or a communication interface. The chip can be used in terminal equipment (such as UE) or core network equipment (such as SMF, AMF, NWDAF, AF, etc.). In another example, the device may be a terminal device (such as UE) or a core network device (such as SMF, AMF, NWDAF, AF, etc.), and the transceiver unit may be a transceiver, a radio frequency chip, and the like.

The communications device 1000 includes one or more processors 1001, and the one or more processors 1001 can implement the method of any network element in any of the preceding embodiments.

Optionally, the processor 1001 may also implement other functions in addition to implementing the method in any of the preceding embodiments.

Optionally, in one design, the processor 1001 may also include an instruction 1003, and the instruction may be executed on the processor, so that the communication device 1000 executes the method described in any one of the foregoing method embodiments.

In yet another possible design, the communication device 1000 may also include a circuit, and the circuit may implement a function of any network element in any of the foregoing method embodiments.

In yet another possible design, the communication device 1000 may include one or more memories 1002, on which are stored instructions 1004, the instructions can be executed on the processor, so that the communication device 1000 executes any of the above-mentioned Methods described in the Methods Examples. Optionally, data may also be stored in the memory. Instructions and/or data may also be stored in the optional processor. For example, the one or more memories 1002 may store the DCI or SCI described in the above embodiments, or other information involved in the above embodiments. The processor and memory can be set separately or integrated together.

In yet another possible design, the communication device 1000 may further include a transceiver unit 1005 and an antenna 1006, or, include a communication interface. The transceiver unit 1005 may be called a transceiver, a transceiver circuit, or a transceiver, etc., and is used to realize the transceiver function of the device through the antenna 1006 . The communication interface (not shown in the figure) may be used for communication between the core network device and the access network device, or between the access network device and the access network device. Optionally, the communication interface may be an interface for wired communication, such as an interface for optical fiber communication.

The processor 1001 may be referred to as a processing unit, and controls an apparatus (such as a communication device).

It should be understood that the processor in the embodiment of the present application may be a central processing unit (central processing unit, CPU), and the processor may also be other general-purpose processors, digital signal processors (digital signal processor, DSP), dedicated integrated Circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.

It should also be understood that the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the non-volatile memory can be read-only memory (read-only memory, ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically programmable Erases programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, many forms of random access memory (RAM) are available, such as static random access memory (static RAM, SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory Access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory Access memory (synchlink DRAM, SLDRAM) and direct memory bus random access memory (direct rambus RAM, DR RAM).

The above-mentioned embodiments may be implemented in whole or in part by software, hardware (such as circuits), firmware, or other arbitrary combinations. When implemented using software, the above-described embodiments may be implemented in whole or in part in the form of computer program products. The computer program product comprises one or more computer instructions or computer programs. When the computer instruction or computer program is loaded or executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center through wired, such as optical fiber, or wireless, such as infrared, wireless, microwave, etc. The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center that includes one or more sets of available media. The available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media. The semiconductor medium may be a solid state drive.

An embodiment of the present application further provides a computer program product, where the computer program product includes computer program code, and when the computer program code is run on a computer, the computer is made to execute the method steps of any network element described in the foregoing embodiments.

An embodiment of the present application also provides a computer-readable storage medium, where program instructions are stored on the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer is made to execute the method of any network element described in the foregoing embodiments step.

The embodiment of the present application also provides a device, and the device may be a chip. The chip includes a processor. The processor is configured to read and execute the computer program stored in the memory, so as to execute the method in any possible implementation manner of any of the foregoing embodiments. Optionally, the chip further includes a memory, and the memory is connected to the processor through a circuit or wires. Further optionally, the chip further includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive data and/or signals to be processed, and the processor obtains the data and/or signals from the communication interface, processes the data and/or signals, and outputs processing results through the communication interface. The communication interface may be an input-output interface.

In another embodiment of the present application, a communication system is also provided. The communication system includes an SMF, and the SMF can execute the method in any of the foregoing embodiments. Optionally, the communication system further includes a UE, and the UE can execute the method in any one of the foregoing embodiments. Optionally, the communication system further includes an AF, and the AF can execute the method in any of the foregoing embodiments. Optionally, the communication system further includes an AMF, and the AMF can execute the method in any one of the foregoing embodiments. Optionally, the communication system further includes a NWDAF, and the NWDAF can execute the method in any one of the preceding embodiments.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments are realized. The processes can be completed by computer programs to instruct related hardware. The programs can be stored in computer-readable storage media. When the programs are executed , may include the processes of the foregoing method embodiments. The aforementioned storage medium includes: ROM or random access memory RAM, magnetic disk or optical disk, and other various media that can store program codes.

The above is only a specific implementation of the application, but the scope of protection of the application is not limited thereto. Anyone familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the application. Should be covered within the protection scope of this application. Therefore, the protection scope of the present application should be determined by the protection scope of the claims.

Claims

A communication method, characterized in that, comprising:

The session management function entity obtains the specific first edge configuration server ECS provider identifier of the terminal device;

The session management function entity sends first ECS configuration information to the terminal device;

Wherein, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS corresponds to the first ECS provider identifier.
The method according to claim 1, wherein the session management function entity obtains the first ECS provider identifier specific to the terminal device, comprising:

The session management function entity receives the first ECS provider identifier from the terminal device, the access and mobility management function entity, the network data analysis function entity, or the application function entity.
The method according to claim 1, wherein the session management function entity obtains the first ECS provider identifier specific to the terminal device, comprising:

The session management function entity receives the terminal device-specific first application identifier from the terminal device or the access and mobility management function entity;

The session management function entity acquires the first ECS provider identifier corresponding to the first application identifier.
The method according to claim 3, wherein the session management functional entity obtaining the first ECS provider identifier corresponding to the first application identifier comprises:

The session management functional entity obtains the corresponding relationship between the application ID and the ECS provider ID;

The session management function entity determines the first ECS provider identifier corresponding to the first application identifier according to the correspondence relationship.
The method according to any one of claims 1-3, wherein the first ECS provider identifier is one or more ECS provider identifiers;

After the session management function entity sends the first ECS configuration information to the terminal device, the method further includes:

If the second ECS corresponding to the second ECS provider ID changes and the second ECS provider ID belongs to the first ECS provider ID, the session management function entity sends the second The ECS provider ID and the changed address of the second ECS.
The method according to any one of claims 1-5, wherein after the session management function entity sends the first ECS configuration information to the terminal device, the method further comprises:

The session management function entity receives a first message from the terminal device, where the first message is used to indicate to update the terminal device-specific first ECS provider identifier or the terminal device-specific first application identifier ;

The session management function entity updates the first ECS provider identifier according to the first message to obtain a third ECS provider identifier specific to the terminal device;

The session management function entity sends third ECS configuration information to the terminal device, the third ECS configuration information includes a third ECS provider identifier and a third ECS address, and the third ECS and the third ECS The provider ID corresponds.
The method according to any one of claims 1-2, 5, wherein the session management function entity obtains the first ECS provider identifier specific to the terminal device, comprising:

The session management function entity sends a first request message to the network data analysis function entity, where the first request message is used to obtain the ECS provider identifier specific to the terminal device;

The session management function entity receives the terminal device-specific first ECS provider identifier from the network data analysis function entity.
A communication method, characterized in that, comprising:

The terminal device receives first ECS configuration information from the session management function entity, where the first ECS configuration information includes the first ECS provider identifier specific to the terminal device and the address of the first ECS, and the first ECS is related to the Corresponding to the first ECS provider identifier;

The terminal device determines, according to the first ECS configuration information, an ECS used for discovery by an edge-enabled server (EES).
The method according to claim 8, wherein before the terminal device receives the first ECS configuration information from the session management function entity, the method further comprises:

The terminal device sends the first ECS provider identifier and/or the terminal device-specific first application identifier to the session management functional entity or the access and mobility management functional entity, where the first application identifier is used for Determine the first ECS provider identifier specific to the terminal device.
The method according to claim 9, characterized in that the method further comprises:

The terminal device determines the terminal device-specific first ECS provider identifier and/or the terminal device-specific first An application identifier.
The method according to any one of claims 8-10, wherein the first ECS provider identifier is one or more ECS provider identifiers;

After the terminal device receives the first ECS configuration information from the session management function entity, the method further includes:

The terminal device receives the second ECS provider ID and the changed address of the second ECS from the session management function entity, the second ECS provider ID belongs to the first ECS provider ID, and the second ECS provider ID belongs to the first ECS provider ID. The second ECS corresponding to the second ECS provider identifier changes.
The method according to any one of claims 8-11, wherein after the terminal device receives the first ECS configuration information from the session management function entity, the method further comprises:

The terminal device sends a first message to the session management function entity, where the first message is used to indicate to update the terminal device-specific first ECS provider identifier or the terminal device-specific first application identifier;

The terminal device receives third ECS configuration information from the session management function entity, the third ECS configuration information includes a third ECS provider identifier and a third ECS address, and the third ECS provider identifier is for The terminal device-specific first ECS provider identifier is updated, and the third ECS corresponds to the third ECS provider identifier.
A communication method, characterized in that, comprising:

The access and mobility management functional entity obtains the terminal device-specific first ECS provider identifier and/or the terminal device-specific first application identifier;

The access and mobility management functional entity sends the first ECS provider identifier and/or the first application identifier to the session management functional entity, and the first application identifier is used to determine the first ECS Provider ID.
The method according to claim 13, wherein the first ECS provider identification is obtained according to one or more of the following information:

The application program installed in the terminal device, and the usage of the application program by the terminal device.
The method according to claim 13 or 14, wherein the access and mobility management functional entity obtains the terminal device-specific first ECS provider identifier and/or the terminal device-specific first application identifier ,include:

The access and mobility management functional entity receives the terminal device-specific first ECS provider identifier or the terminal device-specific first application identifier from the terminal device.
The method according to claim 13 or 14, wherein the access and mobility management functional entity obtains the first ECS provider identifier specific to the terminal equipment, comprising:

The access and mobility management functional entity sends a first request message to the network data analysis functional entity, where the first request message is used to obtain the ECS provider identifier specific to the terminal device;

The access and mobility management functional entity receives the terminal device-specific identifier of the first ECS provider from the network data analysis functional entity.
The method according to claim 13 or 14, wherein the access and mobility management functional entity acquires the first ECS provider identifier specific to the terminal device, comprising:

The access and mobility management functional entity obtains the terminal device-specific identifier of the first ECS provider from the application functional entity.
A communication method, characterized in that, comprising:

The network data analysis functional entity obtains the first ECS provider identifier specific to the terminal device;

The network data analysis function entity sends the first ECS provider identifier to a session management function entity or an access and mobility management function entity.
The method according to claim 18, wherein before the network data analysis functional entity sends the first ECS provider identifier to the session management functional entity, the method further comprises:

The network data analysis function entity receives a first request message from the session management function entity, where the first request message is used to request the ECS provider identifier specific to the terminal device.
The method according to claim 18, wherein before the network data analysis functional entity sends the first ECS provider identifier to the access and mobility management functional entity, the method further comprises:

The network data analysis function entity receives a first request message from the access and mobility management function entity, where the first request message is used to obtain the terminal device-specific ECS provider identifier.
The method according to any one of claims 18-20, wherein the network data analysis functional entity acquires the first ECS provider identifier specific to the terminal device, comprising:

The network data analysis functional entity requests one or more application functional entities to subscribe to the usage of the application program by the terminal device;

The network data analysis functional entity receives the application usage information of the terminal device from the one or more application functional entities;

The network data analysis function entity determines the first ECS provider identifier specific to the terminal device according to the use of the application program by the terminal device.
The method according to any one of claims 18-21, characterized in that, after the network data analysis functional entity obtains the first ECS provider identifier specific to the terminal device, the method further includes:

The network data analysis functional entity determines a fourth ECS provider identifier updated for the first ECS provider identifier according to the change of the application program usage of the terminal device received from one or more application functional entities ;

The network data analysis function entity sends the fourth ECS provider identifier to the session management function entity or the access and mobility management function entity.
A communication method, characterized in that, comprising:

The application function entity determines the first ECS provider identifier specific to the terminal device according to the use of the application program by the terminal device;

The application function entity sends the first ECS provider identifier to the access and mobility management function entity or the session management function entity.
The method according to claim 23, wherein after the application functional entity sends the first ECS provider identifier to the access and mobility management functional entity or the session management functional entity, the method further comprises:

The application function entity sends a fourth ECS provider identifier updated with respect to the first ECS provider identifier to the access and mobility management function entity or the session management function entity.
A communication device, characterized in that the communication device is a session management functional entity or a chip or circuit therein, and the communication device includes:

A processing unit, configured to obtain a terminal device specific first edge configuration server ECS provider identifier;

a transceiver unit, configured to send first ECS configuration information to the terminal device;

Wherein, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS corresponds to the first ECS provider identifier.
The communication device according to claim 25, wherein the processing unit is specifically configured to receive information from a terminal device, an access and mobility management functional entity, a network data analysis functional entity, or an application functional entity through the transceiver unit. The ID of the first ECS provider.
The communication device according to claim 25, wherein the processing unit is specifically used for:

receiving the first application identifier specific to the terminal device from the terminal device or the access and mobility management functional entity through the transceiving unit;

Obtain the first ECS provider identifier corresponding to the first application identifier.
The communication device according to claim 27, wherein the processing unit is further specifically configured to:

Obtain the correspondence between the application ID and the ECS provider ID;

Determine the first ECS provider identifier corresponding to the first application identifier according to the correspondence.
The communication device according to any one of claims 25-27, wherein the first ECS provider identifier is one or more ECS provider identifiers;

The transceiving unit is further configured to: when the second ECS corresponding to the second ECS provider identifier changes and the second ECS provider identifier belongs to the first ECS provider identifier, send the The second ECS provider identifier and the changed address of the second ECS.
The communication device according to any one of claims 25-29, wherein the transceiver unit is further configured to receive a first message from the terminal device, and the first message is used to instruct to update the terminal A device-specific first ECS provider identifier or the terminal device-specific first application identifier;

The processing unit is further configured to update the first ECS provider ID according to the first message to obtain a third ECS provider ID specific to the terminal device;

The transceiver unit is further configured to send third ECS configuration information to the terminal device, the third ECS configuration information includes a third ECS provider identifier and a third ECS address, and the third ECS is related to the third ECS Corresponding to the ECS provider ID.
The communication device according to any one of claims 25-26, 29, wherein the processing unit is specifically configured to: send a first request message to the network data analysis functional entity through the transceiver unit, the second A request message is used to acquire the terminal device-specific ECS provider identifier; and receive the terminal device-specific first ECS provider identifier from the network data analysis function entity through the transceiving unit.
A communication device, characterized in that the communication device is a terminal device or a chip or circuit therein, and the communication device includes:

A transceiver unit, configured to receive first ECS configuration information from a session management function entity, where the first ECS configuration information includes a first ECS provider identifier specific to the communication device and an address of the first ECS, and the first ECS Corresponding to the first ECS provider identifier;

A processing unit, configured to determine an ECS used for edge-enabled server EES discovery according to the first ECS configuration information.
The communication device according to claim 32, wherein the transceiver unit is further configured to send the first ECS provider identifier and/or the first ECS provider identifier to a session management functional entity or an access and mobility management functional entity. The first application identifier specific to the communication device, where the first application identifier is used to determine the first ECS provider identifier specific to the communication device.
The communication device according to claim 33, wherein the processing unit is further configured to determine the A first ECS provider identifier specific to the communication device and/or a first application identifier specific to the communication device.
The communication device according to any one of claims 32-34, wherein the first ECS provider identifier is one or more ECS provider identifiers;

The transceiving unit is further configured to receive a second ECS provider ID from the session management function entity and a changed second ECS address, the second ECS provider ID belongs to the first ECS provider ID, The second ECS corresponding to the second ECS provider identifier changes.
The communication device according to any one of claims 32-35, wherein the transceiver unit is further configured to:

sending a first message to the session management function entity, where the first message is used to indicate to update the communication device-specific first ECS provider identifier or the communication device-specific first application identifier;

receiving third ECS configuration information from the session management function entity, where the third ECS configuration information includes a third ECS provider identifier and an address of a third ECS, and the third ECS provider identifier is for the communication device The specific first ECS provider ID is updated, and the third ECS corresponds to the third ECS provider ID.
A communication device, characterized in that the communication device is an access and mobility management functional entity or a chip and a circuit therein, and the communication device includes:

a processing unit, configured to obtain a terminal device-specific first ECS provider identifier and/or a terminal device-specific first application identifier;

A transceiving unit, configured to send the first ECS provider identifier and/or the first application identifier to the session management function entity, where the first application identifier is used to determine the first ECS provider identifier.
The communication device according to claim 37, wherein the first ECS provider identifier is obtained according to one or more of the following information:

The application program installed in the terminal device, and the usage of the application program by the terminal device.
The communication device according to claim 37 or 38, wherein the processing unit is specifically configured to receive the terminal device-specific first ECS provider identifier or the terminal device-specific ECS provider identifier from the terminal device through the transceiver unit. The first application ID for .
The communication device according to claim 37 or 38, wherein the processing unit is specifically used for:

Sending a first request message to a network data analysis functional entity through the transceiver unit, where the first request message is used to obtain the ECS provider identifier specific to the terminal device;

The first ECS provider identifier specific to the terminal device is received from the network data analysis function entity by the transceiving unit.
The communication device according to claim 37 or 38, wherein the processing unit is specifically used for:

Obtain the first ECS provider identifier specific to the terminal device from the application function entity.
A communication device, characterized in that the communication device is a network data analysis functional entity or a chip or circuit therein, and the communication device includes:

a processing unit, configured to obtain a first ECS provider identifier specific to the terminal device;

A transceiver unit, configured to send the first ECS provider identifier to a session management function entity or an access and mobility management function entity.
The communication device according to claim 42, wherein the transceiver unit is further configured to receive a first request message from a session management function entity, and the first request message is used to request the terminal device-specific ECS Provider ID.
The communication device according to claim 42, wherein the transceiver unit is further configured to receive a first request message from an access and mobility management functional entity, and the first request message is used to acquire the terminal Device-specific ECS provider ID.
The communication device according to any one of claims 42-44, wherein the processing unit is specifically configured to:

requesting one or more application function entities to subscribe to the usage of the application program by the terminal device through the transceiver unit;

receiving from the one or more application function entities the use of the application program by the terminal device through the transceiver unit;

Determine the first ECS provider identifier specific to the terminal device according to the use of the application program by the terminal device.
The communication device according to any one of claims 42-45, wherein the processing unit is further configured to: Change, determining a fourth ECS provider ID updated for the first ECS provider ID;

The transceiving unit is further configured to send the fourth ECS provider identifier to the session management functional entity or the access and mobility management functional entity.
A communication device, characterized in that the communication device is an application function entity or a chip or a circuit therein, and the communication device includes:

A processing unit, configured to determine the first ECS provider identifier specific to the terminal device according to the usage of the application program by the terminal device;

A transceiving unit, configured to send the first ECS provider identifier to an access and mobility management functional entity or a session management functional entity.
The communication device according to claim 47, wherein the transceiver unit is further configured to send an update to the first ECS provider identity to the access and mobility management functional entity or the session management functional entity The ID of the fourth ECS provider.
A communication device, characterized by comprising a processor configured to execute computer program instructions stored in a memory, so that the communication device executes the method according to any one of claims 1-24.
The communication device according to claim 49, wherein the communication device is a chip or a circuit.
A system, characterized by comprising one or more of the communication devices according to claims 25-50.
A computer-readable storage medium, characterized in that, the computer-readable storage medium stores program instructions, and when the program instructions are run on the computer, the computer executes any one of claims 1-24. method described in the item.
A computer program product comprising program instructions, characterized in that, when the program instructions are run on a computer, the computer is made to execute the method according to any one of claims 1-24.
A communication method, characterized in that, comprising:

The session management function entity obtains the specific first edge configuration server ECS provider identifier of the terminal device;

The session management function entity sends first ECS configuration information to the terminal device;

The terminal device receives the first ECS configuration information;

Wherein, the first ECS configuration information includes the first ECS provider identifier and the address of the first ECS, and the first ECS corresponds to the first ECS provider identifier.
A communication method, characterized in that, comprising:

The access and mobility management functional entity obtains the terminal device-specific first ECS provider identifier and/or the terminal device-specific first application identifier;

The access and mobility management functional entity sends the first ECS provider identifier and/or the first application identifier to the session management functional entity, and the first application identifier is used to determine the first ECS provider identification;

The session management function entity receives the first ECS provider identifier and/or the first application identifier.
A communication method, characterized in that, comprising:

The network data analysis functional entity obtains the first ECS provider identifier specific to the terminal device;

The network data analysis function entity sends the first ECS provider identifier to a session management function entity or an access and mobility management function entity;

The session management function entity or the access and mobility management function entity receives the first ECS provider identifier.
A communication method, characterized in that, comprising:

The application function entity determines the first ECS provider identifier specific to the terminal device according to the use of the application program by the terminal device;

The application function entity sends the first ECS provider identifier to the access and mobility management function entity or the session management function entity;

The access and mobility management functional entity or the session management functional entity receives the first ECS provider identifier.