CN117812140A

CN117812140A - Method and device for acquiring terminal information

Info

Publication number: CN117812140A
Application number: CN202211214232.8A
Authority: CN
Inventors: 陈泽昊; 王亚鑫; 李永翠; 倪慧
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-09-30
Filing date: 2022-09-30
Publication date: 2024-04-02
Also published as: WO2024067547A1

Abstract

The embodiment of the application provides a method and a device for acquiring terminal information. The method comprises the following steps: the method comprises the steps that a first Vertical Application Layer Server (VALS) receives a first message from a first network element, wherein the first message comprises SEAL server information acquired by the first network element, and the SEAL server information is used for determining a first SEAL server; and the first VALS requests the first SEAL server to obtain the related information of the first terminal. The scheme provided by the application can enable the VALS to acquire the related information of the target terminal in the scene of edge deployment of the SEAL server.

Description

Method and device for acquiring terminal information

Technical Field

The embodiment of the application relates to the technical field of communication, and more particularly relates to a method and a device for acquiring terminal information.

Background

The SEAL (service enabler architecture layer, service enabling architecture layer) may provide services for vertical traffic (vertical application). When the SEAL servers are deployed in a centralized manner, that is, only one SEAL server is visible to the SEAL client and the vertical application layer server (vertical application layerserver, VALS), the SEAL client and the VALS can acquire the address of the SEAL server through self configuration or (domain name system, DNS) query and the like, so that when a certain VALS needs to acquire the relevant information (such as the location information, the group management information and the like of a certain terminal), the SEAL server can be called, and the SEAL server can acquire the relevant information of the terminal through the SEAL client.

For the scenario of edge deployment of SEAL servers, different SEAL servers may be deployed in different edge data networks (edge data network, EDNs), and SEAL clients of different terminals may register with different SEAL servers, so in this scenario the SEAL client or the val may not be able to obtain relevant information of a specific terminal according to the above method.

Disclosure of Invention

The embodiment of the application provides a method and a device for acquiring terminal information, which can enable related network elements to acquire related information of a target terminal in a scene of edge deployment of a SEAL server.

In a first aspect, a method for acquiring terminal information is provided. The method may be performed by the first VALS, or may be performed by a component (e.g., a chip or a system-on-chip, etc.) disposed in the first VALS, which is not limited in this application. The method comprises the following steps: the first VALS receives a first message from a first network element, wherein the first message comprises SEAL server information, and the SEAL server information is used for determining a first SEAL server; the first VALS requests the related information of the first terminal from the first SEAL server; the first vans receives related information of a first terminal from a first SEAL server.

Based on the above scheme, when the first val needs to acquire the related information of the first terminal, it can be determined from which SEAL server the related information of the first terminal can be requested, so that the determined first SEAL server is requested for the related information of the first terminal. The problem that the first VALS can not acquire the related information of the first terminal when the related information of the first terminal can not be acquired from which SEAL server can be requested is avoided.

With reference to the first aspect, in certain implementations of the first aspect, the first message further includes identification information of the first terminal.

For example, the first terminal may be a specific terminal or a terminal logged in by a specific user account, so the identification information of the first terminal may be an identification of a specific terminal or an identification of a user, for example, an identification of a specific user account, which is not limited in this application.

Based on the above scheme, the first VALS can determine, through the identification information, which terminal or user related information the first SEAL server can obtain.

With reference to the first aspect, in certain implementation manners of the first aspect, the first message further includes first indication information, where the first indication information indicates that the related information of the first terminal can be obtained from the first SEAL server.

Based on the above scheme, the first VALS can more clearly know the meaning indicated by the SEAL server information in the first message or the first message, so that the function of determining the SEAL server information in the first message by internal logic is not needed, the complexity of implementing the first VALS is reduced, or the internal logic of the first terminal is not provided with the function of sensing the meaning indicated by the SEAL server information in the first message or the first message, the sense indicated by the SEAL server information in the first message is required to be triggered by the first indication information, or different indicated meanings appear in the first message or the SEAL server information in the first message along with the evolution and development of a communication system, or can be understood as different indicated meanings, and at this time, the first indication information can limit the meaning indicated by the SEAL server information in the first message or the first message.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: the first vans sends a first request message to the first network element, the first request message being for requesting SEAL server information.

Based on the above scheme, when the first vans needs to acquire the related information of the first terminal or the user, the first vans requests the SEAL server information from the first network element, that is, the first vans acquires the SEAL server information as required, so as to avoid invalid transmission of information between the first network element and the first vans.

With reference to the first aspect, in certain implementations of the first aspect, the first request message includes at least one of: identification information of the first terminal; or second indication information for requesting SEAL server information.

With reference to the first aspect, in certain implementation manners of the first aspect, before the first sals sends the first request message to the first network element, the method further includes: the first VALS receives a second request message from a second network element, wherein the second request message is used for requesting related information of the first terminal, and the second network element is a second VALS, a SEAL client or a second terminal.

Based on the above scheme, when the second network element has a requirement of acquiring the related information of the first terminal, the related information of the first terminal is requested to the first VALS, and the first VALS is triggered to acquire the SEAL server information, namely, the first VALS acquires the SEAL server information as required, so that invalid transmission of the information between the first network element and the first VALS can be avoided.

With reference to the first aspect, in certain implementation manners of the first aspect, the related information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

Based on the above-mentioned scheme, when the related information of the first terminal is location information, the first SEAL server is a SEAL server that can process the location information, for example, a location management server; when the related information of the first terminal is group management information, the first SEAL server is a SEAL server which can process the group management information, such as a group management server; when the related information is configuration management information, the first SEAL server is a SEAL server which can process the configuration management information, for example, a configuration management server; when the related information of the first terminal is identity management information, the first SEAL server is a SEAL server which can process the identity management information, such as an identity management server; when the related information of the first terminal is key management information, the first SEAL server is a SEAL server which can process the key management information, for example, a key management server; when the related information of the first terminal is network resource management information, the first SEAL server is a SEAL server that can process the network resource management information, for example, a network resource management server.

With reference to the first aspect, in some implementations of the first aspect, the first network element is a vertical application layer client, VALC, or an edge enabled server EES, and when the first network element is a VALC, the first terminal is associated with the VALC.

Based on the above scheme, when the first network element is the VALC, since the VALC and the VALS are corresponding clients and servers, the VALS requests information from the VALC more directly, the logic is simpler, and in addition, the request and response speed of sending the SEAL server information through the application layer message is faster. When the first network element is EES, because the VALS is managed by EES as EAS in the EC architecture, when the VALS needs information crossing the EDN, the information is requested to EES and processed uniformly by EES, that is, EES and EEC are respectively used as centralized management points of server side and client side, so that the existing assumption of the architecture is more satisfied. In addition, the interaction of the data stream of the SEAL server information is suitably implemented by the interaction of the edge enabled layer EELs, which requires an interface between EES and EECs, and the logic of VAL, i.e. the logic between the server providing the service and the client, can be simplified, and the traffic data and the information stream of the enabled layer are decoupled.

With reference to the first aspect, in certain implementations of the first aspect, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

Illustratively, address information such as an internet protocol, IP, address, media access control, MAC, address, uniform resource locator, URL, or uniform resource identifier, URI; domain name information such as full domain name FQDN; the identification information comprises an internal identification and an external identification, such as a general public subscription identifier GPSI or a subscriber permanent identifier SUPI.

In a second aspect, a method for acquiring terminal information is provided. The method may be performed by the first network element, or may be performed by a component (such as a chip or a chip system) configured in the first network element, which is not limited in this application. The method comprises the following steps: the method comprises the steps that a first network element obtains SEAL server information, the SEAL server information is used for determining a first SEAL server, and the first SEAL server is used for obtaining relevant information of a first terminal; the first network element sends a first message to the first VALS, the first message including SEAL server information.

Based on the above scheme, the first network element can determine which SEAL server can request to obtain the related information of the first terminal and indicate the related information to the first val, so that the first val can request the related information of the first terminal from the first SEAL server indicated by the first network element, and the problem that the first val can not request the related information of the first terminal from a certain SEAL server when the first val does not know which SEAL server can request to obtain the related information of the first terminal is avoided.

With reference to the second aspect, in certain implementations of the second aspect, the first message further includes identification information of the first terminal.

With reference to the second aspect, in certain implementations of the second aspect, the first message further includes first indication information, where the first indication information indicates that the related information of the first terminal can be obtained from the first SEAL server.

Based on the above scheme, the first VALS can more clearly know the meaning indicated by the SEAL server information in the first message or the first message, so that the first VALS can determine the function of the SEAL server information in the first message without using internal logic, thereby reducing the complexity of implementing the first VALS, or the internal logic of the first terminal does not have the function of sensing the meaning indicated by the SEAL server information in the first message or the first message, and needs to trigger to sense the meaning indicated by the SEAL server information in the first message or the first message through the first indication information, or further, as the communication system evolves and develops, the SEAL server information in the first message or the first message has different indicated meanings or can be understood as different indicated meanings, and at this time, the first indication information can limit the meaning indicated by the SEAL server information in the first message or the first message.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the first network element receives first request information from a first VALS, the first request information being for requesting SEAL server information.

With reference to the second aspect, in certain implementations of the second aspect, the first request message includes at least one of: identification information of the first terminal; or second indication information for requesting SEAL server information.

With reference to the second aspect, in certain implementations of the second aspect, the relevant information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

Based on the above scheme, when the related information is location information, the first SEAL server is a SEAL server that can process the location information, for example, a location management server; when the related information is group management information, the first SEAL server is a SEAL server which can process the group management information, such as a group management server; when the related information is configuration management information, the first SEAL server is a SEAL server which can process the configuration management information, for example, a configuration management server; when the related information is identity management information, the first SEAL server is a SEAL server which can process the identity management information, for example, an identity management server; when the related information is key management information, the first SEAL server is a SEAL server capable of processing the key management information, for example, a key management server; when the related information is network resource management information, the first SEAL server is a SEAL server that can process the network resource management information, for example, a network resource management server.

With reference to the second aspect, in some implementations of the second aspect, the first network element is a vertical application layer client VALC or an edge enabled server EES.

Based on the above scheme, when the first network element is the VALC, since the VALC and the VALS are corresponding clients and servers, the VALS requests information from the VALC more directly, the logic is simpler, and in addition, the request and response speed of sending the SEAL server information through the application layer message is faster. When the first network element is EES, because the VALS is managed by EES as EAS in the EC architecture, when the VALS needs information crossing the EDN, the information is requested to EES and processed uniformly by EES, that is, EES and EEC are respectively used as centralized management points of server side and client side, so that the existing assumption of the architecture is more satisfied. In addition, the interaction of the data stream of the SEAL server information is suitable for being realized by the interaction of the EELs, which requires an interface between the EES and the EECs, and the logic of the VAL, that is, the logic between the server providing the service and the client can be simplified, and the information stream of the service data and the enabling layer can be decoupled.

With reference to the second aspect, in some implementations of the second aspect, the first network element is a VALC, where the VALC is associated with the first terminal, and the first network element obtains SEAL server information, including: the VALC receives SEAL server information from a SEAL client or EEC.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the VALC requests the SEAL server information from the SEAL client or edge enabled client EEC.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the VALC acquires third indication information from the SEAL client or EEC, wherein the third indication information indicates the first network element to send the SEAL server information to the first VALS.

With reference to the second aspect, in some implementations of the second aspect, the first network element is an EES, and the first network element obtains SEAL server information, including: the EES determines the SEAL server information according to the association relationship of the first val, the first SEAL server and the first terminal.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the EES determines the association.

With reference to the second aspect, in certain implementations of the second aspect, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

In a third aspect, a method for acquiring terminal information is provided. The method may be performed by the SEAL client or may be performed by a component (e.g., a chip or a system-on-chip, etc.) configured in the SEAL client, which is not limited in this application. The method comprises the following steps: the method comprises the steps that a SEAL client acquires SEAL server information, wherein the SEAL server information is used for determining a first SEAL server, and the first SEAL server is used for acquiring related information of a first terminal; the SEAL client sends SEAL server information to the VALC associated with the first terminal.

Based on the above scheme, the SEAL client can determine from which SEAL server the related information of the first terminal can be requested and inform the VALC, so that the VALC can indicate the determined SEAL server information to the first VALS, and the first VALS can request the related information of the first terminal from the first SEAL server indicated by the VALC. The problem that the first VALS cannot request the related information of the first terminal from a certain SEAL server when the first VALS does not know from which SEAL server the related information of the first terminal can be requested is avoided.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the SEAL client receives a SEAL server request message from the VALC for requesting SEAL server information.

Based on the above scheme, the SEAL client can determine which SEAL server can request to obtain the related information of the first terminal, and indicates the obtained SEAL server information to the VALC when the VALC has a demand, so that invalid transmission of information between the SEAL client and the VALC can be avoided.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the SEAL client sends third indication information to the VALC, the third indication information instructs the VALC to send the SEAL server information to the first VALS.

With reference to the third aspect, in certain implementations of the third aspect, the relevant information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

With reference to the third aspect, in certain implementations of the third aspect, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

In a fourth aspect, a method for acquiring terminal information is provided. The method may be performed by the EEC or may be performed by a component (e.g., a chip or a system-on-chip, etc.) disposed in the EEC, which is not limited in this application. The method comprises the following steps: the EEC acquires SEAL server information, wherein the SEAL server information is used for determining a first SEAL server, and the first SEAL server is used for acquiring related information of a first terminal; the EEC sends SEAL server information to the VALC associated with the first terminal.

Based on the above scheme, the EEC may determine from which SEAL server the related information of the first terminal may be requested and inform the VALC, so that the VALC may indicate the determined SEAL server information to the first VALS, so that the first VALS may request the related information of the first terminal from the first SEAL server indicated by the VALC. The problem that the first VALS cannot request the related information of the first terminal from a certain SEAL server when the first VALS does not know from which SEAL server the related information of the first terminal can be requested is avoided.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the EEC determines the association relationship between the first VALS and the first SEAL server; the EEC sends the association to the EES.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the EEC sends third indication information to the VALC, the third indication information indicating to the VALC to send the SEAL server information to the first VALS.

With reference to the fourth aspect, in some implementations of the fourth aspect, the related information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

In a fifth aspect, a method for acquiring terminal information is provided. The method may be performed by the first LMS, or may be performed by a component (e.g., a chip or a system-on-chip, etc.) disposed in the first LMS, which is not limited in this application. The method comprises the following steps: the method comprises the steps that a first Location Management Server (LMS) obtains location information of a first terminal; the first LMS transmits location information of the first terminal to the second LMS.

Based on the above scheme, the LMSs can interactively acquire the position information of the first terminal, so that, for example, when the first VALS has a requirement of acquiring the position information of the first terminal, the position information of the first terminal can be requested to any LMS, and if the requested LMS cannot acquire the position information of the first terminal, the position information of the first terminal can be requested to other LMSs, so that the complexity of acquiring the position information of the terminal can be reduced for the first VALS.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the first LMS sends location information of the first terminal to the second LMS, including: the first LMS transmits location information of the first terminal and identification information of the first terminal to the second LMS.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the method further includes: the first LMS receives a third request message from the second LMS for requesting location information of the first terminal.

Based on the above scheme, when the second LMS has a need to obtain the location information of the first terminal, and the second LMS cannot obtain the location information of the first terminal, for example, the second LMS cannot directly request the location information of the first terminal to the LMC associated with the first terminal, the location information of the first terminal may be requested to the first LMS.

With reference to the fifth aspect, in certain implementations of the fifth aspect, the third request message includes identification information of the first terminal.

With reference to the fifth aspect, in some implementations of the fifth aspect, before the first LMS obtains the location information of the first terminal, the method further includes: the first LMS transmits location management client configuration information to the second LMS, the location management client configuration information including identification information of the first terminal.

Based on the above scheme, the LMSs can know which LMS can acquire the position information of which terminal through the position management client configuration information, so that when the second LMS cannot acquire the position information of the first terminal, the second LMS can know that the position information of the first terminal can be acquired from the first LMS through the position management client configuration information, and request the position information of the first terminal to the first LMS, thereby avoiding the problem that the second LMS may not request the position information of the first terminal to any LMS.

