Information acquisition method, function, terminal and storage medium

Abstract

The present application discloses an information acquisition method, the method including: a first function triggering a first terminal to send a first request message to a second function, the first request message being used to obtain a first identifier of the first terminal; the first terminal sending the first request message to the second function; the second function receiving the first request message sent from the first terminal; the second function obtaining the first identifier based on the first request message and the service of the second function; and the second function sending the first identifier to the first terminal or the first function. The present application further discloses a first function, a second function, a third function, a first terminal, and a computer-readable storage medium.

Description

[Technical Field]

[0001] The present application relates to, but is not limited to, the field of communications, and in particular to an information acquisition method, a first function, a second function, a third function, a first terminal, and a computer-readable storage medium.

[0002] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application is based on and claims priority from a Chinese patent application bearing application number 202310022461.8 and filed on January 7, 2023, the entire contents of which are incorporated herein by reference. [Background technology]

[0003] In current networks, the User Plane Function (UPF) is often the egress point from the core network, followed by the Network Address Translation (NAT) function. A UPF supporting NAT functionality can register with the Network Repository Function (NRF), which provides UPF provisioning information. The UPF provisioning information can include public Internet Protocol (IP) address pool information (i.e., public IP address range, additional port number range) for the NAT. The public IP address pool information may be based on the Digital Network Name (DNN) and Single Network Slice Selection Assistance Information (S-NSSAI). (An UPF supporting the NAT functionality may register in the NRF providing UPF provision information. The UPF provision information may include public IP address pool information (i.e., public IP address range, additionally port number range)) for the NAT. The public IP address pool information may be on a per-DNN and S-NSSAI basis. Packets after UPF use public IP addresses and may be shared by multiple User Equipment (UE) devices if network address and port translation is applied.The UPF interacts with the Application Function (AF) via the next generation (NG) interface 6 (abbreviated as N6 interface). The AP detects abnormal events in those packets associated with the UE based on the IP address and port number (public UE address information). Summary of the Invention [Problem to be solved by the invention]

[0004] However, the post-NAT user identifier is not unique, and the AF cannot fully utilize the core network's user identifier (ID: Identity document) open capability using the post-NAT user identifier, thereby failing to obtain the required user ID. The AF cannot obtain the UE private IP address used within the 5th generation mobile communication technology core (5GC). Because the AF cannot obtain the UE private IP address corresponding to the public UE address information, the AF may not be able to request appropriate action (e.g., UE policy change) against the UE that caused the abnormal event. [Means for solving the problem]

[0005] The embodiments of the present application provide an information acquisition method, a first function, a second function, a third function, a first terminal, and a computer-readable storage medium, and provide a UE ID open solution that supports NAT address translation with few changes to the core network.

[0006] In a first aspect, there is provided an information acquisition method applicable to a first function, the information acquisition method comprising: Triggering a first terminal to send a first request message to a second function, where the first request message is used to obtain a first identifier of the first terminal; receiving a first identifier of the first terminal transmitted from the second function.

[0007] In a second aspect, there is provided an information acquisition method applied to a second function, the information acquisition method including: receiving a first request message sent from a first terminal or a first function, the first request message being used to obtain a first identifier of the first terminal; obtaining the first identifier based on the first request message and the service of the second function; and transmitting the first identifier to the first terminal or the first function.

[0008] In a third aspect, there is provided an information acquisition method to be applied to a first terminal, the information acquisition method comprising: sending a first request message to a second function, wherein the first request message is used to obtain a first identifier of the first terminal; receiving a first identifier of the first terminal transmitted from the second function.

[0009] In a fourth aspect, there is provided an information acquisition method applied to the third function, the information acquisition method including: receiving a second request message sent from a first function, the second request message including a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; determining an identity of the second function based on a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function;

[0010] and transmitting an identification of the second function to the first function.

[0011] In a fifth aspect, a first function is provided, said first function comprising: a first processing module configured to trigger a first terminal to send a first request message to a second function, the first request message being used to obtain a first identifier of the first terminal; a first receiving module configured to receive a first identifier of the first terminal transmitted from the second function.

[0012] In a sixth aspect, a second function is provided, the second function comprising: a second receiving module configured to receive a first request message sent from a first terminal or a first function, the first request message being used to obtain a first identifier of the first terminal; a second processing module configured to obtain the first identifier based on the first request message and the service of the second function; and a second transmitting module configured to transmit the first identifier to the first terminal or the first function.

[0013] In a seventh aspect, there is provided a first terminal, the first terminal comprising: a third sending module configured to send a first request message to a second function, the first request message being used to obtain a first identifier of the first terminal; and a third receiving module configured to receive a first identifier of the first terminal transmitted from the second function.

[0014] In an eighth aspect, a third function is provided, the third function comprising: a fourth receiving module configured to receive a second request message sent from a first function, the second request message including a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; and a fourth processing module configured to determine an identity of the second function based on a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; and and a fourth transmitting module configured to transmit the identification information of the second function to the first function.

[0015] In a ninth aspect, a first function is provided, the first function comprising: a first memory for storing executable instructions; and a first processor for implementing the above-mentioned information acquisition method when executing executable instructions stored in the first memory.

[0016] In a tenth aspect, a second function is provided, the second function comprising: a second memory for storing executable instructions; and a second processor for implementing the above-mentioned information acquisition method when executing executable instructions stored in the second memory.

[0017] In an eleventh aspect, there is provided a first terminal, the first terminal comprising: a third memory for storing executable instructions; and a third processor for implementing the above-mentioned information acquisition method when executing executable instructions stored in the third memory.

[0018] In a twelfth aspect, a third function is provided, the third function comprising: a fourth memory for storing executable instructions; and a fourth processor for implementing the above-mentioned information acquisition method when executing executable instructions stored in the fourth memory.

[0019] In a thirteenth aspect, an embodiment of the present application provides a chip for realizing the above-mentioned information acquisition method, the chip comprising a processor that calls and executes a computer program from a memory to cause a device in which the chip is installed to execute the above-mentioned information acquisition method.

[0020] In a fourteenth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program that causes a computer to execute the information acquisition method described above.

[0021] In a fifteenth aspect, embodiments of the present application provide a computer program product comprising computer program instructions for causing a computer to perform the information acquisition method described above.

[0022] In a sixteenth aspect, an embodiment of the present application provides a computer program which, when executed on a computer, causes the computer to perform the information acquisition method described above. [Effects of the Invention]

[0023] In a method provided in an embodiment of the present invention, a first function triggers a first terminal to send a first request message to a second function. The first request message is used to obtain a first identifier of the first terminal. The first terminal sends the first request message to a second function. The second function receives the first request message sent from the first terminal. The second function obtains the first identifier based on the first request message and the service of the second function. The second function sends the first identifier to the first terminal or the first function. In other words, this application provides a UE ID open solution that supports NAT address translation with minimal changes to the core network. The first function uses a request forwarding scheme, i.e., the first function triggers the first terminal to send a request message to the second function, so that the second function can directly obtain the identifier of the first terminal, i.e., the UE ID, and then feed the identifier of the first terminal back to the first function. In this way, this application relies on a small number of core network elements and can also obtain the UE ID. There is no need to modify multiple core network elements in the current network, saving resources used for modifying network elements. [Brief explanation of the drawings]

