Communication method and communication apparatus
By obtaining and analyzing the address information in the AF request, the difficulty of NEF in judging the roaming type in the edge computing scenario is solved, ensuring that the AF request can correctly affect the session and improve the quality of business services.
Patent Information
- Application Number
- PCT/CN2024/091675
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-11
- Filing Date
- 2024-05-08
- Publication Date
- 2024-11-14
AI Technical Summary
In the edge computing scenario, the problem of private address overlap caused by network address conversion makes NEF unable to correctly judge the roaming type of AF request, resulting in the AF request being unable to affect the correct session.
By receiving the first address in the AF request, obtaining its corresponding second address and address field, and sending a request to the unified data repository UDR network element to determine the roaming type or forwarding path of the AF request, so that the AF request can affect the correct Session.
Ensure that AF requests can correctly affect the terminal device's sessions and improve the service quality in roaming scenarios.
Smart Images

Figure CN2024091675_14112024_PF_FP_ABST
Abstract
Description
Communication method and communication device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on May 11, 2023, with application number 202310532410.X and application name “A Communication Method and Communication Device”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communication technology, and in particular to a communication method and a communication device. Background Art
[0003] With the growth of mobile service traffic, the industry has proposed the concept of Edge Computing (EC). Edge computing scenarios can achieve local processing of distributed service traffic by moving the User Plane Function (UPF) and service processing functions down to the edge of the network, avoiding excessive concentration of traffic, thereby greatly reducing the specification requirements for core computer rooms and centralized gateways. At the same time, it shortens the distance of the backhaul network and reduces the end-to-end (E2E) delay and jitter of user messages. In the EC scenario, in order to ensure that user equipment (UE) can receive better service, the application function (AF) will perceive the service quality of the UE service and influence the UE session through the Session Management Function (SMF) by sending an AF request, so that the UE can obtain better service. The AF request can affect the session by requesting to establish or modify the UE user plane path, or by providing new application service deployment information.
[0004] In a certain country or region, a certain type of cellular mobile communication network of a certain operator is called a public land mobile network (PLMN). The PLMN to which the UE subscribes is called the Home PLMN (HPLMN), which represents the home operator of the subscriber. When the UE leaves the coverage of the HPLMN due to movement or other reasons, if there is a PLMN that meets the following conditions: (1) it can cover the current location of the UE, and (2) its operator has signed a roaming agreement with the operator of the UE's HPLMN, then the UE can access this PLMN, which is called a Visited PLMN (VPLMN). UE accessing a VPLMN is called roaming.
[0005] Network Address Translation (NAT) can translate private Internet Protocol (IP) addresses into public network addresses. If a terminal device's session uses a private IP address to access the network through a NATed public address, and the NEF receives an AF request for the UE's session, the AF request includes the NATed public address of the UE's session. In this case, the NEF cannot determine the roaming type corresponding to the terminal device's session, nor can it determine how to subsequently process the AF request.
[0006] Release 18 proposes a new roaming scenario, called the Home Routed with Session Breakout (HR-SBO) roaming scenario. The UE can access the edge hosting environment (EHE) through the VPLMN. In this scenario, the network exposure function (NEF) of the VPLMN can serve the HR-SBO roaming session as a visited domain NEF (Visited NEF, V-NEF). At the same time, the NEF can also serve the non-roaming session or local breakout (LBO) roaming session of the VPLMN as a (home) NEF network element. Therefore, when the NEF receives an AF request, it is necessary to distinguish the session type affected by the AF request for the UE IP to determine the action after receiving the AF request, so that the AF request can affect the correct session. In particular, when the UE IP targeted by the AF request is an address after NAT translation, due to the overlap of private addresses, it is more difficult for the NEF to judge the roaming type of the session, and the AF request sent by the AF network element may not affect the correct session.
[0007] Summary of the Invention
[0008] The present application provides a communication method and a communication device, which enable a NEF to determine the roaming type of a session corresponding to an AF request or a forwarding path of the AF request when the NEF obtains the AF request, and enable the AF request to affect the correct session.
[0009] In the first aspect, the present application provides a communication method, which can be applied to a first network open function NEF network element, the method including: receiving an AF request from an application function AF network element, the AF request being used to affect a session of a terminal device, the AF request from the AF network element including a first address; obtaining a second address corresponding to the first address and an address domain corresponding to the second address; and sending an AF request to a unified data repository UDR network element.
[0010] Based on the method described in the first aspect, the first NEF network element can determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request through the address field corresponding to the second address, so that the AF request can affect the correct session.
[0011] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0012] In one possible implementation method, the second address corresponding to the first address and the address domain corresponding to the second address are obtained. The specific implementation method is: sending first information to the user plane function UPF network element, the first information including the first address, the UPF network element is the UPF network element that performs NAT on the second address, and the first information requests the second address and the address domain corresponding to the second address; receiving second information from the UPF network element, the second information including the second address, and the address domain corresponding to the second address.
[0013] In a possible implementation manner, the address domain corresponding to the second address does not belong to the public land mobile network PLMN to which the first NEF network element belongs.
[0014] In a possible implementation, the method further includes: determining, according to the address domain corresponding to the second address, a PLMN that allocates the second address to the session.
[0015] In one possible implementation, the AF request sent to the UDR network element includes first target information, and the first target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, a single network slice selection support information S-NSSAI, an internal group identifier, and an external group identifier.
[0016] In a possible implementation manner, the AF request from the AF network element does not include the first target information.
[0017] In a possible implementation manner, the AF request sent to the UDR network element does not include the first address.
[0018] In a possible implementation, when the first target information includes one or more of a SUPI, a GPSI, and an internal group identifier, the method further includes: sending seventh information to a user data management (UDM) network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier, the seventh information including the second address and / or an address field corresponding to the second address, and the seventh information being used to request one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier; and receiving one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier from the UDM network element or the BSF network element.
[0019] In one possible implementation, before sending an AF request to a unified data repository UDR network element, the method further includes: sending storage request information to the UDR network element, the storage request information including first target information; receiving response information sent from the UDR network element in response to the storage request information, the response information indicating that the storage AF request is allowed.
[0020] In one possible implementation, the method also includes: sending third information to the network storage function NRF network element, the third information including the second address, and the third information is used to request to query the address of the binding support function BSF network element corresponding to the second address; receiving fourth information from the NRF network element, the fourth information indicating that the address of the BSF network element cannot be queried.
[0021] In one possible implementation, the method further includes: sending fifth information to the BSF network element, the fifth information including the second address, the fifth information requesting to query the address of the policy control function PCF network element corresponding to the second address; and receiving sixth information from the BSF network element, the sixth information indicating that the address of the PCF network element cannot be queried.
[0022] In the second aspect, the present application provides a communication method, which can be applied to a first network open function NEF network element, the method including: receiving an AF request from an application function AF network element, the AF request being used to affect a session of a terminal device, the AF request from the AF network element including a first identifier, the first identifier being used to distinguish a public land mobile network PLMN; sending the AF request to a unified data repository UDR network element.
[0023] Based on the method described in the second aspect, the first NEF network element can determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request through the first identifier, so that the AF request can affect the correct session.
[0024] In a possible implementation manner, the first identifier is one of the following: a PLMN identifier, a home public land mobile network (HPLMN) identifier, or a virtual local area network (VLAN) identifier.
[0025] In one possible implementation, the AF request sent to the UDR network element includes first target information, and the first target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a HPLMN identifier, a data network name DNN, single network slice selection support information S-NSSAI, an internal group identifier, an external group identifier, and a first identifier.
[0026] In a possible implementation manner, the AF request from the AF network element does not include the first target information.
[0027] In a possible implementation, the first target information includes one or more of a SUPI, a GPSI, an internal group identifier, and an external group identifier. The method further includes: sending seventh information to a user data management (UDM) network element or a BSF network element belonging to a PLMN corresponding to the HPLMN identifier, the seventh information including the second address and / or an address field corresponding to the second address, the seventh information being used to request one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier; and receiving one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier from the UDM or BSF network element.
[0028] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0029] In one possible implementation, before sending an AF request to a unified data repository UDR network element, the method further includes: sending storage request information to the UDR network element, the storage request information including first target information; receiving response information sent from the UDR network element in response to the storage request information, the response information indicating that the storage AF request is allowed.
[0030] In the third aspect, the present application provides a communication method, which can be applied to a second network open function NEF network element, and the method includes: receiving a first subscription information sent from a first session management function SMF network element, the first subscription information is used to request a subscription application function AF request, the AF request is used to affect the session of the terminal device, the first subscription information includes second target information, and the second target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identity GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, a single network slice selection support information S-NSSAI, an internal group identifier, and an external group identifier; sending a second subscription information to a unified data repository UDR network element, the second subscription information is used to request a subscription AF request, and the second subscription information includes the second target information; receiving the AF request from the UDR network element, the AF request from the UDR network element includes the second target information; sending an AF request to the first SMF network element.
[0031] In a possible implementation manner, the second target information further includes a first identifier, and the first identifier is used to distinguish PLMNs.
[0032] In a possible implementation manner, the first identifier is one of the following: a public land mobile network PLMN identifier, a HPLMN identifier, or a virtual local area network VLAN identifier.
[0033] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0034] In a fourth aspect, the present application provides a communication method, which can be applied to a first session management function SMF network element, the method comprising: sending first subscription information to a second network open function NEF network element, the first subscription information including second target information, the second target information including one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, a single network slice selection support information S-NSSA, an internal group identifier, and an external group identifier; receiving an application function AF request sent from the second NEF network element, the AF request being used to affect a session of a terminal device, and the AF request from the second NEF network element including the second target information.
[0035] In a possible implementation manner, the second target information further includes a first identifier, where the first identifier is used to distinguish a public land mobile network PLMN.
[0036] In a possible implementation manner, the first identifier is one of the following: a PLMN identifier, a HPLMN identifier, and a virtual local area network (VLAN) identifier.
[0037] In a possible implementation, when the second target information includes one or more of a SUPI, a GPSI, a HPLMN identifier, an internal group identifier, and an external group identifier; the method further includes: receiving eighth information sent from a second SMF network element or a policy control function PCF network element, where the eighth information includes one or more of a SUPI, a GPSI, a HPLMN identifier, an internal group identifier, and an external group identifier.
[0038] In one possible implementation, the second SMF network element and the first SMF network element do not belong to the same PLMN.
[0039] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0040] In the fifth aspect, the present application provides a communication method, which can be applied to a user plane function UPF network element, and the method includes: receiving a first message sent from a first network open function NEF network element, the first message including a first address, the first address being a public network address obtained by network address translation NAT of the second address, the second address being a private network address of the session of the terminal device, the first message requesting the second address and the address domain corresponding to the second address; sending a second message to the first NEF network element, the second information including the second address, and the address domain corresponding to the second address.
[0041] In a sixth aspect, the present application provides a communication method, which can be applied to a unified data repository UDR network element, the method including: receiving second subscription information sent from a second NEF network element, the second subscription information being used to request subscription to an AF request, the AF request being used to affect a session of a terminal device, the second subscription information including second target information, the second target information including one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, a single network slice selection support information S-NSSAI, an internal group identifier, and an external group identifier; receiving and storing an AF request from the first NEF network element, the AF request including the first target information, the first target information including the following one or more items: a first address, a second address, an address domain corresponding to the second address, SUPI, GPSI, HPLMN identifier, DNN, S-NSSA, an internal group identifier, and an external group identifier; sending an AF request to the second NEF network element, the AF request sent to the second NEF network element including the second target information.
[0042] In a possible implementation, the second target information further includes a first identifier, and the first target information further includes a first identifier, where the first identifier is used to distinguish PLMNs.
[0043] In a possible implementation manner, the first identifier is one of the following: a public land mobile network PLMN identifier, a HPLMN identifier, or a virtual local area network VLAN identifier.
[0044] In a possible implementation manner, the first target information and the second target information include the same information.
[0045] In a possible implementation, before storing the AF request from the first NEF network element, the method further includes: determining that the first target information is subscribed by the second NEF network element.
[0046] In one possible implementation, before receiving and storing the AF request from the first NEF, the method further includes: receiving storage request information from the first NEF network element, the storage request information including first target information, and the first target information is subscribed to by the second NEF network element; and sending response information to the first NEF network element for the storage request information, the response information indicating that the storage of the AF request is allowed.
[0047] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0048] In the seventh aspect, the present application provides a communication method, which can be applied to a first session management function SMF network element, the method including: receiving one or more internal group identifiers sent from a second SMF network element; sending a first subscription information to a second network open function NEF network element, the first subscription information being used to request a subscription to an AF request, the first subscription information including second target information, the second target information including one or more internal group identifiers; receiving an AF request from the second NEF network element, the AF request from the second NEF network element including the second target information.
[0049] Based on the method described in the seventh aspect, the first SMF network element can obtain the internal group identifier, so that the first SMF network element can subscribe to the AF request of the group identifier index, and subsequent AF requests for the group identifier index can be sent to the first SMF to affect the corresponding session.
[0050] In one possible implementation, before receiving one or more internal group identifiers sent from the second SMF network element, the method further includes: sending internal group identifier request information to the second SMF network element.
[0051] In one possible implementation, one or more internal group identifiers sent from the second SMF network element are received. The specific implementation method is: during the establishment of the home routing HR-SBO session of the edge computing session group, one or more internal group identifiers sent from the second SMF network element are received.
[0052] In an eighth aspect, the present application provides a communication method, which can be applied to a first network open function NEF network element, the method including: receiving an AF request sent from an application function AF network element, the AF request being used to affect a session of a terminal device, the AF request sent by the AF network element including one or more external group identifiers, the first public land mobile network PLMN to which the one or more external group identifiers belong is not the PLMN where the first NEF network element is located; sending a ninth message to a user data management UDM network element belonging to the first PLMN, the ninth message being used to request one or more internal group identifiers corresponding to one or more external group identifiers; receiving a tenth message sent from the UDM network element, the tenth message including one or more internal group identifiers; and sending an AF request to a unified data repository UDR network element.
[0053] In a possible implementation manner, the method further includes: determining the first PLMN to which the one or more external group identifiers belong according to the domain identifier in the one or more external group identifiers.
[0054] In one possible implementation method, the ninth information is sent to the UDM network element corresponding to the first PLMN, and the specific implementation method is: the ninth information is sent to the UDM network element belonging to the first PLMN through the fourth NEF network element belonging to the first PLMN; the tenth information sent from the UDM network element is received, and the specific implementation method is: the tenth information from the UDM network element is received through the fourth NEF network element.
[0055] In a possible implementation, the AF request sent to the UDR includes first target information, where the first target information includes one or more internal group identifiers.
[0056] In a ninth aspect, the present application provides a communications device, which may be a NEF network element, a device within a NEF network element, or a device capable of being used in conjunction with a NEF network element. The communications device may also be a system-on-a-chip. The communications device may execute the methods described in the first, second, third, or eighth aspects. The functions of the communications device may be implemented in hardware, or by hardware executing corresponding software implementations. The hardware or software may include one or more units or modules corresponding to the aforementioned functions. The units or modules may be software and / or hardware.
[0057] In a tenth aspect, the present application provides a communication device, which may be a NEF network element, a device within a NEF network element, or a device capable of being used in conjunction with a NEF network element. The communication device may also be a system-on-a-chip. The communication device may execute the methods described in the first, second, third, or eighth aspects. The functions of the communication device may be implemented in hardware, or by hardware executing corresponding software implementations. The hardware or software may include one or more units or modules corresponding to the aforementioned functions. The units or modules may be software and / or hardware.
[0058] In an eleventh aspect, the present application provides a communication device, which may be an SMF network element, a device within an SMF network element, or a device capable of being used in conjunction with an SMF network element. The communication device may also be a chip system. The communication device may execute the method described in the fourth aspect or the seventh aspect. The functions of the communication device may be implemented by hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above-mentioned functions. The units or modules may be software and / or hardware.
[0059] In a twelfth aspect, the present application provides a communication device, which may be a UPF network element, a device in a UPF network element, or a device that can be used in conjunction with a UPF network element. The communication device may also be a chip system. The communication device may execute the method described in the fifth aspect. The functions of the communication device may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The units or modules may be software and / or hardware.
[0060] In a thirteenth aspect, the present application provides a communication device, which may be a UPF network element, a device in a UPF network element, or a device that can be used in conjunction with a UPF network element. The communication device may also be a chip system. The communication device may execute the method described in the fifth aspect. The functions of the communication device may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions. The units or modules may be software and / or hardware.
[0061] In a fourteenth aspect, the present application provides a communication device, which may be a UDR network element, a device in a UDR network element, or a device that can be used in conjunction with a UDR network element. The communication device may also be a chip system. The communication device may execute the method described in the sixth aspect. The functions of the communication device may be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more units or modules corresponding to the above functions. The units or modules may be software and / or hardware.
[0062] In a fifteenth aspect, the present application provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method of any one of the first to eighth aspects is executed.
[0063] In the sixteenth aspect, the present application provides a communication device, which includes a processor and a memory, and the processor and the memory are coupled; the processor is used to implement the method as described in any one of the first to eighth aspects.
[0064] In the seventeenth aspect, the present application provides a communication device, which includes a processor, a memory and a transceiver, and the processor and the memory are coupled; the transceiver is used to send and receive data, and the processor is used to implement any one of the methods in the first to eighth aspects.
[0065] In the eighteenth aspect, the present application provides a communication device, which includes a processor and an interface, and the processor and the interface are coupled; the interface is used to receive or output signals, and the processor is used to execute code instructions so that any method as described in the first aspect to the eighth aspect is executed.
[0066] In the nineteenth aspect, the present application provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a communication device, the method described in any one of the first to eighth aspects is implemented.
[0067] In the twentieth aspect, the present application provides a computer program product comprising instructions, which, when a communication device reads and executes the instructions, enables the communication device to execute the method described in any one of the first to eighth aspects.
[0068] In aspect 21, the present application provides a communication system comprising a communication device for executing the methods described in aspect 1, aspect 3, aspect 4, aspect 5 and aspect 6 above, or comprising a communication device for executing the methods described in aspect 2, aspect 3, aspect 4, aspect 5 and aspect 6 above, or comprising a communication device for executing the methods described in aspect 7 and aspect 8 above. BRIEF DESCRIPTION OF THE DRAWINGS
[0069] FIG1 is a schematic diagram of a network system architecture provided in an embodiment of the present application;
[0070] FIG2 is a schematic diagram of a communication system architecture for an HR-SBO roaming scenario provided by an embodiment of the present application;
[0071] 3 to 8 are flowcharts of a communication method according to an embodiment of the present application;
[0072] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0073] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0074] FIG11 is a schematic structural diagram of a chip provided in an embodiment of the present application. DETAILED DESCRIPTION
[0075] The terms "first" and "second" and the like in the specification, claims, and drawings of this application are used to distinguish between different objects, not to describe a specific order. Furthermore, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.
[0076] References herein to "embodiments" mean that a particular feature, structure, or characteristic described in connection with the embodiments may be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor does it constitute an independent or alternative embodiment that is mutually exclusive of other embodiments. It is understood, both explicitly and implicitly, by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0077] In this application, "at least one (item)" refers to one or more, "more than one" refers to two or more, "at least two (items)" refers to two or three and more than three, and "and / or" is used to describe the corresponding relationship of associated objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0078] In order to better understand the present application, several system architectures provided in the embodiments of the present application are introduced below:
[0079] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), new radio (NR), the 3rd generation partner project (3GPP) service-based network architecture (SBA), and other fifth generation (5G) communication systems or sixth generation (6G) communication systems and other communication systems evolved after 5G.
[0080] Please refer to Figure 1, which is a schematic diagram of a network system architecture provided by an embodiment of the present application. As shown in Figure 1, a terminal device can access a wireless network to obtain services of an external network (such as a data network (DN)) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other terminal devices. The wireless network includes a (radio) access network ((R)AN) and a core network (CN), wherein the (R)AN (hereinafter described as RAN) is used to access the terminal device to the wireless network, and the CN is used to manage the terminal device and provide a gateway for communicating with the DN. The terminal device, RAN, CN and DN involved in the system architecture in Figure 1 are described in detail below.
[0081] 1. Terminal Equipment
[0082] Terminal devices include devices that provide voice and / or data connectivity to users. For example, a terminal device is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites, etc.). The terminal device can be a mobile phone, a set-top box (STB), a tablet computer (Pad), a computer with wireless transceiver capabilities, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a vehicle-mounted terminal, a wireless terminal in self-driving, a wireless terminal in remote medical care, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a wearable terminal, etc. The embodiments of the present application do not limit the application scenarios. Terminal equipment may sometimes also be referred to as terminal, user equipment (UE), access terminal, vehicle-mounted terminal, industrial control terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication equipment, UE agent or UE device, etc. The terminal may also be fixed or mobile. It will be understood that all or part of the functions of the terminal in this application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The terminal device in this application may be a terminal for 5G or a terminal for 6G, and this application does not limit this.
[0083] 2. RAN
[0084] The RAN may include one or more radio access network elements (or access network devices). The interface between the radio access network element and the terminal device may be a Uu interface (or air interface). Of course, in communications evolved after 5G, the names of these interfaces may remain unchanged or may be replaced by other names, and this application is not limited to this.
[0085] A radio access network element is a node or device that connects a terminal device to a wireless network. Examples of radio access network elements include, but are not limited to, next generation node B (gNB), evolved node B (eNB), next generation eNB (ng-eNB), wireless backhaul equipment, radio network controller (RNC), node B (NB), home evolved node B (HeNB) or home node B (HNB), baseband unit (BBU), transmitting and receiving point (TRP), transmitting point (TP), mobile switching center, and devices that perform base station functions in device-to-device (D2D), vehicle-to-everything (V2X), and machine-to-machine (M2M) communications in 5G communication systems. It may also include centralized units (C-RAN) in cloud radio access network (C-RAN) systems. The RAN in this application may be a 5G RAN or a 6G RAN, and this application does not limit this.
[0086] 3. CN
[0087] The CN may include one or more network elements (which may be understood as functional network elements (NF) or CN devices).
[0088] The CN architecture applicable to the embodiment of the present application can also be shown in Figure 2. The CN network elements mainly involved include: network exposure function (NEF) network element, application function (AF) network element, session management function (SMF) network element, user plane function (UPF) network element, policy control function (PCF) network element, unified data repository (UDR) network element, binding support function (BSF) network element, network storage function (NRF) network element, and unified data management (UDM) network element.
[0089] The NEF network element provides the capability exposure of the 5G core network, allowing external network elements to interact with the 5G core network through the network element.
[0090] AF network elements can interact with other core network control planes and provide business services. For example, AF supports the following functions: influencing sessions, accessing NEF network elements, and interacting with PCF network elements for policy management.
[0091] The SMF network element is responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting the UPF that provides packet forwarding capabilities.
[0092] The UPF network element is mainly responsible for processing user messages, such as forwarding, billing statistics, etc.
[0093] The PCF network element supports unified policy management of network behavior; provides policy rules to the control plane function for execution; and obtains contract-related information from the UDR to make policy decisions.
[0094] The UDR network element mainly provides storage capabilities for post-contract data, policy data, and capability exposure-related data.
[0095] The BSF network element is mainly responsible for storing PCF network element registration information for PCF network element discovery and selection.
[0096] The NRF network element is mainly responsible for storing network element information of the home public land mobile network (HPLMN) for network element discovery.
[0097] The UDM network element is mainly responsible for user contract management, access authorization, authentication information generation, etc.
[0098] It should be noted that the above-mentioned CN network elements may also be referred to as functional network elements or CN devices. In a 5G communication system, each functional network element may be the name of each functional network element described above. In a communication system evolved after 5G (such as a 6G communication system), each functional network element may still be the name of each functional network element described above, or may have other names. For example, in a 5G communication system, the user plane function may be a UPF. In a communication system evolved after 5G (such as a 6G communication system), the user plane function may still be a UPF, or may have other names, which is not limited in this application.
[0099] It should also be noted that in a 5G communication system, the functions implemented by each functional network element may be independent. In a communication system that evolves after 5G (such as a 6G communication system), each functional network element may still be in an independent state, or the functions of the multiple functional network elements described above may be implemented by an integrated functional network element. For example, in a 5G communication system, user-plane related functions are implemented by the UPF, and unified policy management related functions are implemented by the PCF. In a communication system that evolves after 5G (such as a 6G communication system), user-plane related functions may still be implemented by the UPF, and unified policy management related functions may still be implemented by the PCF, or an integrated functional network element may simultaneously implement user-plane related functions and unified policy management related functions, which is not limited in this application.
[0100] 4. DN
[0101] DN, also known as packet data network (PDN), is a network located outside the operator network. The operator network can access multiple DNs, and application servers corresponding to various services can be deployed in the DN to provide services for terminal devices.
[0102] Release 18 introduces a new roaming scenario, called the Home Routed with Session Breakout (HR-SBO) roaming scenario. Figure 2 illustrates the communication system architecture for this HR-SBO roaming scenario, and the methods proposed in this embodiment of the present application are applicable to this communication architecture. The UE can access the Edge Hosting Environment (EHE) through the Virtual Private Network (VPLMN).
[0103] Among them, the SMF belonging to the VPLMN is the visited domain SMF (visited SMF, V-SMF) that serves the user when the user is roaming, and the PCF belonging to the VPLMN is the visited domain PCF (visited PCF, V-PCF) that serves the user when the user is roaming. The SMF belonging to the HPLMN is the home domain SMF (home SMF, H-SMF) that serves the user when the user is roaming. The PCF belonging to the HPLMN is the home domain PCF (home PCF, H-PCF) that serves the user when the user is roaming. The UPF directly connected to the DN through N6 in the session is called the Protocol Data Unit Session Anchor (PSA), and the anchor point UPF for local diversion is called the local PDU Session Anchor (local PSA, L-PSA). The UPF serving as a diversion point is called a branching point (BP) or an uplink classifier (ULCL). Unlike non-roaming edge computing scenarios, in order to maintain the HPLMN's control over local offload services, the H-SMF indicates to the V-SMF the services that are authorized to be accessed in the VPLMN when the session is established.
[0104] AF requests are designed to timely impact UE sessions in edge computing (EC) scenarios, enabling better service for UEs. AF requests can impact sessions by requesting to establish or modify the UE's user plane path, or by providing new application service deployment information.
[0105] The network exposure function (NEF) element of the VPLMN in the HR-SBO scenario can serve as a visited NEF (V-NEF) element to serve HR-SBO roaming sessions. At the same time, the NEF element can also serve as a (home) NEF element to serve non-roaming sessions of the VPLMN or local breakout (LBO) roaming sessions. Therefore, when the NEF element receives an AF request, it needs to distinguish the session type affected by the AF request for the UE IP address to determine the action after receiving the AF request, so that the AF request can affect the correct session.
[0106] Network Address Translation (NAT) can convert private Internet Protocol Address (IP) addresses into public network addresses. If a terminal device's session uses a private IP address to access the network through a NAT's public address, when the NEF network element obtains an AF request for the UE's session, the AF request includes the public network address of the UE's session after NAT conversion. In this case, the NEF network element cannot determine the roaming type corresponding to the terminal device's session, nor can it determine how to handle the AF request subsequently. In particular, when the UE IP targeted by the AF request is an address after NAT conversion, due to the overlap of private addresses, it is more difficult for the NEF network element to determine the roaming type of the session, and the AF request sent by the AF network element may not affect the correct session.
[0107] In order to enable the AF request to affect the correct session, the embodiment of the present application proposes a communication method and a communication device. The communication method and the communication device provided by the embodiment of the present application are further described in detail below.
[0108] Figure 3 is a flow chart of a communication method provided in an embodiment of the present application. As shown in Figure 3, the communication method includes the following steps 301 to 307. The execution subject of the method shown in Figure 3 can be a first SMF network element, a second NEF network element, a UDR network element, a first NEF network element and an AF network element. Alternatively, the execution subject of the method shown in Figure 3 can be a device or chip having the functions of a first SMF network element, a second NEF network element, a UDR network element, a first NEF network element and an AF network element, which is not limited in the embodiment of the present application. Figure 3 takes the first SMF network element, the second NEF network element, the UDR network element, the first NEF network element and the AF network element as the execution subject of the method as an example for explanation. The first SMF network element involved in the embodiment described in FIG3 may be the V-SMF network element shown in FIG2 , the UDR network element and the AF network element involved in the embodiment described in FIG3 may be the UDR network element and the AF network element shown in FIG2 , the first NEF network element and the second NEF network element involved in the embodiment described in FIG3 may be the NEF network element shown in FIG2 , the first NEF network element and the second NEF network element may be the same NEF network element or may be two different NEF network elements. FIG3 is introduced with the first NEF network element and the second NEF network element being two different NEF network elements.
[0109] 301. An AF network element sends an AF request to a first NEF network element. Correspondingly, the first NEF network element receives the AF request from the AF network element. The AF request sent by the AF network element includes a first address.
[0110] In an embodiment of the present application, an AF request is used to affect a session of a terminal device. The way in which the AF request affects the session may be to instruct the session to change traffic, or to provide application service deployment information, etc. The embodiment of the present application does not limit the specific way in which the AF request affects the session. The first NEF network element described in the embodiment of the present application is applicable to any NEF network element that can receive AF requests for roaming and non-roaming. That is, for example, when an AF request affects a PDU session, the first NEF can act as a home domain NEF (H-NEF) for some sessions affected by the AF request, such as non-roaming sessions, and as a visited domain (V-NEF) for other sessions, such as HR-SBO sessions. For AF requests for different sessions, the first NEF network element needs to forward the AF request in different ways to affect the correct session.
[0111] One implementation of including the first address in the AF request sent by the AF network element is that the target UE identifier (target UE identifier) in the AF request includes the first address. The first address is a public network address obtained by NATing the private network address of the terminal device's session. Optionally, the first address may specifically be the public Internet Protocol (IP) address of the terminal device, or may specifically be the public IP address and port number of the terminal device.
[0112] The first address included in the AF request is a public network address obtained through NAT for the private network address of the terminal device's session, and may be discovered by the first NEF network element through judgment. One implementation of the first NEF network element's judgment is that the first NEF network element is configured with a public network IP (IP segment) in the PLMN to which it belongs that can be used for NAT. If the first address included in the received AF request belongs to this IP segment, the first NEF network element determines that the first address is a public network address obtained through NAT for the private network address of the terminal device's session.
[0113] 302. The first NEF network element obtains a second address corresponding to the first address and an address domain corresponding to the second address.
[0114] In this embodiment of the present application, the second address corresponding to the first address means that the first address is the address obtained after the second address is NATed. The first NEF network element can obtain the corresponding second address through the first address based on the corresponding relationship between the first address and the second address. In one possible implementation, the second address is the private IP address of the terminal device session. The second address being the private IP address of the terminal device session specifically means that the IP address assigned to the terminal device by the 5G core network is a private IP address. The first NEF network element obtains the second address corresponding to the first address by providing the first address. For example, the first NEF network element uses the Nupf_GetPrivateUEIPaddr service to provide the first address to the UPF network element. After receiving the first address, the UPF network element responds to the first NEF network element with the NATed UE IP address uniquely identified by the first address provided by the first NEF, i.e., the second address. In addition, the first address and the second address may have other corresponding relationships. For example, the second address may be an address used within the 5G core network and the first address may be an address used outside the 5G core network, and both are used to mark the same session. This embodiment of the present application is not limited to this.
[0115] The address domain corresponding to the second address refers to the address domain to which the second address belongs. For example, the address domain includes many addresses, and the second address is one of them. The address domain corresponding to the second address can be used to indicate the roaming type of the session corresponding to the AF request, or to indicate the forwarding path of the AF request, or as a basis for the first NEF network element to determine the roaming type of the session corresponding to the AF request. Optionally, the second address is the private IP address of the terminal device session, and the address domain corresponding to the second address is the IP domain.
[0116] A specific implementation manner in which the first NEF network element obtains the second address corresponding to the first address and the address domain corresponding to the second address may be:
[0117] S31. A first NEF network element sends a first message to a UPF network element. In response, the UPF network element receives the first message from the first NEF network element. The first message includes a first address. Optionally, the first message requests a second address and an address domain corresponding to the second address. The UPF network element performs NAT on the second address.
[0118] s32. The UPF network element sends the second information to the first NEF network element. Correspondingly, the first NEF network element receives the second information from the UPF network element. The second information includes the second address and the address field corresponding to the second address.
[0119] The manner in which the first NEF network element determines the UPF network element that performs NAT on the second address may be specifically as follows: the first NEF network element sends a query message to the NRF network element, the query message being used to request the address of the UPF network element that performs NAT on the second address, the query message carrying the first address; after receiving the query message, the NRF network element sends the corresponding UPF network element address to the first NEF network element. The NRF network element may locally configure the correspondence between the address and the UPF network element, or the UPF network element may send the address of the UPF network element, the second address, and the first address to the NRF network element when performing NAT on the second address.
[0120] The specific implementation method for the first NEF network element to determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request session based on the address domain corresponding to the second address can be: the first NEF network element configures the correspondence between each address domain and each PLMN, and the first NEF network element determines the PLMN to which the second address is assigned for the session based on the address domain corresponding to the second address. If the address domain corresponding to the second address does not belong to the PLMN to which the first NEF network element belongs, the first NEF network element can determine that the roaming type corresponding to the session is the first roaming type. A PLMN includes one or more address domains for assigning addresses to terminal devices. If the address domain corresponding to the second address does not belong to the PLMN to which the first NEF network element belongs, it can be understood that the address domain corresponding to the second address is not one or more address domains included in the PLMN where the first NEF network element is located, nor is it a subset of one or more address domains included in the PLMN where the first NEF network element is located.
[0121] In the communication system scenario corresponding to the first roaming type, the home PLMN of the terminal device's session is different from the PLMN where the edge environment accessed by the terminal device's session is located. Optionally, the first roaming type is HR-SBO roaming. Optionally, when the PLMN to which the second address is assigned to the session is different from the PLMN where the edge environment accessed by the terminal device's session is located, the session is determined to be an HR-SBO session.
[0122] Specifically, for HR-SBO roaming, as shown in Figure 2, the UPF network element located in the HPLMN allocates a second address corresponding to the session of the terminal device. The address domain corresponding to the second address belongs to the address domain of the HPLMN. The first NEF network element is located in the VPLMN. Therefore, the address domain corresponding to the second address does not belong to the PLMN described by the first NEF network element. Therefore, the PLMN where the address domain corresponding to the second address is located is different from the PLMN where the first NEF network element is located.
[0123] For non-roaming scenarios, the terminal device does not need to access the network through the VPLMN. Therefore, the UPF network element that allocates the second address for the terminal device's session is located in the HPLMN, and the first NEF network element that receives the session for the terminal device is also located in the HPLMN. Therefore, the PLMN where the address domain corresponding to the second address is located is the same as the PLMN where the first NEF network element is located.
[0124] For the local breakout (LBO) roaming scenario, the UPF network element is located in the VPLMN, and the HPLMN does not include the UPF network element. Therefore, the UPF network element that allocates the second address for the session of the terminal device is located in the VPLMN, and the first NEF network element that receives the session for the terminal device is also located in the VPLMN. Therefore, the PLMN where the address domain corresponding to the second address is located is the same as the PLMN where the first NEF network element is located.
[0125] Based on this implementation, since the first NEF network element can determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request through the address field corresponding to the second address, the AF request can affect the correct session.
[0126] In the above implementation, the method for determining the roaming type of the session corresponding to the AF request based on the address domain corresponding to the second address, and then determining the subsequent processing method of the AF request based on the roaming type corresponding to the session is described. It should also be noted that the first NEF network element may also process the AF request in other ways based on the address domain of the second address, and this embodiment of the present application is not limited to this. For example, the first NEF network element may not need to determine the roaming type corresponding to the session. That is, if the address domain corresponding to the second address does not belong to the PLMN to which the first NEF network element belongs or the address domain corresponding to the second address belongs to another PLMN, the first NEF network element performs the same actions as described above after determining that the roaming type of the session is the first roaming type, that is, continues to execute step 303.
[0127] The first NEF network element may also determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request by other means, which are specifically implemented as follows:
[0128] In one possible implementation, the first NEF network element sends third information to the NRF network element, where the third information includes the second address, and the third information is used to request to query the BSF network element address corresponding to the second address; the first NEF network element receives fourth information from the NRF network element, where the fourth information indicates that the BSF address cannot be queried.
[0129] Among them, for HR-SBO roaming, since the second address is allocated by the network element located in the HPLMN, and the first NEF that receives the AF request for the terminal device session is located in the VPLMN, the first NEF network element sends a third information request to the NRF network element under the VPLMN to query the BSF address corresponding to the second address, and cannot query the BSF network element address under the HPLMN.
[0130] In another possible implementation, the first NEF network element sends fifth information to the BSF network element, where the fifth information includes the second address and requests to query the PCF address corresponding to the second address; the first NEF network element receives sixth information from the BSF network element, where the sixth information indicates that the PCF address cannot be queried.
[0131] For HR-SBO roaming, since the second address is allocated by a network element in the HPLMN, and the first NEF receiving the AF request for the terminal device session is located in the VPLMN, the first NEF network element sends a fifth information request to the PCF network element in the VPLMN to query the PCF network element address corresponding to the second address, but cannot query the PCF network element address in the HPLMN. In this case, the address of the BSF network element can be locally configured by the NEF network element.
[0132] Based on the two implementations described above, the first NEF network element can determine the roaming type of the session corresponding to the AF request, or the forwarding path of the AF request, so that the AF request can affect the correct session.
[0133] In a possible implementation, the first information sent by the first NEF network element described in the above steps s31 and s32 may also specifically indicate the IP domain corresponding to the second address and / or the address of the SMF network element corresponding to the second address, and the second information replied by the UPF network element may also specifically include the IP domain corresponding to the second address and / or the address of the SMF network element corresponding to the second address.
[0134] Among them, if the UPF saves the address of the SMF network element corresponding to the address of the session, the UPF can query the address of the SMF network element corresponding to the second address. When the second information includes the address of the SMF network element corresponding to the second address, the first NEF network element can directly forward the received AF request to the SMF network element corresponding to the second address. Based on this implementation method, it is beneficial for the SMF to receive the AF request more quickly.
[0135] 303. The first NEF network element sends an AF request to the UDR network element. Correspondingly, the UDR network element receives and stores the AF request.
[0136] In an embodiment of the present application, the AF request sent by the first NEF network element to the UDR network element may further include first target information, where the first target information includes one or more of the following: a first address, a second address, an address field corresponding to the second address, a subscription permanent identifier (SUPI), a generic public subscription identifier (GPSI), an HPLMN identifier, a data network name (DNN), single network slice selection assistance information (S-NSSAI), an internal group ID, and an external group ID. The HPLMN identifier may be determined based on the address field corresponding to the second address. The first target information may be understood as a data key. When the UDR network element determines that a certain network element has subscribed to the AF request corresponding to the first target information, the UDR network element will forward the AF request. The first target information may be used to indicate the target session affected by the AF request, and also has the function of identifying information stored in the UDR. For example, when subscribing to the UDR network element, the first target information may be used to retrieve content (such as an AF request) stored using the same first target information.
[0137] In one possible implementation, when the first target information includes one or more of a SUPI, a GPSI, an internal group identifier, and an external group identifier, the first NEF network element sends seventh information to a UDM network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier. The seventh information includes a second address, and the seventh information is used to request one or more of the SUPI, GPSI, internal group identifier, and external group identifier. Optionally, the seventh information may also include an address field corresponding to the second address. After receiving the seventh information, the UDM network element or the BSF network element sends the one or more of the SUPI, GPSI, internal group identifier, and external group identifier to the first NEF network element. Based on this implementation, each network element can subscribe to an AF request using multiple parameters so that the AF request can affect the correct session.
[0138] Specifically, the first NEF network element sends the seventh information to the UDM network element or BSF network element of the PLMN corresponding to the HPLMN identifier through a third NEF network element, where the third NEF network element is an H-NEF network element. Correspondingly, the UDM network element or BSF network element also replies to the first NEF network element through the third NEF with one or more of the SUPI, GPSI, internal group identifier, and external group identifier. This embodiment of the present application does not limit the manner in which the first NEF network element and the UDM network element or BSF network element of the PLMN corresponding to the HPLMN identifier exchange information (e.g., through a third NEF network element).
[0139] Specifically, the first NEF network element obtains one or more of the SUPI, GPSI, internal group identifier, and external group identifier through the UDM network element as follows: the first NEF network element first determines the HPLMN corresponding to the session based on the address field of the second address, and based on the HPLMN, queries / locally configures the address of a third NEF network element corresponding to the HPLMN from a visited NRF (V-NRF). The V-NRF network element queries the address of the third NEF network element through a home NRF (H-NRF). After obtaining the address of the third NEF network element, the first NEF network element queries the third NEF network element for one or more of the SUPI, GPSI, internal group identifier, and external group identifier by calling the Nnef_UEId_Get interface. After receiving the address, the third NEF queries or locally configures the address of the UDM network element through the H-BSF network element or the H-NRF network element. After obtaining the address of the UDM network element, the first NEF network element sends the second address to the UDM network element. After receiving the second address, the UDM network element replies to the third NEF network element with one or more of the SUPI, GPSI, internal group identifier, and external group identifier. After receiving the second address, the H-NEF network element forwards the one or more of the SUPI, GPSI, internal group identifier, and external group identifier to the first NEF network element.
[0140] In an embodiment of the present application, the AF request sent by the first NEF network element to the UDR network element and the AF request sent by the AF network element to the first NEF network element, the information indicating how to affect the session is the same, but another part of the information may be different. For example, the information used to indicate the target session may be different. In one possible implementation, the target UE Identifier included in the AF request sent by the AF network element to the first NEF network element includes the first address, and the Data Key included in the AF request sent by the first NEF network element to the UDR network element includes the SUPI (this SUPI is the SUPI corresponding to the first address). The target UE Identifier and the Data Key both have the function of indicating the target session.
[0141] Specifically, this implementation involves the AF request sent by the AF network element to the first NEF network element not including the first target information. The AF request sent by the AF network element to the first NEF network element not including the first target information can also be understood as adding the first target information to the AF request sent by the first NEF network element to the UDR network element, while the AF request sent by the AF network element does not include the first target information. Optionally, the AF request sent by the first NEF network element to the UDR network element does not include the first address. Exemplarily, when the first target information includes SUPI, the first target information may also optionally include DNN or S-NSSAI, etc. The AF request sent by the AF network element to the first NEF network element does not include the first target information, i.e., does not include SUPI. In this implementation, since the first address included in the AF request sent by the AF network element to the first NEF network element is the public network address obtained after the second address is NATed, multiple terminal devices may share the same public network address, and the AF request may only be for the session of one terminal device, and the sessions of other terminal devices do not need to be affected. The first NEF network element obtains the SUPI from the corresponding UDM network element or BSF network element through the third NEF network element. By adding the SUPI in the AF request sent to the UDR network element, optionally, the first address included in the AF request can be deleted, so as to accurately indicate the session of the terminal device targeted by the AF request, which is conducive to making the AF request affect the correct session.
[0142] Before a UDR NE stores an AF request, the following two implementation methods can be used to improve the security of the UDR storage space:
[0143] Method 1: Before the UDR network element receives the AF request from the first NEF network element, the method further includes: the first NEF network element sends a storage request message to the UDR network element, the storage request message including first target information; the UDR network element determines, based on the first target information, whether any network element has subscribed to the AF request corresponding to the first target information; if a network element has subscribed to the AF request corresponding to the first target information, the UDR network element sends a response message to the first NEF network element in response to the storage request message, the response message indicating that the storage of the AF request is allowed. If no network element has subscribed to the first target information, the UDR network element refuses to receive the AF request corresponding to the first target information.
[0144] Method 2: The UDR network element receives the AF request from the first NEF network element. The UDR network element determines, based on the first target information, whether there is a network element that has subscribed to the AF request corresponding to the first target information. If there is a network element that has subscribed to the AF request corresponding to the first target information, the UDR network element stores the AF request. If there is no network element that has subscribed to the AF request corresponding to the first target information, the UDR network element will discard the AF request.
[0145] Based on the method described above, the UDR network element only stores the AF request that has subscribed to the first target information, which can avoid the occupation of the UDR storage space due to illegal attacks and improve the security of the UDR storage space.
[0146] 304. The first SMF network element sends the first subscription information to the second NEF network element. Correspondingly, the second NEF network element receives the first subscription information from the first SMF network element. The first subscription information is used to request to subscribe to the AF request.
[0147] In an embodiment of the present application, the first subscription information instructs the first SMF network element to subscribe to the AF request from the second NEF network element. The first subscription message includes second target information, and the second target information includes one or more of the following: the first address, the second address, the IP domain corresponding to the second address, SUPI, GPSI, HPLMN identifier, DNN, S-NSSA, internal group identifier, and external group identifier. When the second NEF network element receives the AF request corresponding to the second target information, the second NEF network element will forward the AF request to the first SMF network element. Optionally, the first SMF network element may send the first subscription information to the second NEF network element when the HR-SBO session is established.
[0148] In a possible implementation, if the second target information includes one or more of a SUPI, a GPSI, an HPLMN identifier, an internal group identifier, and an external group identifier, the method further includes, the first SMF network element receiving, from a second SMF network element or a PCF network element, eighth information sent, where the eighth information includes one or more of a SUPI, a GPSI, an HPLMN identifier, an internal group identifier, and an external group identifier. The second SMF network element and the first SMF network element are not in the same PLMN.
[0149] It should also be noted that before the first SMF network element receives the eighth information sent from the second SMF network element or the PCF network element, the first SMF network element may send query information for one or more of the SUPI, GPSI, HPLMN identifier, internal group identifier, and external group identifier to the second SMF network element or the PCF network element when the HR-SBO session is established. After the second SMF network element or the PCF network element obtains the query information for one or more of the SUPI, GPSI, HPLMN identifier, internal group identifier, and external group identifier from the UDM network element, it will return the one or more of the SUPI, GPSI, HPLMN identifier, internal group identifier, and external group identifier to the first SMF.
[0150] Based on this implementation, each network element can subscribe to an AF request using multiple parameters, thereby improving the accuracy of the AF request affecting the session.
[0151] 305. The second NEF network element sends second subscription information to the UDR network element. Correspondingly, the UDR network element receives the second subscription information from the second NEF network element. The second subscription information is used to request subscription to the AF request.
[0152] In an embodiment of the present application, the second subscription information indicates that the second NEF network element subscribes to the AF request from the UDR network element. In the second subscription information, the second subscription message includes second target information. When the storage space of the UDR network element stores the AF request corresponding to the second target information, the UDR network element will forward the AF request to the second NEF network element.
[0153] It should be noted that steps 304 and 305 can be performed before step 306. Figure 3 shows that steps 304 and 305 can be performed before step 303. It should also be noted that steps 304 and 305 can also be performed after step 303. This embodiment of the present application does not limit this.
[0154] 306. The UDR network element sends an AF request to the second NEF network element. Correspondingly, the second NEF network element receives the AF request from the UDR network element.
[0155] In the embodiment of the present application, when the first target information and the second target information are the same, the UDR network element will send the AF request to the second NEF network element, and the AF request sent by the UDR network element to the second NEF network element includes the second target information.
[0156] Among them, the first target information and the second target information are the same, which can be understood as that all parameter information contained in the first target information and the second target information are the same, and the content corresponding to each parameter information in the first target information and the second target information is the same one by one.
[0157] For example, assuming that the first target information includes a SUPI, a DNN, and an S-NSSAI, and the second target information also includes a SUPI, a DNN, and an S-NSSAI, it can be concluded that all parameter information included in the first target information and the second target information is the same. The fact that the content corresponding to each parameter information in the first target information and the second target information is identical means that the SUPI in the first target information and the SUPI in the second target information are the same, the DNN in the first target information and the DNN in the second target information are the same, and the DNN in the first target information and the DNN in the second target information are the same.
[0158] For another example, the first target information includes SUPI, the second target information also includes SUPI, all parameter information contained in the first target information and the second target information are the same, and the content corresponding to each parameter information in the first target information and the second target information is the same one by one, which means that the S-NSSAI in the first target information and the S-NSSAI in the second target information are the same.
[0159] Alternatively, the first target information and the second target information are the same, which can be understood as the first target information and the second target information containing some of the same parameter information, and the content corresponding to each parameter information in the same parameter information in the first target information and the second target information is the same one by one.
[0160] For example, assuming that the first target information includes a SUPI, a DNN, and an S-NSSAI, and the second target information includes a SUPI and a DNN, the partially identical parameter information included in the first target information and the second target information means that both the first target information and the second target information include a SUPI and a DNN. In the identical parameter information in the first target information and the second target information, the content corresponding to each parameter information is identical, meaning that the SUPI in the first target information is the same as the SUPI in the second target information, and the DNN in the first target information is the same as the DNN in the second target information.
[0161] 307. The second NEF network element sends an AF request to the first SMF network element. Correspondingly, the first SMF network element receives the AF request from the second NEF network element.
[0162] In an embodiment of the present application, after the first SMF network element receives the AF request, it will affect the session of the terminal device based on the instruction of the AF request, such as establishing or modifying the session, or taking corresponding actions on the session of the terminal device. Based on the method described in the embodiment of the present application, the first NEF network element can determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request through the address field corresponding to the second address, so that the AF request is forwarded to the corresponding first SMF network element, so that the AF request can affect the correct session.
[0163] Figure 3 illustrates the first NEF network element and the second NEF network element as two different NEF network elements. The first NEF network element and the second NEF network element may also be the same NEF network element. This is because, when the AF network element sends an AF request, it selects a NEF network element as the sender. When the first SMF network element subscribes to an AF request, it also selects a NEF network element as the sender. The NEF network element selected by the AF network element and the NEF network element selected by the first SMF network element may be the same NEF network element or different NEF network elements.
[0164] FIG4 shows a specific implementation flow of the communication method when the first NEF network element and the second NEF network element are the same network element. The first NEF network element and the second NEF network element are both referred to as the first NEF network element, and includes steps 401 to 407 .
[0165] 401. The AF network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the AF network element. The AF request sent by the AF network element includes a first address.
[0166] 402. The first NEF network element obtains a second address corresponding to the first address and an address domain corresponding to the second address.
[0167] 403. The first NEF network element sends an AF request to the UDR network element. Correspondingly, the UDR network element receives and stores the AF request.
[0168] 404. The first SMF network element sends the first subscription information to the first NEF network element. Correspondingly, the first NEF network element receives the first subscription information from the first SMF network element. The first subscription information is used to request to subscribe to the AF request.
[0169] 405. The first NEF network element sends second subscription information to the UDR network element. Correspondingly, the UDR network element receives the second subscription information from the first NEF network element. The second subscription information is used to request subscription to the AF request.
[0170] Among them, in the embodiment of the present application, step 404 and step 405 can be executed before step 406. Figure 4 shows that step 404 and step 405 are executed before step 401. It should also be noted that they can also be executed after step 401, step 402 or step 403. This application does not limit this.
[0171] 406. The UDR network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the UDR network element.
[0172] 407. The first NEF network element sends an AF request to the first SMF network element. Correspondingly, the first SMF network element receives the AF request from the first NEF network element.
[0173] Among them, the specific implementation method of steps 401 to 407 is the same as that of steps 301 to 307, and will not be repeated here in the embodiment of this application.
[0174] In order to enable the AF request to affect the correct session, the embodiment of the present application further proposes a communication method and a communication device. The communication method and the communication device provided by the embodiment of the present application are further described in detail below.
[0175] Figure 5 is a flow chart of a communication method provided in an embodiment of the present application. As shown in Figure 5, the communication method includes the following steps 501 to 506. The execution subject of the method shown in Figure 5 can be a first SMF network element, a second NEF network element, a UDR network element, a first NEF network element and an AF network element. Alternatively, the execution subject of the method shown in Figure 5 can be a device or chip having the functions of a first SMF network element, a second NEF network element, a UDR network element, a first NEF network element and an AF network element, which is not limited in the embodiment of the present application. Figure 5 takes the first SMF network element, the second NEF network element, the UDR network element, the first NEF network element and the AF network element as the execution subject of the method as an example for explanation. The first SMF network element involved in the embodiment described in FIG5 may be the V-SMF network element shown in FIG2 , the UDR network element and the AF network element involved in the embodiment described in FIG5 may be the UDR network element and the AF network element shown in FIG2 , the first NEF network element and the second NEF network element involved in the embodiment described in FIG5 may be the NEF network element shown in FIG2 , the first NEF network element and the second NEF network element may be the same NEF network element or may be two different NEF network elements. FIG5 is introduced with the first NEF network element and the second NEF network element being two different NEF network elements.
[0176] 501. The AF network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the AF network element. The AF request sent by the AF network element includes a first identifier, and the first identifier is used to distinguish PLMNs.
[0177] In an embodiment of the present application, an AF request is used to affect a session of a terminal device. The way in which the AF request affects the session may be to instruct the session to change traffic, or to provide application service deployment information, etc. The embodiment of the present application does not limit the specific way in which the AF request affects the session. The first NEF network element described in the embodiment of the present application is applicable to any NEF network element that can receive AF requests for roaming and non-roaming. That is, for example, when an AF request affects a PDU session, the first NEF can act as a home domain NEF (H-NEF) for some sessions affected by the AF request, such as non-roaming sessions, and as a visited domain (V-NEF) for other sessions, such as HR-SBO sessions. For AF requests for different sessions, the first NEF network element needs to forward the AF request in different ways to affect the correct session.
[0178] The first identifier may be a PLMN identifier, an HPLMN identifier, a virtual local area network (VLAN) identifier, or the like. The first identifier may also be a newly defined identifier used to distinguish PLMNs. The first identifier may be included in the same message as the AF request or in a different message. The identifier may also be a feature of the AF request message. For example, the VLAN identifier may be a feature corresponding to the AF request message, rather than a separate information element. The first NEF network element may determine by the first identifier whether the session corresponding to the AF request and the first NEF network element belong to the same PLMN. If they do not belong to the same PLMN, the roaming type corresponding to the session may be determined to be the first roaming type. In the communication system scenario corresponding to the first roaming type, the UPF network element that allocates the second address for the session of the terminal device and the NEF network element that receives the AF request for the session of the terminal device do not belong to the same PLMN. Optionally, the first roaming type is HR-SBO roaming.
[0179] Based on this method, since the first NEF network element can determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request through the first identifier, the AF request can affect the correct session.
[0180] 502. The first NEF network element sends an AF request to the UDR network element. Correspondingly, the UDR network element receives and stores the AF request.
[0181] In an embodiment of the present application, the AF request sent by the first NEF network element to the UDR network element may also include first target information, and the first target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, SUPI, GPSI, HPLMN identifier, DNN, S-NSSAI, an internal group identifier, an external group identifier, and a first identifier. The first target information can be understood as a data key. When the UDR network element determines that a certain network element has subscribed to the AF request corresponding to the first target information, the UDR network element will forward the AF request. The first target information can be used to indicate the target session affected by the AF request, and also has the function of identifying the information stored in the UDR network element. For example, when subscribing to the UDR, the first target information can be used to retrieve the content stored using the same first target information (such as the AF request).
[0182] When the first target information includes the first address, since the AF request sent by the AF network element includes the first address, the first NEF network element can determine the first address based on the AF request sent by the AF network element. The first address is a public address obtained by NATing the private network address of the terminal device's session. Optionally, the first address can be the public IP address of the terminal device, or the public IP address and port number of the terminal device.
[0183] The first address included in the AF request is a public network address obtained through NAT for the private network address of the terminal device's session, and may be discovered by the first NEF network element through judgment. One implementation of the first NEF network element's judgment is that the first NEF network element is configured with a public network IP (IP segment) in the PLMN to which it belongs that can be used for NAT. If the first address included in the received AF request belongs to this IP segment, the first NEF network element determines that the first address is a public network address obtained through NAT for the private network address of the terminal device's session.
[0184] When the first target information includes the second address corresponding to the first address and / or the address domain corresponding to the second address, the first address corresponding to the second address means that the first address is the address obtained after the second address is NATed. The first NEF network element can obtain the corresponding second address through the first address based on the corresponding relationship between the first address and the second address. In a possible implementation, the second address is the private network address (private IP) of the terminal device session. The second address being the private network address of the terminal device session specifically means that the IP address assigned to the terminal device by the 5G core network is a private network address. The first NEF network element obtains the second address corresponding to the first address, which means that the first NEF network element obtains the second address by providing the first address. For example, the first NEF network element uses the Nupf_GetPrivateUEIPaddr service to provide the first address to the UPF network element. After receiving the first address, the UPF network element replies to the first NEF network element with the NATed UE IP address uniquely identified by the first address provided by the first NEF, that is, the second address. In addition, other correspondences may exist between the first address and the second address. For example, the second address is an address used within the 5G core network, and the first address is an address used outside the 5G core network, and both are used to mark the same session. This is not limited in this embodiment of the present application. The address domain corresponding to the second address refers to the address domain to which the second address belongs. For example, the address domain includes multiple addresses, and the second address is one of them. Optionally, the second address is the private IP address of the terminal device session, and the address domain corresponding to the second address is the IP domain. The specific implementation method for the first NEF network element to obtain the second address and the address domain corresponding to the second address can be as follows: the first NEF network element sends a first message to the UPF network element, and the UPF network element receives the first message from the first NEF network element. Optionally, the first message requests the second address and the address domain corresponding to the second address. The first message includes the first address, and the UPF network element is the network element that performs NAT on the second address. The UPF network element sends a second message to the first NEF network element, and the first NEF network element receives a second message from the UPF network element. The second message includes the second address and the address domain corresponding to the second address.
[0185] The manner in which the first NEF network element determines the UPF network element that performs NAT on the second address may be specifically as follows: the first NEF network element sends a query message to the NRF network element, the query message being used to request the address of the UPF network element that performs NAT on the second address, the query message carrying the first address; after receiving the query message, the NRF network element sends the corresponding UPF network element address to the first NEF network element. The NRF network element may locally configure the correspondence between the address and the UPF network element, or the UPF network element may send the address of the UPF network element, the second address, and the first address to the NRF network element when performing NAT on the second address.
[0186] When the first target information includes a HPLMN identifier, the HPLMN identifier may be determined based on an address domain corresponding to the second address.
[0187] When the first target information includes one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier, the first NEF network element sends seventh information to a UDM network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier. The seventh information includes the second address, and the seventh information is used to request one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier. Optionally, the seventh information may further include an address field corresponding to the second address. After receiving the seventh information, the UDM network element or the BSF network element sends the one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier to the first NEF network element.
[0188] Based on the implementation described above, each network element can subscribe to the AF request through various parameters, so that the AF request can affect the correct session.
[0189] Optionally, the first NEF network element sends the seventh information to the UDM network element or BSF network element of the PLMN corresponding to the HPLMN identifier through a third NEF network element, where the third NEF network element is an H-NEF network element. Correspondingly, the UDM network element or BSF network element also replies to the first NEF network element through the third NEF with one or more of the SUPI, GPSI, internal group identifier, and external group identifier. This embodiment of the present application does not limit the manner in which the first NEF network element and the UDM network element or BSF network element of the PLMN corresponding to the HPLMN identifier exchange information (e.g., through a third NEF network element).
[0190] Specifically, the first NEF network element obtains one or more of the SUPI, GPSI, internal group identifier, and external group identifier through the UDM network element in the following manner: the first NEF network element first determines the HPLMN corresponding to the session based on the address field of the second address, and queries the V-NRF for the address of the third NEF based on the HPLMN, wherein the V-NRF network element queries or locally configures the address of the third NEF network element corresponding to the HPLMN through the H-NRF. After the address of the third NEF network element is queried, the first NEF network element queries the third NEF network element for one or more of the SUPI, GPSI, internal group identifier, and external group identifier by calling the Nnef_UEId_Get interface. After receiving the address, the third NEF network element queries or locally configures the address of the UDM network element through the H-BSF network element or the H-NRF network element. After the address of the UDM network element is queried, the second address is sent to the UDM network element. After receiving the second address, the UDM network element replies to the third NEF network element with one or more of the SUPI, GPSI, internal group identifier, and external group identifier. After receiving the second address, the H-NEF network element forwards the one or more of the SUPI, GPSI, internal group identifier, and external group identifier to the first NEF network element.
[0191] In an embodiment of the present application, the AF request sent by the first NEF network element to the UDR network element and the AF request sent by the AF network element to the first NEF network element, the information indicating how to affect the session is the same, but another part of the information may be different. For example, the information used to indicate the target session may be different. In one possible implementation, the target UE Identifier included in the AF request sent by the AF network element to the first NEF network element includes the first address, and the Data Key included in the AF request sent by the first NEF network element to the UDR network element includes the SUPI (this SUPI is the SUPI corresponding to the first address). The target UE Identifier and the Data Key both have the function of indicating the target session.
[0192] Specifically, in this implementation, the AF request sent by the AF network element to the first NEF network element does not include the first target information. The fact that the AF request sent by the AF network element to the first NEF network element does not include the first target information can also be understood as adding the first target information to the AF request sent by the first NEF network element to the UDR network element, while the AF request sent by the AF network element does not include the first target information. Optionally, the AF request sent by the first NEF network element to the UDR network element does not include the first address. Exemplarily, when the first target information includes a SUPI, the first target information may also optionally include a DNN or S-NSSAI, etc. The AF request sent by the AF network element to the first NEF network element does not include the first target information, i.e., does not include a SUPI. In this implementation, because the first address included in the AF request sent by the AF network element to the first NEF network element is the public network address obtained by NATing the second address, multiple terminal devices may share the same public network address. The AF request may only be for a session of one terminal device, and the sessions of other terminal devices do not need to be affected. The first NEF network element obtains the SUPI from the corresponding UDM network element or BSF network element through the third NEF network element. By adding the SUPI in the AF request sent to the UDR network element, optionally, the first address included in the AF request can be deleted, so as to accurately indicate the session of the terminal device targeted by the AF request, which is conducive to making the AF request affect the correct session.
[0193] Before the UDR network element stores the AF request, the following two implementation methods can be used to improve the security of the UDR storage space:
[0194] Method 1: Before the UDR network element receives the AF request from the first NEF network element, the method further includes: the first NEF network element sends a storage request message to the UDR network element, the storage request message including first target information; the UDR network element determines, based on the first target information, whether any network element has subscribed to the AF request corresponding to the first target information; if a network element has subscribed to the AF request corresponding to the first target information, the UDR network element sends a response message to the first NEF network element in response to the storage request message, the response message indicating that the storage of the AF request is allowed. If no network element has subscribed to the first target information, the UDR network element refuses to receive the AF request corresponding to the first target information.
[0195] Method 2: The UDR network element receives the AF request from the first NEF network element. The UDR network element determines, based on the first target information, whether there is a network element that has subscribed to the AF request corresponding to the first target information. If there is a network element that has subscribed to the AF request corresponding to the first target information, the UDR network element stores the AF request. If there is no network element that has subscribed to the AF request corresponding to the first target information, the UDR network element will discard the AF request.
[0196] Based on the method described above, the UDR network element only stores the AF request that has subscribed to the first target information, which can avoid the occupation of the UDR storage space due to illegal attacks and improve the security of the UDR storage space.
[0197] 503. The first SMF network element sends the first subscription information to the second NEF network element. Correspondingly, the second NEF network element receives the first subscription information from the first SMF network element. The first subscription information is used to request to subscribe to the AF request.
[0198] In an embodiment of the present application, the first subscription information instructs the first SMF network element to subscribe to the AF request from the second NEF network element, and the first subscription message includes second target information, and the second target information includes one or more of the following: the first address, the second address, the IP domain corresponding to the second address, SUPI, GPSI, HPLMN identifier, DNN, S-NSSA, internal group identifier, external group identifier, and the first identifier. When the second NEF network element receives the AF request corresponding to the first target information, the second NEF network element will forward the AF request to the first SMF network element. Optionally, the first SMF network element can send the first subscription information to the second NEF network element when the HR-SBO session is established.
[0199] In a possible implementation, if the second target information includes one or more of a SUPI, a GPSI, a HPLMN identifier, an internal group identifier, and an external group identifier, the method further includes, the first SMF network element receiving, from a second SMF network element or a PCF network element, eighth information sent, where the eighth information includes one or more of a SUPI, a GPSI, a HPLMN identifier, an internal group identifier, and an external group identifier. The second SMF network element and the first SMF network element are not in the same PLMN.
[0200] It should also be noted that before the first SMF network element receives the eighth information sent from the second SMF network element or the PCF network element, the first SMF network element may send query information for one or more of the SUPI, GPSI, HPLMN identifier, internal group identifier, and external group identifier to the second SMF network element or the PCF network element when the HR-SBO session is established. After the second SMF network element or the PCF network element obtains the query information for one or more of the SUPI, GPSI, HPLMN identifier, internal group identifier, and external group identifier from the UDM network element, it will return the one or more of the SUPI, GPSI, HPLMN identifier, internal group identifier, and external group identifier to the first SMF.
[0201] Based on this implementation, each network element can subscribe to an AF request using multiple parameters, thereby improving the accuracy of the AF request affecting the session.
[0202] 504. The second NEF network element sends second subscription information to the UDR network element. Correspondingly, the UDR network element receives the second subscription information from the second NEF network element. The second subscription information is used to request subscription to the AF request.
[0203] In an embodiment of the present application, the second subscription information indicates that the second NEF network element subscribes to the AF request from the UDR network element. In the second subscription information, the second subscription message includes second target information. When the storage space of the UDR network element stores the AF request corresponding to the second target information, the UDR network element will forward the AF request to the second NEF network element.
[0204] 505. The UDR network element sends an AF request to the second NEF network element. Correspondingly, the second NEF network element receives the AF request from the UDR network element.
[0205] In the embodiment of the present application, when the first target information and the second target information are the same, the UDR network element will send the AF request to the second NEF network element, and the AF request sent by the UDR network element to the second NEF network element includes the second target information.
[0206] Among them, the first target information and the second target information are the same, which can be understood as that all parameter information contained in the first target information and the second target information are the same, and the content corresponding to each parameter information in the first target information and the second target information is the same one by one.
[0207] For example, assuming that the first target information includes a SUPI, a DNN, and an S-NSSAI, and the second target information also includes a SUPI, a DNN, and an S-NSSAI, it can be concluded that all parameter information included in the first target information and the second target information is the same. The fact that the content corresponding to each parameter information in the first target information and the second target information is identical means that the SUPI in the first target information and the SUPI in the second target information are the same, the DNN in the first target information and the DNN in the second target information are the same, and the DNN in the first target information and the DNN in the second target information are the same.
[0208] For another example, the first target information includes SUPI, the second target information also includes SUPI, all parameter information contained in the first target information and the second target information are the same, and the content corresponding to each parameter information in the first target information and the second target information is the same one by one, which means that the S-NSSAI in the first target information and the S-NSSAI in the second target information are the same.
[0209] Alternatively, the first target information and the second target information are the same, which can be understood as the first target information and the second target information containing some of the same parameter information, and the content corresponding to each parameter information in the same parameter information in the first target information and the second target information is the same one by one.
[0210] For example, assuming that the first target information includes a SUPI, a DNN, and an S-NSSAI, and the second target information includes a SUPI and a DNN, the partially identical parameter information included in the first target information and the second target information means that both the first target information and the second target information include a SUPI and a DNN. In the identical parameter information in the first target information and the second target information, the content corresponding to each parameter information is identical, meaning that the SUPI in the first target information is the same as the SUPI in the second target information, and the DNN in the first target information is the same as the DNN in the second target information.
[0211] 506. The second NEF network element sends an AF request to the first SMF network element. Correspondingly, the first SMF network element receives the AF request from the second NEF network element.
[0212] In an embodiment of the present application, after the first SMF network element receives the AF request, it will affect the session of the terminal device based on the instruction of the AF request, such as establishing or modifying the session, or taking corresponding actions on the session of the terminal device. Based on the method described in the embodiment of the present application, the first NEF network element can determine the roaming type of the session corresponding to the AF request or the forwarding path of the AF request through the first identifier, so that the AF request is forwarded to the corresponding first SMF network element, so that the AF request can affect the correct session.
[0213] Figure 5 illustrates the first NEF network element and the second NEF network element as two different NEF network elements. The first NEF network element and the second NEF network element may also be the same NEF network element. This is because, when the AF network element sends an AF request, it selects a NEF network element as the sender. When the first SMF network element subscribes to an AF request, it also selects a NEF network element as the sender. The NEF network element selected by the AF network element and the NEF network element selected by the first SMF network element may be the same NEF network element or different NEF network elements.
[0214] FIG6 shows a specific implementation flow of the communication method when the first NEF network element and the second NEF network element are the same network element. The first NEF network element and the second NEF network element are both referred to as the first NEF network element, and includes steps 601 to 606 .
[0215] 601. The AF network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the AF network element. The AF request sent by the AF network element includes a first identifier, and the first identifier is used to distinguish PLMNs.
[0216] 602. The first NEF network element sends an AF request to the UDR network element. Correspondingly, the UDR network element receives and stores the AF request.
[0217] 603. The first SMF network element sends the first subscription information to the first NEF network element. Correspondingly, the first NEF network element receives the first subscription information from the first SMF network element. The first subscription information is used to request subscription to the AF request.
[0218] 604. The first NEF network element sends second subscription information to the UDR network element. Correspondingly, the UDR network element receives the second subscription information from the first NEF network element. The second subscription information is used to request subscription to the AF request.
[0219] Among them, in the embodiment of the present application, step 603 and step 604 can be executed before step 605. Figure 5 shows that step 603 and step 604 are executed before step 601. It should also be noted that step 603 and step 604 can also be executed after step 601, and this application does not limit this.
[0220] 605. The UDR network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the UDR network element.
[0221] 606. The first NEF network element sends an AF request to the first SMF network element. Correspondingly, the first SMF network element receives the AF request from the first NEF network element.
[0222] Among them, the specific implementation method of steps 601 to 606 is the same as that of steps 501 to 506, and will not be repeated here in the embodiment of the present application.
[0223] Currently, the V-SMF in an HR-SBO session obtains AF requests by subscribing to the V-NEF and obtaining AF requests indexed by the Data Key from the V-NEF. AF requests can use the group ID index, but because the V-SMF is unaware of the group ID to which this HR-SBO session belongs, and an HR-SBO session can belong to multiple groups at the same time, the V-SMF cannot subscribe to AF requests indexed by the group ID. As a result, AF requests indexed by the group ID cannot be sent to the V-SMF, affecting the session.
[0224] In order to enable the AF request indexed by the internal group identifier to be forwarded to the V-SMF to affect the session, an embodiment of the present application proposes a communication method. Figure 7 is a flow chart of a communication method provided by an embodiment of the present application. As shown in Figure 7, the communication method includes the following steps 701 to 709. The execution subject of the method shown in Figure 7 can be the first SMF network element, the second SMF network element, the second NEF network element, the UDR network element, the first NEF network element, the AF network element and the UDM network element. Alternatively, the execution subject of the method shown in Figure 7 can be a device or chip having the functions of the first SMF network element, the second SMF network element, the second NEF network element, the UDR network element, the first NEF network element, the AF network element and the UDM network element, which is not limited in the embodiment of the present application. Figure 7 takes the first SMF network element, the second SMF network element, the second NEF network element, the UDR network element, the first NEF network element, the AF network element and the UDM network element as the execution subject of the method for illustration. The first SMF network element involved in the embodiment described in FIG7 may be the V-SMF network element shown in FIG2 , the second SMF network element involved in the embodiment described in FIG7 may be the H-SMF network element shown in FIG2 , the UDR network element, AF network element, and UDM network element involved in the embodiment described in FIG7 may be the UDR network element, AF network element, and UDM network element shown in FIG2 , the first NEF network element and the second NEF network element involved in the embodiment described in FIG7 may be the NEF network element shown in FIG2 , the first NEF network element and the second NEF network element may be the same NEF network element, or may be two different NEF network elements. FIG7 is introduced with the first NEF network element and the second NEF network element being two different NEF network elements.
[0225] 701. The second SMF network element sends one or more internal group identifiers to the first SMF network element. Correspondingly, the first SMF network element receives the one or more internal group identifiers from the second SMF network element.
[0226] In the embodiment of the present application, the second SMF network element and the first SMF network element do not belong to the network elements under the same PLMN. The first SMF network element may be a V-SMF network element, and the second SMF network element may be an H-SMF network element. The second SMF network element sends one or more internal group identifiers to the first SMF network element during the process of establishing an HR-SBO session, and the second SMF network element obtains one or more internal group identifiers to which the session belongs through the UDM network element. Since a session can belong to one or more groups, the second SMF network element sends one or more internal group identifiers for the session.
[0227] Optionally, it can be assumed that the second SMF network element actively sends one or more internal group identifiers to the first SMF network element during the HR-SBO session establishment process.
[0228] An optional way is that during the session establishment process, if the second SMF network element authorizes this session as an HR-SBO session, it sends a group identifier to the first SMF network element.
[0229] Alternatively, during the process of establishing or modifying an HR-SBO session, the first SMF network element may send an internal group identifier request message to the second SMF network element. After the second SMF network element receives the internal group identifier request message, the second SMF network element sends one or more internal group identifiers to the first SMF network element. It should be noted that, in the process of establishing a session, the second SMF network element will first obtain one or more internal group identifiers belonging to the session from the UDM network element, and then receive the internal group identifier request message from the first SMF network element.
[0230] Based on this method, the first SMF network element can obtain the internal group identifier, so that the first SMF network element can subscribe to the AF request of the group identifier index. Subsequent AF requests for the group identifier index can be sent to the first SMF to affect the corresponding session.
[0231] 702. The first SMF network element sends first subscription information to the second NEF network element. Correspondingly, the second NEF network element receives the first subscription information from the first SMF network element, where the first subscription information is used to request a subscription to an AF request, the first subscription information includes second target information, and the second target information includes the one or more internal group identifiers.
[0232] In an embodiment of the present application, the first subscription information instructs the first SMF network element to subscribe to the AF request from the second NEF network element. When the second NEF network element receives the AF request corresponding to the second target information, the second NEF network element will forward the AF request to the first SMF network element.
[0233] Among them, the first SMF network element can immediately send the first subscription information to the second NEF network element after receiving one or more internal group identifiers, or the first SMF network element does not need to send the first subscription information immediately, but can send the first subscription information to the second NEF network element at any time during the entire life cycle of the HR-SBO session.
[0234] Optionally, the second target information also includes one or more of the following: the first address, the second address, the IP domain corresponding to the second address, SUPI, GPSI, HPLMN identifier, DNN, and S-NSSA.
[0235] Among them, the first address corresponds to the second address, and the first address corresponds to the second address means that the first address is the address obtained after the second address is NATed. The first NEF network element can obtain the corresponding second address through the first address based on the corresponding relationship between the first address and the second address. In a possible implementation, the second address is the private network address (private IP) of the terminal device session, and the first address is the public network address obtained through NAT of the private network address of the terminal device session. The second address being the private network address of the terminal device session specifically means that the IP address assigned to the terminal device by the 5G core network is a private network address. The first NEF network element obtains the second address corresponding to the first address, which means that the first NEF network element obtains the second address by providing the first address. For example, the first NEF network element uses the Nupf_GetPrivateUEIPaddr service to provide the first address to the UPF network element. After receiving the first address, the UPF network element replies to the first NEF network element with the NATed UE IP address uniquely identified by the first address provided by the first NEF, that is, the second address. In addition, there may be other corresponding relationships between the first address and the second address. For example, the second address is the address used within the 5G core network, and the first address is the address used outside the 5G core network. Both are used to mark the same session, and the embodiments of the present application are not limited to this. The address domain corresponding to the second address refers to the address domain to which the second address belongs. For example, the address domain includes many addresses, and the second address is one of them. Optionally, the first address can be specifically the public IP address of the terminal device, or it can be specifically the public IP address and port number of the terminal device. Optionally, the second address is the private IP address of the terminal device session, and the address domain corresponding to the second address is the IP domain.
[0236] 703. The second NEF network element sends second subscription information to the UDR network element. Correspondingly, the UDR network element receives the second subscription information from the second NEF network element. The second subscription information is used to request subscription to the AF request. The second subscription information includes second target information.
[0237] In an embodiment of the present application, the second subscription information indicates that the second NEF network element subscribes to the AF request from the UDR network element. In the second subscription information, the second subscription message includes second target information. When the storage space of the UDR network element stores the AF request corresponding to the second target information, the UDR network element will forward the AF request to the second NEF network element.
[0238] Among them, steps 701 to 703 only need to be executed before step 708. Figure 7 shows that steps 701 to 703 are executed before step 707. Steps 701 to 703 can also be executed after step 707. This embodiment of the present application does not limit this.
[0239] 704. The AF network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the AF network element. The AF request sent by the AF network element includes one or more external group identifiers.
[0240] In this embodiment of the present application, the AF request is intended to affect sessions associated with one or more internal group identifiers corresponding to the one or more external group identifiers. The AF request may affect the session by instructing the session to change traffic flow or providing application service deployment information. This embodiment of the present application does not limit the specific manner in which the AF request affects the session. The first NEF network element is a V-NEF network element.
[0241] 705. The first NEF network element sends ninth information to the UDM network element. Correspondingly, the UDM network element receives ninth information from the first NEF network element. The ninth information is used to request one or more internal group identifiers corresponding to one or more external group identifiers.
[0242] In an embodiment of the present application, when the first SMF is unaware of the external group identifier, the first NEF needs to obtain one or more internal group identifiers corresponding to the one or more external group identifiers. Therefore, the first NEF can determine the first PLMN to which the external group identifier belongs based on the domain identifier in the external group identifier, and then obtain the one or more internal group identifiers from the UDM network element belonging to the first PLMN.
[0243] Among them, the specific implementation method of the first NEF network element sending the ninth information to the UDM network element is to send the ninth information to the UDM network element belonging to the first PLMN through the fourth NEF network element belonging to the first PLMN, wherein the first PLMN to which the external group identifier belongs is determined according to the domain identifier in the external group identifier.
[0244] When the first SMF network element perceives the external group identifier, if the first NEF network element determines, based on the domain identifier in the external group identifier, that the first PLMN to which the external group identifier belongs is not the PLMN where the first NEF network element is located, then step 707 is directly executed. In another optional real-time manner, the first NEF network element does not need to determine the PLMN to which the external group identifier belongs, but directly sends the external group identifier to the UDM network element that belongs to the same PLMN as the first NEF network element to obtain the corresponding internal group identifier. If the acquisition fails, step 707 is executed.
[0245] 706. The UDM network element sends the tenth information to the first NEF network element. Correspondingly, the first NEF network element receives the tenth information from the UDM network element. The tenth information includes the one or more internal group identifiers.
[0246] The specific implementation manner of the UDM network element sending the tenth information to the first NEF network element is to send the tenth information to the first NEF network element through the fourth NEF network element.
[0247] 707. The first NEF network element sends an AF request to the UDR network element. Correspondingly, the UDR network element receives the AF request from the first NEF network element. The AF request includes first target information, and the first target information includes one or more internal group identifiers.
[0248] In this embodiment of the present application, the first target information can be understood as a data key. When the UDR network element determines that a certain network element has subscribed to the AF request corresponding to the first target information, the UDR network element will forward the AF request. The first target information can be used to indicate the target session affected by the AF request and also has the function of identifying information stored in the UDR. For example, when subscribing to the UDR network element, using the first target information can retrieve content (such as the AF request) stored using the same first target information.
[0249] Optionally, the AF request sent by the first NEF network element to the UDR network element does not include an external group identifier.
[0250] Optionally, in addition to the internal group identifier, the first target information may also include one or more of the following: the first address, the second address, the IP domain corresponding to the second address, SUPI, GPSI, HPLMN identifier, DNN, and S-NSSA.
[0251] In one possible implementation, when the first target information includes one or more of a SUPI, a GPSI, and an internal group identifier, the first NEF network element sends seventh information to a UDM network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier. The seventh information includes a second address and is used to request one or more of the SUPI and the GPSI. Optionally, the seventh information may also include an address field corresponding to the second address. After receiving the seventh information, the UDM network element or the BSF network element sends the one or more of the SUPI and the GPSI to the first NEF network element. Based on this implementation, each network element can subscribe to an AF request using multiple parameters so that the AF request can affect the correct session.
[0252] Optionally, the first NEF network element sends the seventh information to a UDM network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier through a third NEF network element, where the third NEF network element is a home NEF (H-NEF) network element. Correspondingly, the UDM network element or the BSF network element also replies to the first NEF network element through the third NEF with one or more of the SUPI and the GPSI.
[0253] Specifically, the first NEF network element obtains one or more of the SUPI and GPSI through the UDM network element in the following manner: the first NEF network element first determines the HPLMN corresponding to the session based on the address field of the second address, and queries the V-NRF or locally configures the address of the third NEF network element corresponding to the HPLMN based on the HPLMN, wherein the V-NRF network element queries the address of the third NEF network element through the H-NRF. After the address of the third NEF network element is queried, the first NEF network element queries the third NEF network element for one or more of the SUPI and GPSI by calling the Nnef_UEId_Get interface. After receiving the address, the third NEF queries or locally configures the address of the UDM network element through the H-BSF network element or the H-NRF network element. After the address of the UDM network element is queried, the second address is sent to the UDM network element. After receiving the second address, the UDM network element replies to the third NEF network element with one or more of the SUPI and the GPSI. After receiving the second address, the H-NEF network element forwards the one or more of the SUPI and the GPSI to the first NEF network element. This embodiment of the present application does not limit the manner in which the first NEF network element exchanges information with the UDM network element or BSF network element of the PLMN corresponding to the HPLMN identifier (e.g., through the third NEF network element).
[0254] Before a UDR NE stores an AF request, the following two implementation methods can be used to improve the security of the UDR storage space:
[0255] Method 1: Before the UDR network element receives the AF request from the first NEF network element, the method further includes: the first NEF network element sends a storage request message to the UDR network element, the storage request message including first target information; the UDR network element determines, based on the first target information, whether any network element has subscribed to the AF request corresponding to the first target information; if a network element has subscribed to the AF request corresponding to the first target information, the UDR network element sends a response message to the first NEF network element in response to the storage request message, the response message indicating that the storage of the AF request is allowed. If no network element has subscribed to the first target information, the UDR network element refuses to receive the AF request corresponding to the first target information.
[0256] Method 2: The UDR network element receives the AF request from the first NEF network element. The UDR network element determines, based on the first target information, whether there is a network element that has subscribed to the AF request corresponding to the first target information. If there is a network element that has subscribed to the AF request corresponding to the first target information, the UDR network element stores the AF request. If there is no network element that has subscribed to the AF request corresponding to the first target information, the UDR network element will discard the AF request.
[0257] Based on the method described above, the UDR network element only stores the AF request that has subscribed to the first target information, which can avoid the occupation of the UDR storage space due to illegal attacks and improve the security of the UDR storage space.
[0258] 708. The UDR network element sends an AF request to the second NEF network element. Correspondingly, the first NEF network element receives the AF request from the UDR network element.
[0259] In the embodiment of the present application, when the first target information and the second target information are the same, the UDR network element will send the AF request to the second NEF network element, and the AF request sent by the UDR network element to the second NEF network element includes the second target information.
[0260] Among them, the first target information and the second target information are the same, which can be understood as that all parameter information contained in the first target information and the second target information are the same, and the content corresponding to each parameter information in the first target information and the second target information is the same one by one.
[0261] For example, assuming that the first target information includes an internal group identifier and a DNN, and the second target information also includes an internal group identifier and a DNN, it can be concluded that all parameter information included in the first target information and the second target information are identical. "The content corresponding to each parameter information in the first target information and the second target information is identical" means that the internal group identifier in the first target information and the internal group identifier in the second target information are identical, and the DNN in the first target information and the DNN in the second target information are identical.
[0262] Alternatively, the first target information and the second target information are the same, which can be understood as the first target information and the second target information containing some of the same parameter information, and the content corresponding to each parameter information in the same parameter information in the first target information and the second target information is the same one by one.
[0263] For example, assuming that the first target information includes an internal group identifier and a DNN, and the second target information includes an internal group identifier, the partially identical parameter information included in the first target information and the second target information means that both the first target information and the second target information include the internal group identifier. In the identical parameter information in the first target information and the second target information, the content corresponding to each parameter information is identical, which means that the internal group identifier in the first target information and the internal group identifier in the second target information are the same.
[0264] 709. The second NEF network element sends an AF request to the first SMF network element. Correspondingly, the first SMF network element receives the AF request from the first NEF network element.
[0265] In an embodiment of the present application, after the first SMF network element receives the AF request, it will affect the session of the terminal device based on the instruction of the AF request, such as establishing or modifying the session, or taking corresponding actions on the session of the terminal device. Based on the method described in the embodiment of the present application, the first SMF network element can obtain the internal group identifier, so that the first SMF network element can subscribe to the AF request indexed by the group identifier, and the AF network element can send the AF request indexed by the group identifier to the first SMF to affect the session.
[0266] Among them, Figure 7 introduces the first NEF network element and the second NEF network element as two different NEF network elements. The first NEF network element and the second NEF network element can also be the same NEF network element. The reason is that when the AF network element sends an AF request, it selects a NEF network element as the sending end. When the first SMF network element subscribes to the AF request, it also selects a NEF network element as the sending end. The NEF network element selected by the AF network element and the NEF network element selected by the first SMF network element can be the same NEF network element or different NEF network elements.
[0267] FIG8 shows a specific implementation flow of the communication method when the first NEF network element and the second NEF network element are the same network element. The first NEF network element and the second NEF network element are both referred to as the first NEF network element, including steps 801 to 809 .
[0268] 801. The second SMF network element sends one or more internal group identifiers to the first SMF network element. Correspondingly, the first SMF network element receives one or more internal group identifiers from the second SMF network element.
[0269] 802. The first SMF network element sends first subscription information to the first NEF network element. Correspondingly, the second NEF network element receives the first subscription information from the first SMF network element, where the first subscription information is used to request a subscription to an AF request, the first subscription information includes second target information, and the second target information includes one or more internal group identifiers.
[0270] 803. The first NEF network element sends second subscription information to the UDR network element. Correspondingly, the UDR network element receives the second subscription information from the second NEF network element. The second subscription information is used to request subscription to the AF request. The second subscription information includes second target information.
[0271] Among them, steps 801 to 803 only need to be executed before step 808. Figure 7 shows that steps 801 to 803 are executed before step 807. Steps 801 to 803 can also be executed after step 807. This embodiment of the present application does not limit this.
[0272] 804. The AF network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the AF network element. The AF request sent by the AF network element includes one or more external group identifiers.
[0273] 805. The first NEF network element sends ninth information to the UDM network element. Correspondingly, the UDM network element receives ninth information from the first NEF network element. The ninth information is used to request one or more internal group identifiers corresponding to one or more external group identifiers.
[0274] 806. The UDM network element sends tenth information to the first NEF network element. Correspondingly, the first NEF network element receives tenth information from the UDM network element. The tenth information includes the one or more internal group identifiers.
[0275] 807. The first NEF network element sends an AF request to the UDR network element. Correspondingly, the UDR network element receives the AF request from the first NEF network element. The AF request includes first target information, and the first target information includes one or more internal group identifiers.
[0276] 808. The UDR network element sends an AF request to the first NEF network element. Correspondingly, the first NEF network element receives the AF request from the UDR network element.
[0277] 809. The first NEF network element sends an AF request to the first SMF network element. Correspondingly, the first SMF network element receives the AF request from the first NEF network element.
[0278] Among them, the specific implementation method of steps 801 to 809 is the same as that of steps 701 to 709, and will not be repeated here in the embodiment of this application.
[0279] Please refer to Figure 9, which shows a schematic diagram of the structure of a communication device according to an embodiment of the present application. The communication device shown in Figure 9 can be used to perform some or all of the functions of the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element in the methods shown in Figures 3 to 8 above. The device can be the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element, or a device within the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element, or a device that can be used in conjunction with the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element. The communication device can also be a system-on-chip. The communication device shown in Figure 9 may include a communication unit 901 and a processing unit 902. The processing unit 902 is configured to perform data processing. The communication unit 901 is configured to communicate with other devices. The communication unit 901 integrates a receiving unit and a transmitting unit. The communication unit 901 can also be referred to as a transceiver unit. Alternatively, the communication unit 901 may be split into a receiving unit and a sending unit. The same applies to the processing unit 902 and the communication unit 901 below, and will not be described in detail below.
[0280] The communication device 900 may be used to perform the function of the first NEF network element in the aforementioned method embodiments corresponding to FIG. 3 to FIG. 8 .
[0281] When the communication device 900 is applied to the function of the first NEF network element in the method embodiment corresponding to Figure 3 or Figure 4, the communication unit 901 is used to receive an AF request from the application function AF network element, the AF request is used to affect the session of the terminal device, and the AF request from the AF network element includes a first address; the communication unit 901 is also used to obtain the second address corresponding to the first address and the address field corresponding to the second address; the communication unit 901 is also used to send an AF request to the unified data repository UDR network element.
[0282] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0283] In one possible implementation, when the communication unit 901 obtains the second address corresponding to the first address and the address domain corresponding to the second address, it is specifically used to: send first information to the user plane function UPF network element, the first information includes the first address, the UPF network element is a UPF network element that performs NAT on the second address, and the first information requests the second address and the address domain corresponding to the second address; receive second information from the UPF network element, the second information includes the second address, and the address domain corresponding to the second address.
[0284] In a possible implementation manner, the address domain corresponding to the second address does not belong to the public land mobile network PLMN to which the first NEF network element belongs.
[0285] In a possible implementation, the processing unit 902 is configured to determine, according to the address domain corresponding to the second address, a PLMN that allocates the second address for the session.
[0286] In one possible implementation, the AF request sent to the UDR network element includes first target information, and the first target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, a single network slice selection support information S-NSSAI, an internal group identifier, and an external group identifier.
[0287] In a possible implementation manner, the AF request from the AF network element does not include the first target information.
[0288] In a possible implementation manner, the AF request sent to the UDR network element does not include the first address.
[0289] In one possible implementation, the first target information includes one or more of a SUPI, a GPSI, and an internal group identifier. The communication unit 901 is further configured to send seventh information to a user data management (UDM) network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier, where the seventh information includes the second address and / or an address field corresponding to the second address, and the seventh information is used to request one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier; and receive one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier from the UDM network element or the BSF network element.
[0290] In one possible implementation, before sending an AF request to the unified data repository UDR network element, the communication unit 901 is also used to send storage request information to the UDR network element, where the storage request information includes first target information; the communication unit 901 is also used to receive response information sent from the UDR network element in response to the storage request information, where the response information indicates that the storage of the AF request is allowed.
[0291] In one possible implementation, the communication unit 901 is also used to send third information to the network storage function NRF network element, where the third information includes the second address, and the third information is used to request to query the address of the binding support function BSF network element corresponding to the second address; the communication unit 901 is also used to receive fourth information from the NRF network element, where the fourth information indicates that the address of the BSF network element cannot be queried.
[0292] In one possible implementation, the communication unit 901 is further used to send fifth information to the BSF network element, where the fifth information includes the second address, and the fifth information requests to query the address of the policy control function PCF network element corresponding to the second address; the communication unit 901 is further used to receive sixth information from the BSF network element, where the sixth information indicates that the address of the PCF network element cannot be queried.
[0293] When the communication device 900 is applied to the function of the first NEF network element in the method embodiment corresponding to Figure 5 or Figure 6, the communication unit 901 is used to receive an AF request from the application function AF network element, the AF request is used to affect the session of the terminal device, and the AF request from the AF network element includes a first identifier, and the first identifier is used to distinguish the public land mobile network PLMN; the communication unit 901 is used to send the AF request to the unified data repository UDR network element.
[0294] In a possible implementation manner, the first identifier is one of the following: a PLMN identifier, a home public land mobile network (HPLMN) identifier, or a virtual local area network (VLAN) identifier.
[0295] In one possible implementation, the AF request sent to the UDR network element includes first target information, and the first target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a HPLMN identifier, a data network name DNN, single network slice selection support information S-NSSAI, an internal group identifier, an external group identifier, and a first identifier.
[0296] In a possible implementation manner, the AF request from the AF network element does not include the first target information.
[0297] In one possible implementation, the first target information includes one or more of a SUPI, a GPSI, an internal group identifier, and an external group identifier. The communication unit 901 is further configured to send seventh information to a user data management (UDM) network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier. The seventh information includes the second address and / or an address field corresponding to the second address, and the seventh information is used to request one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier. The communication unit 901 is further configured to receive one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier from the UDM or BSF network element.
[0298] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0299] In one possible implementation, before sending an AF request to the unified data repository UDR network element, the communication unit 901 is also used to send storage request information to the UDR network element, where the storage request information includes first target information; the communication unit 901 is also used to receive response information sent from the UDR network element in response to the storage request information, where the response information indicates that the storage of the AF request is allowed.
[0300] When the communication device 900 is applied to the function of the first NEF network element in the method embodiment corresponding to Figure 7 or Figure 8, the communication unit 901 is used to receive an AF request sent from the application function AF network element, the AF request is used to affect the session of the terminal device, and the AF request sent by the AF network element includes one or more external group identifiers, and the first public land mobile network PLMN to which the one or more external group identifiers belong is not the PLMN where the first NEF network element is located; the communication unit 901 is also used to send ninth information to the user data management UDM network element belonging to the first PLMN, and the ninth information is used to request one or more internal group identifiers corresponding to the one or more external group identifiers; the communication unit 901 is also used to receive tenth information sent from the UDM network element, and the tenth information includes one or more internal group identifiers; the communication unit 901 is also used to send an AF request to the unified data repository UDR network element.
[0301] In a possible implementation, the processing unit 902 is configured to determine the first PLMN to which the one or more external group identifiers belong according to the domain identifier in the one or more external group identifiers.
[0302] In one possible implementation, when the communication unit 901 sends the ninth information to the UDM network element corresponding to the first PLMN, it is specifically used to send the ninth information to the UDM network element belonging to the first PLMN through the fourth NEF network element belonging to the first PLMN; when the communication unit 901 receives the tenth information sent from the UDM network element, it is specifically used to receive the tenth information from the UDM network element through the fourth NEF network element.
[0303] In a possible implementation, the AF request sent to the UDR includes first target information, where the first target information includes one or more internal group identifiers.
[0304] The communication device 900 may be used to perform the function of the second NEF network element in the aforementioned method embodiments corresponding to FIG. 3 , FIG. 5 or FIG. 7 . When the communication device 900 is applied to the function of the second NEF network element in the method embodiment corresponding to Figure 3, Figure 5 or Figure 7, the communication unit 901 is used to receive first subscription information sent from the first session management function SMF network element, where the first subscription information is used to request subscription to the application function AF request, and the AF request is used to affect the session of the terminal device. The first subscription information includes second target information, and the second target information includes one or more of the following: the first address, the second address, the address domain corresponding to the second address, the user permanent identifier SUPI, the general public user identity GPSI, the home public land mobile network HPLMN identifier, the data network name DNN, the single network slice selection support information S-NSSAI, the internal group identifier, and the external group identifier; the communication unit 901 is also used to send second subscription information to the unified data repository UDR network element, where the second subscription information is used to request subscription to the AF request, and the second subscription information includes the second target information; the communication unit 901 is also used to receive the AF request from the UDR network element, and the AF request from the UDR network element includes the second target information; the communication unit 901 is also used to send the AF request to the first SMF network element.
[0305] In a possible implementation manner, the second target information further includes a first identifier, and the first identifier is used to distinguish PLMNs.
[0306] In a possible implementation manner, the first identifier is one of the following: a public land mobile network PLMN identifier, a HPLMN identifier, or a virtual local area network VLAN identifier.
[0307] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0308] Among them, the communication device 900 can be used to perform the function of the first SMF network element in the aforementioned method embodiments corresponding to Figures 3 to 8.
[0309] When the communication device 900 is applied to the function of the first SMF network element in the method embodiment corresponding to Figures 3 to 6, the communication unit 901 is used to send first subscription information to the second network open function NEF network element, where the first subscription information includes second target information, and the second target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, a single network slice selection support information S-NSSA, an internal group identifier, and an external group identifier; the communication unit 901 is also used to receive an application function AF request sent from the second NEF network element, where the AF request is used to affect the session of the terminal device, and the AF request from the second NEF network element includes the second target information.
[0310] In a possible implementation manner, the second target information further includes a first identifier, where the first identifier is used to distinguish a public land mobile network PLMN.
[0311] In a possible implementation manner, the first identifier is one of the following: a PLMN identifier, a HPLMN identifier, and a virtual local area network (VLAN) identifier.
[0312] In a possible implementation, when the second target information includes one or more of a SUPI, a GPSI, a HPLMN identifier, an internal group identifier, and an external group identifier; the communication unit 901 is further used to receive eighth information sent from a second SMF network element or a policy control function PCF network element, where the eighth information includes one or more of a SUPI, a GPSI, a HPLMN identifier, an internal group identifier, and an external group identifier.
[0313] In one possible implementation, the second SMF network element and the first SMF network element do not belong to the same PLMN.
[0314] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0315] When the communication device 900 is applied to the function of the first SMF network element in the method embodiment corresponding to Figure 7 or Figure 8, the communication unit 901 is used to receive one or more internal group identifiers sent from the second SMF network element; the communication unit 901 is also used to send first subscription information to the second network open function NEF network element, the first subscription information is used to request to subscribe to the AF request, the first subscription information includes second target information, and the second target information includes one or more internal group identifiers; the communication unit 901 is also used to receive an AF request from the second NEF network element, and the AF request from the second NEF network element includes the second target information.
[0316] In one possible implementation, before the communication unit 901 receives one or more internal group identifiers sent from the second SMF network element, the communication unit 901 is further used to send internal group identifier request information to the second SMF network element.
[0317] In one possible implementation, when the communication unit 901 receives one or more internal group identifiers sent from the second SMF network element, it is specifically used to receive one or more internal group identifiers sent from the second SMF network element during the establishment process of the home routing HR-SBO session of the edge computing session group.
[0318] When the communication device 900 is applied to the UPF network element function in the method embodiment corresponding to FIG3 , the communication unit 901 is configured to receive first information sent from a first network open function (NEF) network element, the first information including a first address, the first address being a public network address obtained by using network address translation (NAT) for a second address, the second address being a private network address of a terminal device session, the first information requesting the second address, and the address domain corresponding to the second address; and the communication unit 901 is further configured to send second information to the first NEF network element, the second information including the second address and the address domain corresponding to the second address.
[0319] When the communication device 900 is applied to the function of the UPF network element in the method embodiments corresponding to Figures 3 to 8. The communication unit 901 is used to receive second subscription information sent from the second NEF network element, where the second subscription information is used to request subscription to an AF request, where the AF request is used to affect the session of the terminal device, where the second subscription information includes second target information, where the second target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, single network slice selection support information S-NSSAI, an internal group identifier, and an external group identifier; the communication unit 901 is also used to receive and store an AF request from the first NEF network element, where the AF request includes the first target information, where the first target information includes one or more of the following: the first address, the second address, an address domain corresponding to the second address, SUPI, GPSI, HPLMN identifier, DNN, S-NSSA, an internal group identifier, and an external group identifier; the communication unit 901 is also used to send an AF request to the second NEF network element, where the AF request sent to the second NEF network element includes the second target information.
[0320] In a possible implementation, the second target information further includes a first identifier, and the first target information further includes a first identifier, where the first identifier is used to distinguish PLMNs.
[0321] In a possible implementation manner, the first identifier is one of the following: a public land mobile network PLMN identifier, a HPLMN identifier, or a virtual local area network VLAN identifier.
[0322] In a possible implementation manner, the first target information and the second target information include the same information.
[0323] In a possible implementation, before storing the AF request from the first NEF network element, the processing unit 902 is configured to determine whether the first target information is subscribed by the second NEF network element.
[0324] In one possible implementation, before receiving and storing the AF request from the first NEF, the communication unit 901 is further used to receive storage request information from the first NEF network element, where the storage request information includes first target information, and the first target information is subscribed to by the second NEF network element; the communication unit 901 is further used to send response information to the first NEF network element for the storage request information, where the response information indicates that the storage of the AF request is allowed.
[0325] In a possible implementation, the first address is a public network address obtained by using Network Address Translation (NAT) to translate the second address, and the second address is a private network address of a session of the terminal device.
[0326] Figure 10 shows a schematic diagram of the structure of a communication device. The communication device 1000 can be the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element in the above-mentioned method embodiments. It can also be a chip, chip system, or processor that supports the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element in implementing the above-mentioned method. This communication device can be used to implement the method described in the above-mentioned method embodiments. For details, please refer to the description of the above-mentioned method embodiments.
[0327] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor. For example, it may be a baseband processor or a central processing unit (CPU). The baseband processor may be used to process communication protocols and communication data, while the CPU may be used to control a communication device (e.g., a base station, a baseband chip, a terminal, a terminal chip, a DU or a CU), execute software programs, and process data from the software programs.
[0328] Optionally, the communication device 1000 may include one or more memories 1002, on which instructions 1004 may be stored. The instructions may be executed on the processor 1001, causing the communication device 1000 to perform the method described in the above method embodiment. Optionally, data may also be stored in the memory 1002. The processor 1001 and memory 1002 may be provided separately or integrated together.
[0329] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is configured to implement transceiver functions. The transceiver 1005 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, etc., and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is configured to implement a transmitting function.
[0330] The communication device 1000 is a first NEF network element, a second NEF network element, a first SMF network element, a UPF network element, or a UDR network element. The processor 1001 is configured to perform data processing operations on the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element in the above method embodiment. The transceiver 1005 is configured to perform data transmission and reception operations on the first NEF network element, the second NEF network element, the first SMF network element, the UPF network element, or the UDR network element in the above method embodiment.
[0331] In another possible design, processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.
[0332] In another possible design, processor 1001 may optionally store instructions 1003. Instructions 1003, when executed on processor 1001, may cause communication device 1000 to perform the method described in the above method embodiment. Instructions 1003 may be fixed in processor 1001. In this case, processor 1001 may be implemented by hardware.
[0333] In another possible design, the communication device 1000 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the embodiments of the present application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc.
[0334] The communication device described in the above embodiment may be a first NEF network element, a second NEF network element, a first SMF network element, a UPF network element, or a UDR network element, but the scope of the communication device described in the embodiment of the present application is not limited thereto, and the structure of the communication device may not be limited to FIG10. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:
[0335] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;
[0336] (2) A set of one or more ICs, optionally including a storage component for storing data and instructions;
[0337] (3) ASIC, such as modem (MSM);
[0338] (4) Modules that can be embedded in other devices;
[0339] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;
[0340] (6)Others, etc.
[0341] In the case where the communication device can be a chip or a chip system, please refer to the chip structure diagram shown in Figure 11. The chip shown in Figure 11 includes a processor 1101 and an interface 1102. Optionally, it may also include a memory 1103. The number of processors 1101 can be one or more, and the number of interfaces 1102 can be multiple.
[0342] In one design, for a case where the chip is used to implement the function of the first NEF network element in the embodiment of the present application:
[0343] The interface 1102 is used to receive or output signals;
[0344] The processor 1101 is configured to execute the data processing operation of the first NEF network element in the above method embodiment.
[0345] In another design, for a case where the chip is used to implement the function of the second NEF network element in the embodiment of the present application:
[0346] The interface 1102 is used to receive or output signals;
[0347] The processor 1101 is configured to execute the data processing operation of the second NEF network element in the above method embodiment.
[0348] In another design, for the case where the chip is used to implement the functions of the UPF network element in the embodiment of the present application:
[0349] The interface 1102 is used to receive or output signals;
[0350] The processor 1101 is used to execute the data processing operation of the UPF network element in the above method embodiment.
[0351] In another design, for the case where the chip is used to implement the functions of the UDR network element in the embodiment of the present application:
[0352] The interface 1102 is used to receive or output signals;
[0353] The processor 1101 is configured to execute the data processing operation of the UDR network element in the above method embodiment.
[0354] It is understandable that some optional features in the embodiments of the present application may, in certain scenarios, be implemented independently of other features, such as the solution on which they are currently based, to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in certain scenarios as needed. Accordingly, the communication device provided in the embodiments of the present application may also implement these features or functions accordingly, which will not be described in detail here.
[0355] It should be understood that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software. The above processor can 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, discrete gate or transistor logic device, discrete hardware component.
[0356] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.
[0357] The present application also provides a computer-readable medium for storing computer software instructions, which, when executed by a communication device, implement the functions of any of the above method embodiments.
[0358] The present application also provides a computer program product for storing computer software instructions, which, when executed by a communication device, implements the functions of any of the above method embodiments.
[0359] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. 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 in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0360] An embodiment of the present application further provides a computer program product. When the computer program product is run on a processor, the method flow of the above method embodiment is implemented.
[0361] The descriptions of the various embodiments provided in this application can refer to each other. The descriptions of each embodiment have their own focus. For parts not described in detail in a particular embodiment, please refer to the relevant descriptions of other embodiments. For the convenience and brevity of description, for example, the functions and operations performed by the various devices and equipment provided in the embodiments of this application can refer to the relevant descriptions of the method embodiments of this application. The various method embodiments and the various device embodiments can also refer to, be combined with, or quote each other.
[0362] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functions are implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the functions for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present application.
[0363] The present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer-readable storage medium is executed by a computer, the functions of any of the above method embodiments are realized.
[0364] The present application also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.
[0365] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions according to the embodiments of the present application are generated. 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 in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).
[0366] Those skilled in the art will understand that the various numerical numbers such as first and second involved in this application are only for the convenience of description and are not used to limit the scope or sequence of the embodiments of this application.
[0367] The correspondences shown in the tables in this application can be configured or predefined. The values of the information in each table are merely examples and can be configured to other values, which are not limited by this application. When configuring the correspondence between information and parameters, it is not necessary to configure all the correspondences shown in each table. For example, the correspondences shown in certain rows of the tables in this application may not be configured. For another example, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that are understandable to the communication device, and the values or representations of the parameters can also use other values or representations that are understandable to the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables. Predefined in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, solidification, or pre-burning.
[0368] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0369] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
Claims
1. A communication method, characterized in that: Applied to a first network open function NEF network element, the method includes: receiving an AF request from an application function AF network element, where the AF request is used to affect a session of a terminal device, and the AF request from the AF network element includes a first address; Obtaining a second address corresponding to the first address and an address domain corresponding to the second address; Send an AF request to the unified data repository UDR network element.
2. The method according to claim 1, characterized in that: The first address is a public network address obtained by the second address through network address translation NAT, and the second address is a private network address of the session of the terminal device.
3. The method according to claim 1 or 2, characterized in that: The acquiring the second address corresponding to the first address and the address domain corresponding to the second address includes: Sending first information to a user plane function UPF network element, where the first information includes the first address, the UPF network element is a UPF network element that performs NAT on the second address, and the first information requests the second address and the address domain corresponding to the second address; Receive second information from the UPF network element, where the second information includes the second address and an address field corresponding to the second address.
4. The method according to any one of claims 1 to 3, characterized in that: The address domain corresponding to the second address does not belong to the public land mobile network PLMN to which the first NEF network element belongs.
5. The method according to claim 4, characterized in that The method further comprises: The PLMN that allocates the second address to the session is determined according to the address domain corresponding to the second address.
6. The method according to any one of claims 1 to 5, characterized in that: The AF request sent to the UDR network element includes first target information, and the first target information includes one or more of the following: the first address, the second address, the address domain corresponding to the second address, the user permanent identifier SUPI, the general public user identifier GPSI, the home public land mobile network HPLMN identifier, the data network name DNN, the single network slice selection support information S-NSSAI, the internal group identifier and the external group identifier.
7. The method according to claim 6, characterized in that The AF request from the AF network element does not include the first target information.
8. The method according to claim 6 or 7, characterized in that: The AF request sent to the UDR network element does not include the first address.
9. The method according to any one of claims 6 to 8, characterized in that: The first target information includes one or more of SUPI, GPSI, and internal group identifier, and the method further includes: sending seventh information to a user data management UDM network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier, the seventh information including the second address and / or an address field corresponding to the second address, the seventh information being used to request one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier; receiving one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier from the UDM network element or the BSF network element.
10. A communication method, characterized in that: Applied to a first network open function NEF network element, the method includes: receiving an AF request from an application function AF network element, where the AF request is used to affect a session of a terminal device, where the AF request from the AF network element includes a first identifier, where the first identifier is used to distinguish a public land mobile network PLMN; Send an AF request to the unified data repository UDR network element.
11. The method according to claim 10, characterized in that The first identifier is one of the following: a PLMN identifier, a home public land mobile network HPLMN identifier, or a virtual local area network VLAN identifier.
12. The method according to claim 10 or 11, characterized in that: The AF request sent to the UDR network element includes first target information, and the first target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a HPLMN identifier, a data network name DNN, a single network slice selection support information S-NSSAI, an internal group identifier, an external group identifier and the first identifier.
13. The method according to claim 12, characterized in that The AF request from the AF network element does not include the first target information.
14. The method according to claim 12 or 13, characterized in that The first target information includes one or more of a SUPI, a GPSI, an internal group identifier, and an external group identifier, and the method further includes: sending seventh information to a user data management UDM network element or a BSF network element belonging to the PLMN corresponding to the HPLMN identifier, the seventh information including the second address and / or an address field corresponding to the second address, the seventh information being used to request one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier; Receive one or more of the SUPI, the GPSI, the internal group identifier, and the external group identifier from the UDM or BSF network element.
15. The method according to any one of claims 12 to 14, characterized in that: The first address is a public network address obtained by the second address through network address translation NAT, and the second address is a private network address of the session of the terminal device.
16. A communication method, characterized in that: Applied to a second network open function NEF network element, the method includes: Receive first subscription information sent from a first session management function SMF network element, where the first subscription information is used to request a subscription application function AF request, where the AF request is used to affect a session of a terminal device, where the first subscription information includes second target information, where the second target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, single network slice selection support information S-NSSAI, an internal group identifier, and an external group identifier; Sending second subscription information to a unified data repository UDR network element, where the second subscription information is used to request a subscription to an AF request, and the second subscription information includes the second target information; receiving an AF request from the UDR network element, wherein the AF request from the UDR network element includes second target information; Send an AF request to the first SMF network element.
17. The method according to claim 16, characterized in that The second target information also includes a first identifier, and the first identifier is used to distinguish PLMN.
18. The method according to claim 16 or 17, characterized in that The first identifier is one of the following: a public land mobile network PLMN identifier, a HPLMN identifier, or a virtual local area network VLAN identifier.
19. The method according to any one of claims 16 to 18, characterized in that: The first address is a public network address obtained by the second address through network address translation NAT, and the second address is a private network address of the session of the terminal device.
20. A communication method, characterized in that: Applied to a first session management function SMF network element, the method comprises: Sending first subscription information to a second network open function NEF network element, where the first subscription information includes second target information, where the second target information includes one or more of the following: a first address, a second address, an address domain corresponding to the second address, a user permanent identifier SUPI, a general public user identifier GPSI, a home public land mobile network HPLMN identifier, a data network name DNN, single network slice selection support information S-NSSA, an internal group identifier, and an external group identifier; An application function AF request sent from the second NEF network element is received, where the AF request is used to affect a session of a terminal device, and the AF request from the second NEF network element includes the second target information.
21. The method according to claim 20, characterized in that The second target information further includes a first identifier, where the first identifier is used to distinguish a public land mobile network PLMN.
22. The method according to claim 20 or 21, characterized in that The first identifier is one of the following: a PLMN identifier, a HPLMN identifier, and a virtual local area network VLAN identifier.
23. The method according to any one of claims 20 to 22, characterized in that: When the second target information includes one or more of the SUPI, the GPSI, the HPLMN identifier, the internal group identifier, and the external group identifier; the method further includes: receiving eighth information sent from a second SMF network element or a policy control function PCF network element, wherein the eighth information includes one or more of the SUPI, the GPSI, the HPLMN identifier, the internal group identifier, and the external group identifier.
24. The method according to claim 22, characterized in that The second SMF network element and the first SMF network element do not belong to the same PLMN.
25. The method according to any one of claims 19 to 23, characterized in that: The first address is a public network address obtained by the second address through network address translation NAT, and the second address is a private network address of the session of the terminal device.
26. A communication device, characterized in that: The method comprises a function or a unit for executing the method according to any one of claims 1 to 9, or executing the function or a unit for executing the method according to any one of claims 10 to 15, or executing the function or a unit for executing the method according to any one of claims 16 to 19, or executing the function or a unit for executing the method according to any one of claims 20 to 25.
27. A communication device, characterized in that: The invention comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, wherein the processor is used to implement the method as described in any one of claims 1 to 9 through a logic circuit or by executing code instructions, or the processor is used to implement the method as described in any one of claims 10 to 15 through a logic circuit or by executing code instructions, or the processor is used to implement the method as described in any one of claims 16 to 19 through a logic circuit or by executing code instructions, or the processor is used to implement the method as described in any one of claims 20 to 25 through a logic circuit or by executing code instructions.
28. A computer-readable storage medium, characterized in that: The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, it implements the method as described in any one of claims 1 to 9, or implements the method as described in any one of claims 10 to 15, or implements the method as described in any one of claims 16 to 19, or implements the method as described in any one of claims 20 to 25.
Citation Information
Patent Citations
Communication method and communication device
CN118945766A
Method for influencing data service routing in core network through service application
CN114365518A
Service function chaining services in edge data network and 5g networks
US20230135699A1