In a sixth aspect, a method for acquiring terminal information is provided. The method may be performed by the second LMS or may be performed by a component (e.g., a chip or a system-on-chip, etc.) disposed in the second LMS, which is not limited in this application. The method comprises the following steps: the second LMS determines that the position information of the first terminal can be acquired from the first LMS; the second LMS sends a third request message to the first LMS, wherein the third request message is used for requesting the position information of the first terminal; the second LMS receives location information of the first terminal from the first LMS.

Based on the above scheme, in the case that the second LMS determines that the location information of the first terminal cannot be acquired by itself, it may be determined from which LMS the location information of the first terminal can be acquired, thereby requesting the determined first LMS for the location information of the first terminal. The problem that the second LMS can not request the position information of the first terminal when requesting the position information of any LMS is avoided.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the method further includes: the second LMS sends the position information of the first terminal to a third network element, and the third network element is a VALS or SEAL client.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the second LMS receives location information of the first terminal and identification information of the first terminal from the first LMS.

With reference to the sixth aspect, in certain implementations of the sixth aspect, the third request message includes identification information of the first terminal.

With reference to the sixth aspect, in certain implementations of the sixth aspect, before the second LMS sends the third request message to the first LMS, the method further includes: the second LMS receives position management client configuration information from the first LMS, wherein the position management client configuration information comprises identification information of the first terminal; the second LMS determines that the location information of the first terminal can be acquired from the first LMS according to the location management client configuration information.

Based on the above scheme, the LMSs can know which LMS can acquire the position information of which terminal through the position management client configuration information, so that when the second LMS cannot acquire the position information of the first terminal by itself, for example, when the second LMS cannot directly request the position information of the first terminal to the LMC associated with the first terminal, the second LMS can know that the position information of the first terminal can be acquired from the first LMS through the position management client configuration information and request the position information of the first terminal to the first LMS, thereby avoiding the problem that the second LMS may not request the position information of the first terminal to any LMS.

With reference to the sixth aspect, in certain implementations of the sixth aspect, before the second LMS sends the third request message to the first LMS, the method further includes: the second LMS receives a fourth request message from the third network element, the fourth request message requesting location information of the first terminal.

It will be appreciated that the solutions provided in the fifth aspect and the sixth aspect may also be used to obtain group management information, configuration management information, identity management information, key management information, network resource management information, etc. of the first terminal, which is not limited in this application.

For example, in any implementation manner provided in the fifth aspect and the sixth aspect, the location information may be replaced with group management information, where the first/second LMS is replaced with the first/second group management server; or the location information may be replaced with configuration management information, in which case the first/second LMS is replaced with the first/second configuration management server; or the location information may be replaced with the identity management information, in which case the first/second LMS is replaced with the first/second identity management server; or the location information may be replaced with key management information, in which case the first/second LMS is replaced with the first/second key management server; or the location information may be replaced with network resource management information, in which case the first/second LMS is replaced with the first/second network resource management server.

In a seventh aspect, a method for acquiring terminal information is provided. The method may be performed by the first VALS, or may be performed by a component (e.g., a chip or a system-on-chip, etc.) disposed in the first VALS, which is not limited in this application. The method comprises the following steps: the first VALS sends a second message to the first VALC, wherein the second message comprises SEAL server information, the SEAL server information is used for determining a first SEAL server, and the first VALC is associated with the first terminal; the first VALS requests the related information of the first terminal from the first SEAL server; the first vans receives related information of a first terminal from a first SEAL server.

Based on the above scheme, in the scenario that the first val has determined the first SEAL server, the first val may send SEAL server information to the first val, so that the first val forwards the SEAL server information to the first SEAL client, and therefore the SEAL server determined by the first val is the same as the SEAL server determined by the first SEAL client, and at this time, the first val may request to the first SEAL server to obtain relevant information of the first terminal.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the second message further includes: fourth indication information or fifth indication information, the fourth indication information indicates that the first VALC transmits the SEAL server information to the first SEAL client, and the fifth indication information indicates that the first SEAL client selects or uses the first SEAL server.

Based on the above scheme, the first VALC can more clearly know the meaning indicated by the second message or the SEAL server information in the second message, so that the function of determining the SEAL server information in the second message by internal logic is not needed, the complexity of implementing the first VALC is reduced, or the internal logic of the first VALC does not have the function of sensing the meaning indicated by the SEAL server information in the second message or the second message, the sense indicated by the SEAL server information in the second message is required to be triggered by fourth indication information or fifth indication information, and/or the subsequent action required to be executed by the SEAL server information in the second message or the second message is required to be determined by the fourth indication information or the fifth indication information; further alternatively, as the communication system evolves and evolves, the second message or the SEAL server information in the second message has a different meaning, or may be understood as a different meaning, where the fourth indication information or the fifth indication information may define the meaning of the second message or the SEAL server information in the second message, or define a subsequent action that the second message or the SEAL server information in the second message indicates that the first VALC needs to perform.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the second message further includes identification information of the first terminal.

Based on the above scheme, the first VALC can determine which terminal or user related information needs to be determined by the identification information.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the relevant information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

With reference to the seventh aspect, in certain implementations of the seventh aspect, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

In an eighth aspect, a method for acquiring terminal information is provided. The method may be performed by the first VALC or may be performed by a component (e.g., a chip or a system-on-chip, etc.) disposed in the first VALC, which is not limited in this application. The method comprises the following steps: the method comprises the steps that a first VALC obtains SEAL server information, the SEAL server information is used for determining a first SEAL server, the first SEAL server is used for obtaining relevant information of a first terminal, and the first terminal is associated with the first VALC; the first VALC sends the SEAL server information to the first SEAL client.

Based on the above scheme, the first VALC may send the SEAL server information to the first SEAL client, so that the first SEAL client selects or uses the first SEAL server, thereby achieving the technical effect that the first SEAL client and the first VALS use a common SEAL server, that is, the first SEAL server, and further the first VALS may obtain the related information of the first terminal through the first SEAL server.

With reference to the eighth aspect, in some implementations of the eighth aspect, the first VALC receives a second message from the first VALS, the second message including SEAL server information.

Based on the above scheme, in the scenario that the first val has determined the first SEAL server, the first val may send the SEAL server information to the first val, so that the first val forwards the SEAL server information to the first SEAL client, and therefore the SEAL server determined by the first val is the same as the SEAL server determined by the first SEAL client, and at this time, the first val may obtain relevant information of the first terminal through the first SEAL server.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the second message further includes: fourth indication information or fifth indication information, the fourth indication information indicates that the first VALC transmits the SEAL server information to the first SEAL client, and the fifth indication information indicates that the first SEAL client selects or uses the first SEAL server.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the second message further includes identification information of the first terminal.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the method further includes: the first VALC sends a sixth indication to the first SEAL client, the sixth indication indicating that the first SEAL client selects or uses the first SEAL server.

Based on the above scheme, the first SEAL client can more clearly know the meaning indicated by the SEAL server information sent by the first VALC, so that the function of determining the SEAL server information by internal logic is not needed, the complexity of implementing the first SEAL client is reduced, or the internal logic of the first SEAL client implements the function of not sensing the meaning indicated by the SEAL server information sent by the VALC, and the meaning indicated by the SEAL server information sent by the VALC is required to be triggered and sensed by the sixth indication information; further alternatively, as the communication system evolves and evolves, the SEAL server information sent by the first VALC may have different meaning of representation, or may be understood as different meaning of representation, and the sixth indication information may define the meaning of the SEAL server information representation sent by the VALC.

With reference to the eighth aspect, in some implementations of the eighth aspect, the relevant information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

With reference to the eighth aspect, in certain implementations of the eighth aspect, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

In a ninth aspect, a method for acquiring terminal information is provided. The method may be performed by the first SEAL client, or may be performed by a component (e.g., a chip or a system-on-chip, etc.) configured in the first SEAL client, which is not limited in this application. The method comprises the following steps: the first SEAL client receives SEAL server information from the first VALC, wherein the SEAL server information is used for determining a first SEAL server, the first SEAL server is used for acquiring related information of a first terminal, and the first terminal is associated with the first VALC; the first SEAL client side sends the related information of the first terminal to the first SEAL server.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the method further includes: the first SEAL client receives a sixth indication from the first VALC, the sixth indication indicating that the first SEAL client selects or uses the first SEAL server.

Based on the above scheme, the first SEAL client can more clearly know the meaning indicated by the SEAL server information sent by the first VALC, so that the function of determining the SEAL server information by internal logic is not needed, the complexity of implementing the first SEAL client is reduced, or the internal logic of the first SEAL client is implemented without the function of sensing the meaning indicated by the SEAL server information, and the meaning indicated by the SEAL server information sent by the first VALC is required to be triggered and sensed by the sixth indication information; further alternatively, as the communication system evolves and evolves, the SEAL server information sent by the first VALC may have different meaning of representation, or may be understood as different meaning of representation, and the sixth indication information may define the meaning of the SEAL server information representation sent by the VALC.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the relevant information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

With reference to the ninth aspect, in certain implementations of the ninth aspect, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

A tenth aspect provides a communication device for performing the method of any of the possible implementations of the first to ninth aspects. In particular, the apparatus may comprise means and/or modules, such as a processing unit and/or a communication unit, for performing the method in any of the possible implementations of the first to ninth aspects.

In an implementation form, the apparatus is a communication device (e.g. an execution body as exemplified in any of the above first to ninth aspects). When the apparatus is a communication device, the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation form, the apparatus is a chip, a chip system or a circuit for a communication device (e.g. the execution body as exemplified in any of the above-mentioned first to ninth aspects). When the apparatus is a chip, a system-on-chip or a circuit for a communication device, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin, or a related circuit, etc. on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.

An eleventh aspect provides a communication apparatus, the apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform a method according to any one of the possible implementations of the first to ninth aspects. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

In an implementation form, the apparatus is a communication device (e.g. an execution body as exemplified in any of the above first to ninth aspects).

In another implementation form, the apparatus is a chip, a chip system or a circuit for a communication device (e.g. the execution body as exemplified in any of the above-mentioned first to ninth aspects).

In a twelfth aspect, a processor is provided for performing the method provided in the above aspects.

The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as output and input of the processor, and may also be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited in this application.

In a thirteenth aspect, a computer readable storage medium is provided, the computer readable storage medium storing program code for execution by a user equipment, the program code comprising instructions for performing the method of any one of the possible implementations of the first to ninth aspects.

In a fourteenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the possible implementations of the first to ninth aspects described above.

In a fifteenth aspect, a communication system is provided that includes the aforementioned first VALS and a first network element.

Drawings

Fig. 1-3 are schematic diagrams of a functional model architecture according to an embodiment of the present application.

Fig. 4 is a schematic diagram of a SEAL online function model architecture for providing location management according to an embodiment of the present application.

Fig. 5 is a flow chart of a method for location reporting configuration provided in an embodiment of the present application.

Fig. 6-8 are flow diagrams of a method for reporting location information according to an embodiment of the present application.

Fig. 9 is a schematic diagram of a network architecture of edge computing according to an embodiment of the present application.

Fig. 10 is a flow chart of a method for EES discovery provided in an embodiment of the present application.

Fig. 11 is a flowchart of a method for discovering EAS according to an embodiment of the application.

Fig. 12 is a flow chart of another method for discovering EAS provided in an embodiment of the application.

Fig. 13 is a schematic diagram of a network architecture for deploying SEAL in an EDN according to an embodiment of the present application.

Fig. 14 to 25 are flowcharts of a method for acquiring terminal information according to an embodiment of the present application.

Fig. 26 is a schematic diagram of a communication device 2600 according to an embodiment of the present application.

Fig. 27 is a schematic diagram of a communication device 2700 provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

Wireless communication systems mentioned in embodiments of the present application include, but are not limited to: global system for mobile communications (global system of mobile communication, GSM), long term evolution (long term evolution, LTE) frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), LTE system, long term evolution-Advanced (LTE-a) system, next generation communication system (e.g., 6G communication system), a converged system of multiple access systems, or evolved system.

The technical solutions provided herein may also be applied to machine-type communication (machine type communication, MTC), inter-machine communication long term evolution technology (Long Term Evolution-machine, LTE-M), device-to-device (D2D) networks, machine-to-machine (machine to machine, M2M) networks, internet of things (internet of things, ioT) networks, or other networks. The IoT network may include, for example, an internet of vehicles. The communication modes in the internet of vehicles system are generally called as vehicle to other devices (V2X, X may represent anything), for example, the V2X may include: vehicle-to-vehicle (vehicle to vehicle, V2V) communication, vehicle-to-infrastructure (vehicle to infrastructure, V2I) communication, vehicle-to-pedestrian communication (vehicle to pedestrian, V2P) or vehicle-to-network (vehicle to network, V2N) communication, etc.

In the embodiment of the present application, the SEAL may provide services for vertical applications/services, or may provide services for general applications/services (for example, non-vertical applications/services), which is not limited in this application.

By way of example, SEAL services may include group management (group management), configuration management (configuration management), location management (location management), identity management (identity management), key management (key management), and network resource management (network resource management) services.

Fig. 1 is a schematic diagram of a functional model architecture according to an embodiment of the present application.

The SEAL models defined by the TS 23.434 standard include an on-line functional model (on-network functional model) and an off-line functional model (off-network functional model). FIG. 1 illustrates an online functional model, and FIG. 2 illustrates an offline functional model. Wherein the vertical application layer clients (vertical application layerclient, VALC) and clients and servers where the VALS provide vertical services are located at the VAL. The SEAL client and the SEAL server are clients and servers providing the SEAL service and are located in the SEAL.

For the online functional model, the standard may also support a model of interconnection between SEAL servers as shown in fig. 3.

It should be understood that fig. 1 to 3 are only examples, and do not limit the scope of protection of the present application.

The SEAL servers illustrated in the above figures may be deployed centrally, e.g., the SEAL servers may be deployed at higher or more centralized network locations, and the group management server (location management server, GMS) may be unique to a particular functional SEAL server (e.g., location management server (group management server, LMS), etc.) that is visible to the client side.

For example, a SEAL server performing location management, i.e. LMS is centrally deployed, only one LMS is visible to the corresponding location management client (location management client, LMC) or the VALS that can call the LMS (including the case where only one LMS is deployed, or multiple LMSs are deployed, the addresses of the multiple LMSs may be the same or different, which is not a limitation in the present application).

The SEAL servers providing other services (e.g., group management, configuration management, etc.) may be similar to LMS deployments and are not listed one by one.

Fig. 4 is a schematic diagram of a SEAL online function model architecture providing location management according to an embodiment of the present application.

In fig. 4, the SEAL service is exemplified by location management, the SEAL client is exemplified by LMC, and the SEAL server is exemplified by LMS. In the location management service process, the LMS serves as a centralized point, and may acquire location information of a corresponding terminal or user from the LMC to perform management of the location of each terminal or user, and when the vans needs to acquire location information of a certain terminal or user, may request the location of the terminal or user from the LMS.

A terminal in an embodiment of the present application may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment.

The terminals in embodiments of the present application may be mobile phones (mobile phones), tablet computers (pad), computers with wireless transceiving functionality, virtual Reality (VR) terminals, augmented reality (augmented reality, AR) terminals, wireless terminals in industrial control (industrial control), wireless terminals in unmanned aerial vehicle (self driving), wireless terminals in telemedicine (remote media), wireless terminals in smart grid (smart grid), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (smart city), wireless terminals in smart home (smart home), cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication functionality, computing devices or other processing devices connected to a wireless modem, vehicle devices, wearable devices, terminals in a 5G network or future networks, etc.

The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wearing and developing wearable devices by applying a wearable technology, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

Fig. 5 is a flow chart of a method for location reporting configuration provided in an embodiment of the present application. The method comprises the following steps:

501, the lmc sends a location report configuration request to the LMS, and correspondingly, the LMS receives the location report configuration request.

The location report configuration request includes, for example, an Identification (ID) of the user equipment, such as a VAL UE ID or a VAL user ID.

The user ID may be understood as the ID of a user account, which may be logged in at a different device. The UE ID may be understood as a terminal ID.

502, the lms sends a location reporting configuration response to the LMC, and the LMC receives the location reporting configuration response.

For example, the location report configuration response may include a condition for reporting location information by the LMC, a content related to the location information by the LMC, and a minimum time difference between two adjacent LMCs reporting location information.