[0024] [Figure 1] 1 is a schematic diagram of a communication system according to an embodiment of the present application; [Figure 2] 1 is a schematic flowchart of UE IP address mapping information published by UPF according to the related art; [Figure 3] 1 is a first schematic flowchart of an information acquisition method according to an embodiment of the present application; [Figure 4] 2 is a second schematic flowchart of an information acquisition method according to an embodiment of the present application. [Figure 5] 1 is a schematic flow chart of obtaining an NEF address according to the present application; [Figure 6] 1 is a schematic flowchart of an NEF registering a new service to an NRF according to an embodiment of the present application; [Figure 7]3 is a third schematic flowchart of an information acquisition method according to an embodiment of the present application. [Figure 8] 1 is a schematic flow chart of an AF / UE specific UE ID search according to the present application. [Figure 9] FIG. 2 is a schematic block diagram of a first function according to an embodiment of the present application. [Figure 10] FIG. 2 is a schematic block diagram of a second function according to an embodiment of the present application. [Figure 11] FIG. 2 is a schematic block diagram of a first terminal according to an embodiment of the present application; [Figure 12] FIG. 10 is a schematic block diagram of a third function according to an embodiment of the present application. [Figure 13] 1 is a schematic structural diagram of a communication device according to an embodiment of the present application; [Figure 14] 1 is a schematic structural diagram of a chip according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0025] Hereinafter, the technical solutions in the embodiments of the present application will be described with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without any creative efforts fall within the scope of protection of the present application. It should be noted that the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other if they are not contradictory.

[0026] FIG. 1 is a schematic diagram of a communication system according to an embodiment of the present application.

[0027] 1, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 communicates with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0028] It should be understood that the embodiments of the present application are illustratively described using only the communication system 100 as an example and are not limited thereto. That is, the technical solutions of the embodiments of the present application are applicable to various communication systems, such as a Long Term Evolution (LTE) system, a LTE Time Division Duplex (TDD), a Universal Mobile Telecommunication System (UMTS), an Internet of Things (IoT) system, a Narrow Band Internet of Things (NB-IoT) system, an Enhanced Machine-Type Communications (eMTC) system, a 5G communication system (also called a New Radio (NR) communication system), or a future communication system. 1, the network equipment 120 may be an access network equipment that communicates with the terminal equipment 110. The access network equipment may provide communication coverage to a particular geographic area and may communicate with the terminal equipment 110 (e.g., UE) located within the coverage area.

[0029] The network device 120 may be an evolved base station (eNB or eNodeB: Evolutional Node B) in a Long Term Evolution (LTE) system, or a Next Generation Radio Access Network (NG RAN) device, or a base station (gNB) in an NR system, or a radio controller in a Cloud Radio Access Network (CRAN), or the network device 120 may be a relay station, an access point, an in-vehicle device, a wearable device, a hub, a switch, a bridge, a router, or a network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0030] Terminal device 110 includes, but is not limited to, any terminal device connected to network device 120 or other terminal devices via wired or wireless connections.

[0031] For example, the terminal device 110 may refer to an access terminal, User Equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user equipment. An access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved network, etc.

[0032] The terminal device 110 can be used for device-to-device (D2D) communication.

[0033] The communication system 100 may further include a core network device 130 that communicates with a base station. The core network device 130 may be a 5G core network (5GC: 5G Core) device, such as an Access and Mobility Management Function (AMF) device, such as an Authentication Server Function (AUSF) device, such as a UPF device, or such as a Session Management Function (SMF) device. Optionally, the core network device 130 may be an Evolved Packet Core (EPC) device of an LTE network, such as a Session Management Function + Core Packet Gateway (SMF + PGW-C) device. It should be understood that the SMF + PGW-C can simultaneously realize the functions that the SMF and PGW-C can realize. During the network evolution process, the names of the above-mentioned core network devices may change, or the core network functions may be divided to form new network entities, but this is not limited to the embodiments of the present application.

[0034] Each functional unit in the communication system 100 can also establish a connection and realize communication via the NG interface.

[0035] For example, a terminal device establishes an air interface connection with an access network device via an NR interface to transmit user plane data and control plane signaling. The terminal device can establish a control plane signaling connection with an AMF via NG interface 1 (abbreviated as N1). An access network device such as a next-generation radio access base station (gNB) can establish a user plane data connection with a UPF via NG interface 3 (abbreviated as N3). The access network device can establish a control plane signaling connection with an AMF via NG interface 2 (abbreviated as N2). The UPF can establish a control plane signaling connection with an SMF via NG interface 4 (abbreviated as N4). The UPF can interact with a data network for user plane data via N6. The AMF can establish a control plane signaling connection with an SMF via NG interface 11 (abbreviated as N11). The SMF can establish a control plane signaling connection with a PCF via NG interface 7 (abbreviated as N7).

[0036] 1 exemplarily illustrates one base station, one core network device, and two terminal devices. Optionally, the communication system 100 may include multiple base station devices, and may include other numbers of terminal devices within the coverage area of ​​each base station, and the embodiments of the present application are not limited thereto.

[0037] It should be noted that FIG. 1 illustrates an exemplary system to which the present application is applicable, and the methods described in the embodiments of the present application are also applicable to other systems. In this specification, the terms "system" and "network" are always used interchangeably. The term "and / or" in this specification is merely used to describe a relation between related objects and indicates that three relationships can exist. For example, A and / or B can indicate three situations: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " in this specification generally indicates that the related objects before and after it are in an "or" relationship. It should be understood that the "reference" referred to in the embodiments of the present application may be a direct reference or an indirect reference, and may further indicate a relational relationship. For example, A referring to B may indicate that A directly refers to B, or that B can be obtained through A, or that A indirectly refers to B, or that A refers to C, and B can be obtained through C, and further indicate that there is a relational relationship between A and B. It should be further understood that the term "correspondence" referred to in the embodiments of the present application may indicate a direct or indirect correspondence between the two, an association relationship between the two, or a relationship such as indicating and being indicated, arranging and being arranged, etc. The terms "predefined" or "predefined rule" referred to in the embodiments of the present application may be implemented by pre-storing a code, table, or other method for indicating related information in a device (e.g., including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, the term "predefined" may refer to a protocol. In the embodiments of the present application, the term "protocol" may refer to a standard protocol in the communications field, and may include, for example, an LTE protocol, an NR protocol, and related protocols applied to future communication systems, but the present application is not limited thereto.

[0038] In order to facilitate understanding of the technical solutions of the embodiments of the present application, the related arts of the embodiments of the present application are described below. The following related arts can be arbitrarily combined with the technical solutions of the embodiments of the present application as alternative solutions, and all of them fall within the protection scope of the embodiments of the present application.

[0039] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application pertains. The terms used herein are used only to describe the examples of this application and are not intended to limit this application.

[0040] The third version of the 5G standard, Release 17, specifies that the AF-specific UE ID search uses the Generic Public Subscription Identifier (GPSI) corresponding to the AF request as the UE IP address. However, this version does not support the case where the UE IP address provided by the AF to the Network Exposure Function (NEF) corresponds to an IP address that has been NATed (Network and Port Address Translation).

