Communication method and communication apparatus
By passing the private address, public address and port number of the terminal device in a 3GPP network, verifying the private address provided by the terminal device, solving the problem of insufficient security of the edge enable server to obtain the terminal device identifier, and achieving higher identification Get security and accuracy.
Patent Information
- Application Number
- PCT/CN2024/092241
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-14
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-21
AI Technical Summary
In the third-generation Partner Program (3GPP) network, the Edge Enable Server (EES) has insufficient security to obtain terminal device identifiers from the Edge Application Server (EAS) and Edge Enable Client (EEC). The terminal device provides The risk of still providing an identifier if the private address is inaccurate.
By passing the private address, public address and port number of the terminal device between the edge enable server and the network open function network element, the network open function network element can verify the accuracy of the private address provided by the terminal device, thereby determining whether to provide the terminal or not The device identifier improves the security of obtaining terminal device identifiers.
It effectively avoids identifier provision errors caused by inaccurate private addresses provided by terminal devices, improves the security of terminal device identifier acquisition, and ensures the accuracy and reliability of identifiers.
Smart Images

Figure CN2024092241_21112024_PF_FP_ABST
Abstract
Description
Communication method and communication device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 14, 2023, with application number 202310541737.3 and invention name “A Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communications, and more particularly, to a communication method and a communication device. Background Art
[0003] In order to enable edge applications on the 3rd Generation Partnership Project (3GPP) network, the architecture, processes, and information flows for enabling edge applications are defined. Specifically, in order to obtain an identifier that uniquely identifies a terminal device, the Edge Enabler Server (Edge Enabler Server, EES) in the architecture that enables edge applications opens a terminal device identifier application programming interface (Application program interface, API) to the Edge Application Server (Edge Application Server, EAS) and the Edge Enabler Client (Edge Enabler Client, EEC). The terminal device identifier API is used by EAS or EEC to obtain the terminal device's identification from EES.
[0004] Exemplarily, EEC calling the terminal device identifier API can be used in the following scenario: EAS directly calls the terminal device identifier API to EES. When obtaining the terminal device identifier fails, EAS can choose to send signaling to the application client (AC) to enable AC to initiate a terminal device identifier query to EEC. Further, EEC uses the Internet Protocol (IP) address allocated by the core network to call the terminal device identifier API of EES to obtain the terminal device identifier, and sends the obtained terminal device identifier to EAS through AC.
[0005] However, how to improve the security of EAS obtaining terminal device identifiers through EEC has become an urgent problem to be solved.
[0006] Summary of the Invention
[0007] The present application provides a communication method and a communication device to improve the security of EEC obtaining terminal device identifiers.
[0008] In a first aspect, the present application provides a communication method. The method may be executed by an edge-enabled server or by a component of the edge-enabled server (eg, a chip or circuit), which is not limited in the present application.
[0009] The communication method includes: receiving a first request message from a terminal device, the first request message is used to obtain an identifier of the terminal device, and the first request message includes a first private address of the terminal device; obtaining a public address and a port number of the terminal device, and sending a second request message to a network open function network element, the second request message is used to obtain an identifier of the terminal device, and the second request message includes the first private address, the public address and the port number; receiving first indication information from the network open function network element or the identifier of the terminal device, the first indication information is used to indicate that the identifier acquisition of the terminal device failed.
[0010] Based on the above solution, after the edge enabling server receives a request message from a terminal device to obtain the terminal device, the request message sent to the network open function network element carries the first private address received from the terminal device, as well as the obtained public address and port number. This allows the network open function network element to determine whether the first private address provided by the terminal device is accurate based on the received public address and port number, so as to decide whether to provide the terminal device with an identifier for the terminal device. This avoids providing the terminal device with an identifier for the terminal device even if the first private address provided by the terminal device is inaccurate, thereby improving the security of the terminal device obtaining the identifier for the terminal device.
[0011] In conjunction with the first aspect, in some implementations of the first aspect, the receiving a first request message from the terminal device includes: receiving an Internet Protocol (IP) data packet from a user plane function network element, wherein a payload portion of the IP data packet includes the first request message from the terminal device;
[0012] The obtaining of the public address and the port number includes: determining the public address and the port number according to the source address and the source port number of the IP data packet, wherein the source address is used to characterize the public address, and the source port number is used to characterize the port number.
[0013] Exemplarily, the obtaining the public address and the port number further includes: obtaining the public address and the port number from an edge application server.
[0014] Based on the above solution, the edge enabling server can obtain the required public address and the port number in different ways, thereby improving the flexibility of the solution and meeting different application scenarios.
[0015] In conjunction with the first aspect, in certain implementations of the first aspect, upon receiving the first indication information of the terminal device from the network open function network element, the method further includes: receiving a cause value of the terminal device from the network open function network element, the cause value being used to indicate a reason why the terminal device failed to obtain an identifier. The first indication information and the cause value may be carried in the second response message.
[0016] Based on the above scheme, when the second response message indicates that the terminal device's identifier acquisition fails, the reason for the failure to acquire the terminal device's identifier can be indicated by carrying a reason value in the first response message, so that the edge enabling server can correctly process the EEC request based on the reason value.
[0017] In combination with the first aspect, in certain implementations of the first aspect, when receiving the identifier of the terminal device from the network open function network element, the method also includes: sending a first response message to the terminal device, wherein the first response message includes the identifier of the terminal device.
[0018] In combination with the first aspect, in some implementations of the first aspect, sending the second request message to the network open function network element includes: sending the second request message to the network open function network element when the terminal device is not authenticated.
[0019] In a second aspect, the present application provides a communication method, which may be executed by a network open function element or a component of the network open function element (eg, a chip or circuit), and the present application does not limit this.
[0020] The communication method includes: receiving a second request message from an edge enabling server, the second request message is used to obtain an identifier of a terminal device, the second request message includes a first private address of the terminal device, a public address and a port number of the terminal device; when it is determined that the first private address is valid based on the public address and the port number, obtaining the identifier of the terminal device, and sending the identifier of the terminal device to the edge enabling server.
[0021] Based on the above solution, the edge enabling server sends a request message to the network open function element to obtain the terminal device, which carries the first private address received from the terminal device, as well as the public address and port number obtained by the network open function element. This allows the network open function element to determine whether the first private address provided by the terminal device is accurate based on the received public address and port number, thereby deciding whether to provide the terminal device with an identifier. This avoids providing the terminal device with an identifier even if the first private address provided by the terminal device is inaccurate, thereby improving the security of the terminal device obtaining the terminal device identifier.
[0022] In combination with the second aspect, in certain implementations of the second aspect, when it is determined that the first private address is invalid based on the public address and the port number, a first indication message is sent to the edge enabling server, where the first indication message is used to indicate that the identifier acquisition of the terminal device failed.
[0023] In combination with the second aspect, in some implementations of the second aspect, the method further includes: determining whether the first private address is valid based on the public address and the port number.
[0024] In combination with the second aspect, in certain implementations of the second aspect, determining whether the first private address is valid based on the public address and the port number includes: whether the first private address is the same as the second private address, wherein the second private address is determined based on the public address and the port number.
[0025] Exemplarily, the method further includes: sending a third request message to the user plane functional network element, the third request message including the public address and the port number; and receiving a third response message from the user plane functional network element, the third response message including the second private address.
[0026] Exemplarily, the method also includes: obtaining at least one private address corresponding to the public network address, and a port number corresponding to the at least one private address; obtaining the second private address based on the obtained at least one private address and the port number corresponding to the at least one private address, and the port number in the second request message.
[0027] Exemplarily, the method further includes: sending a fourth request message to a user plane function network element, the fourth request message including the public address; and receiving a fourth response message from the user plane function network element, the fourth response message including at least one private address corresponding to the public address and a port number corresponding to the at least one private address. Optionally, before sending the fourth request message to the user plane function network element, querying whether the at least one private address corresponding to the public network address and the port number corresponding to the at least one private address are locally stored.
[0028] Exemplarily, the method further includes: sending a subscription request message to a user plane function network element, the subscription request message including the public address; and receiving one or more subscription response messages from the user plane function network element, the one or more subscription response messages including at least one private address corresponding to the public address and a port number corresponding to the at least one private address. Optionally, before sending the fourth request message to the user plane function network element, querying whether the at least one private address corresponding to the public network address and the port number corresponding to the at least one private address are locally stored.
[0029] If the at least one private address does not include the first private address, the first private address is determined to be invalid; or, if the at least one private address includes the first private address, and the port number corresponding to the first private address is the same as the port number, the first private address is determined to be valid.
[0030] Exemplarily, the method also includes: sending a fifth request message to the user plane functional network element, the fifth request message including the first private address, the public address and the port number, the fifth request message being used to request the user plane functional network element to determine whether the first private address is valid; and receiving a fifth response message from the user plane functional network element, the fifth response message being used to indicate whether the first private address is valid.
[0031] Based on the above solution, the network open function network element can verify the first private address provided by the terminal device in different ways. For example, it can query the user plane function network element based on the received public address and port number to obtain the second private address corresponding to the public address and port number, and then verify the first private address based on the second private address obtained from the user plane function network element. For another example, it can obtain at least one private address corresponding to the public address and the port number corresponding to the at least one private address from the user plane function network element based on the received public address, and then verify the first private address based on the at least one private address obtained from the user plane function network element and the port number corresponding to the at least one private address. For another example, the received first private address, public address and port number can be provided to the user plane function network element, which verifies the first private address and provides the verification result to the network open function network element. Providing different verification methods improves the flexibility of the solution.
[0032] In combination with the second aspect, in certain implementations of the second aspect, the method further includes: sending a discovery request message to a network function repository function network element, the discovery request message including the public address, and the discovery request message being used to obtain the address of a user plane function network element that implements an address conversion function; and receiving a discovery response message from the network function repository function network element, the discovery response message including the address of the user plane function network element.
[0033] In combination with the second aspect, in some implementations of the second aspect, when sending the first indication information to the edge enabling server, the method further includes: sending a reason value to the edge enabling server, where the reason value is used to indicate the reason for the failure to obtain the identifier of the terminal device.
[0034] On the third aspect, the present application provides a communication method, which can be executed by a user plane functional network element or by a component of the user plane functional network element (such as a chip or circuit), and the present application does not limit this.
[0035] The communication method includes: receiving a third request message from a network open function network element, the third request message being used to obtain a second private Internet Protocol address of a terminal device, the third request message including a public address and a port number of the terminal device; determining the second private address of the terminal device based on the public address and the port number; and sending a third response message to the network open function network element, the third response message including the second private address.
[0036] In a fourth aspect, the present application provides a communication method. The method may be executed by a user plane function network element, or by a component of the user plane function network element (eg, a chip or circuit), which is not limited in the present application.
[0037] The communication method includes: receiving a fourth request message from a network open function network element, the fourth request message including a first public Internet Protocol address of a terminal device; determining, based on the public address, at least one private address corresponding to the public address, and a port number corresponding to the at least one private address; and sending a fourth response message to the network open function network element, the fourth response message including the at least one private address and the port number corresponding to the at least one private address.
[0038] Alternatively, a subscription request message is received from the network open function network element, wherein the subscription request message includes a first public Internet interconnection protocol address of the terminal device; and one or more subscription response messages are sent to the network open function network element, wherein the one or more subscription response messages include at least one private address corresponding to the public address and a port number corresponding to the at least one private address.
[0039] In a fifth aspect, the present application provides a communication method. The method can be executed by a user plane function network element, or by a component of the user plane function network element (such as a chip or circuit), and the present application does not limit this.
[0040] The communication method includes: receiving a fifth request message from a network open function network element, the fifth request message including a first private Internet Protocol address of a terminal device, a public address of the terminal device, and a port number, the fifth request message being used to request the user plane function network element to determine whether the first private address is valid; determining whether the first private address is valid based on a locally stored correspondence between the private address, the public address, and the port number; and sending a fifth response message to the network open function network element, the fifth response message being used to indicate whether the first private address is valid.
[0041] In combination with the fifth aspect, in certain implementations of the fifth aspect, determining whether the first private address is valid based on the correspondence between the locally stored private address, public address and port number includes: determining the public address and port number corresponding to the first private address based on the correspondence and the first private address; if the public address and port number corresponding to the first private address are the same as the public address and port number, the fifth response message is used to indicate that the first private address is valid; otherwise, the fifth response message is used to indicate that the first private address is invalid.
[0042] In combination with the fifth aspect, in certain implementations of the fifth aspect, determining whether the first private address is valid based on the correspondence between the locally stored private address, public address and port number includes: based on the correspondence and the first private address, determining that the public address and port number corresponding to the first private address cannot be obtained, then the fifth response message is used to indicate that the first private address is invalid.
[0043] In combination with the fifth aspect, in certain implementations of the fifth aspect, determining whether the first private address is valid based on the correspondence between the locally stored private address, public address and port number includes: determining the private address corresponding to the public address and the port number based on the correspondence, the public address and the port number; if the private address corresponding to the public address and the port number is the same as the first private address and port number, the fifth response message is used to indicate that the first private address is valid; otherwise, the fifth response message is used to indicate that the first private address is invalid.
[0044] In a sixth aspect, a communication device is provided for implementing the method described in the first aspect. The device includes a transceiver unit and a processing unit, wherein the transceiver unit is used to send and receive information, and the processing unit is used to perform internal processing actions.
[0045] In a seventh aspect, a communication device is provided for implementing the method described in the second aspect. The device includes a transceiver unit and a processing unit, wherein the transceiver unit is used to send and receive information, and the processing unit is used to perform internal processing actions.
[0046] In an eighth aspect, a communication device is provided for implementing the methods described in the third to fifth aspects. The device includes a transceiver unit and a processing unit, wherein the transceiver unit is used to send and receive information, and the processing unit is used to perform internal processing actions.
[0047] In a ninth aspect, the present application provides a communication method. The method can be executed by an edge application server or by a component of the edge application server (such as a chip or circuit), and the present application does not limit this.
[0048] The communication method includes: receiving second indication information from an edge enabling server, wherein the second indication information is used to indicate whether the edge enabling client in the terminal device and / or the terminal device are authenticated; when the edge enabling client and / or the terminal device are not authenticated, sending a sixth request message to the edge enabling server, wherein the sixth request message is used to obtain an identifier of the terminal device, and the sixth request message includes a public address and port number of the terminal device.
[0049] Based on the above scheme, before obtaining the identifier of the terminal device from the edge enabling server, the edge application server can determine whether the edge enabling client and / or the terminal device have been authenticated based on the second indication information received from the edge enabling server. If the edge enabling client and / or the terminal device have not been authenticated, the edge application server can carry the public address and port number of the terminal device in the request message for obtaining the identifier of the terminal device, so that the edge enabling server obtains the identifier of the terminal device based on the public address and port number of the terminal device, avoiding the failure to obtain the identifier of the terminal device based on the private address of the terminal device when the edge enabling client and / or the terminal device are not authenticated, or avoiding obtaining the identifier of the wrong terminal device.
[0050] In combination with the ninth aspect, in certain implementations of the ninth aspect, before receiving the second indication information from the edge enabling server, the method further includes: sending a seventh request message to the edge enabling server, the seventh request message being used to obtain the identifier of the terminal device, the seventh request message including the public address of the terminal device; the receiving of the second indication information from the edge enabling server includes: receiving a seventh response message from the edge enabling server, the seventh response message being used to indicate that the identifier acquisition of the terminal device failed, and the seventh response message including the second indication information.
[0051] In combination with the ninth aspect, in certain implementations of the ninth aspect, the seventh request message includes third indication information, and the third indication information is used to indicate that the edge application server has the ability to obtain the identifier of the terminal device through the edge enabling client.
[0052] In a tenth aspect, the present application provides a communication method. The method can be executed by an edge-enabled server or by a component of the edge-enabled server (such as a chip or circuit), and the present application does not limit this.
[0053] The communication method includes: sending second indication information to the edge application server, wherein the second indication information is used to indicate whether the edge-enabled client in the terminal device and / or the terminal device are authenticated; when the edge-enabled client and / or the terminal device are not authenticated, receiving a sixth request message from the edge application server, wherein the sixth request message is used to obtain an identifier of the terminal device, and the sixth request message includes a public address and port number of the terminal device.
[0054] In combination with the tenth aspect, in certain implementations of the tenth aspect, before sending the second indication information to the edge application server, the method also includes: receiving a seventh request message from the edge application server, the seventh request message being used to obtain an identifier of the terminal device, the seventh request message including the public address of the terminal device; sending the second indication information to the edge application server includes: sending a seventh response message to the edge application server, the seventh response message being used to indicate that the identifier of the terminal device has failed to be obtained, and the seventh response message including the second indication information.
[0055] In combination with the tenth aspect, in some implementations of the tenth aspect, the seventh request message includes third indication information, and the third indication information is used to indicate that the edge application server has the ability to obtain the identifier of the terminal device through the edge enabling client.
[0056] In combination with the tenth aspect, in certain implementations of the tenth aspect, before determining whether the edge-enabled client in the terminal device and / or the terminal device is authenticated, the method further includes: determining whether the edge application server has the ability to obtain the identifier of the terminal device through the edge-enabled client.
[0057] In an eleventh aspect, a communication device is provided for implementing the method of the ninth aspect. The device comprises a transceiver unit and a processing unit, wherein the transceiver unit is used to send and receive information, and the processing unit is used to perform internal processing actions.
[0058] In a twelfth aspect, a communication device is provided for implementing the method shown in the tenth aspect. The device includes a transceiver unit and a processing unit, wherein the transceiver unit is used to send and receive information, and the processing unit is used to perform internal processing actions.
[0059] In a thirteenth aspect, the present application provides a communication method. The method can be executed by an edge-enabled server or by a component of the edge-enabled server (such as a chip or circuit), and the present application does not limit this.
[0060] The communication method includes: receiving a first request message from a terminal device, the first request message being used to obtain an identifier of the terminal device, the first request message including a first private address of the terminal device; determining whether an edge-enabled client of the terminal device and / or the terminal device is authenticated; and if the edge-enabled client and / or the terminal device are not authenticated, obtaining a public address and a port number of the terminal device, and obtaining an identifier of the terminal device based on the public address and the port number.
[0061] Based on the above scheme, after receiving the first request message from the terminal device to obtain the identifier of the terminal device, the edge enabling server can determine whether the edge enabling client of the terminal device and / or the terminal device are authenticated. If not authenticated, the edge enabling server can obtain the public address and port number of the terminal device, and obtain the identifier of the terminal device based on the public address and port number, thereby avoiding obtaining the identifier of the terminal device based on the first private address of the terminal device when it is not authenticated, thereby improving security.
[0062] In combination with the thirteenth aspect, in some implementations of the thirteenth aspect, the method further includes: sending a first response message to the terminal device, the first response message including an identifier of the terminal device.
[0063] In a fourteenth aspect, a communication device is provided for implementing the method shown in the above-mentioned thirteenth aspect. The device includes: a transceiver unit and a processing unit, wherein the transceiver unit is used to send and receive information, and the processing unit is used to perform internal processing actions.
[0064] In the fifteenth aspect, a communication system is provided, including an edge enabling server, a network open function network element and a user plane function network element, wherein the edge enabling server is used to execute the method shown in the above-mentioned first aspect, the network open function network element executes the method shown in the above-mentioned second aspect, and the user plane function network element executes the method shown in the above-mentioned third aspect.
[0065] In the sixteenth aspect, a communication system is provided, including an edge application server and an edge enabling server, wherein the edge application server is used to execute the method shown in the above-mentioned ninth aspect, and the edge enabling server is used to execute the method shown in the above-mentioned tenth aspect.
[0066] In the seventeenth aspect, a communication device is provided, which includes: a memory for storing programs; a processor for executing the programs stored in the memory, and when the programs stored in the memory are executed, the processor is used to execute the methods provided in the above aspects.
[0067] In the eighteenth aspect, the present application provides a processor for executing the methods provided in the above aspects. In the process of executing these methods, the process of sending the above information and obtaining / receiving the above information in the above methods can be understood as the process of the processor outputting the above information, and the process of the processor receiving the input above information. When outputting the above information, the processor outputs the above information to the transceiver so that the transceiver can transmit it. After being output by the processor, the above information may also need to undergo other processing before reaching the transceiver. Similarly, when the processor receives the input above information, the transceiver obtains / receives the above information and inputs it into the processor. Furthermore, after the transceiver receives the above information, the above information may need to undergo other processing before being input into the processor.
[0068] Based on the above principles, for example, the receiving request message mentioned in the above method can be understood as the processor receiving input information.
[0069] For the operations such as transmission, sending and acquisition / reception involved in the processor, unless otherwise specified, or if they do not conflict with their actual functions or internal logic in the relevant descriptions, they can be more generally understood as processor output, reception, input and other operations, rather than the transmission, sending and receiving operations directly performed by the RF circuit and antenna.
[0070] During implementation, the processor may be a processor specifically configured to execute these methods, or may be a processor that executes computer instructions in a memory to execute these methods, such as a general-purpose processor. The memory may be a non-transitory memory, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on separate chips. The embodiments of the present application do not limit the type of memory or the configuration of the memory and the processor.
[0071] In a nineteenth aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, and the program code includes a method for executing the methods provided in the above aspects.
[0072] In the twentieth aspect, a computer program product comprising instructions is provided, which, when run on a computer, enables the computer to execute the methods provided in the above aspects.
[0073] In the twenty-first aspect, a chip is provided, which includes a processor and a communication interface. The processor reads instructions stored in a memory through the communication interface to execute the methods provided in the above aspects.
[0074] Optionally, as an implementation method, the chip may further include a memory storing instructions, and the processor is used to execute the instructions stored in the memory. When the instructions are executed, the processor is used to execute the methods provided in the above aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0075] FIG1 is a schematic diagram of the architecture of a communication system 100 used in an embodiment of the present application.
[0076] FIG2 is a schematic diagram of the architecture of a communication system 200 used in an embodiment of the present application.
[0077] FIG3 is a schematic flow chart of the EEC calling the UE identifier API.
[0078] FIG4 is a schematic flow chart of an EES acquiring a UE identifier.
[0079] FIG5 is a schematic flow chart of IP address verification provided by an EEC according to the present application.
[0080] FIG6 is a schematic flow chart of a communication method provided in this application.
[0081] (a) in Figure 7 is a schematic diagram of the UPF performing NAT provided by this application.
[0082] (b) in FIG7 is a schematic flowchart of another communication method provided in the present application.
[0083] FIG8 is a schematic flowchart of another communication method provided in this application.
[0084] FIG9 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application.
[0085] FIG10 is a schematic diagram of another communication device 20 provided in an embodiment of the present application.
[0086] FIG11 is a schematic diagram of a chip system 30 provided in an embodiment of the present application. DETAILED DESCRIPTION
[0087] The technical solution in this application will be described below with reference to the accompanying drawings.
[0088] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as the fifth generation (5 thgeneration, 5G) mobile communication system, new radio access technology (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), or world-wide interoperability for microwave access (WiMAX) communication system. Among them, the mobile communication system may include non-standalone (NSA) and / or standalone (SA). Alternatively, the technical solution provided in this application may be applied to future communication systems, such as the sixth generation mobile communication system. This application is not limited to this.
[0089] The technical solution provided in this application can also be applied to machine type communication (MTC), long term evolution technology for machine-to-machine communication (LTE-M), device-to-device (D2D) network, machine-to-machine (M2M) network, internet of things (IoT) network or other networks. Among them, IoT network can include, for example, Internet of Vehicles. Among them, the communication mode in the Internet of Vehicles system is collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication or vehicle to network (V2N) communication, etc.
[0090] The technical solutions of this application can be applied to various communication scenarios, such as service continuity scenarios and mobile edge computing (MEC) scenarios, and are not limited by this application. MEC can utilize wireless access networks to provide telecom users with the services and cloud computing capabilities they need nearby, creating a telecom-grade service environment with high performance, low latency, and high bandwidth. This accelerates the download of various content, services, and applications on the network, allowing consumers to enjoy an uninterrupted, high-quality network experience.
[0091] FIG1 is a schematic diagram of the architecture of a communication system 100 used in an embodiment of the present application. As shown in FIG1 , the communication system includes a terminal 110, a core network 120, an edge data network (EDN) 130, and an edge configuration server (ECS) 140. The terminal 110 may be deployed with one or more application clients (ACs) 111 and one or more edge enabler clients (EECs) 112, and the EDN 130 may be deployed with one or more edge application servers (EASs) 131 and one or more edge enabler servers (EESs) 132.
[0092] Among them, the EDGE-1 interface is the interface between EES 132 and EEC 112, the EDGE-2 interface is the interface between EES 132 and core network 120, the EDGE-3 interface is the interface between EAS 131 and EES 132, the EDGE-4 interface is the interface between EEC 112 and ECS 140, the EDGE-5 interface is the interface between AC 111 and EEC 112, the EDGE-6 interface is the interface between EES 132 and ECS 140, the EDGE-7 interface is the interface between EAS 131 and core network 120, the EDGE-8 interface is the interface between ECS 140 and core network 120, and the EDGE-9 interface is the interface between EES 132. Figure 1 is only a schematic diagram, and the communication system may also include other network devices, which are not shown in Figure 1.
[0093] Application users sign a service agreement with the application provider, which provides services to the application users. Application users can log in to the AC111 on the terminal 110 and communicate with the EAS131 through the AC111. The EEC112 is a middleware layer, generally located in the operating system or between the AC111 and the operating system. The AC111 can obtain edge-enabling services from the EEC112 in the form of an application programming interface (API).
[0094] The architecture shown in Figure 1 can be used by terminal devices in a 3rd Generation Partnership Project (3GPP) network to discover edge applications deployed near the edge. The functional entities in this architecture are briefly described as follows:
[0095] 1. EDN: It is a local data network that includes EES and EAS.
[0096] One understanding is that EDN corresponds to only one data network, which is a special local data network that includes edge enabling functions. It can be identified by the data network access identifier (DNAI) and the data network name (DNN) and is a network logical concept.
[0097] Another way to understand it is that EDN is the equivalent concept of the central cloud, which can be understood as a local data center (geographical location concept), can be identified by DNAI, and can contain one or more local data networks.
[0098] 2. EAS: An application deployed in an EDN can be called an EAS. Specifically, EAS can refer to an instance of a server application (e.g., social media software, augmented reality (AR), virtual reality (VR)) deployed and running on an EDN.
[0099] An application can deploy one or more EASs in one or more EDNs. EASs deployed and running in different EDNs can be considered different EASs for the same application. They can share a domain name and use the same IP address or different IP addresses.
[0100] EAS can also be called edge application, edge application server, application instance, edge application instance, MEC application, MEC application server, EAS function, etc., which is not limited in this application. For the convenience of description, it is collectively referred to as edge application server below.
[0101] 3. AC: This is the terminal-side counterpart of the application server, used by application users to obtain application services from the application server. The AC can be a client program applied on the terminal side, which can connect to the application server in the cloud to obtain application services, or to the EAS deployed and running in one or more EDNs to obtain application services. The AC can also be called an application client, which is not limited in this application.
[0102] 4. EES: Provides necessary functions for ECS and EAS, such as providing configuration information to EEC, enabling UE to exchange application data with EAS, and supporting the transfer of application context. EES can interact directly or indirectly with the 3GPP network. EAS can initiate a registration process with EES to register EAS information with the EES. Alternatively, EAS information can be registered with the EES through a management system, and the EES manages EASs registered with the EES.
[0103] It also provides enabling capabilities for the EAS deployed in the EDN. The EES supports edge application server registration, terminal authentication and authorization, and provides terminals with edge application server IP address information. The EES also supports obtaining edge application server identifiers and IP address information and sending this information to the ECS. The EES is deployed in the EDN.
[0104] Generally, an EAS is registered on an EES, or an EAS information is configured on an EES through a management system. The EES is called the EES associated with the EAS, or the EAS is called the EAS associated with the EES. The EES controls or manages the EAS registered or configured on the EES.
[0105] The EAS associated with EES can also be replaced with the EAS corresponding to the EES, and the EES associated with EAS can also be replaced with the EES corresponding to the EAS. This application is not limited.
[0106] 5. EEC: Used to discover available EASs in the EDN network. It is the terminal-side counterpart of EES. The EEC can register EEC and AC information with the EES, perform security authentication and authorization, obtain the EAS IP address from the EES, and provide edge computing capabilities to the AC. For example, the EEC can return the EAS IP address to the AC through the EAS discovery service.
[0107] 6. ECS: Used to provide EES information to EEC, and can be deployed by operators or third parties. Application users communicate through the connection between the application client and EAS. The edge enabling client is a middleware layer, generally located in the operating system, or between the application client and the operating system. AC can obtain edge enabling services from EEC in the form of API. ECS is mainly responsible for the configuration of EDN. For example, ECS can provide EES information to the terminal. For another example, ECS can also interact with the application's DNS to obtain EAS information and provide EAS information directly to the terminal. ECS can also obtain and save EAS and IP address information from other functional entities.
[0108] 7. Terminal: It can also be called terminal equipment, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver function, wearable device, vehicle, drone, helicopter, airplane, ship, robot, robotic arm, smart home device, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal.
[0109] The core network 120 shown in FIG1 may be a system architecture of a 5G core network (5G core, 5GC). The system architecture of 5GC is briefly introduced below in conjunction with FIG2 .
[0110] Figure 2 is a schematic diagram of a network architecture 200 provided in this application, taking the 5G network architecture based on a service-oriented architecture in a non-roaming scenario defined in the 3GPP standardization process as an example. As shown in the figure, the network architecture can include three parts: the terminal device part, the DN, and the operator network public land mobile network (PLMN) part. The functions of the network elements in each part are briefly described below.
[0111] The terminal device part may include a terminal device 210. The terminal device 210 is described with reference to the description of the terminal 110 in FIG. 1 , and will not be described again here.
[0112] The operator network PLMN part may include but is not limited to the (radio) access network (R)AN) 220 and the core network (CN) part.
[0113] (R)AN 220 can be considered a subnetwork of the operator network, serving as the implementation system between service nodes (e.g., network elements providing services) in the operator network and terminal device 210. To access the operator network, terminal device 210 first passes through (R)AN 220, which then connects to service nodes in the operator network. The access network device (RAN device) in the embodiment of the present application is a device that provides wireless communication functions for the terminal device 210, and can also be called a network device. The RAN device includes but is not limited to: the next generation node base station (gNB) in the 5G system, the evolved node B (eNB) in the long term evolution (LTE), the radio network controller (RNC), the node B (NB), the base station controller (BSC), the base transceiver station (BTS), the home base station (for example, home evolved node B, or home node B, HNB), the base band unit (BBU), the transmission point (TRP), the transmitting point (TP), the small base station device (pico), the mobile switching center, or the network device in the future network. In systems using different wireless access technologies, the name of the device with the access network device function may be different. For the convenience of description, in all embodiments of the present application, the above-mentioned device that provides wireless communication functions for the terminal device 210 is collectively referred to as the access network device or simply referred to as RAN or AN. It should be understood that this document does not limit the specific type of access network equipment.
[0114] The CN part may include but is not limited to the following NFs: user plane function (UPF) 230, network exposure function (NEF) 231, network function repository function (NRF) 232, policy control function (PCF) 233, unified data management function (UDM) 234, unified data repository function (UDR) 235, binding support function (BSF) 236, authentication server function (AUSF) 237, access and mobility management function (AMF) 238, session management function (SMF) 239.
[0115] Data network DN 240, also known as a packet data network (PDN), is typically located outside of a carrier network, such as a third-party network. Of course, in some implementations, the DN may also be deployed by the carrier. This application does not restrict whether the DN is deployed by the carrier. A carrier network PLMN can access multiple data network DNs 240. Multiple services can be deployed on the data network DN 240, providing data and / or voice services to the terminal device 210. For example, data network DN 240 may be the private network of a smart factory. Sensors installed in the workshop of the smart factory may be terminal devices 210. A control server for the sensors is deployed in data network DN 240, and the control server can provide services to the sensors. The sensors can communicate with the control server, obtain instructions from the control server, and transmit collected sensor data to the control server according to the instructions. For another example, data network DN 240 may be the internal office network of a company. The mobile phones or computers of employees of the company may be terminal devices 210, and the employees' mobile phones or computers can access information and data resources on the company's internal office network. Terminal device 210 can establish a connection with the operator network through an interface provided by the operator network (e.g., N1) and use data and / or voice services provided by the operator network. Terminal device 210 can also access data network DN 240 through the operator network and use operator services deployed on data network DN 240 and / or services provided by third parties.
[0116] The following is a brief description of the NF functions included in CN.
[0117] 1. UPF: This is a gateway provided by the operator, serving as the gateway for communication between the operator network and the data network DN 240. The UPF includes user-plane-related functions such as packet routing and transmission, packet inspection, service usage reporting, quality of service (QoS) processing, lawful interception, uplink packet inspection, and downlink packet storage.
[0118] 2. NEF: It is a control plane function provided by the operator. It mainly enables third parties to use the services provided by the network, supports the network to open its capabilities, event and data analysis, provides PLMN security configuration information from external applications, and converts interactive information inside and outside the PLMN. It provides an API interface open to the operator network and provides interaction between external servers and internal operator networks.
[0119] 3. NRF: This is a control plane function provided by the operator, which is used to maintain real-time information about network functions and services in the network. For example, it supports network service discovery, maintains the services supported by the NF profile of the NF instance, supports service discovery of the service communication proxy (SCP), maintains the SCP profile of the SCP instance, sends notifications about newly registered, deregistered, and updated NFs and SCPs, and maintains the health status of NF and SCP operations.
[0120] 4. PCF: It is a control plane function provided by the operator. It supports a unified policy framework to govern network behavior, provide policy rules to other control functions, and provide contract information related to policy decisions.
[0121] 5. UDM: It is a control plane function provided by the operator, responsible for storing information such as the subscriber permanent identifier (SUPI) of the subscriber in the operator network, the generic public subscription identifier (GPSI) of the subscriber, and credentials. The SUPI will be encrypted during transmission, and the encrypted SUPI is called the hidden subscriber subscription identifier (SUCI). The information stored in the UDM can be used for authentication and authorization of the terminal device to access the operator network. The subscribers of the above-mentioned operator network can specifically be users who use the services provided by the operator network, such as users who use China Telecom's subscriber identity module (SIM) card, or users who use China Mobile's SIM card. The credentials of the above-mentioned subscribers can be a small file storing long-term keys stored in the SIM card or information related to SIM card encryption, which is used for authentication and / or authorization. It should be noted that the permanent identifier, credentials, security context, authentication data (cookie), and token are equivalent to information related to verification / authentication and authorization. In the embodiment of this application, for the sake of convenience of description, no distinction or restriction is made.
[0122] 6. UDR: It is a control plane function provided by the operator. It provides the functions of storing and retrieving subscription data for UDM, storing and retrieving policy data for PCF, and storing and retrieving user NF group ID information.
[0123] 7. BSF: Mainly used to store the internal information corresponding to the selected PCF. Specifically, for a Protocol Data Unit (PDU) session, the internal information stored by the BSF includes the user identifier (such as SUPI), DNN, UE address (IP address or MAC address), etc. For a UE, the internal information stored by the BSF includes the user identifier, the selected PCF address, etc. In this application, the BSF is mainly responsible for session information binding. Therefore, in this application, the BSF can also be understood as a network element with a session information binding function. The network element with a session information binding function is called BSF for example. There may be other network element names in the future, and this application does not limit this.
[0124] 8. AUSF: This is a control plane function provided by the operator, typically used for primary authentication, i.e., authentication between the terminal device 110 (subscriber) and the operator's network. After receiving an authentication request initiated by a subscriber, the AUSF can authenticate and / or authorize the subscriber using the authentication information and / or authorization information stored in the UDM, or generate authentication and / or authorization information for the subscriber through the UDM. The AUSF can also provide feedback on the authentication and / or authorization information to the subscriber.
[0125] 9. AMF: It is a control plane network function provided by the operator network, responsible for access control and mobility management of terminal devices accessing the operator network, such as mobile state management, allocation of user temporary identity, authentication and authorization of users, etc.
[0126] AMF is used to establish NAS connection with UE and has the same 5G NAS security context as UE. 5G NAS security context includes K AMF NAS layer keys include the NAS encryption key and the NAS integrity protection key, which are used for confidentiality protection and integrity protection of NAS messages, respectively.
[0127] 10. SMF: It is a control plane network function provided by the operator network and is responsible for managing the PDU session of the terminal device. The PDU session is a channel for transmitting PDUs. The terminal device needs to transmit PDUs to and from the data network DN through the PDU session. The SMF is responsible for establishing, maintaining, and deleting PDU sessions. The SMF includes session management (such as session establishment, modification, and release, including tunnel maintenance between the user plane function UPF 130 and the (R)AN 120), UPF selection and control, service and session continuity (SSC) mode selection, roaming, and other session-related functions.
[0128] 11. AF: This is a control plane network function provided by the operator network. It is used to provide application layer information. It can interact with the policy framework through network open function elements or directly interact with the policy framework to make policy decision requests. It can be located inside or outside the operator network.
[0129] It is understood that the above network elements or functions can be physical entities in hardware devices, software instances running on dedicated hardware, or virtualized functions instantiated on a shared platform (e.g., a cloud platform). Simply put, an NF can be implemented by hardware or software.
[0130] In Figure 2, Nnef, Nnrf, Npcf, Nudm, Nudr, Nnwdaf, Nausf, Namf, Nsmf, N1, N2, N3, N4, and N6 are interface serial numbers. For example, the meaning of the above interface serial numbers can be found in the meaning defined in the 3GPP standard protocol, and this application does not limit the meaning of the above interface serial numbers. It should be noted that the interface name between the various network functions in the figure is only an example. In a specific implementation, the interface name of the system architecture may also be other names, which is not limited by this application. In addition, the name of the message (or signaling) transmitted between the above network elements is only an example and does not constitute any limitation on the function of the message itself.
[0131] For ease of explanation, in the embodiments of this application, network functions (such as NEFs, SMFs, etc.) are collectively referred to as NFs. That is, the NFs described later in the embodiments of this application can be replaced with any network function. Furthermore, Figure 2 only schematically illustrates some network functions, and the NFs described later are not limited to the network functions shown in Figure 2.
[0132] It should be understood that the above-mentioned network architecture applied to the embodiment of the present application is only a network architecture described from the perspective of service-oriented architecture. The network architecture applicable to the embodiment of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiment of the present application.
[0133] It should also be understood that the AMF, SMF, UPF, NEF, AUSF, NRF, PCF, and UDM shown in the figure can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.
[0134] It should also be understood that the above naming is defined only to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other future networks. For example, in a 6G network, some or all of the above network elements may continue to use the terminology used in 5G, or may adopt other names.
[0135] To facilitate understanding of the embodiments of the present application, some basic concepts involved in the present application are briefly explained.
[0136] 1. Local Data Network (local DN): This can be an access point to a data network that is very close to the user's attachment point.
[0137] 2. Application context: This refers to the operational status information associated with one or a group of users, such as game progress, historical ML data, etc. Optionally, the application context may also include the subscription context of the one or more users in the EAS and the core network, such as the subscription transaction identifier. Optionally, the application context may also include the context of the one or more users on the EES, such as the transaction identifier of the EAS subscription to the one or more users.
[0138] 3. UE Identifier API: To obtain the identifier that uniquely identifies the UE (also known as the UE ID), EES opens the UE Identifier API to EAS and EEC. The UE Identifier API is used by EAS or EEC to obtain the UE's identity from EES. The EEC calling the UE Identifier API can be used in the following scenarios:
[0139] When EAS directly calls the UE identifier API to EES and fails to obtain the UE ID due to the use of Network Address Translation (NAT), EAS can choose to send signaling to AC to enable AC to initiate a UE ID query to EEC. Further, EEC uses the IP address allocated by the core network (such as IPv4 and / or IPv6) to call the UE identifier API of EES to obtain the UE identifier, and sends the obtained UE identifier to EAS through AC.
[0140] For ease of understanding, the following briefly describes the process of the EEC calling the UE identifier API with reference to Figure 3. Figure 3 is a schematic flow chart of the EEC calling the UE identifier API, including the following steps:
[0141] S310, the EEC sends a UE identifier API request to the EES.
[0142] The UE identifier API request includes the UE private IP address, which is the IP address provided by the core network to the UE (it can be an IPv4 address or an IPv6 address).
[0143] S320: The EES obtains a UE identifier.
[0144] Specifically, the EES obtains the UE identifier from the core network according to the UE private IP address in the UE identifier API request. How the EES obtains the UE identifier (ID) will be described in detail below in conjunction with FIG4 , and will not be repeated here.
[0145] S330 , the EES sends a UE identifier API response to the EEC.
[0146] The UE identifier API response includes a UE identifier, which is the UE identifier obtained in step S320 above.
[0147] FIG4 is a schematic flow chart of an EES obtaining a UE identifier, including the following steps:
[0148] S410, AF sends a request message #A to NEF.
[0149] The request message #A is used to request the UE ID. For example, the AF requests the UE ID through the Nnef_UEId_Get service operation.
[0150] The request message #A should include the UE address (such as IP address or MAC address) and AF identifier, and may also include the port number associated with the IP address, application port ID, IP domain, etc.
[0151] Optionally, AF can also provide the corresponding data network name (Data Network Name, DNN) and / or single network slice selection assistance information (S-NSSAI).
[0152] S420, NEF authorizes the AF request.
[0153] If the NEF does not authorize the AF request, the NEF returns a result value to the AF, indicating that the authorization failed; otherwise, the NEF continues to perform the following steps.
[0154] Optionally, the NEF determines the corresponding DNN and / or S-NSSAI information: the DNN and / or S-NSSAI may be provided by the AF, or determined by the NEF based on the AF identifier in the request message #A.
[0155] If the NEF receives the port number in step S410, then, depending on the configuration, the NEF can determine whether the received address is a different IP address from the actual private UE IP address assigned by the 5GC. If so, the NEF executes steps S430 to S460. Otherwise, steps S430 to S460 are skipped.
[0156] S430, NEF sends a request message #B to NRF.
[0157] The request message #B is used to obtain the address of the UPF that implements the NAT function for the UE (public) IP address. For example, the NEF uses the Nnrf_NFDiscovery service operation to obtain the address of the UPF that implements the NAT function.
[0158] The request message #B includes the UE (public network) IP address, and may also include the DNN and S-NSSAI associated with the AF ID, as well as the IP domain, etc.
[0159] S440, NRF sends a response message #B to NEF.
[0160] The response message #B responds to the request message #B, and includes the address of the UPF that implements the NAT function for the UE (public) IP address. For example, the NRF sends an Nnrf_NFDiscovery response message to the NEF.
[0161] S450, NEF sends a request message #C to UPF.
[0162] The request message #C is used to obtain the UE (private) IP address. For example, the NEF sends the Nupf_GetPrivateUEIP_Get service operation to the UPF.
[0163] The request message #C includes the UE (public) IP address and port number, and optionally the IP domain associated with the AF ID, DNN and S-NSSAI.
[0164] S460, UPF sends a response message #C to NEF.
[0165] The response message #C responds to the request message #C, and includes the UE's IP address and an optional IP domain. For example, the UPF sends a Nupf_GetPrivateUEIP_Get response message to the NEF.
[0166] If the UPF applies the NAT function, the UE IP address returned by the UPF is the UE's private IP address.
[0167] S470, NEF sends a request message #D to BSF.
[0168] The request message #D contains the UE address and IP domain and / or DNN and / or S-NSSAI to retrieve the UE's session binding information. For example, the NEF sends the Nbsf_Management_Discovery service operation to the BSF.
[0169] S480, BSF sends a response message #D to NEF.
[0170] The response message #D responds to the request message #D. If the response message #D does not carry the SUPI, the NEF replies to the AF with a Result value indicating that the UE ID is unavailable.
[0171] S490, NEF sends a request message #E to UDM.
[0172] The NEF interacts with the UDM, for example, to retrieve the AF-specific UE identifier via the Nudm_SDM_Get service operation. The request message #E includes at least one of the SUPI, the Application Port ID, or the AF identifier.
[0173] S491, UDM sends a response message #E to NEF.
[0174] The UDM responds to the NEF with an AF-specific UE identifier, which is represented as an external identifier of the UE and is uniquely associated with the application port ID, MTC provider information and / or AF identifier.
[0175] S492, NEF sends a response message #A to AF.
[0176] The NEF responds to the AF with the information received from the UDM (including the external identifier).
[0177] In addition, in order to facilitate understanding of the embodiments of the present application, the following explanations are made.
[0178] First, in this application, "used to indicate" can include being used for direct indication and being used for indirect indication. When describing that a certain indication information is used to indicate A, it can include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must include A.
[0179] The information indicated by the indication information is referred to as the information to be indicated. During the specific implementation process, there are many ways to indicate the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately. The transmission period and / or transmission timing of these sub-information can be the same or different. The specific transmission method is not limited in this application. The transmission period and / or transmission timing of these sub-information can be predefined, for example, according to a protocol, or can be configured by the transmitting device through sending configuration information to the receiving device.
[0180] Second, "at least one" shown in the present application refers to one or more, and "a plurality of" refers to two or more. In addition, in the embodiments of the present application, "first", "second" and various digital numbers (for example, "#1", "#2", etc.) are only for the convenience of description and are not used to limit the scope of the embodiments of the present application. The size of the sequence number of each process below does not mean the order of execution. The execution order of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application. It should be understood that the objects described in this way can be interchanged where appropriate, so that the schemes other than the embodiments of the present application can be described. In addition, in the embodiments of the present application, words such as "510", "520" are only for the convenience of description and are not used to limit the order of execution of steps.
[0181] Third, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.
[0182] Fourth, the term "storage" used in the embodiments of this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, a processor, or a communication device. The memory may be any type of storage medium, and this application is not limited thereto.
[0183] Fifth, the "protocol" involved in the embodiments of the present application may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems. This application does not limit this.
[0184] Sixth, in the embodiments of the present application, "under the circumstances", "when", and "if" can sometimes be used interchangeably. It should be pointed out that when the distinction between them is not emphasized, the meanings they intend to express are consistent.
[0185] Seventh, in the embodiments of this application, various terms and English abbreviations, such as radio resource control (RRC), are provided for ease of description and should not constitute any limitation on this application. This application does not exclude the possibility of defining other terms in existing or future protocols that can achieve the same or similar functions.
[0186] Eighth, the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0187] The above, in conjunction with Figure 1, briefly describes the scenarios in which the communication method provided in the embodiments of the present application can be applied, as well as the basic concepts that may be involved in the embodiments of the present application. Within these basic concepts, Figures 3 and 4 are used to describe the process by which the EEC calls the UE identifier API. The current protocol stipulates that, regarding the process by which the EEC calls the UE identifier API, if the private IP address provided by the EEC is not verified or the EEC is not authorized to use the provided private IP address, a malicious EEC may use an IP address spoofing attack to obtain the identity of another UE. To prevent a malicious EEC from using an IP address spoofing attack to obtain the identity of another UE, one solution is for the EEC to provide IP address verification. This solution is briefly described below in conjunction with Figure 5.
[0188] FIG5 is a schematic flow chart of an EEC providing IP address verification provided by the present application, including the following steps:
[0189] S510: PDU session establishment.
[0190] In this embodiment, during PDU session establishment, the SMF or UPF generates a random ticket value during the UE IP address allocation process, sends the ticket value to the PCF, and then stores it in the BSF as part of the PDU session binding information. In addition to the private IP address, the ticket value is also sent to the UE.
[0191] S520, UE sends message #1 to EES.
[0192] This message #1 includes the above-mentioned ticket value and private IP address.
[0193] S530, EES calls the UE identifier.
[0194] Specifically, the EES invokes the Nnef_UEId GET service operation with the ticket value and the private IP address. The NEF sends the received ticket value to the BSF in the Nbsf_Management_Discovery service operation. The BSF verifies the ticket value by checking the mapping between the ticket value and the IP address. If successful, the NEF provides the EES with the AF-specific GPSI.
[0195] However, the solution shown in FIG5 needs to modify the existing PDU session establishment process, affecting the UE, SMF and BSF network elements.
[0196] The present application provides a communication method that can be applied in the communication system shown in Figure 1, in order to achieve security protection for EEC calling UE identifier API without affecting the PDU session establishment process.
[0197] It should be understood that the embodiments shown below do not particularly limit the specific structure of the execution subject of the method provided in the embodiments of the present application. As long as it is possible to communicate according to the method provided in the embodiments of the present application by running a program that records the code of the method provided in the embodiments of the present application. For example, the execution subject of the method provided in the embodiments of the present application may be a network element, or a functional module in the network element that can call and execute the program.
[0198] FIG6 is a schematic flow chart of a communication method provided by the present application, which includes the following steps:
[0199] S601: A connection is established between the edge application server and the application client.
[0200] For example, in this embodiment, one possible way to establish a connection between the edge application server and the application client is as follows: when a terminal user needs to obtain a service, the terminal user can operate the application client in the terminal device (e.g., click the application client) so that the application client sends a connection establishment request to the application server providing the service, thereby establishing a connection with the application server. If the application server providing the service obtained by the terminal device is an edge application server, the application client establishes a connection with the edge application server.
[0201] The edge application server can be the EAS shown in Figure 1 above. It should be understood that the name of the edge application server is not limited in this embodiment, and any device that can implement the functions of the edge application server in this embodiment can be considered the edge application server involved in this embodiment. For ease of description, the following explanation uses the EAS as an example.
[0202] Alternatively, the application client may be the AC shown in FIG1 above. It should be understood that the name of the application client is not limited in this embodiment; any device capable of implementing the functions of the application client in this embodiment may be considered an application client in this embodiment. For ease of description, the following description uses the AC as an example application client.
[0203] S602: A connection is established between the edge-enabled client and the edge-enabled server.
[0204] Exemplarily, in this embodiment, a possible way to establish a connection between the edge usage client and the edge enabling server is as follows: when the application client in the terminal device in step 601 needs to discover the application server providing the service, the application client sends a message to the edge enabling client, so that the edge enabling client interacts with the edge configuration function to obtain information about the edge enabling server, and further establishes a connection between the edge enabling client and the edge enabling server. Exemplarily, the connection can be a connection based on transport layer security, wherein the establishment of the secure connection can be based on one-way authentication of the certificate of the edge enabling server, or based on Generic Bootstrapping Architecture (GBA), or based on Authentication and Key Management for Applications (AKMA).
[0205] The edge-enabling client may be the EEC shown in FIG1 above. It should be understood that the name of the edge-enabling client is not limited in this embodiment, and any device that can implement the functions of the edge-enabling client in this embodiment can be considered as the edge-enabling client involved in this embodiment. For ease of description, the following description uses the edge-enabling client as an example.
[0206] The edge enabling server may be the EES shown in FIG1 above. It should be understood that the name of the edge enabling server is not limited in this embodiment, and any device that can implement the functions of the edge enabling server in this embodiment can be considered the edge enabling server involved in this embodiment. For ease of description, the following description uses the EES as an example.
[0207] S610, the EAS sends a request message #1 to the AC, or in other words, the AC receives the request message #1 from the EAS.
[0208] Specifically, in this embodiment, when the EAS determines to obtain the UE identifier through the EEC, the EAS sends a request message #1 to the AC. This request message #1 is used to obtain the UE identifier. For example, when the EAS directly calls the UE identifier API from the EES, if the EAS fails to obtain the UE ID due to the use of NAT, the EAS may choose to send signaling to the AC to cause the AC to initiate a UE ID query with the EEC. The EEC then calls the EES UE identifier API to obtain the UE identifier and sends the obtained UE identifier to the EAS via the AC.
[0209] It should be noted that this embodiment does not limit the reason for EAS to initiate a UE identifier acquisition request to AC. The above-mentioned failure of EAS to directly call the UE identifier API to EES to obtain the UE ID is only an example and does not constitute any limitation on the scope of protection of this application. EAS can also initiate a UE identifier acquisition request to AC in other scenarios. For example, EAS is configured to obtain the UE identifier through AC, which will not be explained one by one here.
[0210] S620: The AC sends a request message #2 to the EEC, or in other words, the EEC receives the request message #2 from the AC.
[0211] Specifically, the AC sends a request message #2 to the EEC to obtain the UE ID based on the request message #1 from the EAS. Request message #2 includes the EAS identifier (ID). For the definition of request message #2, refer to the current protocol (e.g., Section 8.14.2.6 of 3GPP TS 23.558) regarding the request message sent by the AC to the EEC to obtain the UE ID. This is not described in detail in this embodiment.
[0212] Furthermore, after the EEC receives the request message #2 for obtaining the UE ID sent by the AC, it sends a first UE identifier API request message to the edge enabling server. The method shown in FIG6 further includes:
[0213] S630: The EEC sends a first request message to the EES, or in other words, the EES receives the first request message from the EEC, wherein the first request message is used to obtain an identifier of the terminal device.
[0214] Optionally, the first request message is a first UE identifier API request message. For the sake of convenience of description, the following description takes the first request message as an example of the first UE identifier API request message. However, the specific form of the first request message is not limited in the embodiment of the present application. It can also be a message sent by other EECs to the edge enabling server that can be used to obtain the identifier of the terminal device.
[0215] In addition, it should be noted that the EEC is a terminal device, so the above-mentioned EEC sending the first request message to the EES can also be understood as the terminal device sending the first request message to the EES.
[0216] Specifically, the first UE identifier API request message includes the first private address and EAS ID of the terminal device. The first private address of the terminal device can be used to identify the terminal device in the 5GC network, including but not limited to the first private IP address of the terminal device. For the sake of convenience of description, the following description takes the first private address of the terminal device as the first private IP address as an example, but the specific form of the first private address is not limited in the embodiment of the present application, and can also be other addresses that can identify the terminal device in the 5GC network (such as MAC address, etc.).
[0217] It should be noted that the first UE identifier API request message is sent to EES via UPF. If UPF performs NAT processing, the first private IP address of the received IP data packet containing the first UE identifier API request message will be replaced with the public IP address of the UE, and the port number will be set to the port number that identifies the terminal device under the public IP address.
[0218] For ease of understanding, the following briefly describes how the UPF performs NAT processing in conjunction with Figure 7(a). As can be seen from Figure 7(a), the UPF can receive IP packets containing UE identifier API request messages from different EECs or UEs (e.g., UE / EEC 1 and UE / EEC 2 shown in Figure 7(a)). The private IP address of IP packet #1 sent by UE / EEC 1 is private IP address #1, and the private IP address of IP packet #2 sent by UE / EEC 2 is private IP address #2. After the UPF receives IP packet #1 sent by UE / EEC 1, if NAT processing is performed, the private IP address #1 of IP packet #1 is replaced with UE1's public IP address #1 and port number #1, resulting in IP packet #1'. After the UPF receives IP packet #2 sent by UE / EEC 2, if NAT processing is performed, the private IP address #2 of IP packet #2 is replaced with UE2's public IP address #2 and port number #2, resulting in IP packet #2'. The UPF then sends the IP data packet #1' and IP data packet #2' after NAT processing to the EES. The EES side receives IP data packet #1' and IP data packet #2', and the source IP address of IP data packet #1' is public IP address #1 and the source port number is port number #1. The source IP address of IP data packet #2' is public IP address #2 and the source port number is port number #2.
[0219] Optionally, in this embodiment, after the EES receives the first UE identifier API request message, it may determine whether the EEC and / or UE are authenticated. The method flow shown in FIG6 may further include:
[0220] S640: The EES determines whether the EEC and / or the UE are authenticated.
[0221] Exemplarily, the EES may determine whether the EEC and / or UE is authenticated in the following implementations:
[0222] As a possible implementation, in step 602, if a secure connection is established between the EEC and the EES using a two-way authentication mechanism (e.g., Generic Bootstrapping Architecture (GBA) or Authentication and Key Management for Applications (AKMA)), the EES determines that the terminal device is authenticated.
[0223] As another possible implementation, in step 602, if the EEC and the EES perform authentication based on the EES certificate, it indicates that the UE is not authenticated.
[0224] As another possible implementation, in step 602, if the EES authenticates the EEC based on the token, it indicates that the EEC is authenticated.
[0225] Optionally, the information required by the above-mentioned EES to determine whether the EEC and / or UE are authenticated (such as the method for establishing a secure connection between the EEC and EES, the authentication method, etc.) can be stored locally in the EES, such as being stored locally in the EES as the context of the EEC and / or UE.
[0226] It should be understood that the above-mentioned implementation methods are merely examples of how the EES determines whether the EEC and / or UE are authenticated, and do not constitute any limitation on the scope of protection of this application. The EES can also determine whether the EEC and / or UE are authenticated in other possible ways, which will not be illustrated one by one here.
[0227] It should also be understood that in this embodiment, the above step S640 may not be performed, that is, in this embodiment, the EES may not determine whether the EEC and / or UE are authenticated. S650: The EES obtains the public address and port number of the terminal device.
[0228] As a possible implementation method, the EES may obtain the public address and port number of the UE based on the source address bit and source port number bit in the IP data packet header that receives the API request message encapsulating the first UE identifier. The source address of the IP data packet is the public address of the UE, and the source port number of the IP data packet is the port number of the UE. The public address of the UE and the associated port number can be used to uniquely identify a terminal device under the UPF, including but not limited to the public IP address of the terminal device. For ease of description, the following description takes the public address of the terminal device as an example of a public IP address. However, in the embodiment of the present application, the specific form of the public address is not limited, and it can also be other addresses that can be used to uniquely identify a terminal device under the UPF with the associated port number.
[0229] As another possible implementation, the EES requests the EAS to provide the public IP address and port number of the UE according to the EAS ID in the received first UE identifier API request message.
[0230] Exemplarily, the process of the EES obtaining the public IP address and port number of the UE from the EAS includes the following steps 1 to 3:
[0231] Step 1: EES sends an IP address acquisition message to EAS based on the EAS identifier in the UE identifier API request message;
[0232] Step 2: EAS obtains the public IP address and port number of the UE based on the IP data packet interacting with the UE (e.g., AC); or EAS obtains the public IP address and port number of the UE locally, where the locally stored public IP address and port number of the UE can be obtained and stored during the interaction between EAS and UE before step 1.
[0233] Step 3: EAS sends the public IP address and port number of the UE to EES. S660: EES sends a second request message to the network open function network element, or in other words, the network open function network element receives the second request message from EES.
[0234] The network open function network element may be the NEF shown in FIG2 above. It should be understood that the name of the network open function network element is not limited in this embodiment. Any network element that can implement the functions of the network open function network element in this embodiment may be considered as the network open function network element involved in this embodiment. For ease of description, the following description uses the network open function network element as an example.
[0235] Specifically, the first request message includes the first private IP address of the terminal device, the public IP address and the port number of the terminal device.
[0236] Optionally, the second request message is an Nnrf_UEId_Get request.
[0237] Furthermore, after receiving the second request message, the NEF queries the network function repository function network element for the address of the UPF that implements the NAT function. The method flow shown in FIG6 further includes:
[0238] S670 , the NEF sends a discovery request message to the network function repository functional network element, or in other words, the network function repository functional network element receives the discovery request message from the NEF.
[0239] The network function repository function network element may be the NRF shown in FIG2 above. It should be understood that in this embodiment, the name of the network function repository function network element is not limited, and any network element that can implement the functions of the network function repository function network element in this embodiment may be considered as the network function repository function network element involved in this embodiment. For ease of description, the following description takes the network function repository function network element as an NRF as an example.
[0240] Specifically, the discovery request message includes the public IP address of the terminal device.
[0241] Optionally, the discovery request message is an Nnrf_NFDiscovery request. In this embodiment, the NEF determines to send an Nnrf_NFDiscovery request to the NRF based on the port number included in the first request message, where the request is used to obtain the address of the UPF that implements the NAT function.
[0242] S680: The NRF sends a discovery response message to the NEF, or in other words, the NEF receives the discovery response message from the NRF.
[0243] The response message includes the address of the UPF that implements the NAT function for the UE (public) IP address. For example, the response message includes the address of UPF#1, which can implement NAT for the UE (public) IP address.
[0244] Optionally, the discovery response message is an Nnrf_NFDiscovery response.
[0245] In this embodiment, after the NEF obtains the address of the UPF that implements the NAT function for the UE (public) IP address from the NRF, it can obtain information from the UPF for determining whether the first private IP address provided by the EEC is valid, or it can also request the UPF to determine whether the first private IP address is valid. Exemplarily, the validity of the first private IP address can be determined based on the public IP address and port number of the UE. For example, the second private IP address corresponding to the public IP address and port number is obtained. If the first private IP address and the second private IP address are the same, the first private IP address is valid.
[0246] Among them, the validity of the first private IP address can be understood as the first private IP address provided by the EEC is legal, accurate, correct, or assigned to the terminal device belonging to the EEC, or corresponds to the public address and port of the terminal device; the invalidity of the first private IP address can be understood as the first private IP address provided by the EEC is illegal, inaccurate, incorrect, or not assigned to the terminal device of the EEC, or does not correspond to the public address and port number of the terminal device.
[0247] In this embodiment, determining whether the first private IP address is valid includes but is not limited to the following implementations:
[0248] Implementation #1: The NEF requests the UPF to obtain the second private IP address of the terminal device for verifying the first private IP address provided by the EEC. In the case of Implementation #1, the method flow shown in FIG6 further includes:
[0249] S611, NEF sends a third request message to UPF, or in other words, UPF receives the third request message from NEF.
[0250] The third request message is used to obtain the second private address of the terminal device. Specifically, the third request message includes the public IP address and port number of the terminal device.
[0251] S612, the UPF sends a third response message to the NEF, or in other words, the NEF receives the third response message from the UPF.
[0252] The third response message includes the second private address of the terminal device.
[0253] S613: The NEF determines whether the first private IP address is valid.
[0254] As a possible implementation, if the second private IP address of the terminal device is the same as the first private IP address of the terminal device, the NEF determines that the first private IP address is valid and executes subsequent steps S690 to S698. It should be understood that in this implementation, the NEF determines to execute subsequent steps S690 to S698 based on the fact that the second private IP address of the terminal device is the same as the first private IP address of the terminal device.
[0255] As another possible implementation, if the second private IP address of the terminal device is different from the first private IP address of the terminal device, the NEF determines that the first private IP address is invalid. The NEF may indicate to the EES, through a second response message, that acquisition of the UE identifier failed. For example, the second response message may include first indication information indicating that acquisition of the UE identifier failed. Optionally, the second response message may also include a failure reason value, such as an unauthorized or incorrect IP address provided by the EES.
[0256] Implementation #2: The NEF requests the UPF to verify at least one private IP address and a port number corresponding to the at least one private IP address provided by the EEC. In the case of Implementation #2, the method flow shown in FIG6 further includes:
[0257] S621, NEF sends a fourth request message to UPF, or in other words, UPF receives the fourth request message from NEF.
[0258] The fourth request message is used to obtain at least one private IP address corresponding to the public IP address and a port number corresponding to the at least one private IP address. Specifically, the fourth request message includes the public IP address of the terminal device.
[0259] Among them, the at least one private IP address corresponding to the public IP address, and the port number corresponding to the at least one private IP address can be understood as: the public IP address corresponds to: port number 1, private IP address 1, port number 2, private IP address 2... etc., a public IP address can correspond to one or more private IP addresses, and each private IP address corresponds to a port number.
[0260] S622, the UPF sends a fourth response message to the NEF, or in other words, the NEF receives the fourth response message from the UPF.
[0261] The fourth response message includes at least one private IP address corresponding to the public IP address, and a port number corresponding to the at least one private IP address.
[0262] S623: The NEF determines whether the first private IP address is valid.
[0263] As a possible implementation method, NEF obtains the second private IP address based on the port number received from EES, at least one private IP address corresponding to the public IP address received from UPF, and the port number corresponding to at least one private IP address. For example, the at least one private IP address corresponding to the public IP address is: private IP address 1 and private IP address 2, private IP address 1 corresponds to port number 1, and private IP address 2 corresponds to port number 2. If the port number received from EES is port number 2, the second private IP address obtained is private IP address 2.
[0264] In this implementation, the NEF determines whether the first private IP address is valid according to whether the first private IP address and the second private IP address are the same.
[0265] If the second private IP address of the terminal device is the same as the first private IP address of the terminal device, subsequent steps S690 to S698 are executed.
[0266] As another possible implementation manner, the NEF determines that the at least one private IP address does not include the first private IP address, and determines that the first private IP address is invalid.
[0267] In this implementation, the NEF may indicate to the EES that the UE identifier acquisition failed through a second response message. For example, the second response message may carry first indication information indicating that the UE identifier acquisition failed. Optionally, the second response message may also carry a failure reason value, such as that the IP address provided by the EES is unauthorized or incorrect.
[0268] As another possible implementation, if the at least one private address includes the first private address, and the port number corresponding to the first private address is the same as the port number, it is determined that the first private address is valid, and subsequent steps S690 to S698 are executed.
[0269] It should be noted that when the NEF locally stores at least one private IP address corresponding to a public IP address and a port number corresponding to the at least one private IP address, the NEF may not execute the above steps S621 and S622, and may simply execute the above step S623 (for example, before executing the above step S621, the NEF queries and finds that the at least one private IP address corresponding to the public IP address and the port number corresponding to the at least one private IP address are not stored locally). Exemplarily, the NEF has already obtained the above-mentioned at least one private IP address corresponding to the public IP address and the port number corresponding to the at least one private IP address before receiving the second request message.
[0270] Optionally, in the case shown in implementation #2, the NEF may also subscribe to a relationship list with the UPF, which may further include:
[0271] S624, NEF sends a subscription request message to UPF, or in other words, UPF receives the subscription request message from NEF.
[0272] Specifically, NEF sends a Nupf_PrivateUEIP_Subscribe message to UPF, which is used to instruct UPF to notify NEF of the new list when the private IP address and port number information corresponding to the public IP address changes (including adding a new UE private IP address, port number, or deleting a private IP address and port number).
[0273] S625, UPF sends a subscription response message to NEF, or in other words, NEF receives a subscription response message from UPF.
[0274] When the UPF receives a Nupf_PrivateUEIP_Get message containing only the UE's public IP address, it defaults to notifying the NEF of the new list when the private IP address and port number information corresponding to the UE's public IP address changes. For example, the UPF may provide the NEF with at least one private IP address corresponding to the public IP address and the port number corresponding to the at least one private IP address via one or more subscription response messages.
[0275] Implementation #3: The NEF requests the UPF to verify the first private IP address provided by the EEC. In the case of Implementation #3, the method flow shown in FIG6 further includes:
[0276] S631, NEF sends a fifth request message to UPF, or in other words, UPF receives the fifth request message from NEF.
[0277] The fifth request message is used to request the UPF to verify the first private IP address provided by the EEC. The fifth request message includes the public IP address of the terminal device, the first private IP address of the terminal device, and the port number.
[0278] S632, UPF determines whether the first private IP address is valid.
[0279] As a possible implementation method, UPF obtains the corresponding UE public IP address and port number based on the first private IP address of the terminal device received, and compares them with the public IP address and port number of the terminal device received. If they are the same, the first private IP address is determined to be valid; if they are different, the first private IP address is determined to be invalid.
[0280] As another possible implementation method, if the UPF cannot obtain corresponding information based on the first private IP address of the terminal device, it determines that the first private IP address is invalid.
[0281] As another possible implementation method, UPF obtains the corresponding second private IP address based on the received public IP address and port number of the terminal device, and verifies whether the second private IP address is the same as the first private IP address of the terminal device. If they are the same, the first private IP address is determined to be valid; if they are different, the first private IP address is determined to be invalid.
[0282] S633, the UPF sends a fifth response message to the NEF, or in other words, the NEF receives the fifth response message from the UPF.
[0283] The fifth response message is used to indicate whether the first private IP address is valid.
[0284] As a possible implementation manner, if the first private IP address is valid, subsequent steps S690 to S698 are executed.
[0285] As another possible implementation, if the first private IP address is invalid, the NEF may indicate to the EES through a second response message that the UE identifier acquisition failed. For example, the second response message may carry first indication information indicating that the UE identifier acquisition failed. Optionally, the second response message may also carry a failure reason value, such as that the IP address provided by the EES is unauthorized or incorrect.
[0286] S690: The NEF sends a search request message to the binding support function network element, or in other words, the binding support function network element receives the search request message from the NEF.
[0287] The binding support function network element may be the BSF shown in FIG2 above. It should be understood that the name of the binding support function network element is not limited in this embodiment, and any device that can implement the functions of the binding support function network element in this embodiment can be considered as the binding support function network element involved in this embodiment. For ease of description, the following description uses the BSF as an example.
[0288] Specifically, the retrieval request message includes the first private IP address of the terminal device. The retrieval request message is used to retrieve the session binding information of the UE.
[0289] Optionally, the retrieval request message is an Nbsf_Management_Discovery service operation.
[0290] S691: The BSF sends a retrieval response message to the NEF, or in other words, the NEF receives a retrieval response message from the BSF.
[0291] Specifically, the retrieval response message includes session binding information.
[0292] As a possible implementation manner, if no SUPI is received in the session binding information sent by the BSF, the following step S692 is performed.
[0293] S692, NEF replies a result value to EES, indicating that the UE ID is unavailable.
[0294] As another possible implementation, if the session binding information sent by the BSF includes SUPI, the following step S693 is performed.
[0295] S693, the NEF sends a request message #3 to the unified data management function network element, or in other words, the unified data management function network element receives the request message #3 from the NEF.
[0296] The unified data management function network element may be the UDM shown in FIG2 above. It should be understood that the name of the unified data management function network element is not limited in this embodiment, and any device capable of implementing the functions of the unified data management function network element in this embodiment may be considered the unified data management function network element involved in this embodiment. For ease of description, the following description uses the UDM as an example.
[0297] Specifically, the request message #3 includes at least one of the SUPI, the application port ID, the EES identifier, and the EAS identifier.
[0298] S694, UDM sends a response message #3 to NEF, or in other words, NEF receives a response message #3 from UDM.
[0299] Specifically, the response message #3 includes the UE identifier, and the UE identifier may be GPSI.
[0300] S695: The NEF sends a second response message to the EES, or in other words, the EES receives the second response message from the NEF.
[0301] Specifically, the second response message includes the UE identifier, and the UE identifier may be GPSI.
[0302] S696, EES sends a first response message to EEC, the first response message includes the UE identifier. Optionally, the first response message is a first UE identifier API response message
[0303] S697 , the EEC sends a response message #2 to the AC, where the response message #2 includes the UE identifier.
[0304] S698, the AC sends a response message #1 to the EAS, where the response message #1 includes the UE identifier.
[0305] In the communication method shown in Figure 6, after the EES receives a request message from the EEC for obtaining a terminal device, it sends a request message to the NEF containing the first private address received from the EEC, as well as the public address and port number obtained by the EES. This allows the NEF to determine the accuracy of the first private address provided by the EEC based on the received public address and port number, thereby facilitating the decision on whether to provide the terminal device identifier to the EEC. This prevents the EEC from providing the terminal device identifier even if the first private address provided by the EEC is inaccurate, thereby improving the security of the EEC's acquisition of the terminal device identifier.
[0306] The present application also provides a communication method, in which the EAS can determine how to obtain the UE identifier through the EEC based on whether the UE / EEC is authenticated. For ease of understanding, the communication method is described in detail below in conjunction with (b) in FIG. 7 .
[0307] FIG7( b ) is a schematic flow chart of a communication method provided by the present application, which includes the following steps:
[0308] S701: A connection is established between the EAS and the AC.
[0309] Please refer to the description of step S601 in FIG6 , which will not be repeated here.
[0310] S702: A connection is established between the EEC and the EES.
[0311] Please refer to the description of step S602 in FIG6 , which will not be repeated here.
[0312] S710: The EES sends second indication information to the EAS, or the EAS receives second indication information from the EES.
[0313] The second indication information is used to indicate whether the EEC in the terminal device and / or the terminal device is authenticated.
[0314] In this embodiment, the EES determines whether the EEC and / or the terminal device are authenticated, and provides the EAS with second indication information indicating whether the EEC and / or the terminal device are authenticated. The manner in which the EES determines whether the EEC and / or the terminal device are authenticated can be found in the description of step S640 in the embodiment shown in FIG. 6 , and is not further described here.
[0315] S720, the EAS determines a process for obtaining an identifier of the terminal device according to the second indication information.
[0316] As a possible implementation, before EES sends the second indication information to EAS, EES receives EAS's seventh request message for obtaining the identifier of the terminal device, and fails to obtain the identifier of the terminal device based on the public IP address of the terminal device carried in the seventh request message.
[0317] In this implementation, the EES sending the second indication information to the EAS may be: the EES sending a seventh response message to the EAS, where the seventh response message is used to indicate that the identifier acquisition of the terminal device fails, and the seventh response message includes the second indication information.
[0318] In this implementation, the method flow shown in (b) of FIG7 may further include:
[0319] S703 , the EAS sends a seventh request message to the EES, or the EES receives the seventh request message from the EAS.
[0320] Furthermore, in this embodiment, after the EAS learns whether the EEC and / or the terminal device is authenticated, it may obtain the identifier of the terminal device in different ways.
[0321] Method #1: The second indication information indicates that the EEC or the terminal device is authenticated, and the EAS determines, according to the second indication information, that the process of obtaining the identifier of the terminal device based on the private address of the terminal device is process #1.
[0322] In this method #1, process #1 includes the following steps:
[0323] S711 , the EAS sends a request message #1 to the AC, or in other words, the AC receives the request message #1 from the EAS.
[0324] S712, the AC sends a request message #2 to the EEC, or in other words, the EEC receives the request message #2 from the AC.
[0325] S713: The EEC sends a first request message to the EES, or in other words, the EES receives the first request message from the EEC.
[0326] For the description of steps S711 to S713 , reference may be made to the description of steps S610 to S630 in the embodiment shown in FIG6 , and will not be repeated here.
[0327] In this approach #1, after receiving the first request message from the EEC, the EES obtains the identifier of the terminal device based on the first private address of the terminal device carried in the first request message. The method flow shown in (b) of FIG7 further includes:
[0328] S714, EES sends a request message #A1 to NEF.
[0329] The request message #A1 is used to obtain the identifier of the terminal device, and the request message #A1 includes the first private address of the terminal device.
[0330] S715, NEF sends a request message #D1 to BSF.
[0331] The request message #D1 includes the first private address, and the BSF retrieves the session binding information of the UE.
[0332] S716, BSF sends a response message #D1 to NEF.
[0333] The response message #D1 responds to the request message #D1. If the response message #D1 does not carry the SUPI, the NEF replies with a Result value to the EES, indicating that the terminal device identifier acquisition failed.
[0334] S717, NEF sends a request message #E1 to UDM.
[0335] The NEF retrieves the UE identifier specified by the AF through the Nudm_SDM_Get service operation. The request message #E1 includes at least one of the SUPI, the Application Port ID or the AF identifier.
[0336] S718, UDM sends a response message #E1 to NEF.
[0337] The UDM responds to the NEF with an AF-specific UE identifier, which is represented as an external identifier of the UE that is uniquely associated with the application port ID, MTC provider information and / or AF identifier.
[0338] S719, NEF sends a response message #A1 to EES.
[0339] The response message #A1 is used to obtain the identifier of the terminal device, and the response message #A1 includes the identifier of the terminal device.
[0340] S7191, EES sends a first response message to EEC, the first response message includes the identifier of the terminal device. Optionally, the first response message is a first UE identifier API response message
[0341] S7192, EEC sends a response message #2 to AC, and the response message #2 includes the identifier of the terminal device.
[0342] S7193, the AC sends a response message #1 to the EAS, where the response message #1 includes an identifier of the terminal device.
[0343] Method #2: The second indication information indicates that the EEC and / or the terminal device is not authenticated. The EAS determines, based on the second indication information, that the process of obtaining the identifier of the terminal device based on the public address and port number of the terminal device is process #2.
[0344] In this method #2, process #2 includes the following steps:
[0345] S721, EAS obtains the public IP address and port number of the terminal device.
[0346] Specifically, the EAS obtains the public IP address and port number of the UE according to the IP data packets interacting with the UE (eg, AC).
[0347] S722: The EAS sends a sixth request message to the EES, or in other words, the EES receives the sixth request message from the EAS.
[0348] The sixth request message is used to obtain the identifier of the terminal device, and the sixth request message includes the public address and port number of the terminal device. Optionally, the sixth request message is a sixth UE identifier API request message
[0349] S723, EES sends a request message #A2 to NEF.
[0350] The request message #A2 is used to obtain the identifier of the terminal device. The request message #A2 includes the public address and port number of the terminal device.
[0351] S724, NEF sends a request message #B2 to NRF.
[0352] Request message #B2 is used to obtain the address of the UPF that implements the NAT function for the UE's (public) IP address. For example, the NEF uses the Nnrf_NFDiscovery service operation to obtain the address of the UPF that implements the NAT function. Request message #B2 includes the UE's public address and port number.
[0353] S725, NRF sends a response message #B2 to NEF.
[0354] The response message #B2 responds to the above request message #B2, and the response message #B2 includes the address of the UPF that implements the NAT function for the UE public address.
[0355] S726, NEF sends a request message #C2 to UPF.
[0356] The request message #C2 is used to obtain the private address of the UE. The request message #C2 includes the UE public address and port number.
[0357] S727, UPF sends a response message #C2 to NEF.
[0358] The response message #C2 responds to the above request message #C2, and the response message #C2 includes the private address of the UE.
[0359] S728, NEF sends a request message #D2 to BSF.
[0360] The request message #D2 contains the UE's private address, and the BSF retrieves the UE's session binding information.
[0361] S729, BSF sends a response message #D2 to NEF.
[0362] The response message #D2 responds to the request message #D2. If the response message #D2 does not carry the SUPI, the NEF replies to the AF with a Result value indicating that the UE ID is unavailable.
[0363] S7291, NEF sends a request message #E2 to UDM.
[0364] The NEF retrieves the UE identifier specified by the AF through the Nudm_SDM_Get service operation. The request message #E2 includes at least one of the SUPI, the Application Port ID or the AF identifier.
[0365] S7292, UDM sends a response message #E2 to NEF.
[0366] The UDM responds to the NEF with an AF-specific UE identifier, which is represented as an external identifier of the UE that is uniquely associated with the application port ID, MTC provider information and / or AF identifier.
[0367] S7293, NEF sends a response message #A2 to EES.
[0368] The response message #A2 includes the identifier of the terminal device.
[0369] S7294, EES sends a sixth response message to EAS, the sixth response message including the identifier of the terminal device. Optionally, the sixth response message is a sixth UE identifier API response message
[0370] In the communication method shown in (b) of Figure 7, before initiating the UE ID acquisition process, the EAS obtains information from the EES on whether the UE and / or EEC are authenticated, and when the UE is authenticated and / or the EEC is authenticated, the identifier of the terminal device is obtained through the EEC. Optionally, when the UE is authenticated and / or the EEC is authenticated, the identifier of the terminal device can also be obtained based on the public address and port number of the terminal device. When the UE and / or the EEC are not authenticated, the identifier of the terminal device is obtained based on the public address and port number of the terminal device. This allows the EES to obtain the identifier of the terminal device based on the public address and port number of the terminal device, thereby avoiding the failure to obtain the identifier of the terminal device based on the private address of the terminal device when the UE and / or the EEC are not authenticated, or avoiding obtaining the identifier of the wrong terminal device.
[0371] The present application also provides another communication method. After receiving a request message from the EEC to obtain the UE identifier, the EES can determine the subsequent method for obtaining the UE identifier based on whether the EEC and / or the UE are authenticated. For ease of understanding, this is explained in conjunction with Figure 8.
[0372] FIG8 is a schematic flow chart of another communication method provided by the present application, which includes the following steps:
[0373] S801: A connection is established between the EAS and the AC.
[0374] Please refer to the description of step S601 in FIG6 , which will not be repeated here.
[0375] S802: A connection is established between the EEC and the EES.
[0376] Please refer to the description of step S602 in FIG6 , which will not be repeated here.
[0377] S810 , the EAS sends a request message #1 to the AC, or in other words, the AC receives the request message #1 from the EAS.
[0378] S820: The AC sends a request message #2 to the edge-enabled client. In other words, the edge-enabled client receives the request message #2 from the AC.
[0379] S830: The EEC sends a first request message to the EES, or in other words, the EES receives the first request message from the EEC.
[0380] S840: The EES determines whether the EEC and / or the UE are authenticated.
[0381] For the description of steps S810 to S840 in this embodiment, reference may be made to the description of steps S601 to S640 in FIG6 , which will not be repeated here.
[0382] The difference between this embodiment and the embodiment shown in FIG6 is that:
[0383] In this embodiment, the EES no longer performs implementations #1 to #3 in the embodiment shown in FIG6 to determine whether the first private IP address provided by the EEC is valid. Instead, the EES determines how to obtain the UE identifier based on whether the EEC and / or the UE are authenticated. Specifically, in this embodiment, the EES obtains the UE identifier in the following two ways:
[0384] Method #3: EES uses the private IP address provided by EEC to interact with 5GC to obtain the UE ID. In the case of method #1, the method flow shown in Figure 8 also includes the following steps:
[0385] S811, EES sends a request message #A1 to NEF.
[0386] The request message #A1 is used to obtain the identifier of the terminal device, and the request message #A1 includes the first private address of the terminal device.
[0387] S812, NEF sends a request message #D1 to BSF.
[0388] The request message #D1 includes the first private address, and the BSF retrieves the session binding information of the UE.
[0389] S813, BSF sends a response message #D1 to NEF.
[0390] The response message #D1 responds to the request message #D1. If the response message #D1 does not carry the SUPI, the NEF replies with a Result value to the EES, indicating that the terminal device identifier acquisition failed.
[0391] S814, NEF sends a request message #E1 to UDM.
[0392] S815, UDM sends a response message #E1 to NEF.
[0393] S816, NEF sends a response message #A1 to EES.
[0394] The response message #A1 is used to obtain the identifier of the terminal device, and the response message #A1 includes the identifier of the terminal device.
[0395] For the description of steps S811 to S816, reference may be made to the description of steps S714 to S719 in embodiment mode #1 shown in (b) of FIG7 , which will not be repeated here.
[0396] Method #4: The EES uses the UE's public IP address and port number to interact with the 5GC to obtain the UE ID. In the case of Method #4, the method flow shown in Figure 8 also includes the following steps:
[0397] S821, EES sends a request message #A2 to NEF.
[0398] The request message #A2 is used to obtain the identifier of the terminal device. The request message #A2 includes the public address and port number of the terminal device.
[0399] S822, NEF sends a request message #B2 to NRF.
[0400] Request message #B2 is used to obtain the address of the UPF that implements the NAT function for the UE's (public) IP address. For example, the NEF uses the Nnrf_NFDiscovery service operation to obtain the address of the UPF that implements the NAT function. Request message #B2 includes the UE's public address and port number.
[0401] S823, NRF sends a response message #B2 to NEF.
[0402] The response message #B2 responds to the above request message #B2, and the response message #B2 includes the address of the UPF that implements the NAT function for the UE public address.
[0403] S824, NEF sends a request message #C2 to UPF.
[0404] The request message #C2 is used to obtain the private address of the UE. The request message #C2 includes the UE public address and port number.
[0405] S825, UPF sends a response message #C2 to NEF.
[0406] The response message #C2 responds to the above request message #C2, and the response message #C2 includes the private address of the UE.
[0407] S826, NEF sends a request message #D2 to BSF.
[0408] The request message #D2 contains the UE's private address, and the BSF retrieves the UE's session binding information.
[0409] S827, BSF sends a response message #D2 to NEF.
[0410] The response message #D2 responds to the request message #D2. If the response message #D2 does not carry the SUPI, the NEF replies to the AF with a Result value indicating that the UE ID is unavailable.
[0411] S828, NEF sends a request message #E2 to UDM.
[0412] S829, UDM sends a response message #E2 to NEF.
[0413] S8291, NEF sends a response message #A2 to EES.
[0414] The response message #A2 includes the identifier of the terminal device.
[0415] For the description of steps S821 to S8291, please refer to the description of steps S723 to S7293 in embodiment mode #3 shown in (b) of FIG7 , which will not be repeated here.
[0416] After the EES obtains the identifier of the terminal device through the above-mentioned method # and method #4, the method flow shown in FIG8 further includes:
[0417] S850: The EES sends a first response message to the EEC. The first response message includes an identifier of the UE.
[0418] S860 , the EEC sends a response message #2 to the AC, where the response message #2 includes the UE identifier.
[0419] S870 , the AC sends a response message # 1 to the EAS, where the response message # 1 includes the UE identifier.
[0420] In the communication method shown in Figure 8, EES determines the actual method of obtaining the identifier of the terminal device based on whether the UE and / or EEC are authenticated, thereby avoiding obtaining the identifier of the terminal device based on the first private address of the terminal device when the UE and / or EEC are not authenticated, thereby improving security.
[0421] It should be understood that the size of the serial numbers of the above processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0422] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.
[0423] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for exemplary description (such as AMF, etc.), and it should be understood that the embodiments of the present application do not limit the specific form of the device. For example, devices that can achieve the same functions in the future are applicable to the embodiments of the present application.
[0424] It can be understood that in the above-mentioned various method embodiments, the methods and operations implemented by a device (such as AMF) can also be implemented by components of the device (such as a chip or circuit).
[0425] The communication method provided in the embodiments of the present application is described in detail above in conjunction with Figures 6 to 8. The above communication method is mainly introduced from the perspective of the interaction between the various protocol layers of the terminal device. It is understood that in order to implement the above functions, the terminal device includes the corresponding hardware structure and / or software modules for performing each function.
[0426] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.
[0427] The communication device provided in this application is described in detail below with reference to Figures 9 to 11. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, reference can be made to the method embodiment above. For the sake of brevity, some contents will not be repeated.
[0428] In the embodiment of the present application, the functional modules of the transmitting device or the receiving device can be divided according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module according to each function.
[0429] Figure 9 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver module 11 and a processing module 12. The transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used to process data. In other words, the transceiver module 11 is used to perform operations related to receiving and sending, while the processing module 12 is used to perform operations other than receiving and sending. The transceiver module 11 can also be referred to as a communication interface or a communication unit.
[0430] Optionally, the device 10 may further include a storage module 13, which may be used to store instructions and / or data. The processing module 12 may read the instructions and / or data in the storage module so that the device implements the actions of the devices in the aforementioned method embodiments.
[0431] In one design, the device 10 may correspond to the EES in the above method embodiments, or be a component of the EES (such as a chip).
[0432] The device 10 can implement the steps or processes corresponding to those executed by the EES in the above method embodiment, wherein the transceiver module 11 can be used to perform operations related to the transceiver operation of the EES in the above method embodiment, and the processing module 12 can be used to perform operations related to the processing of the EES in the above method embodiment.
[0433] In one possible implementation, the transceiver module 11 is used to receive a first request message from a terminal device, where the first request message is used to obtain an identifier of the terminal device, and the first request message includes a first private address of the terminal device. The transceiver module 11 is also used to obtain a public address and a port number of the terminal device, and send a second request message to a network open function network element, where the second request message is used to obtain an identifier of the terminal device, and the second request message includes the first private address, the public address, and the port number. The transceiver module 11 is also used to receive first indication information from the network open function network element or the identifier of the terminal device, where the first indication information is used to indicate that the terminal device has failed to obtain the identifier.
[0434] In another possible implementation, the transceiver module 11 is configured to send second indication information to the edge application server, where the second indication information is used to indicate whether the edge-enabled client in the terminal device and / or the terminal device is authenticated. The transceiver module 11 is further configured to, if the edge-enabled client and / or the terminal device is not authenticated, receive a sixth request message from the edge application server, where the sixth request message is used to obtain an identifier of the terminal device, and the sixth request message includes a public address and port number of the terminal device.
[0435] In another possible implementation, the transceiver module 11 is configured to receive a first request message from a terminal device, where the first request message is used to obtain an identifier of the terminal device, and the first request message includes a first private address of the terminal device. The processing module 12 is configured to determine whether the edge-enabled client of the terminal device and / or the terminal device is authenticated. The processing module 12 is configured to obtain a public address and port number of the terminal device if the edge-enabled client and / or the terminal device are not authenticated, and obtain an identifier of the terminal device based on the public address and port number.
[0436] In which, when the device 6 is used to execute the method in Figure 3, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S630, S660, S692, S695 and S696; the processing module 12 can be used to execute the processing steps in the method, such as steps S640 and S650.
[0437] When the device 10 is used to execute the method in (b) in Figure 7, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S703, S710, S714, S719, S723, S7293 and S7294; the processing module 12 can be used to execute the processing steps in the method.
[0438] When the device 10 is used to execute the method in Figure 8, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S830, S811, S816, S821, S8291 and S850; the processing module 12 can be used to execute the processing steps in the method, such as step S840.
[0439] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.
[0440] In another design, the device 10 may correspond to the NEF in the above method embodiment, or be a component of the NEF (such as a chip).
[0441] The device 10 can implement the steps or processes corresponding to the NEF execution in the above method embodiment, wherein the transceiver module 11 can be used to perform the NEF transmission and reception related operations in the above method embodiment, and the processing module 12 can be used to perform the NEF processing related operations in the above method embodiment.
[0442] In one possible implementation, the transceiver module 11 is used to receive a second request message from the edge enabling server, where the second request message is used to obtain an identifier of the terminal device, and the second request message includes the first private address of the terminal device, the public address of the terminal device, and the port number; the transceiver module 11 is used to obtain the identifier of the terminal device when it is determined that the first private address is valid based on the public address and the port number, and send the identifier of the terminal device to the edge enabling server.
[0443] In which, when the device 10 is used to execute the method in Figure 6, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S660, S670, S680, S611, S612, S621, S622, S624, S625, S631, S633, S690, S691, S692, S693, S694 and S695; the processing module 12 can be used to execute the processing steps in the method, such as steps S613 and S623.
[0444] When the device 10 is used to execute the method in (b) of Figure 7, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S714, S715, S716, S717, S718, S719, S723, S724, S725, S726, S727, S728, S729, S7291, S7292 and S7293; the processing module 12 can be used to execute the processing steps in the method.
[0445] When the device 10 is used to execute the method in Figure 8, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S811, S812, S813, S814, S815, S816, S821, S822, S823, S824, S825, S826, S827, S828, S829 and S8291; the processing module 12 can be used to execute the processing steps in the method.
[0446] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.
[0447] In another design, the device 10 may correspond to the UPF in the above method embodiment, or be a component of the UPF (such as a chip).
[0448] The device 10 can implement the steps or processes corresponding to the UPF execution in the above method embodiment, wherein the transceiver module 11 can be used to perform the UPF transmission and reception related operations in the above method embodiment, and the processing module 12 can be used to perform the UPF processing related operations in the above method embodiment.
[0449] In one possible implementation, the transceiver module 11 is used to receive a third request message from the network open function network element, where the third request message is used to obtain the second private Internet Protocol address of the terminal device, and the third request message includes the public address and port number of the terminal device; the processing module 12 is used to determine the second private address of the terminal device based on the public address and the port number; the transceiver module 11 is used to send a third response message to the network open function network element, where the third response message includes the second private address.
[0450] In another possible implementation, the transceiver module 11 is used to receive a fourth request message from the network open function network element, where the fourth request message includes a first public Internet interconnection protocol address of the terminal device; the processing module 12 is used to determine, based on the public address, at least one private address corresponding to the public address, and a port number corresponding to the at least one private address; the transceiver module 11 sends a fourth response message to the network open function network element, where the fourth response message includes at least one private address corresponding to the public address, and a port number corresponding to the at least one private address.
[0451] In another possible implementation, the transceiver module 11 is used to receive a fifth request message from the network open function network element, where the fifth request message includes a first private Internet interconnection protocol address of the terminal device, a public address and a port number of the terminal device, and the fifth request message is used to request the user plane function network element to determine whether the first private address is valid; the processing module 12 is used to determine whether the first private address is valid based on the correspondence between the locally stored private address, public address and port number; the transceiver module 11 sends a fifth response message to the network open function network element, where the fifth response message is used to indicate whether the first private address is valid.
[0452] In which, when the device 10 is used to execute the method in Figure 6, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S611, S612, S621, S622, S624, S625, S631 and S633; the processing module 12 can be used to execute the processing steps in the method, such as step S632.
[0453] When the device 10 is used to execute the method in (b) of FIG. 7 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, such as steps S726 and S727 ; the processing module 12 may be used to execute the processing steps in the method.
[0454] When the device 10 is used to execute the method in FIG8 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, such as steps S824 and S825 ; the processing module 12 may be used to execute the processing steps in the method.
[0455] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.
[0456] In another design, the device 10 may correspond to the EAS in the above method embodiment, or be a component (such as a chip) of the EAS.
[0457] The device 10 can implement the steps or processes corresponding to the EAS execution in the above method embodiment, wherein the transceiver module 11 can be used to perform the EAS transceiver-related operations in the above method embodiment, and the processing module 12 can be used to perform the EAS processing-related operations in the above method embodiment.
[0458] In one possible implementation, the transceiver module 11 is used to receive second indication information from the edge enabling server, where the second indication information is used to indicate whether the edge enabling client in the terminal device and / or the terminal device is authenticated; the transceiver module 11 sends a sixth request message to the edge enabling server when the edge enabling client and / or the terminal device is not authenticated, where the sixth request message is used to obtain an identifier of the terminal device, and the sixth request message includes a public address and port number of the terminal device.
[0459] When the device 10 is used to execute the method in FIG6 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, such as steps S610 and S698 ; the processing module 12 may be used to execute the processing steps in the method.
[0460] When the device 10 is used to execute the method in (b) in Figure 7, the transceiver module 11 can be used to execute the steps of sending and receiving information in the method, such as steps S711, S7193, S703, S710, S722 and S7294; the processing module 12 can be used to execute the processing steps in the method, such as steps S720 and S721.
[0461] When the device 10 is used to execute the method in FIG8 , the transceiver module 11 may be used to execute the steps of sending and receiving information in the method, such as steps S810 and S870 ; the processing module 12 may be used to execute the processing steps in the method.
[0462] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.
[0463] It should also be understood that the device 10 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 10 may be specifically the mobile management network element in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the mobile management network element in the above-mentioned method embodiments; or, the device 10 may be specifically the terminal device in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the terminal device in the above-mentioned method embodiments. To avoid repetition, it will not be described here.
[0464] The apparatus 10 of each of the above-described solutions has the function of implementing the corresponding steps performed by the devices (such as terminal devices and network devices) in the above-described methods. This function can be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the above-described functions; for example, the transceiver module can be replaced by a transceiver (for example, the transmitting unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.
[0465] In addition, the transceiver module 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing module may be a processing circuit.
[0466] Figure 10 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. Device 20 includes a processor 21, which is configured to execute computer programs or instructions stored in memory 22, or read data / signaling stored in memory 22, to perform the methods described in the above method embodiments. Optionally, there may be one or more processors 21.
[0467] Optionally, as shown in FIG10 , the device 20 further includes a memory 22 for storing computer programs or instructions and / or data. The memory 22 may be integrated with the processor 21 or may be separately provided. Optionally, there may be one or more memories 22.
[0468] Optionally, as shown in Figure 10, the device 20 further includes a transceiver 23, which is used to receive and / or send signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.
[0469] As a solution, the device 20 is used to implement the operations performed by the EES in the above various method embodiments.
[0470] As another solution, the device 20 is used to implement the operations performed by the NEF in the above various method embodiments.
[0471] As another solution, the device 20 is used to implement the operations performed by the UPF in the above various method embodiments.
[0472] As another solution, the device 20 is used to implement the operations performed by the EAS in the above various method embodiments.
[0473] It should be understood that the processor mentioned in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor, etc.
[0474] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).
[0475] 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 component, the memory (storage module) can be integrated into the processor.
[0476] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0477] 11 is a schematic diagram of a chip system 30 according to an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.
[0478] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, outputting information processed by the chip system 30 or inputting data or signaling information to be processed into the chip system 30 for processing.
[0479] As a solution, the chip system 30 is used to implement the operations performed by the EES, EAS, NEF or UPF in the above various method embodiments.
[0480] For example, the logic circuit 31 is used to implement the processing-related operations performed by EES, EAS, NEF or UPF in the above method embodiments; the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by EES, EAS, NEF or UPF in the above method embodiments.
[0481] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the EES, EAS, NEF, and UPF in the above-mentioned method embodiments are stored.
[0482] For example, when the computer program is executed by a computer, the computer can implement the methods performed by EES, EAS, NEF or UPF in each embodiment of the above method.
[0483] An embodiment of the present application further provides a computer program product comprising instructions, which, when executed by a computer, implement the methods performed by the EES, EAS, NEF, and UPF in the above-mentioned method embodiments.
[0484] An embodiment of the present application also provides a communication system, including the aforementioned EES, EAS, NEF and UPF.
[0485] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.
[0486] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0487] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can 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 the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0488] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A communication method, characterized in that: include: receiving a first request message from a terminal device, where the first request message is used to obtain an identifier of the terminal device, and the first request message includes a first private address of the terminal device; Acquire the public address and port number of the terminal device, and send a second request message to the network open function network element, where the second request message is used to acquire the identifier of the terminal device, and the second request message includes the first private address, the public address and the port number; Receive first indication information from the network open function network element or the identifier of the terminal device, where the first indication information is used to indicate that the identifier of the terminal device has failed to be obtained.
2. The method according to claim 1, characterized in that The receiving a first request message from a terminal device includes: Receiving an Internet Protocol IP data packet from a user plane function network element, wherein a payload portion of the IP data packet includes the first request message from the terminal device; The obtaining of the public address and the port number comprises: The public address and the port number are determined according to the source address and the source port number of the IP data packet, wherein the source address is used to characterize the public address, and the source port number is used to characterize the port number.
3. The method according to claim 1, characterized in that The obtaining of the public address and the port number includes: obtaining the public address and the port number from an edge application server.
4. The method according to any one of claims 1 to 3, characterized in that In the case of receiving the first indication information of the terminal device from the network open function network element, the method further includes: Receive a cause value of the terminal device from the network open function network element, where the cause value is used to indicate a reason why the terminal device fails to obtain an identifier.
5. The method according to any one of claims 1 to 4, characterized in that In case of receiving the identifier of the terminal device from the network open function network element, the method further comprises: A first response message is sent to the terminal device, where the first response message includes an identifier of the terminal device.
6. The method according to any one of claims 1 to 5, characterized in that The sending a second request message to the network open function network element includes: When the terminal device or the edge enabling client in the terminal device is not authenticated, the second request message is sent to the network open function network element.
7. A communication method, characterized in that: include: receiving a second request message from the edge enabling server, where the second request message is used to obtain an identifier of a terminal device, and the second request message includes a first private address of the terminal device, a public address of the terminal device, and a port number; When it is determined that the first private address is valid according to the public address and the port number, an identifier of the terminal device is obtained, and the identifier of the terminal device is sent to the edge enabling server.
8. The method according to claim 7, characterized in that When it is determined that the first private address is invalid according to the public address and the port number, first indication information is sent to the edge enabling server, where the first indication information is used to indicate that the identifier of the terminal device fails to be obtained.
9. The method according to claim 7 or 8, characterized in that: The method further comprises: Determine whether the first private address is valid according to the public address and the port number.
10. The method according to claim 9, characterized in that The determining whether the first private address is valid according to the public address and the port number includes: Whether the first private address is the same as a second private address, wherein the second private address is determined based on the public address and the port number.
11. The method according to claim 10, characterized in that The method further comprises: Sending a third request message to the user plane function network element, wherein the third request message includes the public address and the port number; A third response message is received from the user plane function network element, where the third response message includes the second private address.
12. The method according to claim 10, characterized in that The method further comprises: Obtain at least one private address corresponding to the public network address and a port number corresponding to the at least one private address; The second private address is acquired according to the acquired at least one private address and the port number corresponding to the at least one private address, and the port number in the second request message.
13. The method according to claim 12, characterized in that The method further comprises: Sending a fourth request message to the user plane function network element, where the fourth request message includes the public address; A fourth response message is received from the user plane function network element, where the fourth response message includes at least one private address corresponding to the public address and a port number corresponding to the at least one private address.
14. The method according to claim 12, characterized in that The method further comprises: Sending a subscription request message to a user plane function network element, wherein the subscription request message includes the public address; Receive one or more subscription response messages from the user plane functional network element, wherein the one or more subscription response messages include at least one private address corresponding to the public address and a port number corresponding to the at least one private address.
15. The method according to claim 13 or 14, characterized in that The method further comprises: The at least one private address corresponding to the public network address and the port number corresponding to the at least one private address are queried locally and are not stored.
16. The method according to any one of claims 13 to 15, characterized in that The method further comprises: If the at least one private address does not include the first private address, determining that the first private address is invalid; or, If the at least one private address includes the first private address, and the port number corresponding to the first private address is the same as the port number, it is determined that the first private address is valid.
17. The method according to claim 9, characterized in that The determining whether the first private address is valid according to the public address and the port number includes: Sending a fifth request message to a user plane function network element, where the fifth request message includes the first private address, the public address, and the port number, and the fifth request message is used to request the user plane function network element to determine whether the first private address is valid; A fifth response message is received from the user plane function network element, where the fifth response message is used to indicate whether the first private address is valid.
18. The method according to any one of claims 7 to 17, characterized in that The method further comprises: Sending a discovery request message to a network function repository function network element, the discovery request message including the public address, the discovery request message being used to obtain an address of a user plane function network element that implements an address translation function; A discovery response message is received from the network function repository function network element, wherein the discovery response message includes an address of the user plane function network element.
19. The method according to claim 8, characterized in that In the case of sending the first indication information to the edge enabling server, the method further includes: A reason value is sent to the edge enabling server, where the reason value is used to indicate a reason why the terminal device fails to obtain the identifier.
20. A communication method, characterized in that: include: Receiving a third request message from the network open function network element, the third request message is used to obtain a second private Internet Protocol address of the terminal device, the third request message includes a public address and a port number of the terminal device; Determine a second private address of the terminal device according to the public address and the port number; A third response message is sent to the network open function network element, where the third response message includes the second private address.
21. A communication method, characterized in that: include: receiving a fourth request message from the network open function network element, wherein the fourth request message includes a first public Internet interconnection protocol address of the terminal device; Determine, according to the public address, at least one private address corresponding to the public address, and a port number corresponding to the at least one private address; A fourth response message is sent to the network open function network element, where the fourth response message includes at least one private address corresponding to the public address and a port number corresponding to the at least one private address.
22. A communication method, characterized in that: include: Receiving a subscription request message from the network open function network element, wherein the subscription request message includes a first public Internet protocol address of a terminal device; One or more subscription response messages are sent to the network open function network element, where the one or more subscription response messages include at least one private address corresponding to the public address and a port number corresponding to the at least one private address.
23. A communication method, characterized in that: include: receiving a fifth request message from a network open function network element, the fifth request message including a first private Internet interconnection protocol address of a terminal device, a public address and a port number of the terminal device, and the fifth request message is used to request the user plane function network element to determine whether the first private address is valid; Determining whether the first private address is valid according to the correspondence between the locally stored private address, the public address and the port number; A fifth response message is sent to the network open function network element, where the fifth response message is used to indicate whether the first private address is valid.
24. The method according to claim 23, characterized in that The determining whether the first private address is valid according to the correspondence between the locally stored private address, the public address, and the port number includes: Determine a public address and a port number corresponding to the first private address according to the corresponding relationship and the first private address; If the public address and port number corresponding to the first private address are the same as the public address and port number, the fifth response message is used to indicate that the first private address is valid; otherwise, the fifth response message is used to indicate that the first private address is invalid.
25. The method according to claim 23, characterized in that The determining whether the first private address is valid according to the correspondence between the locally stored private address, the public address, and the port number includes: If it is determined, based on the corresponding relationship and the first private address, that the public address and port number corresponding to the first private address cannot be obtained, the fifth response message is used to indicate that the first private address is invalid.
26. The method according to claim 23, characterized in that The determining whether the first private address is valid according to the correspondence between the locally stored private address, the public address, and the port number includes: Determine, according to the corresponding relationship, the public address and the port number, a private address corresponding to the public address and the port number; If the private address corresponding to the public address and the port number is the same as the first private address and port number, the fifth response message is used to indicate that the first private address is valid; otherwise, the fifth response message is used to indicate that the first private address is invalid.
27. A communication system, characterized in that: Including edge enabling servers and network open function network elements: The edge enabling server is used to receive a first request message from a terminal device, where the first request message is used to obtain an identifier of the terminal device, and the first request message includes a first private address of the terminal device; The edge enabling server is also used to obtain the public address and port number of the terminal device; The edge enabling server is further used to send a second request message to the network open function network element, where the second request message is used to obtain an identifier of the terminal device, and the second request message includes the first private address, the public address and the port number; When it is determined that the first private address is valid according to the public address and the port number, the network open function network element is used to send an identifier of the terminal device to the edge enabling server.
28. The system according to claim 27, characterized in that When it is determined according to the public address and the port number that the first private address is invalid, the network open function network element is further used to send first indication information to the edge enabling server, where the first indication information is used to indicate that the communication device fails to obtain an identifier.
29. A communication device, characterized in that: The device comprises means for performing the method according to any one of claims 1 to 6.
30. A communication device, characterized in that: The device comprises means for performing the method according to any one of claims 7 to 19.
31. A communication device, characterized in that: The device comprises means for performing the method according to any one of claims 20 to 26.
32. A communication device, characterized in that: include: Memory for storing computer programs; A processor, configured to execute the computer program stored in the memory so that the communication device performs the method according to any one of claims 1 to 26.
33. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the method according to any one of claims 1 to 26 is implemented.
34. A computer program product, characterized in that The computer program product comprises instructions for executing the steps performed by the storage function network element in the method according to any one of claims 1 to 26.
Citation Information
Patent Citations
Communication method and communication device
CN118972078A
Method, device and system for acquiring internet protocol IP address of terminal equipment
CN111770207A
Method, device and system for opening network capability
CN116114234A
UE identification using its source IP address
WO2022039835A1
UE id exposure
WO2022151830A1