The conditions under which the LMC reports location information, such as Service Area ID (SAI), change the evolved universal terrestrial radio access network cell global identity (evolved universal terrestrial radio access networkcell global identifier, ECGI). The relevant content of the LMC reporting location information, such as the format of the location information, may be a geographic location, such as SAI or ECGI.

503, the lmc end stores or updates the location reporting event trigger configuration.

Illustratively, after receiving the location report configuration response, the LMC saves the location report configuration in the location report configuration response, and subsequently triggers reporting of the location information according to the configuration.

Fig. 6 is a flowchart of a method for reporting location information according to an embodiment of the present application. The method comprises the following steps:

601, the lmc sends a location information report to the LMS, and the LMS receives the location information report, correspondingly.

For example, the LMC may report location information of a certain user equipment to the LMS when the location of the user equipment changes according to a location reporting configuration of the LMS response, such as a location reporting event trigger configuration stored in 503.

602, the lms updates the location information.

Illustratively, after receiving the location information report, the LMS locally updates the location information of the user equipment involved in the location information report.

Fig. 7 is a flowchart of another method for reporting location information according to an embodiment of the present application. The method comprises the following steps:

701, the lms determines to initiate a location request to a user.

Illustratively, the LMS requests location information of the user 1 or terminal 1 from the LMS according to a local configuration or a request from other network element/entity, e.g. the VALC, at which point the LMS determines to initiate a location request to the user 1 or terminal 1.

And 702, the LMS sends a position information request to the LMC, and correspondingly, the LMC receives the position information request.

Illustratively, the location information request includes an identification of the user 1 or terminal 1 for indicating that the location information of the user 1 or terminal 1 is requested.

703, the LMC informs the user and requests rights to share the location information.

Steps 704-705 are similar to steps 601-602 and are not described in detail herein.

Fig. 8 is a flow chart of another method for reporting location information according to an embodiment of the present application. The method comprises the following steps:

801, the lmc2 or the VALS sends a location report trigger message to the LMS, and the LMS receives the location report trigger message, correspondingly.

For example, the location report trigger message may include the self-identity of LMC2 or VALS, and the identity of the user equipment that is to request the location, such as location reporting trigger message.

802, the lms obtains location information from LMC 1.

Illustratively, the LMS may obtain location information from the LMC1 by the method provided in fig. 6 or 7.

803, the lms sends a location information report to LMC2 or vans, which the corresponding LMC2 or vans receives.

Illustratively, the location information report includes location information of the user equipment to be requested by LMC2 or vans.

It will be appreciated that fig. 5-8 provide a method for obtaining location information, and a method for obtaining information of other SEAL services is similar to the flow provided in fig. 5-8, and the location information may be replaced by information of other SEAL services, such as group management information, configuration management information, identity management information, key management information, network resource management information, and the like.

As shown in fig. 9, the network architecture may specifically include: an edge data network (edge data network, EDN), which may be a local data center, includes an edge enabled server (edge enabler server, EES) and a plurality of edge application servers (edge application server, EAS), each EDN having a particular service area. The EES may be a control network element or a management network element in a mobile edge computing (mobile edge computing, MEC) node (MEC may also be referred to as multi-access edge computing (multi acess edge computing)), and is responsible for managing various EAS deployed in the EDN, such as registration, domain name system (domain name system, DNS) resolution content routing, upper layer application registration management, wireless information interaction, and other basic functions. Furthermore, EES may invoke capability opening function network elements in the 3GPP network. The EES may also provide support functions required by EAS and EECs, such as providing EAS configuration information to the EECs, supporting EAS to register related information with the EES, supporting EAS discovery, application context migration, and the like. An edge configuration server (edge configuration server, ECS) may maintain information for each EDN, including service range and EES address, etc. The ECS may provide support functions required by the EECs to access the EES, including providing edge configuration information (e.g., uniform resource identifiers of the EES, service areas, etc.) to the EECs, supporting the EES to register related information with the ECS, etc. It should be noted that, in some standard protocols, such AS technical specifications (technical specification, TS) 23.501, TS23.502, etc., the EES, EAS, ECS, etc. may be regarded AS an application function (application function, AF) or an application server (application server, AS), which will not be described in detail below.

The UE may include: edge enabled clients (edge enabler client, EEC) and application clients (application client, AC), wherein the EEC provides necessary support for application clients on the terminal, the functionality of the EEC for example includes: EDN information is retrieved by EDGE-4, the UE registers with the EES, available EAS is retrieved, EAS availability changes, EAS migration notification to the EEC. EECs may provide the support functions required by the AC, including EAS discovery (e.g., retrieving available EAS, etc.), obtaining and providing configuration information for traffic exchange of the AC with EAS, etc.

The EDGE-8 reference point in fig. 9 supports interactions between the EDGE configuration server and the core network, which supports: (1) Accessing core network functions and application program interfaces (application programming interface, API) for retrieving network capability information; (2) The core network (e.g., SMF) is provided with a service delivery notification. EDGE-1: an interface between the EES and the EECs supporting registration/de-registration of the EECs in the EES; edge application server discovery in an edge data network. EDGE-2: an interface between the EES and the 3GPP core network for the EES to acquire 3GPP network capabilities. EDGE-3: an interface between the EES and EAS, supporting EES registration/de-registration of EAS, including availability information, service range information, address information, etc. of EAS; EES provides 3GPP network capability information (e.g., location information) to EAS. EDGE-4: the interface between the EEC and the ECS supports the ECS to provide/push configuration information to the EEC. EDGE-5: the interface between the AC and the EEC supports the AC to obtain access to the EAS information from the EEC. EDGE-6: the interface between the ECS and the EES supports the configuration of EES information on the ECS. EDGE-7: the interface between EAS and the 3GPP core network supports EAS acquisition 3GPP network capabilities. EDGE-8: and an interface between the ECS and the 3GPP core network supports the ECS to acquire the capability of the 3GPP network. EDGE-9: and the interfaces between different EESs in the same MEC node are crossed to support the application migration.

The ECS may be preconfigured at the terminal device, or the ECS may be preconfigured at the EEC, or the ECS may be preconfigured at the network side and issued to the EEC through the network.

The terminal device generally adopts the following scheme to acquire the edge service: the EEC sends a service provision request (service provisioning request) or a service subscription request (service provisioningsubscription request) to the preconfigured ECS to acquire address information of the EES, and after the UE or the EEC acquires the address information of the EES, the EEC sends an EAS discovery request (EAS discovery request) to the EES to acquire address information of the edge application server EAS, and further acquires the edge service.

Fig. 10 is a flow chart of a method for EES discovery provided in an embodiment of the present application. The method comprises the following steps:

1001, the eec sends a service provision request to the ECS.

The EEC may obtain the address of the ECS by local configuration, or network side notification, or the like, for example. After acquiring the address of the ECS, a service provision request may be sent to the ECS for discovery of the EES. The service provisioning request may include, for example, an EEC ID, location information of the EES sought, deployment of EAS, and a need for service continuity, etc.

At 1002, the ecs processes the request after receiving the service provision request.

Illustratively, after receiving the service provision request, the ECS determines EES satisfying the condition according to contents included in the service provision request.

1003, the ecs sends a service offer response to the EEC.

For example, one or more EES instances may be included in the service provisioning response.

After the EEC receives the service providing response, if the service providing response includes a plurality of EES instances, the EEC may select one of the EES to use. The EEC may notify the ECS of the selected EES instance after selecting one of them for use, or may not notify the ECS, which is not limited in this application.

It will be appreciated that the flow of information over the EDGE-5 interface between the AC (VALC, SEAL client in the architecture shown in fig. 1, and in particular, the VALC, LMC in the architecture shown in fig. 4, can both be considered AC) and EEC is defined in a standard manner. That is, before 1001, the AC may be executed to send a service provision request to the EEC, and correspondingly after 1003, the EEC may execute the EEC to return a service provision response to the AC. If the ECS returns a plurality of EES in step 1003, one EES may be selected by the EEC and may be transmitted to the AC in the manner described above, or the EEC may not perform the selection, and all or part (at least one) of the plurality of EES provided in step 1003 may be transmitted to the AC, and the EES selection may be performed by the AC. If the AC performs EES selection, the AC may or may not notify the EEC of the selected EES, which is not limiting in this application.

Fig. 11 is a flowchart of a method for discovering EAS according to an embodiment of the application. The method can be applied to EES discovery and comprises the following steps:

1101, the eec sends an EAS discovery request to the EES.

For example, after the EEC discovers the EES, the address of the EES may be determined and an EAS discovery request may be sent thereto for discovery of EAS. The EAS discovery request may include, for example, an EEC ID, the name of the EAS sought, location information of the EAS sought, a need for service continuity, etc.

1102, the ees performs an authorization check.

Illustratively, upon receipt of the EAS discovery request, the EES determines EAS that satisfies the condition based on content included in the EAS discovery request.

1103, the ees sends an EAS discovery response to the EEC.

For example, one or more EAS instances may be included in the EAS discovery response.

After the EEC receives the EAS discovery response, the EEC may select one of the EAS instances for use if the EAS discovery response includes multiple EAS instances. The EEC may or may not notify the EES of the selected EAS instance after selecting one of the uses, which is not limited in this application.

It will be appreciated that, similar to the flow shown in fig. 10, the flow of information over the EDGE-5 interface between the AC (the VALC, SEAL client in the architecture shown in fig. 1, and in particular, the VALC, LMC in the architecture shown in fig. 4, can each be considered an AC) and the EEC is defined in a standard manner. That is, before 1101, the AC may be executed to send an EAS discovery request to the EEC, and accordingly after 1103, the EEC may execute the EEC to return an EAS discovery response to the AC. If the EES returns multiple EAS in step 1103, one EAS may be selected by the EEC and sent to the AC in the manner previously described, or the EEC may not perform the selection, and all or part (more than one) of the multiple EAS provided in step 1103 may be sent to the AC, which performs the EAS selection. If the AC performs an EAS selection, the AC may or may not notify the EEC of the selected EAS, which is not limiting in this application.

It will be further appreciated that the EES discovery process illustrated in fig. 10 and the EAS discovery process illustrated in fig. 11 are both exemplary in terms of requests, and that EES discovery and EAS discovery may be performed in a subscription manner, not specifically illustrated herein.

Fig. 12 is a flow chart of another method for discovering EAS provided in an embodiment of the application. The method may be applied to an application context migration or application context relocation (application context relocation, ACR) scenario, comprising the steps of:

1201, an S-EAS (Source EAS) sends an EAS discovery request to the S-EES.

For example, a T-EAS (target EAS) discovery procedure may be initiated when the S-EAS perceives a change in the UE location transmission or other cause, resulting in the S-EAS no longer being the best EAS to service the UE. I.e., sends an EAS discovery request to the S-EES for discovery of T-EAS.

Or 1201', the S-EES determines that T-EAS needs to be discovered when it is determined to perform application context relocation.

1202, the S-EES obtains the T-EES from the ECS.

1203, after the S-EES acquires the T-EES, an EAS discovery request is sent to the T-EES.

1204, the T-EES sends an EAS discovery response to the S-EES.

Steps 1203-1204 are similar to steps 1101 and 1103 and will not be described again.

Optionally, if there is step 1201, the method further comprises:

1205, the S-EES forwards the EAS discovery response to the S-EAS.

The network architecture illustrated in fig. 13 may be understood as a combination of the network architecture illustrated in fig. 1 and the network architecture illustrated in fig. 9. Wherein the application specific client and the application enabling client may be regarded as the application client in fig. 9, or the VALC in fig. 1. The application specific server and the application enabling server may be considered as EAS in fig. 9 or VALS in fig. 1. The SEAL client may be considered an application client in fig. 9 and the SEAL server may be considered an EAS in fig. 9.

In this network architecture, one or more identically functioning SEAL servers (e.g., LMSs) may be deployed in one EDN.

Fig. 13 is merely an example, and does not limit the scope of the present application. For example, an application specific client, an application enabled client may be considered together as one network element, or as two different network elements. The application specific server and the application enabling server may be considered together as one network element or as two different network elements, which the present application does not limit. The names of the above network elements are also merely examples, and do not limit the protection scope of the present application.

It will be appreciated that in the architecture shown in fig. 13, an application client (e.g., an application specific client or application-enabled client) or a SEAL client may be considered an AC, initiating discovery of an application server (e.g., an application specific server or application-enabled server) or a SEAL server.

It will also be appreciated that VALS is analogous to S-EAS and that when it is desired to initiate the discovery of LMS (which may be analogous to T-EAS), the LMS may be discovered using a procedure similar to that provided in FIG. 12.

For the network architecture provided in fig. 13, different SEAL servers may be deployed by different EDNs, and multiple SEAL servers may also be deployed within the same EDN. When the SEAL client needs to invoke the SEAL server to perform registration or location reporting, or the SEAL server needs to be invoked by the SEAL server to acquire information (e.g., location information) of a certain UE/user, the information (e.g., location information) of the required UE/user may not be acquired because the SEAL server is not centrally deployed, and the SEAL server selected by the SEAL or the SEAL client is different from the SEAL server to which the SEAL client of the UE/user to be requested by the SEAL or the SEAL client is registered.

In addition, with respect to the network architecture provided in fig. 13, if the sals may determine the SEAL server, for example, the relationship between the sals and the SEAL server may be preconfigured, or the sals may determine the SEAL server by other means (e.g., according to a protocol, or a similar non-network flow, or according to an existing EAS discovery flow, such as the flow shown in fig. 10, 11, or 12), and at this time, the SEAL client does not find the SEAL server yet, so if the SEAL server found by the SEAL client and the SEAL server determined by the sals are inconsistent, the SEAL server determined by the sals cannot obtain the information of the UE/user requested by the sals. In view of this, the present application provides a method and apparatus for acquiring terminal information, which can acquire information of a specific terminal in a network architecture of edge deployment SEAL.

Fig. 14 is a flowchart of a method 1400 for obtaining terminal information according to an embodiment of the present application. The method 1400 illustrated in fig. 14 includes the steps of:

1410, the first network element obtains SEAL server information, where the SEAL server information is used to determine a first SEAL server, and the first SEAL server is used to obtain information related to the first terminal.

The first terminal may be understood as a terminal device that a certain specific terminal or a certain specific user account logs in or is associated with a certain specific user; or the first terminal can be understood as a terminal device which is logged in by a certain terminal or a certain user account or is associated with a certain user; or the first terminal may also be understood as a specific user or a specific user account, or a specific user account, which is not limited in this application.

The related information of the first terminal is at least one of the following information of the first terminal: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

Illustratively, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