[0041] To obtain the UE private IP address mapped from the UE public IP address information, the AF can request the UE UPF to disclose UE IP address mapping information. This solution applies to the case where the UPF supports NAT, i.e., does not support a NAT function located outside the UPF.

[0042] FIG. 2 is a schematic flowchart of UE IP address mapping information exposure by UPF according to the related art.

[0043] In step 201, the AF sends an Nnef_EventExposure_Subscribe request to the NEF. That is, the AF initiates an Nnef_EventExposure_Subscribe (i.e., AF ID: NATed addressing information) service operation to request UE IP address mapping information for a UE. Here, Nnef_EventExposure_Subscribe includes post-NAT address information and an AF ID. The post-NAT address information includes a public IP address and a port number. Here, the AF request may be used for one-time notification.

[0044] In step 202, the NEF finds the appropriate UPF using a UPF selection method targeting the UE's post-NAT addressing information and the DNN=S-NSSAI associated with the AF ID. This may use NRF discovery. The NEF may also use the post-NAT addressing information to determine the IP or domain name attribute, i.e., "ipDomain."

[0045] In step 203, the NEF sends a Nupf_EventExposure_Subscribe request to the UPF to request UE IP address mapping information, where the Nupf_EventExposure_Subscribe request carries public UE address information, DNN, and S-NSSAI associated with the AF ID.

[0046] In step 204, the UPF responds with the 5GC UE IP address mapping information to the NEF over the Nupf_EventExposure_Notify service operation. The 5GC UE IP address mapping information comprises a private IP address of the UE.

[0047] In step 205, the NEF responds to the AF over the Nnef_EventExposure_Notify service operation. The Nnef_EventExposure_Notify operation may provide 5GC UE IP address mapping information and may additionally include address assistance information which can help to uniquely identify the related IP address.

[0048] It should be noted that the above solution requires that the post-NAT IP pool of each IP domain be registered in the UPF network service template (NFprofile), and the UPF must support open service for UE IP address mapping information. The NEF must support the newly introduced openness for UE IP address mapping information by the UPF. The NRF must support UPF registration using the UPF NAT information of each IP domain and support UPF discovery using the NATed UE IP address as input. In other words, the above solution requires modifications to multiple core network elements.

[0049] 3 is a schematic flowchart of an information acquisition method according to an embodiment of the present application. As shown in FIG. 3, the method is applied to at least the core network device 130 and the terminal device 110 in the communication system 100 shown in FIG. 1. The method includes steps 301 to 306.

[0050] In step 301, the first function triggers the first terminal to send a first request message to the second function.

[0051] Here, the first request message is used to obtain a first identifier of the first terminal.

[0052] In the embodiment of the present application, the first function may be an AF, an NEF, or another network function (NF) that can trigger the first terminal to send the first request information to the second function. The second function may be an AF, such as an edge enabler server (EES), or an NEF. That is, the first function and the second function may be the same entity, for example, both of them are NEFs.

[0053] In an embodiment of the present application, the first function and the second function belong to the core network equipment 130 and may be functional entities such as a network element, a controller, a server, etc. Here, the network element may be a network element implemented on dedicated hardware, a software instance running on dedicated hardware, or an instance of a virtualized function on a suitable platform.

[0054] In an embodiment of the present application, the first request message is a redirect request triggered by the first function.

[0055] In the embodiment of the present application, the first terminal is a device that supports a dual stack of Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6).

[0056] In an embodiment of the present application, the second function, e.g., NEF, is an IPv6 device, and the NEF needs to support the UE ID open process triggered by the UE and has already registered this capability with the third function, e.g., Network Function Repository Function (NRF).

[0057] In an embodiment of the present application, the timing at which the first function triggers the first terminal to send a first request message to the second function is that the first function determines that it needs to obtain an identifier of the first terminal.

[0058] In an embodiment of the present application, the first identifier of the first terminal, i.e., the UE ID, includes a post-NAT private IP address, a public IP address, an external identifier, and a pre-NAT private IP address corresponding to the first terminal.

[0059] In an embodiment of the present application, the first request message includes a terminal address of the first terminal, for example, an IPv6 address, and / or a second identifier of the first function, for example, an AF ID.

[0060] In the embodiment of the present application, the number of first terminals may be one or more.

[0061] In step 302, the first terminal sends a first request message to the second function.

[0062] In an embodiment of the present application, a client is located in a first terminal, and the first request message may be generated by the first terminal, or the first request message may be generated by the client on the first terminal. That is, when a first function triggers the first terminal to send the first request message to a second function, the client on the first terminal can send the first request message to the second function.

[0063] In the embodiment of the present application, the manner of sending the first request message may be in-band, out-of-band, media, signaling, data, message, control plane, user plane, etc.

[0064] In the embodiment of the present application, the first request message may be a response message, an instruction message, a reply message, etc.

[0065] In step 303, the second function receives a first request message sent from the first terminal.

[0066] In step 304, the second function obtains a first identifier based on the first request message and the service of the second function.

[0067] In an embodiment of the present application, the second function obtains the first identifier based on at least one of the service of the second function, the terminal address of the first terminal, or the second identifier.

[0068] Here, the terminal address of the first terminal includes, but is not limited to, the IP address and media access control address (MAC address) of the first terminal.

[0069] In the embodiment of the present application, the service of the second function may be a service located in the second function, or may be a service located in an associated device that can be directly called by the second function.

[0070] In the embodiment of the present application, when the first function is an AF and the second function is an NEF, the service of the second function is an existing UE ID search service and a received IPv6 address to obtain a UE ID. When the first function is an NEF and the second function is a Unified Data Management function (UDM), the service of the second function is a User Data Get (udm_SDM_Get) service.

[0071] In step 305, the second function transmits the first identifier to the first terminal or first function.

[0072] In an embodiment of the present application, when the second function obtains the first identifier, it can feed back to the first terminal, which can then retransmit it to the first function, or the second function can feed back directly to the first function.

[0073] In an embodiment of the present application, the first identifier may be transmitted in an in-band, out-of-band, media, signaling, data, message, control plane, user plane, or other manner. Since the first identifier is transmitted in-band via an existing media channel, compatibility with existing systems is improved and system modification costs are reduced. Furthermore, when the first identifier is transmitted to multiple recipients, the established media plane communication channel is a one-to-many multicast / broadcast communication channel. In this way, the first identifier can be received by multiple recipients by transmitting it only once via the established multicast / broadcast communication channel, effectively reducing the number of message transmissions.

[0074] In an embodiment of the present application, the second function determines an address of the first function based on the second identifier, and the second function sends a first identifier to the first function based on the address of the first function. The first function receives the first identifier, where the address of the first function includes, but is not limited to, an IP address of the first function and a MAC address of the first function.

[0075] In an embodiment of the present application, a redirect message is sent to a first terminal, and the first terminal receives the redirect message sent from the second function, where the redirect message carries a first identifier.

[0076] In step 306, the first terminal or first function receives the first identifier sent from the second function.

[0077] In a method provided in an embodiment of the present invention, a first function triggers a first terminal to send a first request message to a second function, where the first request message is used to obtain a first identifier of the first terminal. The first terminal sends the first request message to a second function. The second function receives the first request message sent from the first terminal. The second function obtains the first identifier based on the first request message and the service of the second function. The second function sends the first identifier to the first terminal or the first function. The second function sends the first identifier to the first terminal or the first function. In other words, this application is a UE ID open solution that supports NAT address translation with few changes to the core network, where the first function uses a request forwarding method, i.e., the first function triggers the first terminal to send a request message to the second function, so that the second function can directly obtain the identifier of the first terminal, i.e., the UE ID, and then feed the identifier of the first terminal back to the first function. In this way, the small number of core network elements on which the present application relies obtains the UE ID, while there is no need to modify multiple core network elements of the current network, saving resources used for modifying network elements.

[0078] In some embodiments, before the first function triggers the first terminal to send a first request message to the second function in step 301, the method provided by the embodiment of the present invention includes the following content:

[0079] In step A1, a first terminal sends a service request to a first function.

[0080] Here, the service request includes an address for indicating whether the first terminal supports two types of Internet Protocol.

[0081] In an embodiment of the present application, the first terminal can indicate in the service request that it supports dual stack, for example, it can carry two addresses in the service request source, or the first function asks the first terminal whether it supports dual stack.

[0082] In step A2, the first function receives a service request sent from the first terminal.

[0083] In step A3, the first function determines, based on the service request, whether a first identifier of the first terminal needs to be obtained when responding to the service request.

[0084] In an embodiment of the present application, the first function determines, based on a (pre-set) policy, whether it is necessary to trigger the first terminal to send a first request message to the second function. For example, the first function determines that some services of the first terminal have a common demand and need to know the UE ID, and if it is necessary to know the UE ID, it triggers the first terminal to send a first request message to the second function.

[0085] In step A4, if the first function determines that it needs to obtain a first identifier of the first terminal when responding to the service request, it performs step 301.

[0086] If the first function determines that it is not necessary to obtain the first identifier of the first terminal when responding to the service request, the first function may directly respond to the service request and perform the responsive service operation.

[0087] FIG. 4 is a schematic flowchart of the information acquisition method according to the present application.

[0088] In step 401, the UE sends a service request to the AF.

[0089] The AF receives a service request, e.g., HTTP GET (IPv4), sent from the UE, carrying its public network IPv4 address, where the UE indicates in the GET that it supports dual stack, or the AF asks the UE whether it supports dual stack.

[0090] In step 402, the AF determines based on a (pre-configured) policy whether an HTTP 302 redirect needs to be triggered, i.e., whether the UE ID needs to be obtained.

[0091] In step 403, the AF conveys the information of the IP address segment to the NRF based on pre-configuration or dynamic matching.

[0092] In step 404, if the AF determines that some services of the UE have a common demand and need to know the UE ID, the AF triggers the IPv6 NEF to perform a UE ID lookup using a Uniform Resource Identifier (URI), i.e., the AF triggers the UE to send a request to the NEF to perform a UE ID lookup.

[0093] Here, the AF ID may be carried in the "Content-Type" message header of the service request and sent to the UE, triggering the UE to perform automatic redirection and requesting the NEF to search for the UE ID. Of course, the AF's authentication information may also be carried in the "Content-Type" message header, helping the UE to obtain authentication from the NEF.

[0094] In the embodiment of the present application, the UE sends a request to the NEF to trigger a UE ID search, and since it is an interaction with an IPv6 device, the user's IPv6 address is carried in this request.

[0095] In step 405, the NEF obtains the UE ID using an existing UE ID lookup service based on the UE's IPv6 address.

[0096] In step 406, the NEF sends the UE ID to the UE / AF.

[0097] When the NEF sends the UE ID to the UE, a URI is returned that triggers an HTTP redirect, and the UE returns the returned redirect to the AF, or the NEF sends the UE ID to the AF directly (e.g., obtains the URL of the AF from the Referer).

[0098] In step 407, the NEF sends the IPv6 address of the UE to the AF, ie, returns the IPv6 address of the user.

[0099] In step 408, the AF uses the received IPv6 address to interact with the NEF and obtains the UE ID using the existing UE ID lookup service via the NEF.

[0100] In some embodiments, a method provided by an embodiment of the present invention includes:

[0101] In step B1, the first function obtains the identification information of the second function.

[0102] Here, the identification information is a third identifier of the second function; the internet protocol address of the second function, Secondary function Internet Protocol version number, The fully qualified domain name of the second feature, and At least one of the port numbers of the second function is included.

[0103] In the embodiment of the present application, the third identifier of the second function includes, but is not limited to, an EESID.

[0104] In some embodiments, the AF has the capability to obtain the IPv6 address / port of the NEF.

[0105] In some embodiments, step B1 of obtaining the identification information of the second function may be realized by step B11, or by step B12, or by step B13, or by steps B14 to B18.

[0106] In step B11, the first function obtains the identification information of the second function from the local profile of the first function.

[0107] In step B12, the first function performs a domain name system query using the fully qualified domain name of the second function to obtain the identification information of the second function.

[0108] In step B13, the first function executes a service discovery process, ie, TS23.558.clause 8.3.3, using the third identifier of the first terminal to obtain the identification information of the indicated second function.

[0109] In step B14, the first function sends a second request message to the third function.

[0110] Here, the second request message includes the service name of the second function, the function type, the internet protocol address range of the second function, or the expected internet protocol address version.

[0111] In step B15, the third function receives the second request message sent from the first function.

[0112] In step B16, the third function determines the identity of the second function based on the service name of the second function, the function type, the Internet Protocol address range of the second function, or the Internet Protocol address version expected by the second function.

[0113] In step B17, the third function transmits the identification information of the second function to the first function.

[0114] In step B18, the first function receives the identification information of the second function sent from the third function.

[0115] Here, the identification information of the second function is determined by the third function based on the service name of the second function, the function type, the Internet Protocol address range of the second function, or the expected Internet Protocol address version.

[0116] In an embodiment of the present application, the manner in which the AF obtains the IPv6 address / port of the NEF may include local configuration in the AF. Alternatively, the AF may discover the fully qualified domain name (FQDN) or IP address / port of the NEF / L-NEF(s) by performing a DNS query using the external identifier of a single UE or the external group identifier of a group of UEs. Alternatively, the AF may discover the FQDN or IP address / port of the NEF or L-NEF using the NRF. Here, the NRF must support NEF selection based on the requested IP address version.

[0117] 5 is a schematic flow chart of obtaining an NEF address according to the present application. It should be noted that the AF discovers a suitable NEF address via the NRF.

[0118] In step 501, a network function service consumer such as an AF sends a Nnrf_NFDiscovery_Request to an NRF, i.e., the network function service consumer invokes Nnrf_NFDiscovery_Request from an appropriately configured NRF in the same Public Land Mobile Network (PLMN). Here, the Nnrf_NFDiscovery_Request includes the NF service name expected by the AF, the NF type of the expected NF instance, the NF type of the NF consumer, an IP address range, and the expected NF IP address version. The IP address version includes at least one of IPv4 and IPv6.