For example, the identification information of the first SEAL server may be an ID of the first SEAL server (including an internal identification and/or an external identification, such as a general public subscription identifier (generic public subscription identifier, GPSI), a user permanent identifier (subscription permanent identifier, SUPI), etc. address information of the first SEAL server, such as an IP address, a MAC address, a uniform resource locator (uniform resource locator, URL), a uniform resource identifier (uniform resource identifier, URI), etc. domain name information of the first SEAL server, such as a full domain name (fully qualified domain name, FQDN), etc.

Alternatively, 1410 may be replaced with: the first network element acquires the SEAL server information, the SEAL server information is associated with a first SEAL server, and the first SEAL server is used for acquiring related information of the first terminal.

The SEAL server information is associated with the first SEAL server, which may be understood as the SEAL server information may be used to determine the first SEAL server, or the SEAL server information is related information of the first SEAL server. The related information of the first SEAL server is, for example, address information, domain name information, or identification information of the first SEAL server.

Alternatively, 1410 may be replaced with: the first network element acquires the related information of the first SEAL server.

1420, the first network element sends a first message to the first val, the first message comprising the SEAL server information. Correspondingly, the first VALS receives the first message.

Alternatively, 1420 may be replaced with: the first network element sends a first message to the first VALS, the first message including information about the first SEAL server. Correspondingly, the first VALS receives the first message.

Optionally, the first message includes identification information of the first terminal.

The identification information of the first terminal may be identification information of a specific terminal, or identification information of a terminal logged in by a specific user account, or identification information of a specific user account, which is not limited in this application, and the identification information of the first terminal, or the identification of the first terminal, which is related to the embodiment of the present application may be understood according to this.

For example, the identification information of the first terminal may be an ID including an internal identification and/or an external identification. For example, the identification information of the first terminal is GPSI, SUPI, etc., or a group identification of the first terminal. Alternatively, the identification information of the first terminal may be address information, such as an internet protocol (internet protocol, IP) address, a medium access control (media access control, MAC) address, or the like.

Optionally, the first message further includes first indication information, where the first indication information indicates that the related information of the first terminal can be acquired from the first SEAL server, or the first indication information indicates that the related information of the first terminal can be acquired from the first SEAL server when the first val needs to acquire the related information of the first terminal.

1430, the first VALS requests related information of the first terminal from the first SEAL server.

In one possible implementation manner, after the first SEAL server receives the request of the first val, the first SEAL server may acquire the related information of the first terminal from the first SEAL client.

It can be understood that, after the first SEAL server receives the request of the first val, the first SEAL server may further obtain the related information of the first terminal through other manners, which is not limited in this application. Step 1440 may be performed after the first SEAL server obtains information about the first terminal.

For example, if the related information of the first terminal is location information, the first SEAL server may be an LMS, and the first SEAL client is an LMC; if the related information of the first terminal is group management information, the first SEAL server may be a group management server (i.e. a SEAL server capable of performing group management), and the first SEAL client may be a SEAL client capable of acquiring the group management information; if the related information of the first terminal is configuration management information, the first SEAL server may be a configuration management server (i.e. a SEAL server capable of performing configuration management), and the first SEAL client may be a SEAL client capable of acquiring the configuration management information; if the related information of the first terminal is identity management information, the first SEAL server may be an identity management server (i.e. a SEAL server capable of performing identity management), and the first SEAL client may be a SEAL client capable of acquiring identity management information; if the related information of the first terminal is key management information, the first SEAL server may be a key management server (i.e. a SEAL server capable of performing key management), and the first SEAL client may be a SEAL client capable of acquiring the key management information; if the related information of the first terminal is network resource management information, the first SEAL server may be a network resource management server (i.e., a SEAL server that can perform network resource management), and the first SEAL client may be a SEAL client that can acquire network resource management information.

For example, when the related information of the first terminal is location information, that is, the first SEAL server is the first LMS, and the first SEAL client is the first LMC. After receiving the request of the first VALS, the first LMS may obtain the location information of the first terminal from the first LMC. Specifically, the first LMS may obtain the location information of the first terminal from the first LMC through the methods provided in fig. 5 to 8, which is not limited in the manner in which the first LMS obtains the location information of the first terminal.

When the related information of the first terminal is other information, the corresponding method for the first SEAL server to acquire other information from the first SEAL client may refer to the method for the first LMS to acquire the location information of the first terminal from the first LMC, which is not described herein.

It will be appreciated that the above list of first SEAL servers is merely exemplary, and the first SEAL server in the embodiments of the present application is not limited thereto. As the first SEAL server described in this embodiment, any server that can provide information about a certain terminal, for example, if the information about the first terminal is location information, can perform the operation performed by the first SEAL server in this embodiment, that is, the server that can provide information about the location of the first terminal is not limited to LMS, but is not limited to SEAL server, and the above list is a functional example and does not limit the scope of protection of the embodiments of the present application. Similarly, the examples of the SEAL server mentioned later are understood as such.

1440, the first SEAL server sends information about the first terminal to the first VALS. Correspondingly, the first VALS receives the related information of the first terminal.

It should be appreciated that steps 1430 and 1440 are an example of the first sals obtaining the required information about the first terminal from the first SEAL server, and in addition, the first sals may obtain the required information about the first terminal in other manners, for example, the first sals is configured locally or obtained from other network elements or entities, which is not limited in this application.

It is also understood that the acquiring of the related information of the first terminal may include other steps in addition to the steps 1430 and 1440. For example, steps 1430 and 1440 may be replaced by steps 801 and 803 in the flowchart shown in fig. 8, and the step 802 may be further included to implement relevant information of the first terminal required for the sals acquisition.

Optionally, prior to step 1410, the method 1400 further comprises:

the first vans sends a first request message to the first network element, the first request message being for requesting SEAL server information. Correspondingly, the first network element receives the first request message.

In one possible implementation, the first request message includes at least one of: identification information of the first terminal; or second indication information for requesting SEAL server information.

Optionally, prior to step 1410, the method 1400 further comprises:

the first vans receives a second request message from a second network element, where the second request message is used to request information about the first terminal, and the second network element is a second vans, a SEAL client, or a second terminal.

Illustratively, the first VALS receives a second request message from the second network element and sends the first request message to the first network element.

Illustratively, the first network element in steps 1410 and 1420 may be a VALC or EES.

In one possible implementation, the first network element is a VALC, and the VALC may obtain the SEAL server information from the SEAL client or EEC, that is, step 1410 may be replaced by:

the VALC receives SEAL server information from a SEAL client or EEC.

Optionally, before the VALC obtains the SEAL server information, the method 1400 further includes:

the VALC requests the SEAL server information from the SEAL client or EEC.

Optionally, the method 1400 further comprises:

the VALC receives a third indication from the SEAL client or EEC, the third indication indicating that the VALC transmits SEAL server information to the first VALS.

It will be appreciated that the SEAL server information and the third indication information may be carried in the same message or may be carried in different messages, which is not limited in this application.

When the first network element is a VALC, the VALC is associated with the first terminal.

When the first terminal is a certain terminal, a certain specific terminal, a certain user account or a terminal logged in by a certain specific user account, the association of the VALC with the first terminal can be understood as: the VALC is deployed at the first terminal or the first terminal has the VALC installed. When the first terminal is a user, a specific user, a user account or a specific user account, the association of the VALC with the first terminal may be understood as: the VALC is deployed on or installed on the terminal equipment used or logged in by the user or the user account.

It will be appreciated that association of a client (e.g., SEAL client, VALC, or EEC) with a terminal (e.g., first terminal or second terminal) is similar to that described above, and reference may be made to the above description, which will not be repeated.

In another possible implementation, the first network element is EES, that is, step 1410 may be replaced by:

the EES determines the SEAL server information according to the association relationship of the first val, the first SEAL server and the first terminal.

Optionally, before the EES determines the SEAL server information, the method 1400 further includes:

The EES determines an association of the first val, the first SEAL server, and the first terminal.

Based on the scheme provided by the method 1400, when the first val needs to acquire the related information of the first terminal, it may be determined from which SEAL server may request to obtain the related information of the first terminal, thereby requesting the determined first SEAL server for the related information of the first terminal. The problem that the first VALS can not acquire the related information of the first terminal when the related information of the first terminal can not be acquired from which SEAL server can be requested is avoided.

Fig. 15 is a flowchart of a method 1500 for obtaining location information of a terminal according to an embodiment of the present application. The method 1500 may be used to implement aspects of the method 1400 described above. In the method 1500, the first network element is exemplified by a VALC, the first SEAL client is exemplified by a first LMC, the first SEAL server is exemplified by a first LMS, and the related information of the first terminal is exemplified by the location information of the first terminal. The method 1500 includes the steps of:

1510, the valc sends a first message to the first VALS, the first message including information of the first LMS, the information of the first LMS being used to determine the first LMS.

The first terminal and the specific content of the first terminal identification information may be referred to in the description of the method 1400, and are not described herein. The VALC is associated with a first terminal.

Optionally, the first message includes first indication information indicating that the location information of the first terminal can be acquired from the first LMS.

Illustratively, the information of the first LMS includes address information, domain name information, or identification information of the first LMS.

After receiving the first message, the first vans requests location information of the first terminal from the first LMS 1520.

For example, after receiving the request of the first VALS, the first LMS may obtain location information of the first terminal from the first LMC. Specifically, the first LMS may obtain the location information of the first terminal from the first LMC through the methods provided in fig. 5 to 8, which is not limited in the manner in which the first LMS obtains the location information of the first terminal.

1530, the first LMS transmits location information of the first terminal to the first VALS. Correspondingly, the first VALS receives the location information of the first terminal. Steps 1520-1530 are similar to steps 1430-1440, and specific details are described with reference to steps 1430-1440, which are not repeated here.

Prior to step 1510, the VALC obtains information of the first LMS may be divided into the following cases:

case 1 (including steps 1501,1502 a):

1501, the valc initiates a VALS discovery procedure for discovering a first VALS.

It will be appreciated that the vans discovery procedure is similar to the EAS discovery procedure, and that, by way of example, a first vans may be discovered, i.e., treated as EAS, by the methods provided in fig. 10 and 11. The present application does not limit the method of discovering the first VALS. The first LMC initiates 1502 an LMS discovery procedure for discovering the first LMS.

It will be appreciated that the first LMC and EEC described above are associated with a first terminal, and that the LMS discovery procedure is similar to the EAS discovery procedure, and that the first LMS may be discovered, i.e., treated as EAS, by way of example, by the methods provided in fig. 10 and 11. The present application does not limit the method of finding the first LMS.

It will also be appreciated that steps 1501 and 1502 may involve the relevant flows of the ECS and EES during execution, see in particular the flows provided in fig. 10 and 11. Fig. 15 does not show the ECS and EES, and the flows involved in the ECS and EES.

It should be noted that, the execution of steps 1501 and 1502 may be independent of each other, and the execution timing is not necessarily in the order shown in the figure.

After the execution of step 1502 is completed, the first LMC and the first LMS may execute the flow shown in fig. 5 or other flows that may achieve the same technical effect.

It will be appreciated that the EES used in step 1501 and the EES used in step 1502 may be the same or different, and this application is not limited in this respect.

1502a, a first LMC sends information of a first LMS to a VALC.

It is understood that the information of the first LMS transmitted in step 1502a is information for identifying the first LMS found in step 1502.

Illustratively, the information of the first LMS may be an ID of the first LMS (including an internal identifier and/or an external identifier, such as GPSI, SUPI, etc.), or may be address information of the first LMS, such as an IP address, a MAC address, a URL, a URI, etc., or may be domain name information of the first LMS, such as FQDN.

Case 2 (including step 1501,1502,1503,1504,1505,1506):

steps 1501 and 1502, like steps 1501 and 1502 in case 1, can be referred to the above description, and are not repeated here.

1503, the first VALS determines that location information of the first terminal is required.

It is to be appreciated that step 1503 may be used as a triggering step of step 1504, and the first VALS may determine that the location information of the first terminal is needed based on its own requirements (e.g., requirements of an application layer), or a request from another network element or entity, or the first VALS determines that the location information of the first terminal is needed for other reasons, which is not limited in this application.

It will also be appreciated that steps 1501 and 1502 are not triggering steps of step 1503.

1504, the first VALS sends a first request message to the VALC.

For example, the first request message may include identification information of the first terminal; or the first request message includes identification information and second indication information of the first terminal, where the second indication information is used to request information of the first LMS corresponding to the first terminal. In one possible implementation, the second indication information is identification information of the first terminal.

In one possible implementation, the VALC may perform subsequent steps according to the second instruction information or according to internal logic, and embodiments of the present application are not limited to specific internal logic.

Illustratively, after receiving the first request message, the VALC includes identification information of the first terminal, determines from the internal logic that a subsequent step is to be performed (e.g., step 1505).

Illustratively, after receiving the first request message, the VALC includes identification information of the first terminal and second indication information, and determines that a subsequent step is to be performed based on the second indication information (e.g., step 1505).

1505, after receiving the first request message, the valc requests the information of the first LMS from the first LMC.

For example, the VALC may request the information of the first LMS by sending a request message, that is, the request message itself may implement a function of requesting the information of the first LMS, or the request message may carry second indication information, thereby implementing a function of requesting the information of the first LMS, which is not limited in this application.

1506, the first LMC sends information of the first LMS to the VALC in response to the request of the VALC, the information of the first LMS may determine the first LMS.

In addition to the above case 1 and case 2, the VALC may further obtain the information of the first LMS locally, for example, the VALC configures the information of the first LMS locally, which is not limited in the manner in which the VALC obtains the information of the first LMS.

Based on the scheme provided by the method 1500, when the first VALS needs to acquire the location information of the first terminal, it may be determined from which LMS may request the location information of the first terminal, thereby requesting the location information of the first terminal from the determined first LMS. The problem that the first VALS cannot acquire the position information of the first terminal when the first VALS does not know which LMS can request to acquire the position information of the first terminal, and therefore the first VALS requests to a certain LMS is avoided.

The flow provided by the method 1500 may implement a scenario in which the first vans corresponding to the first terminal requests location information of the first terminal, for LMS deployment across EDNs, or one EDN deploys multiple LMSs. The second vans (the second vans may be different from the service provided by the first vans), or the second LMC requesting the location information of the first terminal may be through the method shown in fig. 16.

Fig. 16 is a flowchart of another method 1600 for obtaining location information of a terminal according to an embodiment of the present application. The method 1600 may be used to implement aspects of the method 1400 described above. In the method 1600, the second network element takes the second vans or the second LMC as an example, and the related information of the first terminal takes the location information of the first terminal as an example. The method 1600 illustrated in fig. 16 includes the steps of:

1601, ees1 is registered.

For example, EES1 registers with EES2 or ECS. During the registration process, EES1 sends an identity of the first terminal to EES2 or ECS, indicating that itself serves the first terminal. I.e. EES1 indicates that it can provide LMS managing the location information of the first terminal itself, or EES1 indicates that it manages the VALS serving the first terminal itself.

It is understood that step 1501 may be performed as a preset condition of the method 1500, and not as a trigger condition for a subsequent step.

1602, the second VALS or the second LMC sends an EES discovery request to the ECS or EES 2.

Illustratively, assuming that the ECS is centrally deployed, EES2 is the EES with which the second VALS is registered, or EES2 is the EES that may serve the EEC of the second LMC, which is associated with the second terminal, which is different from the first terminal. The EES discovery request includes an identification of the first terminal, which is a terminal that the second VALS or the second LMC needs to request location information.

The EES discovery request may be understood as a service provision request (service provisioning request), and the EES discovery referred to in the embodiments of the present application may be understood as a service provision (service provisioning), such as the process provided in fig. 10.

1603, the ECS or EES2 returns to the second VALS or second LMC the EES serving the first terminal, EES1.

The EES serving the first terminal may be understood as: EES serving the EEC of the first terminal, or EES registered to the first vans serving the EEC of the first terminal, wherein the first vans is a vans that may call the first LMS to acquire location information of the first terminal, or may be described as a vans that may acquire the location information of the first terminal directly from the first LMS.

It is understood that the VALS serving the first terminal and available to obtain the location information of the first terminal may not be unique, and thus EES satisfying the condition may not be unique. In this case, returning any EES may be implemented as an effect of the first terminal service, or returning a plurality of EES, each of which may be implemented as an effect of the first terminal service, and then selecting one EES by the second VALS or the second LMC. Alternatively, the second VALS or the second LMC may determine EES1 by other means, which is not limited in this application.

Illustratively, the EES returned at step 1603 is EES1 to which the first VALS is registered.

It is appreciated that steps 1602-1603 may not be performed if the second vans or the second LMC may interact directly with EES1 (e.g., the second vans is registered with EES1, or the EEC of the second LMC may interact directly with EES 1), or the second vans or the second LMC has acquired or configured the address of EES1.

1604, the second vans or the second LMC sends an EAS discovery request to EES1.

Illustratively, the EAS discovery request includes an identification of the first terminal, wherein the identification of the first terminal is used to request a vans used by the first terminal.

For example, the EAS discovery request may include an identification of the second vans/second UE (UE corresponding to the second LMC). The identity of the first terminal may be included in the parameters of the EAS discovery request, i.e., parameters characterizing the nature of the sought EAS (EAS discovery filter), such that upon receipt of the EAS discovery request by EES1, it may be resolved from the data structure of the parameters that the first terminal uses, but not the second terminal uses. Or EES1 may determine in other ways that the VALS used by the first terminal needs to be acquired. The present application is not limited in this regard. For example, the EAS discovery request includes the indication information and the identification of the first terminal, such that upon receipt of the EAS discovery request by EES1, it may be determined that the vans used by the first terminal needs to be acquired.

It will be appreciated that if the EAS discovery request is sent by the second LMC, the second LMC needs to interact with EES1 through an EEC, which is not shown in fig. 16.

1605, EES1 sends an EAS discovery response to the second VALS or the second LMC.

Illustratively, the EAS discovery response includes first VALS information, such as an identification, domain name, or address of the first VALS, etc.

It will be appreciated that if the EAS discovery response is sent to the second LMC, EES1 needs to interact with the second LMC through the EEC, which is not shown in fig. 16.

1606, the second vans or the second LMC transmits a second request message to the first vans, the second request message being for requesting location information of the first terminal, the second request message including identification information of the first terminal.

1607, the first VALS obtains location information of the first terminal.

It can be appreciated that the first vans may acquire the relevant information of the first terminal through the method for acquiring the relevant information of the first terminal by using the first vans illustrated in the method 1500, which is not described herein.

1608, the first VALS transmits the location information of the first terminal to the second VALS or the second LMC. Correspondingly, the second vans or the second LMC receives the location information of the first terminal.

Based on the scheme provided by the method 1600, in a scenario where an LMS deploys across EDNs, or one EDN deploys multiple LMS, when the second vans or the second LMC needs to obtain the location information of the first terminal, the location information of the first terminal may be requested to the first vans, and the first vans may obtain, in combination with the method 1500, the location information of the first terminal from the first LMS.

Fig. 17 is a flowchart of a method 1700 for obtaining location information of a terminal according to an embodiment of the present application. The method 1700 may be used to implement the aspects of the method 1400 described above. In the method 1700, the first network element is exemplified by a VALC, the first SEAL client is exemplified by a first LMC, the first SEAL server is exemplified by a first LMS, and the related information of the first terminal is exemplified by the location information of the first terminal. The methods 1700 and 1500 differ in that the method 1700 is an example of the VALC actively pushing a first message to a first VALS and the method 1500 is an example of the VALC sending the first message to the first VALS after the first VALS requests the VALC. Wherein the VALC, the first LMC, and the EEC are all associated with the first terminal. The method 1700 includes the steps of:

steps 1710-1730, similar to steps 1510-1530, are described in detail with reference to steps 1510-1530, and are not repeated here.

The difference is that: the first message in step 1710 may further include first indication information indicating that the location information of the first terminal can be acquired from the first LMS, or the first indication information indicates that the location information of the first terminal can be acquired from the first LMS when the first VALS needs to acquire.

Or when the first indication information is not included in the first message, the first VALS may determine, according to the first message, that the first VALS may acquire the location information of the first terminal when the first VALS needs to acquire the location information of the first terminal. Prior to step 1710, the VALC obtains information of the first LMS may be divided into the following cases:

Case 1 (including steps 1701,1702 a):

step 1701 is similar to step 1501, and reference is made to the relevant description of step 1501, which is not repeated here.

Step 1702 is similar to step 1502 and reference is made to the relevant description of 1502, which is not repeated here.

1702a, the first LMC sends information of the first LMS to the VALC.

It is understood that the information of the first LMS transmitted in step 1702a is information for identifying the first LMS found in step 1702.

Optionally, the first LMC sends third indication information to the VALC, where the third indication information indicates the VALC to send the information of the first LMS to the first VALS.

The third indication information and the information of the first LMS may be carried in the same message, or may be carried in different messages, which is not limited in this application.

Case 2 (including step 1701,1702,1703,1704):

steps 1701-1702 are similar to steps 1501-1502, and reference is made to the relevant descriptions of 1501 and 1502, which are not repeated here.

1703, the eec determines the associated VALS and LMS.

Illustratively, following steps 1701 and 1702, the EEC may determine that the first VALS is associated with the first LMS, the EEC corresponding to the first terminal, e.g., the EEC is deployed on the first terminal.

The first vans and first LMS association may be understood as: the first vans may request location information of the first terminal from a first LMS associated with the first vans if the location information of the first terminal is required.

It is understood that before the EEC determines that the first VALS is associated with the first LMS, the EEC may determine the VALS selected by the VALC through step 1701 (i.e., the first VALS) or may determine the LMS selected by the first LMC through step 1702 (i.e., the first LMS).

Similar to the method provided in fig. 11, the EES may return a plurality of VALS, and the selection of the first VALS from the plurality of VALS may be performed by the EEC or AC or by the VALC. Likewise, the EES may return to the plurality of LMSs, and selecting the first LMS from the plurality of LMSs may be performed by the EEC or the AC or by the first LMC.

If the selection of LMS is performed by the first LMC and the selection of VALS is performed by the VALC, the EEC may not be able to determine the associated VALS and LMS. The EEC is therefore able to determine that the associated vars and LMS need to meet either:

1. the EES returns only one vans (i.e., the first vans) and the EES returns only one SEAL server (i.e., the first SEAL server).

It is understood that the EES return the vans includes the EES returning information about the first vans in an EAS discovery response message, such as the address of the first vans. The EAS discovery response message is merely an example, and EES may also return information regarding the first VALS via other messages, which embodiments of the present application do not limit.

It is also understood that the EES returning to the LMS includes the EES returning to the relevant information of the first LMS, such as the address of the first LMS, in an EAS discovery response message. The EAS discovery response message is merely an example, and EES may also return information regarding the first LMS via other messages, which embodiments of the present application do not limit.

It should be noted that, the EES return vans or LMS may be understood with reference to the above description, and will not be described in detail for brevity.

2. The EES returns a plurality of vans (including the first vans), the selection of the vans being performed by the EEC; and/or, the EES returns a plurality of LMSs (including the first LMS), the selection of the LMSs being performed by the EECs.

Illustratively, the EES returns a plurality of VALSs (including the first VALS), the EES returns one or more LMSs (including the first LMS), the selection of the VALS is performed by the EEC, and if the EES returns a plurality of LMSs, the selection of the LMSs is also performed by the EEC. Or alternatively

The EES returns one vans (i.e., the first vans), the EES returns a plurality of LMSs (including the first LMS), and the selection of LMSs is performed by the EEC.

3. The EES returns a plurality of varss (including the first VALS) and the selection of the VALS is performed by the VALC, but after the VALC performs the VALS selection, a notification message is sent to the EEC to declare the EEC's own selected VALS (i.e., the first VALS). The EES returns only one LMS (i.e., the first LMS).

Or the EES returns multiple varss (including the first VALS) and the selection of the VALS is performed by the VALC, but after the VALC performs the VALS selection, a notification message is sent to the EEC to declare the EEC's own selected VALS (i.e., the first VALS). The EES returns a plurality of LMSs (including the first LMS) and the selection of LMSs is performed by the EEC.

Or the EES returns multiple varss (including the first VALS) and the selection of the VALS is performed by the VALC, but after the VALC performs the VALS selection, a notification message is sent to the EEC to declare the EEC's own selected VALS (i.e., the first VALS). The EES returns a plurality of LMSs and the selection of LMSs is performed by the LMC, but after the LMC performs LMS selection, a notification message is sent to the EEC to declare the EEC's own selected LMS (i.e., the first LMS). Or alternatively

The EES returns only one VALS (i.e., the first VALS). The EES returns a plurality of LMSs and the selection of LMSs is performed by the LMC, but after the LMC performs LMS selection, a notification message is sent to the EEC to declare the EEC's own selected LMS (i.e., the first LMS).

Or the EES returns a plurality of VALS (including the first VALS) and the selection of VALS is performed by the EEC. The EES returns a plurality of LMSs and the selection of LMSs is performed by the LMC, but after the LMC performs LMS selection, a notification message is sent to the EEC to declare the EEC's own selected LMS (i.e., the first LMS).

It can be understood that the EEC is an internal network element of the terminal, so that the EEC may store only the association relationship between the VALS and the LMS when storing the association relationship, but when the EEC sends the association relationship to a network element outside the terminal, the EEC needs to send the association relationship between the VALS, the LMS and the terminal.

1704, the eec sends information of the first LMS to the VALC.

It is understood that the information of the first LMS transmitted in step 1404b is information for determining the first LMS.

As an example, the information of the first LMS may be an ID of the first LMS (including an internal identification and/or an external identification, such as GPSI, SUPI, etc.), or may be address information (such as IP address, MAC address, URL, URI, etc.).

Optionally, the EEC sends third indication information to the VALC, the third indication information indicating that the VALC sends the information of the first LMS to the first VALS.

It will be appreciated that steps 1701 and 1702 need not be repeated when at least one of cases 1 and 2 is to be performed, and both cases 1 and 2 are to be performed.

Based on the scheme provided by the method 1700, the VALC may actively push information of the first LMS to the first VALS, so that when the first VALS needs to obtain the location information of the first terminal, the location information of the first terminal may be requested from the first LMS. The problem that the first VALS cannot acquire the position information of the first terminal when the first VALS does not know which LMS can request to acquire the position information of the first terminal, and therefore the first VALS requests to a certain LMS is avoided.

The flow provided by the method 1700 may implement a scenario in which the first vans corresponding to the first terminal requests location information of the first terminal, for LMS deployment across EDNs, or one EDN deploys multiple LMSs. The second vans (the second vans may be different from the service provided by the first vans), or the second LMC requesting the location information of the first terminal may be by the method described in fig. 18.

Fig. 18 is a flowchart of another method 1800 for obtaining location information of a terminal according to an embodiment of the present application. The method 1800 may be used to implement the aspects of the method 1400 described above. In method 1800, the second network element is exemplified by a second vans or a second LMC, the second LMC being associated with a second terminal, the first terminal being different from the second terminal, the related information of the first terminal being exemplified by location information of the first terminal. The method 1800 illustrated in fig. 18 includes the steps of:

steps 1801-1806, similar to steps 1601-1606, are described with reference to steps 1601-1606 and are not repeated here.

1807, the first VALS obtains location information of the first terminal.

It can be appreciated that the first vans may acquire the location information of the first terminal by using the first vans illustrated in the method 1700 to acquire the location information of the first terminal, which is not described herein.

Step 1808 is similar to step 1608, and is not described in detail herein with reference to the description of step 1608.

Based on the scheme provided by the method 1800, in a scenario where an LMS deploys across EDNs, or one EDN deploys multiple LMS, when a second vans or a second LMC needs to obtain location information of a first terminal, the location information of the first terminal may be requested to the first vans, and the first vans may obtain, in combination with the method 1700, the location information of the first terminal from the first LMS.

Fig. 19 is a flowchart of another method 1900 for obtaining location information of a terminal according to an embodiment of the present application. The method 1900 may be used to implement the aspects of the method 1400 described above. In method 1900, a first network element is illustrated as EES, a first SEAL client is illustrated as a first LMC, a first SEAL server is illustrated as a first LMS, and information related to a first terminal is illustrated as location information of the first terminal. Wherein the VALC, the first LMC, and the EEC are all associated with the first terminal. The method 1900 illustrated in fig. 19 includes the steps of:

1901, a first VALS is found.

Similar to step 1501, further description is omitted herein.

1902, optional step, if the EES returns a plurality of VALS and the selection of VALS is performed by the VALC, the VALC may send the selected first VALS to the EES.

For example, the VALC may send the selected first VALS to the EEC via the EDGE-5 interface, and the first VALS may then be sent to the EES by the EEC. The VALC may or may not send the identity of the first terminal to the EEC, as this application is not limited. Similarly, the EEC may or may not send the identity of the first terminal to the EES, as this application is not limited in this regard.

If the EES returns multiple VALS and the selection of VALS is performed by the EEC, step 1902 may be replaced with the EEC sending the selected first VALS to the EES. The EEC may or may not send the identity of the first terminal to the EES, as this application is not limited.

Alternatively, if the EES returns multiple varss and the selection of a VALS is performed by the VALC or EEC, the VALC or EEC sends the EES the first VALS and the identity of the first terminal.

1903, the first LMS is found.

Similar to step 1502, further description is omitted herein.

1904, optional step, if the EES returns a plurality of LMSs and the selection of LMSs is performed by the first LMC, the first LMC may send information of the selected LMSs to the EES (for determining the first LMS).

The information of the first LMS in step 1502a may be an ID of the first LMS (including an internal identifier and/or an external identifier, such as GPSI, SUPI, etc.), address information of the first LMS, such as an IP address, a MAC address, a URL, a URI, etc., and domain name information of the first LMS, such as FQDN of the first LMS, etc.

For example, the first LMC may send information of the selected first LMS to the EEC via the EDGE-5 interface, and the EEC may then send the information of the first LMS to the EES. The first LMC may or may not send the identity of the first terminal to the EEC, which is not limited in this application. Similarly, the EEC may or may not send the identity of the first terminal to the EES, as this application is not limited in this regard.

If the EES returns multiple LMSs and the selection of an LMS is performed by the EEC, step 1904 may be replaced with the EEC sending information of the selected first LMS to the EES. The EEC may or may not send the identity of the first terminal to the EES, as this application is not limited.

Alternatively, if the EES returns a plurality of LMSs and the selection of an LMS is performed by the first LMC or EEC, the first LMC or EEC transmits information of the first LMS and an identification of the first terminal to the EES.

EES determines the association of VALS and LMS by:

mode one:

1905a, the ees determines the associated first VALS, first LMS and first terminal.

The EES is able to determine an associated first VALS, the first LMS and the first terminal need to satisfy any of the following conditions:

1. The EES returns only one VALS (i.e., the first VALS) and the EES returns only one LMS (i.e., the first LMS).

2. The EES returns a plurality of VALSs but performs step 1902 so that the EES can determine that the VALC or the EEC-selected VALS is the first VALS and/or the EES returns a plurality of LMSs but performs step 1904 so that the EES can determine that the LMC or the EEC-selected LMS is the first LMS.

Illustratively, the EES returns a plurality of varss, and the selection of the VALS is performed by the VALC or the EEC, but after the VALC or the EEC performs the selection of the VALS, a notification message is sent to the EES to declare the EES' own selected VALS (i.e., the first VALS). The EES returns only one LMS (i.e., the first LMS).

Or the EES returns multiple varss and the selection of the VALS is performed by the VALC or EEC, but after the VALC or EEC performs the selection of the VALS, a notification message is sent to the EES to declare the EES' own selected VALS (i.e., the first VALS). The EES returns a plurality of LMSs and the selection of an LMS is performed by the LMC or the EEC, but after the LMC or the EEC performs the LMS selection, a notification message is sent to the EES to declare the EES' own selected LMS (i.e., the first LMS). Or alternatively

The EES returns only one VALS (i.e., the first VALS). The EES returns a plurality of LMSs and the selection of an LMS is performed by the LMC or the EEC, but after the LMC or the EEC performs the LMS selection, a notification message is sent to the EES to declare the EES' own selected LMS (i.e., the first LMS).

Mode two

1905b, the eec determines the associated first VALS and first LMS.

Similar to step 1703, further description is omitted here.

1906b, the eec sends a first VALS to the EES, the association of the first LMS and the first terminal.

The EES may determine a first VALS based on the association transmitted in 1906b, the first LMS being associated with the first terminal.

An understanding of the association may be found in the relevant description of method 1700, which is not repeated here.

It should be noted that at least one of the above first and second modes is executed. The implementation effect of the first mode and/or the second mode is that the EES can determine the association relationship between the first VALS, the first LMS and the first terminal.

1907, after the ees determines the association relationship, a first message may be sent to the first VALS, where the first message includes information of the first LMS, and the information of the first LMS is used to determine the first LMS.

Step 1907 is similar to step 1510, and the details of step 1510 are described in detail below.

The difference is that the first message in step 1907 may include first indication information indicating that the location information of the first terminal can be acquired from the first LMS, or the first indication information indicates that the location information of the first terminal can be acquired from the first LMS when the first VALS needs to acquire.

At 1908, after the first vans receives the first message, relevant information of the first terminal may be acquired.

The method for obtaining the related information of the first terminal may refer to the descriptions of steps 1520-1530, which are not repeated here.

It is understood that step 1908 is not triggered by step 1907 or other steps preceding step 1907, and that step 1908 may be performed when the first vans has a need to obtain information about the first terminal. For example, the first VALS described in step 1503 has a need to obtain the related information of the first terminal, which is not described herein.

Because the VALS is managed by the EES as EAS in the EC architecture, when the VALS needs information across the EDN, the VALS can request the EES and be uniformly processed by the EES, i.e., the EES and the EECs serve as centralized management points on the server side and the client side, respectively, and the prior assumption of the architecture is more satisfied. In addition, the data flow interaction of SEAL server information is suitably implemented by the interaction of edge enabled layers (edge enabler layer, EELs), which requires an interface between EES and EECs, and the method 1900 may simplify the logic of VAL, i.e., between the server providing the service and the client, decoupling the traffic data and the information flow of the enabled layers.

Based on the scheme provided by the method 1900, the EES may actively push information of the first LMS to the first VALS, so that when the first VALS needs to obtain the location information of the first terminal, the location information of the first terminal may be requested from the first LMS. The problem that the first VALS cannot acquire the position information of the first terminal when the first VALS does not know which LMS can request to acquire the position information of the first terminal, and therefore the first VALS requests to a certain LMS is avoided.

The flow provided by the method 1900 may implement a scenario in which the first vans corresponding to the first terminal requests location information of the first terminal, for LMS deployment across EDNs, or one EDN deploys multiple LMSs. The second vans (the service provided by the second vans may be different from the first vans), or the second LMC requesting the location information of the first terminal may be by the method described in fig. 20.

Fig. 20 is a flowchart of another method 2000 for obtaining location information of a terminal according to an embodiment of the present application. The method 2000 may be used to implement the aspects of the method 1400 described above. In the method 2000, the second network element takes a second vans or a second LMC as an example, the second LMC is associated with a second terminal, the second terminal is different from the first terminal, and the related information of the first terminal takes location information of the first terminal as an example. The method 2000 illustrated in fig. 20 includes the steps of:

Steps 2001-2006, similar to steps 1601-1606, are described with reference to steps 1601-1606 and are not repeated here.

2007, the first VALS acquires location information of the first terminal.

It may be appreciated that the first vans may acquire the location information of the first terminal by using the first vans illustrated in the method 1900 to acquire the location information of the first terminal, which is not described herein.

Step 2008 is similar to step 1608, and is not described in detail herein with reference to the description of step 1608.

Based on the scheme provided by the method 2000, in a scenario where an LMS deploys across EDNs or one EDN deploys multiple LMS, when the second vans or the second LMC needs to obtain the location information of the first terminal, the location information of the first terminal may be requested to the first vans, and the first vans may obtain, in combination with the method 1900, the location information of the first terminal from the first LMS.

It should be noted that the method 1500,1600,1700,1800,1900 or 2000 is a specific implementation of the method 1400 in a specific scenario, where, for more clearly describing the scheme provided by the method 1400, the related information of the first terminal is exemplified by the location information of the first terminal, the SEAL server is exemplified by the LMS, and the SEAL client is exemplified by the LMC.

If a network element or entity (e.g., the first vans, the second LMC, or the second terminal) needs to obtain that the related information of the first terminal is other information, the location information of the first terminal in the method 1500,1600,1700,1800,1900 or 2000 may be replaced with other information, the LMS may be replaced with a server corresponding to the other information, and the LMC may be replaced with a client corresponding to the other information.

For example, if a network element or entity (e.g., the first vans, the second LMC, or the second terminal) needs to obtain that the information related to the first terminal is group management information, the location information of the first terminal in the method 1500,1600,1700,1800,1900 or 2000 may be replaced with group management information, the LMS may be replaced with a server capable of performing group management, and the LMC may be replaced with a client capable of obtaining the group management information. The situation that a network element or entity (e.g., the first VALS, the second LMC, or the second terminal) needs to obtain information about the first terminal is configuration management information, identity management information, key management information, network resource management information, and the like, which are similar, and are not listed here.

For the same type of related information (such as location information), when different SEAL servers (a first SEAL server and a second SEAL server) manage related information of different terminals, management situations of the related information of the terminals can be synchronized among the different SEAL servers, so that when a SEAL server selected by a certain VALS does not manage the related information of the terminals required by the VALS, the SEAL server selected by the VALS can acquire the related information of the terminals from the SEAL server managing the related information of the terminals required by the VALS.

Fig. 21 is a flowchart of a method 2100 for acquiring terminal information according to an embodiment of the present application. The method 2100 includes the steps of:

2110, the second SEAL server determines that the information about the first terminal can be acquired from the first SEAL server.

The second SEAL server may be configured to obtain the related information of the first terminal, and when the second SEAL server cannot obtain the related information of the first terminal, for example, when the second SEAL server cannot directly request the related information of the first terminal from the SEAL client associated with the first terminal, the second SEAL server determines that the related information of the first terminal may be obtained from the first SEAL server, as an example. The second SEAL server may determine that the second SEAL server may obtain the relevant information of the first terminal from the first SEAL server according to the registration condition between the SEAL servers, or the second SEAL server may determine that the second SEAL server may obtain the relevant information of the first terminal from the first SEAL server according to the identification of the first terminal received from the first SEAL server.

2120, the second SEAL server sends a third request message to the first SEAL server, where the third request message is used to request related information of the first terminal.

For example, the second SEAL server determines that the related information of the first terminal can be acquired from the first SEAL server, and the related information of the first terminal can be requested through the third request message. The third request message may include identification information of the first terminal, indicating that the relevant information of the first terminal is requested.

2130, after receiving the third request message, the first SEAL server sends information about the first terminal to the second SEAL server.

For example, the first SEAL server may send information about the first terminal to the second SEAL server, and may send identification information of the first terminal to the second SEAL server.

Optionally, the method 2100 further comprises:

the second SEAL server sends the related information of the first terminal to a third network element, and the third network element is a VALS or SEAL client.

Prior thereto, the method 2100 further comprises:

the second SEAL server receives a fourth request message from the third network element, where the fourth request message is used to request information about the first terminal.

The fourth request message includes, for example, identification information of the first terminal.

Optionally, before step 2110, the method 2100 further includes:

the second SEAL server receives the client configuration information from the first SEAL server, the client configuration information comprises the identification information of the first terminal, and the second SEAL server can determine that the relevant information of the first terminal can be acquired from the first SEAL server according to the client configuration information.

Based on the method 2100, the client configuration information can be used to know which SEAL server can obtain the relevant information of which terminal, so that when the second SEAL server cannot obtain the relevant information of the first terminal, the second SEAL server can know that the relevant information of the first terminal can be obtained from the first SEAL server through the client configuration information, and request the relevant information of the first terminal to the first SEAL server, thereby avoiding the problem that the second SEAL server may not request the relevant information of the first terminal when requesting the relevant information of the first terminal to any SEAL server.

It is to be appreciated that the concepts involved in the method 2100, such as the SEAL server, the first terminal, the identification information of the first terminal, and the related information of the first terminal, may refer to the related description in the method 1400, and are not described herein.

Fig. 22 is a flowchart of a method 2200 for obtaining location information of a terminal according to an embodiment of the present application. The method 2200 may be used to implement aspects of the method 2100 described above. In method 2200, the SEAL client is exemplified by LMC, the SEAL server is exemplified by LMS, the requested terminal is exemplified by the first terminal, and the information related to the first terminal is exemplified by the location information of the first terminal. Wherein the first LMC is associated with a first terminal and the second LMC is associated with a second terminal, the first terminal and the second terminal being different.

It is understood that fig. 22 is only an example, and does not limit the scope of the present application. When the related information of the terminal required by the vans is group management information, configuration management information, identity management information, key management information, network resource management information, and the like, the LMS in fig. 22 may be replaced with a group management server, a configuration management server, an identity management server, a key management server, a network resource management server, and the like, and the LMC may also be replaced with a client corresponding to the server replaced with the LMS. And the messages involved in the flow shown in fig. 22 may be replaced with other messages of similar functions according to the replacement adaptability of the server and the location information.

For example, the location report configuration request may be replaced with a group report configuration request, an identity report configuration request, etc., and the replacement of other messages is similar and is not listed here.

The method 2200 includes the steps of:

2201, the first LMC sends a location report configuration request to the first LMS.

Illustratively, step 2201 is similar to step 501, and reference may be made to the description in step 501, which is not repeated herein.

It is appreciated that prior to step 2201, the first LMC has determined the first LMS, e.g., has performed an LMS discovery procedure, i.e., the first LMC has discovered the first LMS.

2202, the first LMS may send a configuration notification to one or more LMSs (including the second LMS) upon receipt of the location report configuration request.

For example, the first LMS transmits LMC configuration information including identification information of the first terminal to one or more LMSs including the second LMS.

In a possible implementation, the LMC configuration information is used to announce to other LMSs (LMSs other than the first LMS) in the EDN that can manage the location information of the first terminal. LMC configuration information may be understood as an inter-LMS capability synchronization message.

In another possible embodiment, the LMC configuration information includes identification information of the first terminal and indication information indicating to one or more LMSs including the second LMS that the first LMS can manage location information of the first terminal. And thus may be obtained from the first LMS when other LMSs have a need to obtain location information of the first terminal.

If multiple EES are deployed in the EDN, the target LMS that the first LMC sends LMC configuration information may also be other LMSs that are registered with the same EES as the first LMS, instead of all other LMSs in the EDN.

2203, one or more LMSs (including a second LMS) send configuration responses to the first LMS.

2204 the first LMS sends a location reporting configuration response to the first LMC.

Illustratively, step 2204 is similar to step 502, and is described in step 502, which is not repeated herein.

It can be appreciated that after step 2204, synchronization of terminal information managed by each LMS within the same EDN/EES management range is achieved.

2205, when the third network element needs to acquire the location information of the first terminal, send a location report trigger message (e.g. location reporting trigger message in step 801, which may correspond to the fourth request message in method 2100) to the second LMS.

For example, the third network element is a second vans or a second LMC, e.g. the vans associated with the first LMS is a first vans, then the second vans may be understood as a vans associated with the second LMS, the first LMS being different from the second LMS. The location report trigger message may include identification information of the first terminal.

It will be appreciated that prior to step 2205, the third network element has selected the second LMS, and thus may send a location report trigger message to the second LMS.

It is also understood that here the second VALS and the first VALS are located at the same EDN, or the EES used by the first LMC and the second LMC are located at the same EDN.

2210, the second LMS determines that the location information of the first terminal can be acquired from the first LMS.

For example, the second LMS2 determines that the location information of the first terminal can be acquired from the first LMS according to the identity of the first terminal and the LMC registration condition synchronized between the LMSs.

In a possible implementation manner, the second LMS determines that the second LMS does not manage the location information of the first terminal according to the identification information carried in the location report trigger message, or the second LMS determines that the second LMS cannot directly determine the location information of the first terminal according to the identification information carried in the location report trigger message, or the second LMS determines that the second LMS cannot directly request the location information of the first terminal from the LMC (i.e., the first LMC) associated with the first terminal according to the identification information carried in the location report trigger message, and determines that the location information of the first terminal is managed by the first LMS according to the LMC configuration information of step 2202, or determines that the first LMS may acquire the location information of the first terminal from the first LMC. The second LMS may determine that the location information of the first terminal can be acquired from the first LMS.

2220, the second LMS transmits a location request message (which may correspond to the third request message in the method 2100) to the first LMS for requesting location information of the first terminal.

Illustratively, the location request message includes identification information of the first terminal.

After receiving the location request message, the first LMS may acquire location information of the first terminal from the first LMC.

Illustratively, the first LMS may acquire the location information of the first terminal through the method illustrated in fig. 7. The method for the first LMS to acquire the position information of the first terminal is not limited.

2230, the first LMS sends a location response message to the second LMS.

The location response message includes location information of the first terminal, and may further include identification information of the first terminal, for example. The identification information of the first terminal has the effect that if the second LMS requests location information of a plurality of UEs/users from the first LMS, the identification information in the location response message can be used to distinguish to which UE/user each location information in the location response message belongs.

Therefore, if the second LMS requests the location information of only one terminal from the first LMS, the identification information of the terminal may not be included in the location response message.

2231, the second LMS sends a location report to the third network element.

The location report includes location information of the first terminal, or the location report includes location information of the first terminal and identification information of the first terminal, for example. Similar to step 803, details are not repeated.

By the method 2200, in case that the second LMS determines that the location information of the first terminal cannot be acquired by itself, it can be determined from which LMS the location information of the first terminal can be acquired, thereby requesting the determined first LMS for the location information of the first terminal. The problem that the second LMS can not request the position information of the first terminal when requesting the position information of any LMS is avoided.

It is appreciated that the first and second vans in method 2200 are located at the same EDN, or the EES used by the first and second LMCs are located at the same EDN.

For LMS deployment across EDNs, or multiple LMSs are deployed centrally in one EDN scenario. The second vans (the second vans may be different from the first vans) or the second LMC requesting the location information of the first terminal may be implemented in connection with the method 2300 described in fig. 23.

It is understood that fig. 23 is only an example, and does not limit the scope of protection of the present application. When the related information of the terminal required by the vans is group management information, configuration management information, identity management information, key management information, network resource management information, and the like, the LMS in fig. 23 may be replaced with a group management server, a configuration management server, an identity management server, a key management server, a network resource management server, and the like, and the LMC may be replaced with a client corresponding to the server after the LMS replacement. And the messages involved in the flow shown in fig. 23 may be replaced with other messages of similar functions according to the replacement adaptability of the server and the location information. Wherein the second LMC is associated with a second terminal, the second terminal being different from the first terminal.

Method 2300 includes the steps of: steps 2301-2305, similar to steps 1601-1605, may be described with reference to steps 1601-1605, and are not described again herein.

2306, the second vans or the second LMC sends a location report trigger message to the second LMS.

Step 2306 is similar to step 2205, and reference is made to the description related to step 2205, which is not repeated here.

It is appreciated that prior to step 2306, the second vans or the second LMC has selected the second LMS, and thus may send a location report trigger message to the second LMS.

2307, the second LMS acquires location information of the first terminal.

For example, the second LMS may acquire location information of the first terminal through the method 2200.

2308, the second LMS transmits the location information of the first terminal to the second vans or the second LMC, or the second LMS transmits the location information of the first terminal and the identification information of the first terminal to the second vans or the second LMC.

Based on the scheme provided by the method 2300, in a scenario where the LMS deploys across the EDN, or one EDN deploys multiple LMSs, when the second vans or the second LMC needs to obtain the location information of the first terminal, the second LMS may request the location information of the first terminal from the second LMS selected by the second vans or the second LMC, and the second LMS may combine the method 2200 to obtain the location information of the first terminal from the first LMS.

Fig. 24 is a flowchart of a method 2400 for acquiring terminal information according to an embodiment of the present application. The method 2400 illustrated in fig. 24 includes the steps of:

2410, the first val obtaining SEAL server information, where the SEAL server information is used to determine a first SEAL server, and the first SEAL server is used to obtain related information of the first terminal.

For example, the first VALS may determine the SEAL server information according to protocol specifications, or a locally configured SEAL server, or according to an existing EAS discovery procedure, such as the procedure shown in fig. 10, 11, or 12.

Alternatively, 2410 may be replaced with: the first VALS acquires the SEAL server information, the SEAL server information is associated with a first SEAL server, and the first SEAL server is used for acquiring related information of the first terminal.

Alternatively, 2410 may be replaced with: the first VALS obtains related information of a first SEAL server.

The specific content of the SEAL server information, the association between the SEAL server information and the first SEAL server, and the specific content of the first terminal may refer to the description in the method 1400, which is not described herein.

2420, the first VALS sends the SEAL server information to the first VALC, and the corresponding first VALC receives the SEAL server information. Wherein the first VALC is a VALC associated with the first terminal.

2420 may be replaced with: the first VALS sends the related information of the first SEAL server to the first VALC, and correspondingly, the first VALC receives the related information of the first SEAL server.

The details of the related information of the first SEAL server may be referred to in the related description of the method 1400, and will not be described herein.

Optionally, the method 2400 further includes:

the first VALS sends fourth indication information to the first VALC, the fourth indication information indicates the first VALC to send the SEAL server information to the first SEAL client, and the first VALC receives the fourth indication information correspondingly.

For example, the fourth indication information and the SEAL server information may be carried in the same message or may be carried in different messages, which is not limited in this application. For example, the SEAL server information is carried in the second message, and the fourth indication information is carried in the third message; or the SEAL server information and the fourth indication information are both carried in the second message.

Optionally, the method 2400 further includes:

the first VALS sends fifth indication information to the first VALC, the fifth indication information indicating that the first SEAL client selects or uses the first SEAL server, and the first VALC receives the fifth indication information.

The fifth indication information and the SEAL server information may be carried in the same message or may be carried in different messages, which is not limited in this application. For example, the SEAL server information is carried in the second message, and the fifth indication information is carried in the third message; or the SEAL server information and the fifth indication information are both carried in the second message.

It will be appreciated that step 2420 is exemplary of the first VALC obtaining SEAL server information.

The first VALC may also obtain the SEAL server information in other manners, such as step 2420', the first VALC obtaining the SEAL server information locally, or the first VALC obtaining the first SEAL server related information locally.

2430, the first VALC sends the SEAL server information to the first SEAL client, and the corresponding first SEAL client receives the SEAL server information, where the first SEAL client is associated with the first terminal.

2430 may be replaced with: the first VALC sends the related information of the first SEAL server to the first SEAL client, and the first SEAL client receives the related information of the first SEAL server correspondingly.

Optionally, the method 2400 further includes:

the first VALC sends sixth indication information to the first SEAL client, the sixth indication information indicates that the first SEAL client selects or uses the first SEAL server, and the first SEAL client receives the sixth indication information correspondingly.

For example, the sixth indication information and the SEAL server information may be carried in the same message or may be carried in different messages, which is not limited in this application.

Optionally, the method 2400 further includes:

2440, the first val requests the first SEAL server for the related information of the first terminal.

Optionally, the method 2400 further includes:

2450, the first SEAL server transmits information about the first terminal to the first VALS. Correspondingly, the first VALS receives the related information of the first terminal.

Steps 2440 and 2450 are similar to steps 1430 and 1440, and reference is made to the relevant descriptions in steps 1430 and 1440, which are not repeated here.

Based on the scheme provided by method 2400, in a scenario where the first val has determined the first SEAL server, the first val may send SEAL server information to the first val, so that the first val forwards the SEAL server information to the first SEAL client, so that the SEAL server determined by the first val is the same as the SEAL server determined by the first SEAL client, and at this time, the first val may obtain relevant information of the first terminal through the first SEAL server.

Fig. 25 is a flowchart of a method 2500 for obtaining location information of a terminal according to an embodiment of the present application. The method 2500 may be used to implement aspects of the method 2400 described above. In method 2500, the first SEAL client is exemplified by a first LMC, the first SEAL server is exemplified by a first LMS, and the related information of the first terminal is exemplified by the location information of the first terminal. The method 2500 includes the steps of:

2501, a first VALC initiates a VALS discovery procedure for discovering a first VALS.

Similar to step 1501, reference is specifically made to the description of step 1501, which is not repeated herein.

2510, the first VALS obtains information of a first LMS, where the information of the first LMS is used to determine the first LMS, and the first LMS is used to obtain location information of the first terminal. Wherein the first terminal is associated with a first VALC.

The information of the first LMS may be referred to the related description in step 1904, and will not be described herein.

In one possible implementation, the first VALS discovers or selects the LMS, which may be understood as information that the first VALS locally configures the LMS.

For example, the first VALS may determine the first LMS according to a protocol specification between the first VALS and a deployment party of the LMS, or information of the locally configured LMS. For example, the protocol may specify a correspondence between the vars and the LMS, or the first VALS and the LMS may be associated or bound when deployed in the network (e.g., deployed in an EDN), where the VALS and the LMS may correspond one to one, or one VALS may correspond to multiple LMSs, or multiple VALS may correspond to one LMS, which is not limited in this application.

It will be appreciated that step 2501 may be performed prior to step 2510, or step 2510 may be performed prior to step 2501, as this application is not limited in this regard.

In another possible embodiment, the first VALS may discover or select the LMS as follows. Step 2510 may be performed before or after step 2501 or simultaneously, and embodiments of the present application do not limit the timing of the execution of steps 2501 or 2510. The embodiments of the present application do not limit the manner in which the first VALS discovers the LMS, for example, the first LMS may be discovered through the method provided in fig. 10, 11, or 12, or the first LMS may also be discovered or selected through a non-standard defined manner or other manners.

In this embodiment, the triggering condition of step 2510 may be step 2501, for example, after step 2501 is performed, the first VALC sends a message to the first VALS or triggers the performance of step 2510, or the first VALC may trigger the performance of step 2510 in other manners, which is not limited in this application.

2520, the first VALS sends information of the first LMS to the first VALC, and the first VALC receives the information of the first LMS.

Optionally, the first VALS further sends identification information of the first terminal to the first VALC, and the identification information of the first terminal and the information of the first LMS may be carried in the same message.

The first terminal, and the identification information of the first terminal, may refer to the related description in the method 1400, which is not described herein.

Optionally, the first VALS sends fourth indication information to the first VALC, where the fourth indication information indicates that the first VALC sends information of the first LMS to the first LMC, and the first VALC receives the fourth indication information.

For example, the fourth indication information and the information of the first LMS may be carried in the same message or may be carried in different messages, which is not limited in this application.

Or, alternatively, the first VALS sends fifth indication information to the first VALC, the fifth indication information indicating that the first LMC selects or uses the first LMS, and the first VALC receives the fifth indication information, correspondingly.

For example, the fifth indication information and the information of the first LMS may be carried in the same message or may be carried in different messages, which is not limited in this application.

It may be appreciated that after the first VALC receives the information of the first LMS transmitted in step 2520, the first VALC may determine to perform step 2530 according to internal logic, or the first VALC may determine to perform step 2530 according to fourth indication information or fifth indication information.

It is further understood that whether the first VALS sends the fourth indication information or the fifth indication information in the specific implementation process may be determined according to the destination network element (the first VALC).

2530, the first VALC sends information of the first LMS to a first LMC (the first LMC is associated with the first terminal), and correspondingly, the first LMC receives the information of the first LMS.

Optionally, the first VALC sends sixth indication information to the first LMC, where the sixth indication information indicates that the first LMC selects or uses the first LMS, and the first LMC receives the sixth indication information.

For example, the sixth indication information and the information of the first LMS may be carried in the same message or may be carried in different messages, which is not limited in this application.

And 2540, performing position report configuration between the first LMS and the first LMC.

The implementation of step 2540 may refer to the flow illustrated in fig. 5, and will not be described herein.

It will be appreciated that step 2540 is not limited to the implementation of the flow illustrated in fig. 5, but may also be implemented in other manners to enable the first LMS to sense the first LMC, or enable the first LMS to initiate communication or interaction with the first LMC.

2550, the first VALS requests location information of the first terminal from the first LMS.

2560, the first LMS transmits location information of the first terminal to the first VALS. Correspondingly, the first VALS receives the location information of the first terminal. Steps 2550 and 2560 are similar to steps 1520 and 1530 and reference is made to the relevant descriptions of steps 1520 and 1530, which are not repeated here.

It is understood that the implementation manners of steps 2540 to 2560 are not limited in the present application, and steps 2540 to 2560 may be replaced by any flow or action that may achieve the technical effect that the first VALS obtains the relevant information of the first terminal from the first LMS.

Based on the scheme provided by the method 2500, in a scenario where the first vans has determined the first LMS, the first vans may send information of the first LMS to the first vanc, so that the first vanc forwards the information of the first LMS to the first LMC, so that the LMS determined by the first vans is the same as the LMS determined by the first LMC, and at this time, the first vans may obtain location information of the first terminal through the first LMS.

It should be noted that, the method 2500 is a specific implementation of the method 2400 in a specific scenario, where, for more clearly introducing a solution provided by the method 2500, the related information of the first terminal is exemplified by the location information of the first terminal, the SEAL server is exemplified by the LMS, and the SEAL client is exemplified by the LMC.

If a network element or entity (e.g., a first vans, a second LMC, or a second terminal) needs to obtain that the relevant information of the first terminal is other information, the location information of the first terminal in the method 2500 may be replaced with other information, the LMS may be replaced with a server corresponding to the other information, and the LMC may be replaced with a client corresponding to the other information.

For example, if a network element or entity (e.g., a first vans, a second LMC, or a second terminal) needs to obtain that the information related to the first terminal is group management information, the location information of the first terminal in method 2500 may be replaced with group management information, the LMS may be replaced with a server capable of performing group management, and the LMC may be replaced with a client capable of obtaining the group management information. The situation that a network element or entity (e.g., the first VALS, the second LMC, or the second terminal) needs to obtain information about the first terminal is configuration management information, identity management information, key management information, network resource management information, and the like, which are similar, and are not listed here.

It will be understood that the steps shown in the dashed lines in the above flowcharts are optional steps, and the sequence of the steps is determined according to the inherent logic of the method, and the serial numbers shown in the figures are only examples, and do not limit the sequence of the steps in the present application. The message names illustrated in the flowcharts of the embodiments of the present application are also merely examples, and do not limit the protection scope of the present application.

It is also understood that the methods provided in the embodiments of the present application may be used alone or in combination, and the present application is not limited in any way. And the same procedures, or the same terms, as referred to in different methods may be referred to each other.

Method embodiments of the present application are described above with reference to the accompanying drawings, and device embodiments of the present application are described below. It will be appreciated that the description of the method embodiments and the description of the apparatus embodiments may correspond to each other and that accordingly, non-described parts may be referred to the previous method embodiments.

In the embodiments of the present application, a plurality refers to two or more unless specifically stated otherwise.

In the embodiments of the present application, "at least one item(s)" means one item(s) or a plurality of items(s), "at least two items(s)" and "a plurality of items(s)" mean two items(s) or more than two items(s). "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

It will be appreciated that the term "and/or" is merely one association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

It is also understood that, in the present application, the information indicated by the indication information is referred to as information to be indicated. In a specific implementation process, there are various ways to indicate the information to be indicated, for example, but not limited to, the information to be indicated may be directly indicated, such as the information to be indicated itself or an index of the information to be indicated. The information to be indicated can also be indicated indirectly by indicating other information, wherein the other information and the information to be indicated have an association relation. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance. For example, the indication of the specific information may also be achieved by means of a pre-agreed (e.g., protocol-specified) arrangement sequence of the respective information, thereby reducing the indication overhead to some extent.

It will also be appreciated that in some of the embodiments described above, the message is sent multiple times. Taking the example of sending the message from a to B, the message from a to B may include sending the message from a directly to B, or may include sending the message from a to B through other devices or network elements, which is not limited.

It should also be understood that the execution bodies illustrated in the above flowcharts are only examples, and the execution bodies may also be components (e.g., chips, chip systems, or processors) of a device that supports the execution bodies to implement the methods illustrated in the above flowcharts, which are not limited in this application.

Corresponding to the methods given by the above method embodiments, the embodiments of the present application also provide corresponding apparatuses, where the apparatuses include corresponding modules for performing the above method embodiments. The module may be software, hardware, or a combination of software and hardware. It will be appreciated that the technical features described in the method embodiments described above are equally applicable to the device embodiments described below.

Fig. 26 is a schematic diagram of a communication device 2600 according to an embodiment of the present application. The device 2600 includes a transceiver unit 2610 and a processing unit 2620. The transceiving unit 2610 may be used to implement a corresponding communication function. The transceiving unit 2610 may also be referred to as a communication interface or a communication unit. The processing unit 2620 may be configured to perform processing operations, such as determining a rendering mode, etc.

Optionally, the apparatus 2600 further includes a storage unit, where the storage unit may be used to store instructions and/or data, and the processing unit 2620 may read the instructions and/or data in the storage unit, so that the apparatus implements the actions of the network device in the foregoing method embodiments.

In a first design, the device 2600 may be the first VALS in the previous embodiment, or may be a component (e.g., a chip) of the first VALS. The apparatus 2600 may implement steps or flows corresponding to those performed by the first VALS in the method embodiment above. The transceiver unit 2610 may be configured to perform the operations related to the transceiving of the first VALS in the above method embodiment (such as the operations of sending and/or receiving data or messages). The processing unit 2620 may be configured to perform operations related to the processing of the first VALS in the above method embodiment, or operations other than transceiving (e.g., operations other than transmitting and/or receiving data or messages).

A possible implementation manner, the transceiver unit 2610 is configured to receive a first message from a first network element, where the first message includes SEAL server information, where the SEAL server information is used to determine a first SEAL server; the transceiver unit 2610 is further configured to request, from the first SEAL server, information related to the first terminal; the transceiver 2610 is further configured to receive information related to the first terminal from the first SEAL server.

In one possible implementation, the first message further includes identification information of the first terminal.

In one possible implementation manner, the first message further includes first indication information, where the first indication information indicates that the related information of the first terminal can be obtained from the first SEAL server.

In one possible implementation, the transceiver unit 2610 is further configured to send a first request message to the first network element, where the first request message is used to request the SEAL server information.

In one possible implementation manner, before the first sals sends the first request message to the first network element, the transceiver unit 2610 is further configured to receive a second request message from a second network element, where the second request message is used to request information about the first terminal, and the second network element is a second sal, SEAL client, or a second terminal.

In one possible implementation manner, the related information of the first terminal includes at least one of the following: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

One possible implementation, the first network element is a VALC or EES.

In one possible implementation, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

In another possible implementation, the transceiver unit 2610 is configured to send a second message to the first VALC, where the second message includes SEAL server information, where the SEAL server information is used to determine a first SEAL server, and the first VALC is associated with the first terminal; the transceiver unit 2610 is further configured to request, from the first SEAL server, information related to the first terminal; the first vans receives related information of a first terminal from a first SEAL server.

Optionally, the second message further includes: fourth indication information or fifth indication information, the fourth indication information indicates that the first VALC transmits the SEAL server information to the first SEAL client, and the fifth indication information indicates that the first SEAL client selects or uses the first SEAL server.

Optionally, the second message further comprises identification information of the first terminal.

Optionally, the relevant information of the first terminal includes at least one of: location information, group management information, configuration management information, identity management information, key management information, network resource management information.

Optionally, the SEAL server information includes at least one of: address information, domain name information, or identification information of the first SEAL server.

In a second design, the device 2600 may be the first network element (e.g., a VALC or EES) in the foregoing embodiment, or may be a component (e.g., a chip) of the first network element. The apparatus 2600 may implement steps or flows performed corresponding to the first network element in the method embodiment above. The transceiver unit 2610 may be configured to perform operations related to the transceiving of the first network element (such as operations of sending and/or receiving data or messages) in the above method embodiment. The processing unit 2620 may be configured to perform operations related to data and/or information processing of the first network element in the above method embodiment, or operations other than transceiving (such as operations other than sending and/or receiving data or messages).

A possible implementation manner, the transceiver unit 2610 is configured to obtain SEAL server information, where the SEAL server information is used to determine a first SEAL server, and the first SEAL server is used to obtain related information of the first terminal; the transceiver unit 2610 is further configured to send a first message to the first val, where the first message includes SEAL server information.

In one possible implementation, the transceiver unit 2610 is further configured to receive first request information from the first val, where the first request information is used to request the SEAL server information.

One possible implementation, the first network element is a vertical application layer client VALC or an edge enabled server EES.

In one possible implementation, the first network element is a VALC, and the transceiver unit 2610 is further configured to receive SEAL server information from a SEAL client or EEC.

In one possible implementation, the first network element is a VALC, and the transceiver unit 2610 is further configured to request the SEAL server information from a SEAL client or EEC.

In one possible implementation, the transceiver unit 2610 is further configured to obtain third indication information from the SEAL client or the EEC, where the third indication information indicates that the first network element sends the SEAL server information to the first val.

In one possible implementation manner, the first network element is an EES, and the processing unit 2620 is configured to determine SEAL server information according to association relationships among the first VALS, the first SEAL server, and the first terminal.

In one possible implementation, the processing unit 2620 is further configured to determine the association relationship.

In a third design, the device 2600 may be a SEAL client in the foregoing embodiment, or may be a component (e.g., a chip) of the SEAL client. The apparatus 2600 may implement steps or flows corresponding to those performed by the SEAL client in the method embodiments above. The transceiver unit 2610 may be configured to perform operations related to the transceiving of the SEAL client (such as operations of sending and/or receiving data or messages) in the above method embodiment. The processing unit 2620 may be configured to perform operations related to processing by the SEAL client in the above method embodiments, or operations other than transceiving (e.g., operations other than sending and/or receiving data or messages).

A possible implementation manner, the transceiver unit 2610 is configured to obtain SEAL server information, where the SEAL server information is used to identify and determine a first SEAL server, and the first SEAL server is used to obtain related information of the first terminal; the transceiver unit 2610 is also used for sending SEAL server information to the VALC.

In one possible implementation, the transceiver unit 2610 is further configured to receive a SEAL server request message from the VALC, where the SEAL server request message is used to request SEAL server information.

In one possible implementation, the transceiver unit 2610 is further configured to send third indication information to the VALC, where the third indication information indicates that the VALC sends the SEAL server information to the first VALS.

In a fourth design, the device 2600 may be an EEC in the previous embodiments, or may be a component (e.g., a chip) of an EEC. The apparatus 2600 may implement steps or processes corresponding to EEC execution in the above method embodiments. The transceiver unit 2610 may be configured to perform operations related to the transceiver of the EEC in the above method embodiments (such as operations of sending and/or receiving data or messages). The processing unit 2620 may be configured to perform operations related to the processing of EECs in the above method embodiments, or operations other than transceiving (e.g., operations other than transmitting and/or receiving data or messages).

A possible implementation manner, the transceiver unit 2610 is configured to obtain SEAL server information, where the SEAL server information is used to determine a first SEAL server, and the first SEAL server is used to obtain related information of the first terminal; the transceiver unit 2610 is also used for sending SEAL server information to the VALC.

A possible implementation manner, a processing unit 2620 is configured to determine an association relationship between the first val and the first SEAL server; the transceiver 2610 is further configured to send the association relationship to the EES.

In a fifth design, the device 2600 may be the first LMS in the foregoing embodiment, or may be a component (e.g., a chip) of the first LMS. The apparatus 2600 may implement steps or processes corresponding to those performed by the first LMS in the method embodiments above. Wherein the transceiver unit 2610 may be configured to perform the operations related to the transceiver of the first LMS in the above method embodiments (e.g., the operations of sending and/or receiving data or messages). The processing unit 2620 may be configured to perform operations related to processing of the first LMS in the above method embodiments, or operations other than transceiving (e.g., operations other than transmitting and/or receiving data or messages).

A possible implementation manner, the transceiver unit 2610 is configured to obtain location information of the first terminal; and is also used to transmit the location information of the first terminal to the second LMS.

A possible implementation manner, the transceiver unit 2610 is configured to send the location information of the first terminal and the identification information of the first terminal to the second LMS.

In a possible implementation manner, the transceiver unit 2610 is further configured to receive a third request message from the second LMS, where the third request message is used to request location information of the first terminal.

In one possible implementation, the third request message includes identification information of the first terminal.

In a possible implementation manner, the transceiver unit 2610 is further configured to send location management client configuration information to the second LMS, where the location management client configuration information includes identification information of the first terminal.

In a sixth design, the device 2600 may be the second LMS of the previous embodiments, or may be a component (e.g., a chip) of the second LMS. The apparatus 2600 may implement steps or processes corresponding to those performed by the second LMS in the method embodiments above. Wherein the transceiver unit 2610 may be configured to perform the operations related to the transceiving of the second LMS in the above method embodiments (e.g., the operations of transmitting and/or receiving data or messages). The processing unit 2620 may be configured to perform operations related to processing of the second LMS in the above method embodiments, or operations other than transceiving (e.g., operations other than transmitting and/or receiving data or messages).

A possible implementation manner, a processing unit 2620 is configured to determine that the location information of the first terminal can be acquired from the first LMS; a transceiving unit 2610 for transmitting a third request message to the first LMS, the third request message requesting location information of the first terminal; the transceiver unit 2610 is also used for receiving the location information of the first terminal from the first LMS.

In one possible implementation manner, the transceiver unit 2610 is further configured to send the location information of the first terminal to a third network element, where the third network element is a vans or SEAL client.

A possible implementation manner, the transceiver unit 2610 is specifically configured to receive the location information of the first terminal and the identification information of the first terminal from the first LMS.

A possible implementation manner, the transceiver unit 2610 is further configured to receive location management client configuration information from the first LMS, where the location management client configuration information includes identification information of the first terminal; the processing unit 2620 is specifically configured to determine, according to the location management client configuration information, that the location information of the first terminal can be obtained from the first LMS.

In a possible implementation manner, the transceiver unit 2610 is further configured to receive, by the second LMS, a fourth request message from the third network element, where the fourth request message is used to request location information of the first terminal.

In a seventh design, the device 2600 may be the first VALC of the previous embodiments, or may be a component (e.g., a chip) of the first VALC. The apparatus 2600 may implement steps or flows performed corresponding to the first VALC in the method embodiment above. The transceiver unit 2610 may be configured to perform operations related to the transceiver of the first VALC in the above method embodiments (such as operations of sending and/or receiving data or messages). The processing unit 2620 may be configured to perform operations related to data and/or information processing of the first VALC in the above method embodiment, or operations other than transceiving (e.g., operations other than transmitting and/or receiving data or messages).

A possible implementation manner, the transceiver unit 2610 is configured to obtain SEAL server information, where the SEAL server information is used to determine a first SEAL server, and the first SEAL server is used to obtain related information of a first terminal, and the first terminal is associated with the first VALC; the transceiver unit 2610 is further configured to send the SEAL server information to the first SEAL client.

In one possible implementation, the transceiver unit 2610 is specifically configured to receive a second message from the first val, where the second message includes SEAL server information.

In one possible implementation, the second message further includes: fourth indication information or fifth indication information, the fourth indication information indicates that the first VALC transmits the SEAL server information to the first SEAL client, and the fifth indication information indicates that the first SEAL client selects or uses the first SEAL server.

In one possible implementation, the second message further includes identification information of the first terminal.

In one possible implementation, the transceiver unit 2610 is further configured to send sixth indication information to the first SEAL client, where the sixth indication information indicates that the first SEAL client selects or uses the first SEAL server.

In an eighth design, the device 2600 may be the first SEAL client in the foregoing embodiment, or may be a component (e.g., a chip) of the first SEAL client. The apparatus 2600 may implement steps or processes corresponding to those performed by the first SEAL client in the method embodiments above. The transceiver unit 2610 may be configured to perform the operations related to the transceiver of the first SEAL client (such as the operations of sending and/or receiving data or messages) in the above method embodiment. The processing unit 2620 may be configured to perform operations related to data and/or information processing of the first SEAL client in the above method embodiment, or operations other than transceiving (such as operations other than sending and/or receiving data or messages).

A possible implementation manner, the transceiver unit 2610 is configured to receive SEAL server information from the first VALC, where the SEAL server information is used to determine a first SEAL server, and the first SEAL server is used to obtain related information of a first terminal, and the first terminal is associated with the first VALC; the transceiver 2610 is further configured to send information related to the first terminal to the first SEAL server.

In one possible implementation, the transceiver unit 2610 is further configured to receive sixth indication information from the first VALC, where the sixth indication information indicates that the first SEAL client selects or uses the first SEAL server.

It will be appreciated that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and for brevity, will not be described in detail herein.

It is also understood that the apparatus 2600 herein is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it will be appreciated by those skilled in the art that the apparatus 2600 may be specifically a first VALS in the foregoing embodiment, and may be used to perform each flow and/or step corresponding to the VALS in each foregoing method embodiment. Alternatively, the apparatus 2600 may be specifically a first network element in the foregoing embodiment, and may be configured to perform each flow and/or step corresponding to the first network element in the foregoing method embodiments.

The apparatus 2600 of each of the above embodiments has a function of implementing the corresponding step performed by the first VALS in the above method; alternatively, the apparatus 2600 of each of the above embodiments has a function of implementing the corresponding step performed by the first network element in the above method. The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions; for example, the transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, a receiving unit in the transceiver unit may be replaced by a receiver), and other units, such as a processing unit, etc., may be replaced by a processor, to perform the transceiver operations and related processing operations in the various method embodiments, respectively.