[0119] In step 502, the NRF authorizes network function service discovery (NRF Authorize NF Service Discovery), i.e., the NRF determines whether the NF service consumer is allowed to discover the expected NF instance(s) based on the profile of the expected NF / NF service, the type of the NF service consumer, and the expected NF IP address version carried in the Nnrf_NFDiscovery_Request (The NRF authorizes the Nnrf_NFDiscovery_Request. Based on the profile of the expected NF / NF service, the type of the NF service consumer, and the Expected NF IP address version, the NRF determines whether the NF service consumer is allowed to discover the expected NF instance(s).

[0120] In step 503, the NRF responds to the network function service consumer via an Nnrf_NFDiscovery_Request. That is, if allowed, the NRF determines a set of NF instances matching the Nnrf_NFDiscovery_Request and the internal policies of the NRF and sends the NF profile(s) of the determined NF instances.

[0121] In some embodiments, the methods provided by the embodiments of the present application include:

[0122] In step C1, the first function sends a third request message to the third function.

[0123] Here, the third request message is used to indicate that the second function supports a terminal identifier search service or a terminal identifier provision service.

[0124] In the embodiment of the present application, the manner of sending the third request message may be in-band, out-of-band, media, signaling, data, message, control plane, user plane, etc.

[0125] In step C2, the third function receives the third request message sent from the first function.

[0126] 6 is a schematic flowchart of the NEF registering a new service to the NRF according to the present application, where the NEF needs to be able to support authentication for the request initiated by the UE when receiving the request from the UE.

[0127] In step 601, a network function service consumer such as an NEF sends an Nnrf_NFManagement_NFRegister request to the NRF, i.e., when the network function service consumer starts operating for the first time, the NEF sends an Nnrf_NFManagement_NFRegister / Update request message to the NRF to inform the NRF of its NF profile when the NF service consumer becomes operative for the first time.

[0128] It should be noted that the Nnrf_NFManagement_NFRegister / Update request message indicates to the NRF that this NEF supports the UE ID search service from the UE and that the IP address of this NEF is IPv6.

[0129] In step 602, the NRF stores the network function profile of the NF service consumer. In an embodiment of the present application, the NRF marks the network function service consumer available when it stores the network function profile of the network function service consumer.

[0130] In step 603, the NRF sends a Nnrf_NFManagement_NFRegiste_response to the network function service consumer, i.e., the NRF acknowledges NF Registration is accepted via the Nnrf_NFManagement_NFRegister response.

[0131] 7 is a schematic flowchart of an information acquisition method according to an embodiment of the present application. As shown in FIG. 7, the method is applied to at least the core network device 130 in the communication system 100 shown in FIG. 1, and includes steps 701 to 705.

[0132] In step 701, a first function sends a first request message to a second function.

[0133] Here, the first request message is used to obtain a first identifier of the first terminal.

[0134] In an embodiment of the present application, the first request message includes a terminal address of the first terminal and / or a second identifier of the first function.

[0135] In an embodiment of the present application, the first request message is a redirect request triggered by the first function.

[0136] In step 702, the second function receives the first request message sent from the first function.

[0137] In step 703, the second function obtains a first identifier based on the first request message and the service of the second function.

[0138] In an embodiment of the present application, the second function obtains the first identifier based on at least one of the service of the second function, the terminal address of the first terminal, or the second identifier.

[0139] In step 704, the second function sends the first identifier to the first function.

[0140] In step 705, the first function receives the first identifier sent from the second function.

[0141] In an embodiment of the present application, the AF / UE supports specific UE ID retrieval, where the UE ID may be represented by the External Identifier as defined in TS 23.003

[33] .

[0142] FIG. 8 is a schematic flow chart of AF / UE specific UE ID search according to the present application.

[0143] In step 801, the AF / UE sends a Nnef_UEId_Get request to the NEF, i.e., the AF / UE retrieves the UE ID via the Nnef_UEId_Get request message service operation. The request message should include the UE address (IP address or MAC address) and the AF identifier, and may also include Machine Type Communications (MTC), provider information, application port ID, and IP domain. If available, the AF may further provide the corresponding DNN and / or S-NSSAI.

[0144] In step 802, the NEF grants the AF / UE request.

[0145] If authorization is not granted, the NEF replies to the AF with a "Result" value indicating authorization failure; otherwise, the NEF determines the corresponding DNN and / or S-NSSAI information, which may have been provided by the AF or determined by the NEF based on the requesting AF Identifier and MTC Provider Information.

[0146] In step 803, the NEF sends an Nbsf_Management_Discovery request to the BSF, i.e., the NEF uses the Nbsf_Management_Discovery service operation with the UE address and IP domain and / or DNN and / or S-NSSAI to retrieve the session binding information of the UE.

[0147] In step 804, the BSF sends an Nbsf_Management_Discovery response to the NEF.

[0148] If no SUPI (Subscription Permanent Identifier) ​​is received in the session binding information returned by the BSF via Nbsf_Management_Discovery, the NEF replies to the AF with a Result value indicating that the UE ID is not available.

[0149] In step 805, the NEF sends a Nudm_SDM_Get request to the UDM. That is, the NEF interacts with the UDM to retrieve the AF-specific UE Identifier via the Nudm_SDM_Get request service operation. The request message includes the SUPI and at least one of the Application Port ID, MTC Provider Information, or AF Identifier.

[0150] In step 806, the UDM sends a Nudm_SDM_Get response to the NEF. That is, the UDM responds to the NEF with an AF-specific UE Identifier represented as an External Identifier for the UE which is uniquely associated with the Application Port ID, MTC provider information, and / or AF Identifier.

[0151] In step 807, the NEF sends a Nnef_UEId_Get response to the AF / UE, i.e., the NEF further responds to the AF / UE with the information (including the AF-specific UE Identifier represented as an External Identifier) ​​received from the UDM.

[0152] In the embodiment of the present application, if the reply is from the AF, the NEF will guess the address of the AF based on the AF ID and send the UE ID to the AF; if the reply is from the UE, the reply should be a redirect URI, and the UE ID will be carried in the content and passed to the AF.

[0153] The embodiment of the present application provides a first function, which may be used to realize the information acquisition method provided by the embodiment corresponding to FIG. 3 and FIG. 7. As shown in FIG. 9, the first function 900 includes: a first processing module 901 configured to trigger a first terminal to send a first request message to a second function, where the first request message is used to obtain a first identifier of the first terminal; a first receiving module 902 configured to receive a first identifier of the first terminal sent from the second function.

[0154] In another embodiment of the present application, the first request message includes a terminal address of the first terminal and / or a second identifier of the first function.

[0155] In another embodiment of the present application, the first identifier is obtained by the second function based on at least one of a service of the second function, a terminal address of the first terminal, or the second identifier.

[0156] In another embodiment of the present application, the first request message is a redirect request triggered by the first function.

[0157] In another embodiment of the present application, the first receiving module 902 is configured to receive a service request sent from a first terminal; The first processing module 901 is configured to determine, based on the service request, whether a first identifier of the first terminal needs to be obtained when responding to the service request; The first processing module 901 is configured to trigger the first terminal to send a first request message to the second function when the first function determines that a first identifier of the first terminal needs to be obtained when responding to a service request.

[0158] In another embodiment of the present application, the first function 900 further includes a first obtaining module 903 configured to obtain identification information of the second function, where the identification information includes at least one of a third identifier of the second function, an Internet Protocol address of the second function, an Internet Protocol version number of the second function, a fully qualified domain name of the second function, and a port number of the second function.

[0159] In another embodiment of the present application, the first obtaining module 903 is configured to obtain the identification information of the second function from the local profile of the first function; The first processing module 901 is configured to perform a domain name system query using a fully qualified domain name of the second function to obtain identification information of the second function; The first processing module 901 is configured to perform a service discovery process using the third identifier of the first terminal to obtain identification information of the indicated second function.

[0160] In another embodiment of the present application, the first function 900 further includes a first sending module 904 configured to send a second request message to a third function, where the second request message includes a service name of the second function, a function type, an Internet Protocol address range of the second function, or an expected Internet Protocol address version; The first receiving module 902 is configured to receive identification information of the second function sent from the third function, where the identification information of the second function is determined by the third function based on the service name of the second function, the function type, the Internet Protocol address range of the second function, or the expected Internet Protocol address version.

[0161] The above description of the apparatus embodiment is similar to the above description of the method embodiment, and has the same beneficial effects as the method embodiment. For technical details not disclosed in the apparatus embodiment of the present application, please refer to the description of the method embodiment of the present application.

[0162] It should be noted that in the embodiments of the present application, the above-mentioned information acquisition method may be implemented in the form of a software functional module and stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solutions of the embodiments of the present application may essentially or in part contribute to the prior art be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a terminal device to execute all or part of the methods of each embodiment of the present application. The storage medium may include various media capable of storing program code, such as a USB flash disk, a mobile hard disk, a ROM, a magnetic disk, or an optical disk. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0163] The embodiment of the present application provides a second function, which may be used to realize the information acquisition method provided by the embodiment corresponding to FIG. 3 and FIG. 7. As shown in FIG. 10, the second function 1000 includes: a second receiving module 1001 configured to receive a first request message sent from a first terminal or a first function, the first request message being used to obtain a first identifier of the first terminal; a second processing module 1002 configured to obtain a first identifier based on the first request message and the service of the second function; and a second sending module 1003 configured to send the first identifier to the first terminal or the first function.

[0164] In another embodiment of the present application, the first request message includes a terminal address of the first terminal and / or a second identifier of the first function; The second processing module 1002 is configured to obtain the first identifier based on at least one of a service of the second function, a terminal address of the first terminal, or a second identifier.

[0165] In another embodiment of the present application, the first request message is a redirect request triggered by the first function.

[0166] In another embodiment of the present application, the second sending module 1003 is configured to send a third request message to the third function, where the third request message is used to indicate that the second function supports a terminal identifier search service or a terminal identifier provision service.

[0167] In another embodiment of the present application, the second processing module 1002 is configured to determine an address of the first function based on the second identifier, and to send the first identifier to the first function based on the address of the first function.

[0168] In another embodiment of the present application, the second sending module 1003 is configured to send a redirect message to the first terminal, where the redirect message carries the first identifier.

[0169] The above description of the apparatus embodiment is similar to the above description of the method embodiment, and has the same beneficial effects as the method embodiment. For technical details not disclosed in the apparatus embodiment of the present application, please refer to the description of the method embodiment of the present application.

[0170] It should be noted that in the embodiments of the present application, the above-mentioned information acquisition method may be implemented in the form of a software functional module and stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solutions of the embodiments of the present application may essentially or in part contribute to the prior art be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a terminal device to execute all or part of the methods of each embodiment of the present application. The storage medium may include various media capable of storing program code, such as a USB flash disk, a mobile hard disk, a ROM, a magnetic disk, or an optical disk. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0171] The embodiment of the present application provides a first terminal, which can be used to realize the information acquisition method provided by the embodiment corresponding to FIG. 3. As shown in FIG. 11, the first terminal 1100: a third sending module 1101 configured to send a first request message to a second function, where the first request message is used to obtain a first identifier of the first terminal; and a third receiving module 1102 configured to receive the first identifier transmitted from the second function.

[0172] In another embodiment of the present application, the first request message includes a terminal address of the first terminal and / or a second identifier of the first function.

[0173] In another embodiment of the present application, the first identifier is obtained by the second function based on at least one of a service of the second function, a terminal address of the first terminal, or the second identifier.

[0174] In another embodiment of the present application, the third receiving module 1102 is configured to receive a redirect message sent from the second function, where the redirect message carries the first identifier.

[0175] In another embodiment of the present application, the third sending module 1101 is configured to send the service request to the first function; The third sending module 1101 is configured to send a first request message to the second function when the first function determines that it needs to obtain a first identifier of the first terminal when responding to a service request.

[0176] In another embodiment of the present application, the service request includes an address to indicate whether the first terminal supports two Internet Protocol types.

[0177] In another embodiment of the present application, the first request message is a redirect request triggered by the first function.

[0178] The above description of the apparatus embodiment is similar to the above description of the method embodiment, and has the same beneficial effects as the method embodiment. For technical details not disclosed in the apparatus embodiment of the present application, please refer to the description of the method embodiment of the present application.

[0179] It should be noted that in the embodiments of the present application, the above-mentioned information acquisition method may be implemented in the form of a software functional module and stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solutions of the embodiments of the present application may essentially or in part contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a terminal device to execute all or part of the methods of each embodiment of the present application. The storage medium includes various media capable of storing program code, such as a USB flash disk, a mobile hard disk, a ROM, a magnetic disk, or an optical disk. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0180] The embodiment of the present application provides a third function, which may be used to realize the information acquisition method provided by the embodiment of the present application. As shown in FIG. 12 , the third function 1200 includes: a fourth receiving module 1201 configured to receive a second request message sent from the first function, wherein the second request message includes a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; a fourth processing module 1202 configured to determine an identity of the second function based on a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; and a fourth sending module 1203 configured to send the identification information of the second function to the first function.

[0181] In another embodiment of the present application, the fourth receiving module 1201 is configured to receive a third request message sent from the first function, where the third request message is used to indicate that the second function supports a terminal identifier search service or a terminal identifier provision service.

[0182] The above description of the apparatus embodiment is similar to the above description of the method embodiment, and has the same beneficial effects as the method embodiment. For technical details not disclosed in the apparatus embodiment of the present application, please refer to the description of the method embodiment of the present application.

[0183] It should be noted that in the embodiments of the present application, the above-mentioned information acquisition method may be implemented in the form of a software functional module and stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solutions of the embodiments of the present application may essentially or in part contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a terminal device to execute all or part of the methods of each embodiment of the present application. The storage medium includes various media capable of storing program code, such as a USB flash disk, a mobile hard disk, a ROM, a magnetic disk, or an optical disk. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0184] 13 is a schematic structural diagram of a communication device 1300 according to an embodiment of the present application. The communication device may be a first function, a second function, a third function, or a first terminal. The communication device 1300 shown in FIG. 13 includes a first processor 1310, which can load and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0185] Optionally, as shown in Fig. 13, the communication device 1300 may further include a first memory 1320. Here, the first processor 1310 can call and execute a computer program from the first memory 1320 to implement the method in the embodiment of the present application. Here, the first memory 1320 may be a single device independent of the first processor 1310 or may be integrated into the first processor 1310.