The transceiver 2610 may be a transceiver circuit (e.g., may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

It will be appreciated that the apparatus of fig. 26 may be the device of the previous embodiment, or may be a chip or a system of chips, for example: system on chip (SoC). The receiving and transmitting unit can be an input and output circuit and a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit on the chip. And are not limited herein.

Fig. 27 is a schematic diagram of another communication device 2700 provided in an embodiment of the present application. The apparatus 2700 includes a processor 2710, the processor 2710 being configured to execute computer programs or instructions stored in a memory 2720 or to read data stored in the memory 2720 to perform the methods in the above method embodiments. Optionally, the processor 2710 is one or more.

Optionally, as shown in fig. 27, the apparatus 2700 further comprises a memory 2720, the memory 2720 for storing computer programs or instructions and/or data. The memory 2720 may be integrated with the processor 2710 or may be separately provided. Optionally, the memory 2720 is one or more.

Optionally, as shown in fig. 27, the apparatus 2700 further includes a transceiver 2730, the transceiver 2730 being used for receiving and/or transmitting signals. For example, the processor 2710 is configured to control the transceiver 2730 to receive and/or transmit signals.

As an option, the apparatus 2700 is configured to implement the operations performed by the first VALS in the method embodiments above.

Alternatively, the apparatus 2700 is configured to implement operations performed by the first network element (e.g., a VALC or EES) in the various method embodiments above.

As yet another approach, the apparatus 2700 is configured to implement the operations performed by the SEAL client, EEC, first LMS, or second LMS in the various method embodiments above.

It will be appreciated that the processors referred to in the embodiments of the present application may be central processing units (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It is also understood that the memory referred to in the embodiments of the present application may be volatile memory and/or nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM). For example, RAM may be used as an external cache. By way of example, and not limitation, RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

It should be noted that when the processor is a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) may be integrated into the processor.