[0186] Optionally, as shown in FIG. 13, the communication device 1300 may further include a transceiver 1330, and the first processor 1310 may control the transceiver 1330 to communicate with other devices, specifically to transmit information or data to other devices or receive information or data transmitted from other devices.

[0187] Here, the transceiver 1330 may include a transmitter and a receiver, and may further include an antenna, the number of which may be one or more.

[0188] Optionally, the communication device 1300 may specifically be the first function / second function / third function of the embodiments of the present application, and the communication device 1300 may realize the corresponding processes realized by the first function / second function / third function in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0189] Optionally, the communication device 1300 may specifically be the first terminal in the embodiments of the present application, and the communication device 1300 may implement the corresponding processes implemented by the first terminal in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0190] 14 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 1400 shown in FIG. 14 includes a second processor 1410, which can call and execute a computer program from memory to implement the method according to the embodiment of the present application.

[0191] Optionally, as shown in Figure 14, the chip 1400 may further include a second memory 1420. Here, the second processor 1410 can call and run a computer program from the second memory 1420 to implement the method in the embodiment of the present application.

[0192] Here, the second memory 1420 may be a single, stand-alone device independent of the second processor 1410, or may be integrated into the second processor 1410.

[0193] Optionally, the chip 1400 may further include an input interface 1430. Here, the second processor 1410 can control the input interface 1430 to communicate with other devices or chips, and specifically can obtain information or data transmitted from other devices or chips.

[0194] Optionally, the chip 1400 may further include an output interface 1440. Here, the second processor 1410 can control the output interface 1440 to communicate with other devices or chips, and specifically can output information or data to other devices or chips.

[0195] Optionally, the chip may be applied to a first terminal in an embodiment of the present application, and the chip can realize the corresponding processes realized by the first terminal in each method of the embodiment of the present application, which will not be repeated here for the sake of brevity.

[0196] Optionally, the chip may be applied to the first function / second function / third function in the embodiments of the present application, and the chip can realize the corresponding processes realized by the first function / second function / third function in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0197] It should be understood that the chips referred to in the embodiments of this application may also be referred to as system level chips, system chips, chip systems, system-on-chip chips, or the like.

[0198] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In the implementation process, each step of the above-described method embodiments can be completed by a hardware integrated logic circuit in the processor or by instructions in software format. The above-described processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, etc., which can realize or execute each method, step, and logic block diagram disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor or by being executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the aforementioned method in combination with the hardware.

[0199] As an example, a processor may include one or more general-purpose central processing units (CPUs), each of which may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor, in this context, may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer-executable instructions).

[0200] It will be understood that the memory in the embodiments of the present application may be volatile or nonvolatile memory, or may include both volatile and nonvolatile memory. Here, nonvolatile memory may be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory may be random access memory (RAM) used as an external cache. By way of example, and not limitation, many forms of RAM can be used, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronously linked dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). It should be noted that memory in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0201] It should be understood that the above memory is an exemplary description and not a limitation. For example, the memory in the embodiments of the present application may further be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), sync link dynamic random access memory (SLDRAM), and direct memory bus random access memory (DRRAM). Thus, the memory in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0202] An embodiment of the present application further provides a computer-readable storage medium for storing a computer program.

[0203] Optionally, the computer-readable storage medium can be applied to a first terminal in the embodiments of the present application, and the computer program causes a computer to execute corresponding processes implemented by the first terminal in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0204] Optionally, the computer-readable storage medium may be applied to the first function / second function / third function in the embodiments of the present application, and the computer program causes a computer to execute the corresponding processes realized by the first function / second function / third function in each method of the embodiments of the present application, which will not be repeated here for the sake of brevity.

[0205] In the above embodiments, all or part of the embodiments can be realized by software, hardware, firmware, or any combination thereof. If realized by software, all or part of the embodiments can be realized in the form of a computer program product.

[0206] A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, processes or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored on a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optics, digital user line (DSL)) or wireless (e.g., infrared, radio, microwave, etc.) methods. The computer-readable storage medium may be any available medium on which a computer can store data, or a data storage device such as an integrated server, data center, or the like that includes one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid state disks (SSDs)).

[0207] The above provides a detailed introduction to the information acquisition method, the first function, the second function, the third function, the first terminal, and the computer-readable storage medium according to the embodiments of the present application. This specification uses specific examples to illustrate the principles and implementation of the present application. The above description of the embodiments is intended only to assist in understanding the method and core idea of ​​the present application. At the same time, those skilled in the art will recognize that there may be changes in the specific embodiments and application scope based on the concept of the present application. In summary, the contents of this specification should not be construed as limitations on the present application.

[0208] References throughout this specification to "one embodiment," "one embodiment," "embodiment of the present application," "the aforementioned embodiment," "some embodiments," or "some embodiments" should be understood to mean that a particular feature, structure, or characteristic associated with an embodiment is included in at least one embodiment of the present application. Therefore, the appearances of "one embodiment," "one embodiment," "embodiment of the present application," "the aforementioned embodiment," "some embodiments," or "some embodiments" throughout this specification do not necessarily refer to the same embodiment. Furthermore, these particular features, structures, or characteristics may be combined in any appropriate manner in one or more embodiments. In each embodiment of the present application, the magnitude of the sequence numbers of each process does not imply an 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 embodiment of the present application. The sequence numbers in the above-mentioned embodiments of the present application are for illustrative purposes only and do not indicate the superiority or inferiority of the embodiments.

[0209] Unless otherwise specified, the first function / second function / third function / first terminal performing any step in the embodiments of the present application may mean that the processor of the first function / second function / third function / first terminal performs the step. Unless otherwise specified, the embodiments of the present application do not limit the order in which the first function / second function / third function / first terminal performs the following steps. In addition, the manner of processing data in different embodiments may be the same or different.

[0210] It should be understood that in some embodiments provided in the present application, the disclosed devices and methods may be realized in other ways. The device embodiments described above are merely illustrative. For example, the division of the units is only a logical and functional division. In actual implementation, other division modes are possible. For example, multiple units or components may be combined or integrated into another system, or some features may be omitted or not implemented. Furthermore, the mutual coupling or direct coupling or communication connection between each component shown or discussed may be an indirect coupling or communication connection via some interfaces, devices, or units, which may be electrical, mechanical, or other forms.

[0211] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units, and some or all of the units may be selected according to actual needs to achieve the objective of the solution of this embodiment.

[0212] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may be a single unit, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be realized in the form of hardware or in the form of a functional unit of hardware and software.

[0213] The methods disclosed in the several method embodiments provided in this application can be combined in any way to obtain new method embodiments, if not inconsistent.

[0214] The features disclosed in the several product embodiments provided in this application may be combined in any manner, where not inconsistent, to obtain new product embodiments.

[0215] The features disclosed in the several method or apparatus embodiments provided in this application may be combined in any manner, where not inconsistent, to produce new method or apparatus embodiments.

[0216] Those skilled in the art will understand that all or part of the steps for implementing the above method embodiments can be completed by instructing related hardware through a program. The above program may be stored in a computer storage medium. When the program is executed, it performs the steps comprising the above method embodiments. The above storage medium includes various media capable of storing program code, such as a mobile storage device, a ROM, a magnetic disk, or an optical disk.