It should also be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The present application also provides a computer-readable storage medium having stored thereon computer instructions for implementing the method performed by the first VALS in the method embodiments described above.

Embodiments of the present application also provide a computer readable storage medium having stored thereon computer instructions for implementing the method performed by the first network element (e.g., the VALC or EES) in the method embodiments described above.

Embodiments of the present application also provide a computer readable storage medium having stored thereon computer instructions for implementing the methods performed by the SEAL client, EEC, first LMS, or second LMS in the method embodiments described above.

Embodiments of the present application also provide a computer program product containing instructions that, when executed by a computer, implement the method performed by the first VALS in the method embodiments described above.

Embodiments of the present application also provide a computer program product comprising instructions which, when executed by a computer, implement the method performed by the first network element (e.g., the VALC or EES) in the method embodiments described above.

Embodiments of the present application also provide a computer program product comprising instructions that when executed by a computer implement the method performed by the SEAL client, EEC, first LMS, or second LMS in the method embodiments described above.

The embodiment of the application also provides a communication system, which comprises at least one of the first VALS and the first network element (such as VALC or EES).

Optionally, the communication system further comprises at least one of a SEAL client, an EEC, a first LMS, or a second LMS.

The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., 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, data center, etc. that contains an integration of one or more available media. For example, the aforementioned usable media include, but are not limited to, U disk, removable hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other various media that can store program code.

The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for acquiring terminal information, comprising:

the method comprises the steps that a first Vertical Application Layer Server (VALS) receives a first message from a first network element, wherein the first message comprises SEAL server information, and the SEAL server information is used for determining a first SEAL server;

the first VALS requests the first SEAL server for the related information of the first terminal;

the first vans receives related information of the first terminal from the first SEAL server.

2. The method of claim 1, wherein the first message further comprises identification information of the first terminal.

3. The method of claim 2, wherein the first message further comprises first indication information indicating that the first terminal related information is available from the first SEAL server.

4. A method according to any one of claims 1 to 3, further comprising:

the first VALS sends a first request message to the first network element, where the first request message is used to request the SEAL server information.

5. The method of claim 4, wherein the first request message comprises at least one of:

identification information of the first terminal; or (b)

And second indication information, wherein the second indication information is used for requesting the SEAL server information.

6. The method according to any one of claims 1 to 5, wherein before the first sals sends a first request message to the first network element, the method further comprises:

the first VALS receives a second request message from a second network element, wherein the second request message is used for requesting related information of the first terminal, and the second network element is a second VALS, a SEAL client or a second terminal.

7. The method according to any of claims 1 to 6, wherein the first network element is a vertical application layer client, VALC, or an edge enabled server, EES, and wherein the first terminal is associated with the VALC when the first network element is the VALC.