[0217] Alternatively, the above-mentioned integrated units of the present application may be realized in the form of software functional modules and stored in a computer storage medium when sold or used as an independent product. Based on this understanding, the technical solutions of the embodiments of the present application may essentially or in part contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes various media capable of storing program code, such as a mobile storage device, a ROM, a magnetic disk, or an optical disk.

[0218] As used in the examples and appended claims of this application, the singular forms "a," "the," and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

[0219] It should be noted that in each embodiment of the present application, all steps may be implemented or only some steps may be implemented, as long as a complete technical solution can be formed.

[0220] The above description is only an embodiment of the present application, and the scope of protection of the present application is not limited thereto. Anyone skilled in the art can easily think of modifications or replacements within the technical scope disclosed in the present application, all of which should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be subject to the scope of protection of the claims.

Claims

1. An information acquisition method applied to a first function, Triggering a first terminal to send a first request message to a second function, the first request message being used to obtain a first identifier of the first terminal; receiving a first identifier of the first terminal transmitted from the second function.

2. The first request message includes a terminal address of the first terminal and / or a second identifier of the first function. The information acquisition method according to claim 1 .

3. the first identifier is obtained by the second function based on at least one of a service of the second function, a terminal address of the first terminal, or a second identifier; The information acquisition method according to claim 2 .

4. the first request message is a redirect request triggered by the first function; The information acquisition method according to any one of claims 1 to 3.

5. The information acquisition method further includes: receiving a service request sent from the first terminal; determining, based on the service request, whether a first identifier of the first terminal needs to be obtained when responding to the service request; triggering the first terminal to send a first request message to a second function if the first function determines that a first identifier of the first terminal needs to be obtained when responding to the service request; The information acquisition method according to any one of claims 1 to 4.

6. The information acquisition method further includes: obtaining an identification of the second function, wherein the identification comprises: a third identifier of the second function; an internet protocol address of said second function; the Internet Protocol version number of said second function; a fully qualified domain name of the second feature; and at least one of the port numbers of the second function; The information acquisition method according to any one of claims 1 to 5.

7. Obtaining the identification information of the second function includes: obtaining an identification of the second function from a local profile of the first function; or performing a domain name system query using the fully qualified domain name of the second function to obtain an identity of the second function; or performing a service discovery process using a third identifier of the first terminal to obtain an identity of the indicated second function; The information acquisition method according to claim 6.

8. Obtaining the identification information of the second function includes: sending a second request message to a third function, the second request message including a service name of the second function, a function type, an internet protocol address range of the second function, or an expected internet protocol address version; receiving identification information of the second function sent from the third function, wherein the identification information of the second function is determined by the third function based on a service name of the second function, the function type, an Internet Protocol address range of the second function, or an expected Internet Protocol address version; The information acquisition method according to claim 6.

9. An information acquisition method applied to a second function, receiving a first request message sent from a first terminal or a first function, the first request message being used to obtain a first identifier of the first terminal; obtaining the first identifier based on the first request message and the service of the second function; transmitting the first identifier to the first terminal or the first function.

10. The first request message includes a terminal address of the first terminal and / or a second identifier of the first function. The information acquisition method according to claim 9.

11. Obtaining the first identifier based on the first request message and the service of the second function includes: obtaining the first identifier based on at least one of a service of the second function, a terminal address of the first terminal, or a second identifier; The information acquisition method according to claim 10.

12. the first request message is a redirect request triggered by the first function; The information acquisition method according to any one of claims 9 to 11.

13. Sending a third request message to a third function, wherein the third request message is used to indicate that the second function supports a terminal identifier lookup service or a terminal identifier provision service. The information acquisition method according to any one of claims 9 to 12.

14. Sending the first identifier to the first function comprises: determining an address of the first function based on the second identifier; and transmitting the first identifier to the first function based on an address of the first function. The information acquisition method according to claim 10.

15. Transmitting the first identifier to the first terminal includes: sending a redirect message to the first terminal, the redirect message carrying the first identifier; The information acquisition method according to any one of claims 9 to 14.

16. An information acquisition method applied to a first terminal, sending a first request message to a second function, the first request message being used to obtain a first identifier of the first terminal; receiving a first identifier of the first terminal transmitted from the second function.

17. The first request message includes a terminal address of the first terminal and / or a second identifier of the first function. The information acquisition method according to claim 16.

18. the first identifier is obtained by the second function based on at least one of a service of the second function, a terminal address of the first terminal, or the second identifier; The information acquisition method according to claim 17.

19. Receiving the first identifier transmitted from the second function includes: receiving a redirect message sent from the second function, the redirect message carrying the first identifier; The information acquisition method according to any one of claims 16 to 18.

20. sending a service request to a first function; If the first function determines that it is necessary to obtain a first identifier of the first terminal when responding to the service request, sending a first request message to the second function. The information acquisition method according to any one of claims 16 to 19.

21. The service request includes an address for indicating whether the first terminal supports two Internet protocol types. The information acquisition method according to claim 20.

22. the first request message is a redirect request triggered by a first function; The information acquisition method according to any one of claims 16 to 21.

23. An information acquisition method applied to a third function, receiving a second request message sent from a first function, the second request message including a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; determining an identity of the second function based on a service name of the second function, the function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; transmitting identification information of the second function to the first function.

24. receiving a third request message sent from the first function, wherein the third request message is used to indicate that the second function supports a terminal identifier lookup service or a terminal identifier provision service; 24. The information acquisition method according to claim 23.

25. a first processing module configured to trigger a first terminal to send a first request message to a second function, the first request message being used to obtain a first identifier of the first terminal; a first receiving module configured to receive a first identifier of the first terminal transmitted from the second function.

26. a second receiving module configured to receive a first request message sent from a first terminal or a first function, the first request message being used to obtain a first identifier of the first terminal; a second processing module configured to obtain the first identifier based on the first request message and the service of the second function; a second transmitting module configured to transmit the first identifier to the first terminal or the first function.

27. a third sending module configured to send a first request message to a second function, the first request message being used to obtain a first identifier of the first terminal; a third receiving module configured to receive a first identifier of the first terminal transmitted from the second function.

28. a fourth receiving module configured to receive a second request message sent from a first function, the second request message including a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; and a fourth processing module configured to determine an identity of the second function based on a service name of the second function, a function type, an Internet Protocol address range of the second function, or an Internet Protocol address version expected by the second function; and a fourth transmission module configured to transmit identification information of the second function to the first function.

29. a first memory for storing executable instructions; a first processor for implementing the information acquisition method of any one of claims 1 to 8 when executing executable instructions stored in said first memory.

30. a second memory for storing executable instructions; a second processor for implementing the information acquisition method of any one of claims 9 to 15 when executing executable instructions stored in said second memory.

31. a third memory for storing executable instructions; a third processor for implementing the information acquisition method of any one of claims 16 to 22 when executing executable instructions stored in said third memory.

32. a fourth memory for storing executable instructions; a fourth processor for implementing the information acquisition method of any one of claims 23 to 24 when executing executable instructions stored in the fourth memory.

33. A computer-readable storage medium storing one or more programs that, when executed by one or more processors, realize the information acquisition method according to any one of claims 1 to 8, claims 9 to 15, claims 16 to 22, or claims 23 to 24.

Images