8. A method for acquiring terminal information, comprising:

the first VALS sends a second message to the first VALC, wherein the second message comprises the SEAL server information, the SEAL server information is used for determining a first SEAL server, and the first VALC is associated with a first terminal;

9. The method of claim 8, wherein the second message further comprises: fourth indication information or fifth indication information, where the fourth indication information indicates that the first VALC sends the SEAL server information to a first SEAL client, and the fifth indication information indicates that the first SEAL client selects or uses the first SEAL server.

10. A method for acquiring terminal information, comprising:

the method comprises the steps that a first network element obtains SEAL server information, wherein the SEAL server information is used for determining a first SEAL server, and the first SEAL server is used for obtaining relevant information of a first terminal;

the first network element sends a first message to a first VALS, the first message including the SEAL server information.

11. The method of claim 10, wherein the first message further comprises identification information of the first terminal.

12. The method of claim 11, wherein the first message further comprises first indication information indicating that information about the first terminal is available from the first SEAL server.

13. The method according to any one of claims 10 to 12, further comprising:

the first network element receives first request information from the first VALS, where the first request information is used to request the SEAL server information.

14. The method of claim 13, wherein the first request message comprises at least one of:

identification information of the first terminal; or (b)

15. The method according to any of the claims 10 to 14, wherein the first network element is a vertical application layer client, VALC, or an edge enabled server, EES.

16. The method according to any of the claims 10 to 15, wherein the first network element is a VALC associated with the first terminal, the first network element obtaining SEAL server information, comprising:

The VALC receives the SEAL server information from a SEAL client or edge enabled client EEC.

17. The method of claim 16, wherein the method further comprises:

the VALC requests the SEAL server information from the SEAL client or the EEC.

18. The method according to claim 16 or 17, characterized in that the method further comprises:

the VALC acquires third indication information from the SEAL client or the EEC, wherein the third indication information indicates the VALC to send the SEAL server information to the first VALS.

19. The method according to any one of claims 10 to 15, wherein the first network element is an EES, and the first network element obtains SEAL server information, including:

and the EES determines the SEAL server information according to the association relation among the first VALS, the first SEAL server and the first terminal.

20. A method for acquiring terminal information, comprising:

the method comprises the steps that a first VALC obtains SEAL server information, wherein the SEAL server information is used for determining a first SEAL server, the first SEAL server is used for obtaining relevant information of a first terminal, and the first terminal is associated with the first VALC;

The first VALC sends the SEAL server information to a first SEAL client.

21. The method of claim 20, wherein the first VALC obtaining SEAL server information comprises:

the first VALC receives a second message from the first VALS, the second message including the SEAL server information.

22. The method of claim 21, wherein the second message further comprises: fourth indication information or fifth indication information, where the fourth indication information indicates that the first VALC sends the SEAL server information to the first SEAL client, and the fifth indication information indicates that the first SEAL client selects or uses the first SEAL server.

23. The method according to any one of claims 1 to 22, wherein the relevant information comprises at least one of:

location information, group management information, configuration management information, identity management information, key management information, network resource management information.

24. The method of any one of claims 1 to 23, wherein the SEAL server information comprises at least one of:

address information, domain name information or identification information of the first SEAL server.

25. A communication device comprising means for performing the method of any one of claims 1 to 9 or means for performing the method of any one of claims 10 to 24.

26. A communication device comprising at least one processor for executing a computer program stored in a memory, to cause the device to perform the method of any one of claims 1 to 9 or to perform the method of any one of claims 10 to 24.

27. The apparatus of claim 26, further comprising the memory and/or a communication interface coupled with the processor,

the communication interface is used for inputting and/or outputting information.

28. A communication system comprising a first VALS and a first network element,

wherein the first VALS is configured to perform the method of any of claims 1 to 9 and the first network element is configured to perform the method of any of claims 10 to 24.

29. A computer readable storage medium for storing a computer program which, when run on a computer, causes the computer to perform the method of any one of claims 1 to 9 or causes the computer to perform the method of any one of claims 10 to 24.

30. A computer program product, the computer program product comprising: computer program code implementing the method according to any of claims 1 to 9 or implementing the method according to any of claims 10 to 24 when said computer program code is run.