Communication method, device and system
By actively acquiring terminal location information and updating DNS processing rules through L-SMF network elements, the problem of DNS rules not being updated in a timely manner due to terminal movement is solved, ensuring the stability of service transmission and user experience.
Patent Information
- Application Number
- CN202410620092.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-05-17
- Publication Date
- 2025-11-18
AI Technical Summary
In mobile scenarios, L-SMF network elements cannot update DNS processing rules in a timely manner, affecting service transmission and leading to a decline in user experience.
L-SMF network elements obtain the terminal's location information, determine the associated DNS processing rules, and send requests to SMF network elements to update the DNS processing rules. This includes periodic subscription or proactive acquisition of location information based on location changes, reducing signaling overhead and flexibly adjusting the granularity of DNS processing rules.
Ensure that L-SMF network elements can update DNS processing rules in a timely manner when the terminal moves, guaranteeing the normality of service transmission and improving user experience.
Smart Images

Figure CN120980465A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of communication, and particularly relates to a communication method, device and system. BACKGROUND
[0002] In an existing communication system, in order to reduce the deployment pressure of a central network element, a local session management function (L-SMF) network element is proposed, and a local session between a terminal and an edge application server (EAS) is established by the L-SMF network element to realize the normal transmission of terminal services. The L-SMF network element establishes the local session between the terminal and the EAS, including an insertion process of the L-SMF network element.
[0003] In the case that the terminal inserts the L-SMF network element through a domain name system (DNS) query process, the terminal sends a DNS query message including a fully qualified domain name (FQDN) to an edge application server discovery function (EASDF) network element, if no DNS processing rule corresponding to the FQDN is configured on the EASDF network element, the EASDF network element provides a list of corresponding L-SMFs to a session management function (SMF) network element, so that the SMF network element determines a suitable L-SMF network element based on specific rules, and the L-SMF network element determines a suitable user plane function (UPF) network element to serve the FQDN queried by the terminal. In the subsequent insertion of the L-SMF network element, the L-SMF network element perceives the location information of the terminal, and based on the perceived location information of the terminal and the FQDN queried by the terminal, the L-SMF network element configures the DNS processing rule corresponding to the FQDN to the SMF network element and the EASDF network element. After the L-SMF network element, the SMF network element and the EASDF network element complete the configuration of the DNS processing rule, if the terminal performs the DNS query process for the same FQDN, the EASDF network element no longer provides the list of L-SMF network elements to the SMF network element, but selects the L-SMF network element and the UPF network element configured on the processing rule to serve the terminal according to the configured DNS processing rule.
[0004] However, the terminal has mobility, in the scenario that the terminal moves, how the L-SMF network element accurately configures the DNS processing rule to ensure the normal transmission of services provided for the terminal becomes a problem to be solved. SUMMARY
[0005] The embodiment of the application provides a communication method, device and system, in the case that a terminal moves, to ensure that a local session management function L-SMF network element accurately configures a domain name system DNS processing rule, and provides normal transmission of services for the terminal.
[0006] To achieve the above object, the application adopts the following technical solutions:
[0007] In a first aspect, the embodiment of the application provides a communication method, which can be executed by a local session management function (L-SMF) network element and a functional module or chip in the L-SMF network element, and is taken as an example that the L-SMF network element executes, the method comprising: the L-SMF network element acquires location information of a terminal, determines a domain name system (DNS) processing rule associated with the location information of the terminal, and sends a first request comprising the DNS processing rule to a session management function (SMF) network element. The location information of the terminal is used to identify the location of the terminal, and the first request is used to request an update related to the DNS processing rule.
[0008] Based on the method of the first aspect, in the case that the terminal moves, the L-SMF network element can acquire the location information of the terminal, determine the DNS processing rule associated with the location information of the terminal, and send the first request to the SMF network element in the case that the DNS processing rule associated with the location information of the terminal needs to be updated. In this way, the problem that the L-SMF network element only perceives the location information of the UE at the time of insertion, and cannot update the DNS processing rule in time in the subsequent terminal movement scenario, affecting service transmission and reducing user experience, is avoided.
[0009] In a possible design, the L-SMF network element acquires the location information of the terminal from a first network element. The first network element can be an SMF network element or an access and mobility management function (AMF) network element.
[0010] Based on the possible design, the L-SMF network element is provided with multiple ways to acquire the location information of the terminal, so that the L-SMF network element can flexibly acquire the location information of the terminal, and the applicability of the application is improved.
[0011] In a possible design, the L-SMF network element sends a subscription request to the first network element. At this time, the L-SMF network element acquires the location information of the terminal by receiving a response from the first network element, and the response comprises the location information of the terminal. The subscription request is used to subscribe to the location information of the terminal.
[0012] Based on the possible design, the L-SMF network element can actively obtain the location information of the terminal by subscribing to the location information of the terminal. For example, the first network element can periodically send the location information of the terminal to the L-SMF network element, thereby saving the signaling overhead of the L-SMF network element requesting the location information of the terminal.
[0013] In a possible design, the L-SMF network element sends a first message to the first network element. At this time, the L-SMF network element obtains the location information of the terminal, including: receiving the location information of the terminal from the first network element, and the location of the terminal is not within the service range of a user plane function (UPF) network element. Wherein, the first message is used to indicate: if the location of the terminal is not within the service range of the UPF network element connected with the terminal, the L-SMF network element is sent the location information of the terminal; and / or, if the location of the terminal is within the service range of the UPF network element connected with the terminal, the L-SMF network element is not sent the location information of the terminal.
[0014] Based on the possible design, the L-SMF network element can flexibly achieve the purpose of obtaining the location information of the terminal in the case of change of the location information of the terminal through the first message sent to the first network element, so that the L-SMF network element can subsequently determine the DNS processing rule related to the location of the terminal according to the location information of the terminal. For example, if the first message indicates that the location of the terminal is not within the service range of the UPF network element connected with the terminal, the first network element sends the location information of the terminal to the L-SMF network element, at this time, the location of the terminal is not within the service range of the UPF network element connected with the terminal, which is an implicit indication that the location information of the terminal has changed.
[0015] In a possible design, the first message includes the service range of the UPF network element connected with the terminal. Based on the possible design, so that the first network element can determine whether to send the location information of the terminal to the L-SMF network element according to the location information of the terminal and the service range of the UPF network element connected with the terminal, and achieve the purpose of the L-SMF network element obtaining the location information of the terminal.
[0016] In a possible design, the L-SMF network element receives a context establishment request from an SMF network element. Wherein, the context establishment request includes the location information of the terminal; and the context establishment request is used to request to establish the context of the terminal. For example, the context establishment request is a terminal context establishment request.
[0017] Based on the possible design, the L-SMF network element can obtain the location information of the terminal through the context establishment request in the case that the terminal requests to establish the context of the terminal, thereby saving the signaling overhead of the L-SMF network element requesting the location information of the terminal.
[0018] In a possible design, the L-SMF network element sends, to the SMF network element, DNS processing rules corresponding to all FQDNs supported by the L-SMF network element; and the first request is used to request an update related to the DNS processing rules. The update related to the DNS processing rules includes updating all DNS processing rules associated with the location information of the terminal.
[0019] Based on this possible design, the update granularity of the DNS processing rules is changed from the granularity of a single FQDN to the DNS processing rules corresponding to all FQDNs supported by the L-SMF network element, which avoids the problem of the EASDF network element repeatedly providing a list of L-SMF network elements to the SMF network element and reduces signaling overhead.
[0020] In a possible design, the L-SMF network element sends, to the SMF network element, the first request including the DNS processing rules, including: determining, by table lookup, that the EAS corresponding to the UE changes, or in a case where the distance between the terminal and an edge application server (EAS) is greater than a distance threshold, the L-SMF network element sends, to the SMF network element, the first request including the DNS processing rules. The EAS is used to provide services corresponding to all FQDNs supported by the L-SMF network element.
[0021] Based on this possible design, the L-SMF network element can determine whether to send the first request to the SMF network element according to the table lookup result or the distance between the terminal and the EAS, so that the L-SMF network element can flexibly send the first request to the SMF network element.
[0022] In a possible design, the DNS processing rules include an EDNS client subnet option (ECS option), and the ECS option is used to indicate the location information of the terminal.
[0023] Based on this possible design, the L-SMF network element synchronously updates the ECS option in a case where the DNS processing rules associated with the location information of the terminal are updated.
[0024] In a possible design, the L-SMF network element supports one or more FQDNs; and each FQDN in the one or more FQDNs corresponds to different DNS processing rules.
[0025] Based on this possible design, the L-SMF network element can implement sending the DNS processing rules corresponding to all FQDNs supported by the L-SMF network element, and each FQDN corresponds to different DNS processing rules, so that there is a one-to-one correspondence between the FQDN and the DNS processing rules.
[0026] In a second aspect, an embodiment of the present application provides a communication method, which can be executed by an SMF network element and a functional module or a chip in the SMF network element. Taking the execution by the SMF network element as an example, the method comprises: the SMF network element receives a first request from an L-SMF network element, and in response to the first request, sends a second request to an edge application server discovery function (EASDF) network element. The first request comprises a new DNS processing rule associated with terminal location information, and the first request is used to request an update related to the new DNS processing rule. The second request comprises the new DNS processing rule associated with the terminal location information, and the second request is used to request the update related to the new DNS processing rule. The EASDF is used to process a DNS request of the terminal.
[0027] Based on the possible design, the SMF network element receives the new DNS processing rule associated with the terminal location information, so that the SMF network element sends the second request to the EASDF network element, so that the EASDF network element can update the DNS processing rule associated with the terminal location information, and ensure that the subsequent SMF network element and the EASDF network element can correctly process the DNS processing rule operation associated with the terminal location information, and realize normal access of the terminal service.
[0028] In a possible design, the SMF network element obtains the location information of the terminal, and sends the location information of the terminal to the L-SMF network element according to the subscription of the L-SMF network element on the terminal location information. The location information of the terminal is used to identify the location where the terminal is located.
[0029] Based on the possible design, the L-SMF network element can actively obtain the location information of the terminal by subscribing to the location information of the terminal. For example, the SMF network element can periodically send the location information of the terminal to the L-SMF network element, thereby saving the signaling overhead of the L-SMF network element requesting the location information of the terminal.
[0030] In a possible design, the SMF network element receives a first message from the L-SMF network element, the first message is used to indicate: if the location of the terminal is not within the service range of the UPF network element connected with the terminal, the SMF network element sends the location information of the terminal to the L-SMF network element; and / or, if the location of the terminal is within the service range of the UPF network element connected with the terminal, the SMF network element does not send the location information of the terminal to the L-SMF network element; and the SMF network element sends the location information of the terminal to the L-SMF network element in the case that the location of the terminal is not within the service range of the UPF network element connected with the terminal.
[0031] Based on the possible design, the SMF network element can flexibly implement, through the first message from the L-SMF network element, sending the location information of the terminal to the L-SMF network element in the case of change of the location information of the terminal, so that the L-SMF network element can subsequently determine the DNS processing rule related to the location of the terminal according to the location information of the terminal. For example, in the case that the first message indicates that the location of the terminal is not within the service range of the UPF network element connected with the terminal, the SMF network element sends the location information of the terminal to the L-SMF network element, at this time, the location of the terminal not within the service range of the UPF network element connected with the terminal belongs to the implicit indication that the location information of the terminal has changed.
[0032] In a possible design, the SMF network element receives the information of the L-SMF network element from the EASDF network element; and sends a context establishment request to the L-SMF network element, the context establishment request including the location information of the terminal.
[0033] Based on the possible design, the L-SMF network element can obtain the location information of the terminal through the context establishment request in the case that the terminal requests to establish the context of the terminal, thereby saving the signaling overhead of the L-SMF network element requesting the location information of the terminal.
[0034] In a possible design, the SMF network element receives all DNS processing rules corresponding to the FQDNs supported by the L-SMF network element from the L-SMF network element; and the first request is used to request an update related to the DNS processing rule, and the update related to the DNS processing rule includes updating all DNS processing rules associated with the location information of the terminal.
[0035] Based on the possible design, the update granularity of the DNS processing rule is changed from the single FQDN granularity to the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element, thereby avoiding the EASDF network element repeatedly providing the L-SMF network element list to the SMF network element, and reducing the problem of large signaling overhead.
[0036] In a possible design, the L-SMF network element supports one or more FQDNs; and each FQDN in the one or more FQDNs corresponds to a different DNS processing rule.
[0037] Based on the possible design, the L-SMF network element can implement sending the DNS processing rule corresponding to all supported FQDNs, and each FQDN corresponds to a different DNS processing rule, so that there is a one-to-one correspondence between the FQDN and the DNS processing rule.
[0038] In a possible design, the first request further includes information of the SMF network element, and the information of the SMF network element is used to identify the SMF network element. The second request further includes information of the EASDF network element, and the information of the EASDF network element is used to identify the EASDF network element. For example, the information of the SMF network element can be an identifier of the SMF network element or address information of the SMF network element; and the information of the EASDF network element can be an identifier of the EASDF network element or address information of the EASDF network element.
[0039] Based on this possible design, the L-SMF network element can accurately send the first request to the SMF network element that manages the L-SMF network element according to the information of the SMF network element in the first request. Meanwhile, the SMF network element can accurately send the second request to the EASDF network element that serves the L-SMF network element according to the information of the EASDF network element in the second request after receiving the first request.
[0040] In a possible design, the DNS processing rule includes an EDNS client subnet option ECS option, and the ECS option is used to indicate location information of the terminal.
[0041] Based on this possible design, the L-SMF network element can synchronously update the ECS option when updating the DNS processing rule associated with the location information of the terminal.
[0042] In a possible design, the first request and the second request include new information in the new DNS processing rule associated with the location information of the terminal. The new information can be information in the new DNS processing rule associated with the location information of the terminal, for example, the ECS option.
[0043] Based on this possible design, the SMF network element receives the new information in the new DNS processing rule associated with the location information of the terminal, so as to send the second request to the EASDF network element, to enable the EASDF network element to update the DNS processing rule associated with the location information of the terminal, to ensure that the SMF network element and the EASDF network element can correctly process the DNS processing rule operation associated with the location information of the terminal, and to enable the terminal service to be normally accessed.
[0044] In a third aspect, a communication apparatus is provided. The communication apparatus can be the L-SMF network element, or a chip or system on chip in the L-SMF network element, or a functional module for implementing the method in the first aspect or any possible design of the first aspect. The communication apparatus can implement the functions of the L-SMF network element in the first aspect or any possible design of the first aspect. The functions can be implemented by hardware or software. The hardware or software includes one or more modules corresponding to the functions. For example, the communication apparatus can include a transceiver unit and a processing unit.
[0045] a transceiver unit, configured to obtain location information of the terminal; the location information of the terminal is used to identify a location where the terminal is located;
[0046] a processing unit, configured to determine a DNS processing rule associated with the location information of the terminal;
[0047] The transceiver unit is further configured to send a first request including the DNS processing rule to an SMF network element; the first request is used to request an update related to the DNS processing rule.
[0048] Specifically, the execution actions of each unit of the communication apparatus can refer to those described in the first aspect or any possible design of the first aspect, and will not be repeated here.
[0049] In a fourth aspect, the present application provides a communication apparatus, which can be an SMF network element or a chip or system on chip in the SMF network element, and can also be a functional module in the SMF network element for implementing the method in the second aspect or any possible design of the second aspect. The communication apparatus can implement the functions performed by the SMF network element in the second aspect or any possible design of the second aspect, and the functions can be implemented by executing corresponding software through hardware. The hardware or software includes one or more modules corresponding to the above functions. For example, the communication apparatus can include a transceiver unit and a processing unit.
[0050] a transceiver unit, configured to receive a first request from an L-SMF network element, wherein the first request includes a new DNS processing rule associated with the location information of the terminal; the first request is used to request an update related to the new DNS processing rule;
[0051] a processing unit, configured to send a second request to an EASDF network element in response to the first request; the second request includes the new DNS processing rule associated with the location information of the terminal; the second request is used to request an update related to the new DNS processing rule; the EASDF is used to process a DNS request of the terminal.
[0052] Specifically, the execution actions of each unit of the communication apparatus can refer to those described in the second aspect or any possible design of the second aspect, and will not be repeated here.
[0053] In a fifth aspect, the present application provides a communication apparatus. In a possible design of the communication apparatus, the communication apparatus includes a processor and a communication interface. The processor and the communication interface are configured to support the communication apparatus to perform the communication method in the first aspect or any possible design of the first aspect, or the processor and the communication interface are configured to support the communication apparatus to perform the communication method in the second aspect or any possible design of the second aspect. In another possible design of the communication apparatus, the communication apparatus further includes a memory. The memory is configured to store computer-executed instructions and data necessary for the communication apparatus. When the communication apparatus is running, the processor executes the computer-executed instructions stored in the memory, so that the communication apparatus performs the communication method in the first aspect or any possible design of the first aspect, or the communication apparatus performs the communication method in the second aspect or any possible design of the second aspect.
[0054] In a sixth aspect, the present application provides a communication system. The communication system includes the communication apparatus in the third aspect and the communication apparatus in the fourth aspect.
[0055] In a seventh aspect, the present application provides a computer-readable storage medium. The computer-readable storage medium stores computer instructions. When the computer instructions are run on a computer, the computer instructions cause the computer to perform the communication method in the first aspect or any possible design of the first aspect, or cause the computer to perform the communication method in the second aspect or any possible design of the second aspect.
[0056] In an eighth aspect, the present application provides a computer program product. The computer program product includes computer instructions. When the computer instructions are run on a computer, the computer instructions cause the computer to perform the communication method in the first aspect or any possible design of the first aspect, or cause the computer to perform the communication method in the second aspect or any possible design of the second aspect. BRIEF DESCRIPTION OF DRAWINGS
[0057] Figure 1 Architecture diagram of 5GS;
[0058] Figure 2 Architecture diagram of 5GS with L-SMF network element deployed;
[0059] Figure 3 Flow insertion diagram of L-SMF network element;
[0060] Figure 4 Flow diagram of the communication method provided by the embodiments of the present application Figure 1 ;
[0061] Figure 5 Flow diagram of the communication method provided by the embodiments of the present application Figure 2 ;
[0062] Figure 6 Flowchart of the communication method provided by the embodiment of the present application Figure 3 ;
[0063] Figure 7 Flowchart of the communication method provided by the embodiment of the present application Figure 4 ;
[0064] Figure 8 Structure diagram of the communication device provided by the embodiment of the present application Figure 1 ;
[0065] Figure 9 Structure diagram of the communication device provided by the embodiment of the present application Figure 2 . DETAILED DESCRIPTION
[0066] For the convenience of understanding, the technical terms involved in the embodiments of the present application are introduced first.
[0067] 1. Fifth generation (5th generation, 5G) mobile communication system (referred to as 5G system (5G system, 5GS)):
[0068] Figure 1 The architecture diagram of the 5GS is shown in FIG. 1. As shown in FIG. 1, the 5GS includes an access network (access network, AN) and a core network (core network, CN), and can also include a terminal and a data network (data network, DN). Figure 1
[0069] The terminal can be a terminal with transceiver function, or a chip or chip system that can be provided in the terminal. The terminal can also be referred to as user equipment (UE), access terminal, subscriber unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal in the embodiments of the present application can be a mobile phone, a cellular phone, a smart phone, a Pad, a wireless data card, a personal digital assistant computer (PDA), a wireless modem, a handset, a laptop computer, a machine type communication (MTC) terminal, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in remote medical treatment, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, a vehicle-mounted terminal, a road side unit (RSU) with terminal function, etc. The terminal in the present application can also be a vehicle-mounted module, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit built in a vehicle as one or more components or units.
[0070] The AN is used to implement access-related functions, can provide network access functions for authorized users, and can determine transmission links of different qualities to transmit user data according to the level of the user, the demand of the service, etc. The AN forwards control signals and user data between the terminal and the CN. The AN can include an access network device, which can also be referred to as a radio access network (RAN) device.
[0071] CN is mainly responsible for maintaining the subscription data of the mobile network, and provides the terminal with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes all or part of the following functional network elements: a user plane function (UPF) network element, an authentication server function (AUSF) network element, an access and mobility management function (AMF) network element, a session management function (SMF) network element, a network slice selection function (NSSF) network element, a network exposure function (NEF) network element, a network repository function (NRF) network element, a policy control function (PCF) network element, a unified data management (UDM) network element, and an application function (AF) network element. Optionally, the CN can also include a unified data repository (UDR) network element (not shown in the figure) and other network elements, which are not limited.
[0072] As shown in Figure 1 , the UE accesses the 5G network through the RAN device, the UE communicates with the AMF network element through the N1 interface (referred to as N1), the RAN communicates with the AMF network element through the N2 interface (referred to as N2), the RAN communicates with the UPF through the N3 interface (referred to as N3), the SMF network element communicates with the UPF network element through the N4 interface (referred to as N4), and the UPF network element accesses the DN through the N6 interface (referred to as N6). In addition, Figure 1The illustrated AUSF network element, AMF network element, SMF network element, NSSF network element, NEF network element, NRF network element, PCF network element, UDM network element, UDR network element, or AF network element and other control plane function network elements adopt a service interface for interaction. For example, the service interface provided by the AUSF network element to the outside is Nausf; the service interface provided by the AMF network element to the outside is Namf; the service interface provided by the SMF network element to the outside is Nsmf; the service interface provided by the NSSF network element to the outside is Nnssf; the service interface provided by the NEF network element to the outside is Nnef; the service interface provided by the NRF network element to the outside is Nnrf; the service interface provided by the PCF network element to the outside is Npcf; the service interface provided by the UDM network element to the outside is Nudm; and the service interface provided by the AF network element to the outside is Naf.
[0073] The RAN device can be a device providing access for a terminal. For example, the RAN device can include an access network device of a next-generation mobile communication system, such as a 6G base station, or in a next-generation mobile communication system, the network device can also have other naming ways, which are all included in the protection scope of the embodiments of the present application, and the present application does not make any limitation on this. Or, the RAN device can also include a gNB in a 5G, such as a new radio (NR) system, or one or a group (including multiple antenna panels) of antenna panels of a base station in 5G, or a network node constituting a gNB, a transmission and reception point (TRP or transmission point, TP) or a transmission measurement function (TMF), such as a building base band unit (BBU), or a centralized unit (CU) or a distributed unit (DU), an RSU with base station function, or a wired access gateway, or a core network of 5G. Or, the RAN device can also include an access point (AP) in a wireless fidelity (WiFi) system, a wireless relay node, a wireless backhaul node, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted devices, and the like.
[0074] UPF network element: mainly responsible for user data processing (forwarding, receiving, charging, etc.). For example, the UPF network element can receive user data from a data network (DN), and forward the user data to the terminal through the access network device. The UPF network element can also receive user data from the terminal through the access network device, and forward the user data to the DN.
[0075] The DN refers to an operator network that provides data transmission services for users. For example, an internet protocol (IP) multi-media service (IMS), an internet, etc. The DN can be an operator external network or an operator controlled network, and is used to provide service services to terminals. In a protocol data unit (PDU) session, the UPF directly connected to the DN through N6 is also called a protocol data unit session anchor (PSA). The DN can include an application server (AS).
[0076] AUSF network element: mainly used for performing security authentication of the terminal.
[0077] AMF network element: mainly used for mobility management in a mobile network. For example, user location update, user registration network, user handover, etc.
[0078] SMF network element: mainly used for session management in a mobile network. For example, session establishment, modification, release. Specific functions, such as allocating an internet protocol (IP) address for a user, selecting a UPF that provides packet forwarding functions, etc.
[0079] PCF network element: mainly supports providing a unified policy framework to control network behavior, provides policy rules to control layer network functions, and is responsible for obtaining user subscription information related to policy decision. The PCF can provide policies such as quality of service (QoS) policies and slice selection policies to AMF and SMF network elements.
[0080] NSSF network element: mainly used for selecting network slices for terminals.
[0081] NEF network element: mainly used for supporting the opening of capabilities and events.
[0082] UDM network element: mainly used for storing user data, such as subscription data, authentication / authorization data, etc.
[0083] AF network element: mainly supports interaction with the CN to provide services, such as affecting data routing decisions, policy control functions, or providing some services of third parties to the network side.
[0084] It can be understood that the functions mentioned in the embodiments of the present application can also be expressed as function network elements or function entities, for example, the UPF network element can be expressed as UPF, the AMF network element can be expressed as AMF, the SMF network element can be expressed as SMF, the PCF network element can be expressed as PCF, and so on. By analogy, no limitation is made.
[0085] 2, local SMF (local SMF, L-SMF) network element:
[0086] The L-SMF network element is a newly introduced network element in R19. The introduction of the L-SMF network element is mainly to solve the local connection problem of PSA.
[0087] For example, R19 MEC WT#1 proposes to reduce the impact of local deployment on the central SMF network element (such as the SMF network element in the CN center in the above Figure 2 ), that is, the central SMF network element does not have local edge application server (EAS) deployment information (EAS deployment information, EDI), and when there is no target PSA in the jurisdiction of the central SMF network element, the L-SMF network element may be needed to help connect the target PSA. Among them, different from the insertion of the intermediate SMF network element (intermediate session management function, I-SMF) network element, one SMF network element can connect multiple L-SMF network elements, and the selection of the L-SMF network element does not depend on the AMF network element. The selection of the L-SMF network element can be determined by the SMF network element or a network element other than the SMF network element. Optionally, there can be no direct interface between the L-SMF network elements, at this time, the SMF network element manages the ULCL / BP network element, and the L-SMF network element is responsible for managing the local PSA (L-PSA) network element.
[0088] Figure 1 The 5GS architecture diagram for deployment with L-SMF network elements, compared with the network elements shown in Figure 2 , the L-SMF network element is added. Figure 3A new core network element deployed in the center is added: an edge application server discovery function (EASDF) network element, a local core network (Local 5GC) network element: an L-SMF network element, a UPF (or referred to as L-UPF or L-PSA) network element, and an EAS. Among them, the L-SMF network element is connected with the SMF network element located in the center through the N16b interface, and is connected with the EASDF through the N88a, the L-SMF network element manages the L-UPF, the L-SMF network element is connected with the L-UPF network element through the N4 interface, the L-UPF network element communicates with the access network device through the UPF (or referred to as UL CL / BP) network element deployed in the center, and accesses the EAS through the N6.
[0089] The EASDF network element is mainly responsible for discovering the EAS.
[0090] The L-SMF network element is mainly responsible for processing tasks related to the local session, such as managing the local data path, performing operations such as creation, modification and deletion of the local session, selecting / managing the L-UPF network element, etc.
[0091] The L-UPF network element is mainly responsible for local user data processing (forwarding, receiving, charging, etc.). For example, the L-UPF network element can receive user data from the EAS and forward the user data to the terminal through the UL CL / BP network element and the access network device. The L-UPF network element can also receive user data from the terminal through the access network device and the UL CL / BP network element, and forward the user data to the EAS.
[0092] 3. Domain name system (DNS) query:
[0093] In an edge computing (EC) deployment scenario, some business services may be provided by multiple edge application servers (EASs) deployed at the edge of the network. These EASs can provide the same business services and content, but have different internet protocol (IP) addresses. When a terminal (or can be referred to as user equipment (UE)) needs to access a certain service, the UE needs to initiate a DNS query to obtain the address information (such as the IP address of the EAS) of the EAS closest to the UE before accessing the EAS, and based on the address information of the EAS, the L-SMF network element is inserted and a local session is established, and the EAS is accessed through the local session, so that the EAS provides services for the UE through the local session.
[0094] As described above, the 3GPP standard TS23.548 defines a new network element EASDF for assisting EAS discovery, so that the address information of the EAS can be queried through the EASDF and fed back to the UE. For example: the EASDF can receive a DNS query message, add an EDNS client subnet option (ECS option) in the DNS query message, forward the DNS query message with the added ECS option to the DNS server, so that the DNS server obtains the address information of the EAS based on the ECS option, and forwards the address information of the EAS in the DNS response to the UE.
[0095] Among them, the ECS option is an extension item in the DNS query message, and the ECS option can be understood as an IP address, which is used to reflect the location information of the UE in the DNS query. The EASDF can add the ECS option in the DNS query message and send the DSN query message with the added ECS option to the DNS server, so that the DNS server selects a server closer to the UE based on the ECS option, and feeds back the address information of the server closer to the UE.
[0096] Optionally, the ECS option can be determined according to the FQDN, EAS deployment information and UE location information.
[0097] For example, for a service, both server #1 and server #2 can provide services, at this time if UE1 wants to access the service, the UE can send a DNS query message carrying the fully qualified domain name (FQDN) corresponding to the service to the EASDF, the EASDF receives the DNS query message, can obtain the ECS option corresponding to the FQDN based on the configuration, and sends the DNS query message with the added ECS option to the DNS server, the DNS server determines the server #1 closest to the ECS option indicated by the address based on the FQDN carried in the DNS query message and the ECS option, and the server #1 is the server closest to the UE1, the address information of the server #1 (such as the IP address of the server #1) is fed back to the UE1, so that the UE1 accesses the server #1 to obtain the service provided by the server #1 for the service.
[0098] 4. L-SMF network element insertion process:
[0099] The L-SMF network element insertion process can be performed / implemented in the DNS query process, specifically, Figure 3 The L-SMF network element insertion process is shown in the schematic diagram as shown in Figure 3 The insertion process of the L-SMF network element can include:
[0100] S101. The L-SMF network element configures BaselineDNSPattern on the EASDF network element.
[0101] The BaselineDNSPattern configured by the L-SMF network element on the EASDF network element can include but is not limited to EAS deployment information. The EAS deployment information can be used to indicate the deployment information of the EAS within the management range of the L-SMF network element, such as: the EAS within the management range of the L-SMF network element, the service supported by the EAS, the location information of the EAS, the address information of the EAS, etc. For example, the EAS deployment information can include the mapping relationship between the service and the EAS, which can be used to represent the service that the EAS can provide, so as to query the EAS providing the service based on the mapping relationship, and the service can be identified by a data network access identifier (DANI).
[0102] Specifically, the execution process of S101 can refer to the description in section 6.3.3.1 of 3GPP protocol standard TS23.548, which will not be repeated here.
[0103] S102. The SMF network element configures BaselineDNSPattern on the EASDF network element.
[0104] The BaselineDNSPattern configured by the SMF network element on the EASDF can include but is not limited to the IP address of the UE (UE IP address) within the jurisdiction of the SMF network element, the data network name (DNN), the notification endpoint, and the DNS message handling rules.
[0105] The IP address of the UE is used to identify the UE. The DNN is used to indicate the network where the server accessed by the UE is located.
[0106] The notification endpoint can refer to the address of the SMF network element.
[0107] The DNS information processing rule can also be replaced by a DNS handling rule. For ease of description, the DNS handling rule is taken as an example in the present application, and the DNS handling rule is determined according to the EAS deployment information. The DNS handling rule can be used to specify the specific action of the EASDF network element when facing a DNS query. For example, the DNS handling rule corresponds to the FQDN, and when facing a DNS query of a UE, the EASDF network element can find the corresponding DNS handling rule based on the FQDN carried in the DNS query message, and then directly select a suitable L-SMF network element to serve the UE. If there is no corresponding DNS handling rule configured for the DNS query of the UE, that is, there is no DNS handling rule corresponding to the FQDN carried in the DNS query, the EASDF network element can provide a list of L-SMFs (or candidate L-SMFs) supporting the UE for the SMF network element to select a suitable L-SMF network element.
[0108] Optionally, the DNS handling rule can include, but is not limited to, an L-SMF network element corresponding to the FQDN, an EAS, an ECS option, and the like.
[0109] In the present application, the process in which the EASDF network element provides a list of L-SMF network elements can refer to the prior art, and will not be described here.
[0110] S102 can also be referred to as a DNS context establishment process, and the execution process of the process can refer to the description in section 6.2.3.2 of TS23.548 of the 3GPP protocol standard, which will not be described here.
[0111] It should be understood that S101 and S102 can be configuration processes, which are pre-processes for executing the following steps.
[0112] S103. Optionally, in response to the location of the UE moving, the SMF network element triggers an update process of the DNS context.
[0113] The DNS context includes, but is not limited to, the DNS handling rule, so the update process of the DNS context includes the update of the DNS handling rule. The trigger of this step can be that the original DNS handling rule configured by the SMF network element to the EASDF network element in S102 is updated, such as updating the relationship between the FQDN and the DNS handling rule.
[0114] For example, in a scenario where the UE moves from position 1 to position 2, the original EAS that provides service 1 for the UE no longer supports the optimal service for providing service 1 for the UE due to the distance from the UE being too far, and at this time, EAS 2 close to the UE is needed to provide service 1. The DNS processing rule corresponding to the FQDN in the original DNS context does not support selecting a suitable L-SMF network element, and at this time, the original DNS context needs to be updated.
[0115] Specifically, the execution process of the flow can refer to the description in section 6.2.3.2 of 3GPP protocol standard TS23.548, which will not be repeated here.
[0116] S104. The UE sends a DNS query message to the EASDF network element.
[0117] The DNS query message can be used to query the address information of the EAS that provides service for the UE.
[0118] Optionally, the DNS query message can include the FQDN and the address information of the UE, and the address information of the UE can be the IP address of the UE.
[0119] S105. The EASDF network element receives the DNS query message and sends a notification message to the SMF network element.
[0120] Optionally, the EASDF network element can determine whether there is a DNS processing rule matching the FQDN carried by the DNS query message based on the BaselineDNSPattern configured by the SMF network element in S102, and if not, S105 is executed.
[0121] The notification message is used to notify the SMF network element of the matching of the DNS processing rule and the list of L-SMF network elements supporting the service. The notification message can carry the FQDN and the address information of the UE.
[0122] It should be understood that if the DNS handling rule is configured, steps S105-S110 are not triggered.
[0123] S106. The SMF network element returns a response message corresponding to the notification message to the EASDF network element.
[0124] S107. The SMF network element determines the L-SMF network element.
[0125] Specifically, the SMF network element determines the L-SMF network element based on the location information of the UE and the information of the L-SMF network element.
[0126] Optionally, the SMF network element can select an L-SMF network element that is closer to the UE and has smaller latency and / or load from the L-SMF network elements in its management range, and determine the L-SMF network element as the selected L-SMF network element.
[0127] S108. The SMF network element sends a query message to the L-SMF network element.
[0128] The query message can be used to query the ECS option corresponding to the UE or obtain information of the local DNS server.
[0129] S109. The L-SMF receives the query message and returns a response message corresponding to the query message to the SMF network element.
[0130] The response message corresponding to the query message can carry the ECS option corresponding to the UE, or the response message corresponding to the query message carries the information of the local DNS server. The local DNS server queries the EAS server that is closer to it by default. In addition to the local DNS server, the DNS server needs the ECS option to indicate the location of the UE, so as to determine the EAS server according to the location of the UE.
[0131] S110. The SMF network element performs a DNS context update process.
[0132] The DNS context update process performed by the SMF network element can include updating the ECS option in the DNS processing rule configured to the EASDF network element. For example, the ECS option obtained by querying can be added to the DNS processing rule corresponding to the FQDN.
[0133] Specifically, the execution process of the process can refer to the description in section 6.2.3.2.2-1 of the 3GPP protocol standard TS23.548, which is not repeated here.
[0134] S111. The EASDF network element initiates a query process to the DNS server and receives a DNS query result from the DNS server.
[0135] For example, the EASDF network element queries the DNS processing rule corresponding to the FQDN based on the BaselineDNSPattern configured by the SMF network element, obtains the ECS option from the DNS processing rule, adds the ECS option in the DNS query message, forwards the DNS query message with the added ECS option to the DNS server, so that the DNS server obtains the address information of the EAS closest to the UE based on the ECS option and the FQDN, and returns the address information of the EAS in the DNS query result to the EASDF network element.
[0136] Optionally, the address information of the EAS can include, but is not limited to, an IP address of the EAS.
[0137] S112. The EASDF network element sends the DNS query result and the candidate L-SMF network element information to the SMF network element.
[0138] Optionally, the candidate L-SMF network element information can be used to indicate the candidate L-SMF network element, such as an identifier of the candidate L-SMF network element.
[0139] The candidate L-SMF network element can be an L-SMF network element with the function of managing the EAS, and the candidate L-SMF network element can be obtained by the EASDF network element according to the BaselineDNSPattern configured in S101. For example, the EASDF network element can determine the L-SMF network element that manages the EAS according to the address information of the EAS queried.
[0140] S113. The SMF network element receives the DNS query result and the candidate L-SMF network element information, and returns a response message to the EASDF network element.
[0141] S114. The SMF network element determines an L-SMF network element (which can be referred to as a target L-SMF network element).
[0142] The SMF network element can determine the L-SMF network element based on the location of the UE and the information of the candidate L-SMF.
[0143] It should be understood that the L-SMF determined in S114 can be referred to as a target L-SMF, and the L-SMF determined in this step is different from the L-SMF selected in S107. The L-SMF determined in S114 can be the same as or different from the L-SMF selected in S107, and is not limited. The L-SMF network element determined in S114 can be inserted into the session and establish a connection with the SMF network element. The L-SMF determined in S114 can establish a local session between the UE and the EAS.
[0144] S115. The SMF network element sends a context establishment request to the determined L-SMF network element.
[0145] The context establishment request can be Nsmf_PDUSession_CreateSMContext Request. The context establishment request can be used to instruct the L-SMF network element to establish UE context information. The UE context information can be referred to as UE context or UE context.
[0146] It should be understood that S115 is a local control plane session establishment, and the specific details are referred to the existing standard, which is not described here.
[0147] S116. The L-SMF network element determines a suitable L-UPF network element.
[0148] The L-SMF network element determining a suitable L-UPF network element can include that the L-SMF network element determines a suitable L-UPF network element based on a DNS query result. For example, a UPF with a shorter distance to the EAS and / or a smaller load can be selected as the determined L-UPF network element.
[0149] S117. The L-SMF network element returns a response message to the SMF network element.
[0150] The returned response message can carry information of the L-UPF network element determined in S116.
[0151] The information of the L-UPF network element can be an IP address of the L-UPF network element.
[0152] S118. The SMF network element inserts an ULCL / BP network element.
[0153] The SMF network element inserts an ULCL / BP network element corresponding to the L-UPF network element determined by the L-SMF network element, so that the SMF network element can establish a connection with the ULCL / BP network element.
[0154] S119. The SMF network element establishes a tunnel of the L-UPF network element.
[0155] It should be understood that S118 and S119 are optional steps. In the case that a connection can be directly established between the L-UPF network element and the access network device, S118 and S119 can not be performed, that is, the L-UPF network element does not need to communicate with the access network device through the UL CL / BP.
[0156] It should be understood that S116-S119 are a local user plane session establishment process, and specific details refer to standards and will not be described here.
[0157] S120. A DNS context update process is performed.
[0158] For example, the SMF network element can configure a corresponding DNS processing rule for the EAS DF network element based on the determined L-SMF network element, such as saving the correspondence between the FQDN and the DNS processing rule. The DNS processing rule information includes the information of the L-SMF network element and the address information of the EAS. Subsequently, if a UE requests the same FQDN, the EAS DF network element can directly select the L-SMF network element and the EAS based on the DNS processing rule corresponding to the FQDN.
[0159] S121. The EAS DF network element sends a DNS response to the UE.
[0160] The address information of the EAS is included in the DNS response, so as to tell the UE the EAS providing service for the UE, so that the UE accesses the EAS according to the address information of the EAS through a local session and accepts the service provided by the EAS.
[0161] From Figure 4 As shown in the flow, the configuration of the DNS processing rule is mainly based on the FQDN in the DNS query message, that is, in the process of querying the corresponding FQDN by the UE, the corresponding DNS processing rule is configured based on the specific FQDN. If the UE queries FQDN#2 in the subsequent process, the previously inserted L-SMF network element supports the FQDN, but since the DNS processing rule corresponding to the FQDN is not configured, the determination process of the L-SMF network element needs to be triggered repeatedly, and the DNS processing rule corresponding to the FQDN is configured after the L-SMF network element is determined, which has large signaling overhead. In addition, in the updating process of the DNS processing rule, the prior art only considers the insertion of the L-SMF network element, such as step S115, the L-SMF network element can perceive the location of the UE, and after the insertion of the L-SMF network element is completed, the L-SMF network element cannot perceive the location information of the subsequent UE. If the UE moves out of a specific area, the previously determined EAS may not be the optimal EAS, and the DNS processing rule may need to be updated to determine a more suitable EAS through the updating of the ECS option. However, the prior art does not consider this problem, which may cause the EAS to be not the optimal EAS in the scenario where the UE moves, thereby affecting the service transmission and reducing the user experience.
[0162] To solve the above problems, in the present application, Figure 1 The flow of the communication method provided by the embodiment of the present application is shown in Figure 4 , Figure 5 The communication method shown in the embodiment of the present application comprises:
[0163] S401. The L-SMF network element acquires the location information of the UE.
[0164] In the present application, the L-SMF network element supports one or more FQDNs; each FQDN in the one or more FQDNs corresponds to a different DNS processing rule.
[0165] The L-SMF network element acquires the location information of the UE, which can include that the L-SMF network element acquires the location information of the UE from a first network element. The first network element can be a network element providing the L-SMF network element with the location information of the UE, such as an SMF network element or an AMF network element, which is not limited.
[0166] In an example, the L-SMF network element obtaining the location information of the UE can comprise: the L-SMF network element sending a subscription request to the first network element, and receiving a response from the first network element, the response comprising the location information of the UE. The subscription request is used to subscribe to the location information of the terminal. For specific implementation, refer to the following Figure 6 The method shown.
[0167] In another example, the L-SMF network element obtaining the location information of the UE can comprise: the L-SMF network element sending a first message to the first network element, and receiving the location information of the UE from the first network element, the location of the UE not being within the service range of the UPF network element connected with the UE. The first message comprises the service range of the UPF network element connected with the UE; the first message can be used to indicate: if the location of the UE is not within the service range of the UPF network element connected with the UE, the location information of the UE is sent to the L-SMF network element; and / or, if the location of the UE is within the service range of the UPF network element connected with the UE, the location information of the UE is not sent to the L-SMF network element. For specific implementation, refer to the following Figure 7 The method shown.
[0168] In another example, the L-SMF network element obtaining the location information of the UE can comprise: the L-SMF network element receiving a context establishment request from the SMF network element, the context establishment request comprising the location information of the UE. The context establishment request is used to request to establish the context of the UE. For example, the context establishment request can be a UE context establishment request. For specific implementation, refer to the following Figure 4 The method shown.
[0169] S402. The L-SMF network element determines a DNS processing rule associated with the location information of the UE.
[0170] The DNS processing rule can comprise an ECS option, the ECS option being used to indicate the location information of the UE.
[0171] The L-SMF network element determining the DNS processing rule associated with the location information of the UE can refer to the SMF network element determining the corresponding DNS processing rule according to the location information of the UE in section 6.2.3.2.2 of TS23.548, which is not described here.
[0172] S403. The L-SMF network element sends a first request comprising the DNS processing rule to the SMF network element, and the SMF network element receives the first request from the L-SMF network element.
[0173] Specifically, the L-SMF network element sends a first request including the DNS processing rule to the SMF network element, including: determining that the EAS corresponding to the UE changes through table lookup, or in the case that the distance between the UE and the EAS is greater than the distance threshold, the L-SMF network element sends a first request including the DNS processing rule to the SMF network element. Wherein, the EAS is used to provide services corresponding to all FQDNs supported by the L-SMF network element.
[0174] In the case that the L-SMF network element sends the first request including the DNS processing rule to the SMF network element, the first request is used to request an update related to the DNS processing rule.
[0175] It should be understood that the L-SMF network element needs to judge whether the DNS processing rule corresponding to the FQDN needs to be updated based on the location information of the UE, and if so, the new DNS processing rule corresponding to the FQDN needs to be notified to the SMF network element, triggering the SMF network element to perform the DNS context update process and update the DNS processing rule associated with the location information of the UE. Therefore, the SMF network element receives the new DNS processing rule associated with the location information of the UE in the first request from the L-SMF network element, at which time the first request is used to request an update related to the new DNS processing rule.
[0176] In this application, the DNS processing rule includes the ECS option used to indicate the location information of the UE, so that the update related to the DNS processing rule can include updating the ECS option associated with the location information of the UE in the DNS processing rule.
[0177] Optionally, in this application, the L-SMF network element sends the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element to the SMF network element, at which time the first request sent by the L-SMF network element to the SMF network element can be used to request an update related to the DNS processing rule. Wherein, the update related to the DNS processing rule includes updating all DNS processing rules associated with the location information of the UE.
[0178] S404. The SMF network element sends a second request to the EAS DF network element in response to the first request.
[0179] Wherein, the EAS DF is used to process the DNS request of the terminal.
[0180] Wherein, the second request includes the new DNS processing rule associated with the location information of the UE; the second request is used to request an update related to the new DNS processing rule.
[0181] It should be understood that, since the SMF network element receives a new DNS rule associated with the UE's location information, in order for the EASDF network element to accurately process the UE's DNS requests in the future, it needs to send the aforementioned second request to the EASDF network element.
[0182] The first request may also include information about the SMF network element, which is used to identify the SMF network element. For example, the SMF network element information may be the identifier of the SMF network element or the address information of the SMF network element.
[0183] The second request also includes information about the EASDF network element, which is used to identify the EASDF network element. For example, the EASDF network element information can be the identifier of the EASDF network element or the address information of the EASDF network element.
[0184] based on Figure 2 The method shown allows the L-SMF network element to obtain the UE's location information and determine the DNS processing rules associated with that location information when the UE moves. If the L-SMF network element determines that the DNS processing rules associated with the UE's location information need updating, it sends a first request to the SMF network element. This allows the L-SMF network element to obtain the UE's location information and update the DNS processing rules associated with that location information. This avoids the problem where the L-SMF network element only perceives the UE's location information at the time of insertion, leading to inaccurate determination of the DNS processing rules based on the UE's location information perceived at the time of insertion, which affects service transmission and reduces user experience.
[0185] The technical solutions in this application will now be described with reference to the accompanying drawings.
[0186] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a wireless fidelity (Wi-Fi) system, a vehicle to everything (V2X) communication system, a device-to-device (D2D) communication system, a vehicle networking communication system, a 4th generation (4G) mobile communication system such as a long term evolution (LTE) system, a worldwide interoperability for microwave access (WiMAX) communication system, a 5th generation (5G) mobile communication system such as a new radio (NR) system, and a future communication system such as a 5.5G, a 6th generation (6G) mobile communication system, and the like. In particular, the technical solutions of the embodiments of the present application are applied to a communication system as shown in FIG. 1. Figure 2 The communication system as shown in FIG. 1 is a communication system in which an L-SMF network element is inserted.
[0187] It can be understood that the above Figure 2 is only a schematic diagram and does not constitute a limitation on the applicable scenarios of the technical solutions provided by the present application. Those skilled in the art should understand that, in the specific implementation process, the communication system of the embodiments of the present application can also include fewer devices than Figure 2 shown, or the communication system of the embodiments of the present application can also include other devices, and the number of devices in the communication system of the embodiments of the present application can also be determined according to specific needs and is not limited.
[0188] Figure 2The terminal can be referred to as terminal equipment, user equipment (UE), mobile station (MS), mobile terminal (MT), or the like, and includes a handheld device, a vehicle-mounted device, a wearable device, or a computing device with wireless communication functions. Specifically, the terminal equipment can be a mobile phone, a tablet computer, or a computer with wireless transceiver functions, and can also be a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote medical treatment, a wireless terminal in smart power grids, a wireless terminal in smart cities, a smart home, a vehicle-mounted terminal, or the like. In the embodiments of the present application, the device for implementing the functions of the terminal equipment can be the terminal equipment, or a device capable of supporting the terminal equipment to implement the functions, such as a chip system (for example, one chip or a processing system composed of multiple chips) or a modem. In the following, the device for implementing the functions of the terminal is taken as an example to describe the communication method provided by the embodiments of the present application.
[0189] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.
[0190] The following will be described in detail with reference to the architecture shown in Figures 5-7 and the method embodiments shown in Figure 5 The actions, terms, and the like involved in the following embodiments can be mutually referred to, and the message names or parameter names in the messages exchanged between devices in each embodiment are only an example, and other names can also be used in specific implementation. For example, the "corresponding" in the following embodiments can be replaced by "associated" or the like, and the "sending" in the following embodiments can be replaced by "transmitting" or the like. The communication method provided by the embodiments of the present application can be applied to the communication system described above and specifically applied to various scenarios mentioned in the communication system described above, which will be specifically introduced below. Figure 2 Flowchart of the communication method provided by the embodiments of the present application Figure 5 As shown in Figure 3 , the method can include the following steps:
[0191] S501. Perform the insertion process of the L-SMF network element.
[0192] Specifically, the insertion process of the L-SMF network element can refer to the method flow as shown in the following Figure 3 The S101-S115 are not described herein again. Figure 5
[0193] In the execution of the insertion process of the L-SMF network element, the EASDF is configured with DNS processing rules corresponding to all FQDNs supported by the L-SMF network element.
[0194] It should be understood that S501 is a pre-process of the method as shown in the following Figure 5 , which is a prerequisite for the subsequent method execution in Figure 3 .
[0195] S502. The L-SMF network element sends a subscription request to the SMF network element, and the SMF network element receives the subscription request from the L-SMF network element.
[0196] The subscription request (subscribe request) can be used to request subscription of the location information of the UE.
[0197] Optionally, in the case of opening an interface between the AMF and the L-SMF network element, i.e., in the case of establishing a connection between the AMF and the L-SMF network element, S502 can also be described as the L-SMF network element sending a subscription request to the AMF, which is not limited.
[0198] S503. The SMF network element returns a subscription response to the L-SMF network element.
[0199] The subscription response (subscribe response) can be used to indicate that the L-SMF network element subscribes successfully.
[0200] Optionally, after the L-SMF network element subscribes successfully, the SMF network element can periodically send the location information of the UE to the L-SMF network element.
[0201] Optionally, if there is an open interface between the L-SMF network element and the AMF, S502 is described as the L-SMF network element sending a subscription request to the AMF, and accordingly, S503 can be described as the AMF returning a subscription response to the L-SMF network element.
[0202] S504. The L-SMF network element sends DNS processing rules corresponding to all FQDNs supported by the L-SMF network element to the SMF network element, and the SMF network element receives the DNS processing rules corresponding to all FQDNs supported by the L-SMF network element.
[0203] S505. The SMF network element returns a response message to the L-SMF network element.
[0204] The response message can be used to indicate all DNS processing rules corresponding to the FQDNs supported by the L-SMF network element.
[0205] S506. Perform the remaining procedures of the L-SMF network element insertion.
[0206] Specifically, the remaining procedures of the L-SMF insertion can refer to the method flow shown in Figure 3 S117-S121 shown in S117-S121, which will not be described here. Figure 5
[0207] The remaining procedures of the L-SMF network element insertion in S506 can include: the SMF network element configures the corresponding DNS processing rules on the EASDF network element. And the SMF network element can configure the DNS processing rules corresponding to all FQDNs received in step 504 on the EASDF network element.
[0208] S507. The AMF network element sends first information to the SMF network element, and the SMF network element receives the first information.
[0209] The AMF network element sending the first information to the SMF network element can include: the AMF network element obtaining the location information of the UE, and sending the first information to the SMF network element.
[0210] The first information can be used to indicate the location information of the UE. Optionally, the first information can include the identifier of the UE and the location information of the UE. The identifier of the UE can include an identifier for identifying the UE, such as the UE ID.
[0211] Optionally, the AMF can obtain the location information of the UE by prior art, which will not be described here.
[0212] S508. The SMF network element sends first information to the L-SMF network element in response to the first information, and the L-SMF network element receives the first information.
[0213] Optionally, if there is an open interface between the L-SMF network element and the AMF network element, and the first information is sent by the L-SMF network element to the AMF network element directly, S507-S508 can be replaced by the AMF network element sending the first information to the L-SMF network element.
[0214] S509. The L-SMF network element determines whether to send a first request to the SMF network element based on the first information.
[0215] The description of the first request can refer to the description in S403, which will not be described here.
[0216] The L-SMF network element determines whether to send the first request to the SMF network element based on the first information, which can include: the L-SMF network element determines the DNS processing rule associated with the location of the UE according to the location information of the UE in the first information, and sends the first request to the SMF network element in the case where the DNS processing rule associated with the location of the UE needs to be updated; and does not send the first request to the SMF network element in the case where the DNS processing rule associated with the location of the UE does not need to be updated.
[0217] In the present application, for any FQDN, the L-SMF network element can obtain the EAS in the EAS it manages that provides the service corresponding to the FQDN, and if it is determined through table lookup that the EAS corresponding to the UE has changed, or it is determined that the UE is far away from the EAS originally providing the service or the distance between the UE and the EAS providing the service is greater than a distance threshold, the DNS processing rule associated with the location of the UE needs to be updated, and then the LMF network element determines the new DNS processing rule associated with the location information of the UE based on the managed EAS deployment information (such as the location information of the EAS) and the location information of the UE and the FQDN. The DNS processing rule can include the ECS option, so the new DNS processing rule associated with the location information of the UE includes the new ECS option corresponding to the FQDN.
[0218] The L-SMF network element determines the new DNS processing rule associated with the location information of the UE based on the managed EAS deployment information (such as the location information of the EAS) and the location information of the UE and the FQDN, which can refer to the prior art and will not be described here.
[0219] S510. The L-SMF network element sends a first request to the SMF network element, and the SMF network element receives the first request from the L-SMF.
[0220] S510 can refer to the related description of S403, which will not be described here.
[0221] S510 is an optional operation, which is executed in the case where the L-SMF network element determines that the first request needs to be sent to the SMF network element, such as the case where the L-SMF network element determines that the ECS option corresponding to the service accessed by the UE needs to be updated, and then sends the first request to the SMF network element; and is not executed in the case where the L-SMF network element determines that the first request is not sent to the SMF network element.
[0222] S511. The SMF network element returns a first response to the L-SMF network element.
[0223] The first response is used to indicate that the SMF network element receives the first request from the L-SMF network element.
[0224] It should be understood that after the SMF network element receives the first request from the L-SMF network element, the DNS processing rule associated with the UE location information in the SMF network element can be updated to a new DNS processing rule associated with the UE location information based on the new DNS processing rule included in the first request.
[0225] S511 is an optional execution operation, which is executed when the SMF network element receives the first request from the L-SMF network element, and is not executed when the SMF network element does not receive the first request from the L-SMF network element.
[0226] S512. The SMF network element sends a second request to the EASDF in response to the first request, and the EASDF network element receives the second request from the SMF network element.
[0227] Wherein, the second request and the related description of the SMF network element sending the second request to the EASDF in response to the first request can refer to the related description of S404, which will not be repeated here.
[0228] S512 is an optional execution operation, which is executed when the SMF network element receives the first request from the L-SMF network element, and is not executed when the SMF network element does not receive the first request from the L-SMF network element.
[0229] S513. The EASDF network element returns a second response to the SMF network element.
[0230] Wherein, the second response is used to indicate that the EASDF network element receives the second request from the SMF network element.
[0231] It should be understood that after the EASDF network element receives the second request from the SMF network element, the DNS processing rule associated with the UE location information in the EASDF network element can be updated to a new DNS processing rule associated with the UE location information based on the new DNS processing rule included in the second request.
[0232] S513 is an optional execution operation, which is executed when the EASDF network element receives the second request from the SMF network element, and is not executed when the EASDF network element does not receive the second request from the SMF network element.
[0233] Based on Figure 6The method shown in the L-SMF network element insertion process, by subscribing to the location information of the UE, the L-SMF network element perceives the location change of the UE, and then realizes the DNS processing rule update process based on the location update of the UE and the DNS processing rule corresponding to the UE location information. At the same time, the update granularity of the DNS processing rule is changed from a single FQDN granularity to the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element, and the EASDF network element repeatedly provides the L-SMF network element list to the SMF network element, reducing the problem of large signaling overhead.
[0234] Figure 3 The flowchart of the communication method provided by the embodiment of the application Figure 3 As Figure 6 shown, it can include:
[0235] S601. Perform the insertion process of the L-SMF network element.
[0236] Specifically, the insertion process of the L-SMF network element can refer to the method flow shown in Figure 6 , such as performing S101-S115 shown in Figure 6 , which will not be described here.
[0237] In the execution of the insertion process of the L-SMF network element, the EASDF is configured with the DNS processing rule corresponding to the FQDN supported by the L-SMF network element.
[0238] It should be understood that S601 is the pre-process of the method shown in Figure 7 , which is a prerequisite for the subsequent method execution in Figure 4 .
[0239] S602. The L-SMF network element sends the TA list of the corresponding PSA under the L-SMF network element to the SMF network element, and the SMF network element receives the TA list of the corresponding PSA under the L-SMF network element.
[0240] Among them, the corresponding PSA under the L-SMF network element can be understood as the PSA managed by the L-SMF network element.
[0241] Among them, the tracking area list (TA list) of the PSA can indicate the area served by the PSA. In the case of dividing the area served by the PSA in cell granularity, the TA list of the PSA can include the identifier of one or more cells served by the PSA. It should be understood that the area served by the PSA can also be divided in other division granularities in the present application, and at this time the TA list of the PSA includes the identifier of the area unit divided in other granularities.
[0242] Optionally, in the case of opening an interface between the AMF and the L-SMF network element, that is, in the case of establishing a connection between the AMF and the L-SMF network element, S602 can also be replaced by the description that the L-SMF network element sends the TA list of the corresponding PSA under the L-SMF network element to the AMF, without limitation.
[0243] S603. The SMF network element returns a response message to the L-SMF network element.
[0244] The response message can be used to indicate that the TA list of the corresponding PSA under the L-SMF network element is successfully received.
[0245] Optionally, if there is an open interface between the L-SMF network element and the AMF, S602 is replaced by the description that the L-SMF network element sends a subscription request to the AMF, and correspondingly, S603 can be replaced by the description that the AMF returns a response message to the L-SMF network element.
[0246] S604. The L-SMF network element sends the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element to the SMF network element, and the SMF network element receives the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element.
[0247] S605. The SMF network element returns a response message to the L-SMF network element.
[0248] S606. Perform the remaining procedures inserted by the L-SMF network element.
[0249] S607. The AMF network element sends first information to the SMF network element, and the SMF network element receives the first information.
[0250] S604-S607 can refer to the related description of S504-S507 described above, and will not be repeated here.
[0251] S608. The SMF network element determines whether to send the first information to the L-SMF network element in response to the first information.
[0252] The SMF network element determines whether to send the first information to the L-SMF network element in response to the first information can include: the SMF network element determines whether to send the first information to the L-SMF network element based on the first information and the TA list of the corresponding PSA under the L-SMF network element received in S602, that is, determines whether the SMF network element performs S609.
[0253] Optionally, if the SMF network element determines that the UE is in the area served by the PSA connected with the UE based on the location information of the UE in the first information and the TA list of the corresponding PSA under the L-SMF network element, the first information does not need to be sent to the L-SMF network element, i.e., the location information of the UE does not need to be informed to the L-SMF network element, if it is determined that the UE is not in the area served by the PSA connected with the UE, i.e., the UE moves out of the area served by the PSA connected with the UE, the first information needs to be sent to the L-SMF network element, S609 is executed, i.e., the location information of the UE needs to be informed to the L-SMF network element, so that the L-SMF network element triggers the DNS processing rule update based on the location information of the UE. The TA list of the corresponding PSA under the L-SMF network element includes the PSA connected with the UE.
[0254] S609. The SMF network element sends the first information to the L-SMF network element, and the L-SMF network element receives the first information.
[0255] Optionally, if there is an open interface between the L-SMF network element and the AMF network element, S607-S609 can be replaced by the following description: the AMF network element determines whether to send the first information to the L-SMF network element in response to the first information, the AMF network element sends the first information to the L-SMF network element, and the L-SMF network element receives the first information.
[0256] It should be understood that the L-SMF network element receives the first information, and can send the TA list corresponding to the new PSA to the SMF network element, so that the SMF network element can update the TA list of the corresponding PSA under the L-SMF network element.
[0257] S609 is an optional execution operation, which is executed in the case that the SMF network element determines to send the first information to the L-SMF network element in S608, and is not executed in the case that the SMF network element determines not to send the first information to the L-SMF network element in S608.
[0258] S610. The L-SMF network element determines whether to send the first request to the SMF network element based on the first information.
[0259] S611. The L-SMF network element sends the first request to the SMF network element, and the SMF network element receives the first request from the L-SMF.
[0260] S612. The SMF network element returns the first response to the L-SMF network element.
[0261] S613. The SMF network element initiates a second request to the EASDF in response to the first request, and the EASDF network element receives the second request from the SMF network element.
[0262] S614. The EASDF network element returns a second response to the SMF network element.
[0263] The related description of S610-S614 can refer to the related description of S509-S513, which is not described here.
[0264] Based on Figure 7 As shown in the method, in the L-SMF network element insertion process, the L-SMF network element sends the TA list of the corresponding PSA under the L-SMF network element to the SMF network element, so that the L-SMF network element can perceive the location change of the UE, and then realize the updating of the DNS processing rule based on the location update of the UE and the UE location information in the DNS processing rule updating process. At the same time, the updating granularity of the DNS processing rule is changed from a single FQDN granularity to the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element, avoiding the problem of repeatedly providing the L-SMF network element list to the SMF network element by the EASDF network element, and reducing the signaling overhead.
[0265] Figure 3 Flowchart of the communication method provided by the embodiment of the application Figure 3 As shown in the method, the method can include: Figure 7
[0266] S701. Perform the insertion process of the L-SMF network element.
[0267] Specifically, the insertion process of the L-SMF network element can refer to the method flow as shown in Figure 7 S101-S115, which is not described here. Figure 7
[0268] In the insertion process of the L-SMF network element, the EASDF is configured with the DNS processing rule corresponding to the FQDN supported by the L-SMF network element.
[0269] It should be understood that S701 is the preceding process of the method as shown in Figure 8 , which is a prerequisite for the subsequent method execution in Figure 1 .
[0270] S702. The L-SMF network element sends the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element to the SMF network element, and the SMF network element receives the DNS processing rule corresponding to all FQDNs supported by the L-SMF network element.
[0271] S703. The SMF network element returns a response message to the L-SMF network element.
[0272] S704. Perform the remaining process of the L-SMF network element insertion.
[0273] Wherein, S702-S704 can refer to the related description of S504-S506, which will not be repeated here.
[0274] S705. The UE sends a DNS query message to the EASDF network element, and the EASDF network element receives the DNS query message.
[0275] Wherein, the FQDN can be included in the DNS query message.
[0276] S706. The EASDF network element sends the matching condition of the DNS query message to the SMF network element in response to the DNS query message; and the SMF network element receives the matching condition of the DNS query message from the EASDF network element.
[0277] Wherein, the matching condition of the DNS query message can include: finding the L-SMF network element supporting the FQDN in the configuration of the EASDF network element; or not finding the L-SMF network element supporting the FQDN in the configuration of the EASDF network element.
[0278] It should be understood that if the EASDF network element does not find the L-SMF network element supporting the FQDN in the DNS query message, it means that the L-SMF network element supporting the FQDN has not been inserted into the network and has not established a connection with the SMF network element, at which time it returns to S701 to perform the insertion process of the L-SMF network element.
[0279] If the EASDF network element finds the L-SMF network element supporting the FQDN in the DNS query message, it sends the L-SMF network element information supporting the FQDN in the DNS query message to the SMF network element, such as the identifier of the L-SMF network element supporting the FQDN in the DNS query message, so that the SMF network element performs S707.
[0280] Optionally, the EASDF network element can send the L-SMF network element information supporting the FQDN in the DNS query message to the SMF network element through the Neasdf DNS Context Notify Request information.
[0281] S707. The SMF network element returns a response message to the EASDF network element.
[0282] Wherein, the response message is used to indicate that the SMF network element receives the matching condition of the DNS query message.
[0283] Optionally, the response message can be the Neasdf DNS Context Notify Response information.
[0284] S708. The SMF network element sends a UE context establishment request to the L-SMF network element in response to the matching of the DNS query message; and the L-SMF network element receives the UE context establishment request.
[0285] The SMF network element sends a UE context establishment request to the L-SMF network element in response to the matching of the DNS query message, which can include that the SMF network element determines the L-SMF network element according to the L-SMF network element information supporting the FQDN in the DNS query message and the location information of the UE, determines the L-SMF network element, and sends the UE context establishment request to the determined L-SMF network element.
[0286] The UE context establishment request is used to request to establish the context of the UE. The UE context establishment request includes the location information of the UE.
[0287] Optionally, the UE context establishment request can be Nsmf_PDUSession_CreateSMContext Request.
[0288] Optionally, the UE context establishment request can carry not only the location information of the UE but also the identification information of the UE.
[0289] S709. The L-SMF network element determines whether to send a first request to the SMF network element based on the UE context establishment request.
[0290] The related description of the first request can refer to the description in S403, which is not repeated here.
[0291] The L-SMF network element determines whether to send a first request to the SMF network element based on the UE context establishment request, which includes that the L-SMF network element determines the DNS processing rule associated with the location of the UE according to the location information of the UE in the UE context establishment request, sends the first request to the SMF network element in the case that the DNS processing rule associated with the location of the UE needs to be updated, and does not send the first request to the SMF network element in the case that the DNS processing rule associated with the location of the UE does not need to be updated.
[0292] S710: The L-SMF network element returns a UE context establishment response to the SMF network element.
[0293] The UE context establishment response is used to indicate that the UE context establishment request is received.
[0294] Optionally, the UE context response can be Neasdf DNS Context Notify Response information.
[0295] The S711.L-SMF network element sends a first request to the SMF network element, and the SMF network element receives the first request from the L-SMF.
[0296] The S712.SMF network element returns a first response to the L-SMF network element.
[0297] In response to the first request, the S713.SMF network element sends a second request to the EASDF, and the EASDF network element receives the second request from the SMF network element.
[0298] The S714.EASDF network element returns a second response to the SMF network element.
[0299] The relevant descriptions of S711-S714 above can be found in the relevant descriptions of S5010-S513, and will not be repeated here.
[0300] based on Figure 8 The method described above involves the L-SMF network element receiving a UE context request, including the UE's location information, during the L-SMF network element insertion process. This allows the L-SMF network element to detect changes in the UE's location and subsequently update the DNS processing rules based on the UE's location information during the DNS processing rule update process. Simultaneously, the update granularity of the DNS processing rules is changed from a single FQDN to configuring DNS processing rules corresponding to all FQDNs supported by the L-SMF network element. This avoids the EASDF network element repeatedly providing the L-SMF network element list to the SMF network element, reducing the problem of high signaling overhead.
[0301] The foregoing mainly describes the solutions provided in the embodiments of this application from the perspective of interaction between various devices. It is understood that each device, such as an L-SMF network element, includes corresponding hardware structures and / or software modules to perform the aforementioned functions. Those skilled in the art should readily recognize that, in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.
[0302] The embodiments of the present application can group the function modules of the station, the access point and the like according to the above method examples. For example, each function module can correspond to each function group, or two or more functions can be integrated in one processing module. The integrated module can be realized in the form of hardware or in the form of a software function module. It should be noted that the grouping of the modules in the embodiments of the present application is illustrative, and is only a logical grouping. In actual implementation, another grouping manner can be used.
[0303] Figure 8 is a structure schematic of a communication apparatus provided by the embodiments of the present application Figures 4-7 . For example, as shown in Figures 4-7 , the communication apparatus 800 includes a transceiving module 801 and a processing module 802. For ease of illustration, Figure 8 only the main components of the communication apparatus are shown.
[0304] The transceiving module 801 is configured to perform the transceiving function of the method shown in the above Figure 8 , and the processing module 802 is configured to perform the functions other than the transceiving function of the method shown in the above Figure 8 .
[0305] Optionally, the transceiving module 801 can include a sending module (not shown in the above Figures 4-7 ) and a receiving module (not shown in the above Figures 4-7 ). The sending module is configured to implement the sending function of the communication apparatus 800, and the receiving module is configured to implement the receiving function of the communication apparatus 800.
[0306] Optionally, the communication apparatus 800 can further include a storage module (not shown in the above Figure 9 ). The storage module stores a program or an instruction. When the processing module 802 executes the program or the instruction, the communication apparatus 800 can perform the functions in the method shown in the above Figure 2 .
[0307] It can be understood that the communication apparatus 800 can be a terminal or a network device, or can be a chip (system) or other components or assemblies that can be arranged in the terminal or the network device, or can be an apparatus containing the terminal or the network device, and the present application does not limit this.
[0308] In addition, the technical effects of the communication apparatus 800 can refer to the technical effects of the communication method shown in the above Figure 9 , and details are not described herein.
[0309] Figure 9 is a structure schematic of a communication apparatus provided by the embodiments of the present application Figures 4-7Exemplarily, the communication apparatus can be a terminal, or a chip (system) or other components or assemblies which can be arranged in the terminal. As shown in Figure 9 The communication apparatus 900 can include a processor 901. Optionally, the communication apparatus 900 can also include a memory 902 and / or a transceiver 903. The processor 901 is coupled with the memory 902 and the transceiver 903, for example, through a communication bus.
[0310] The following will be specifically introduced in combination with Figure 9 The various constituent components of the communication apparatus 900 will be introduced in detail as follows:
[0311] The processor 901 is the control center of the communication apparatus 900, and can be one processor or a collective term of multiple processing elements. For example, the processor 901 is one or more central processing units (CPUs), or can be an application specific integrated circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, for example, one or more digital signal processors (DSPs), or one or more field programmable gate arrays (FPGAs).
[0312] Optionally, the processor 901 can execute various functions of the communication apparatus 900 by running or executing software programs stored in the memory 902, and calling data stored in the memory 902, for example, the communication method shown in Figure 9
[0313] In a specific implementation, as an embodiment, the processor 901 can include one or more CPUs, for example, the CPU0 and the CPU1 shown in Figure 9
[0314] In a specific implementation, as an embodiment, the communication apparatus 900 can also include multiple processors, for example, the processor 901 and the processor 904 shown in Figure 9 Each of the processors can be a single-CPU or a multi-CPU. Here, the processor can refer to one or more devices, circuits, and / or processing cores for processing data (for example, computer program instructions).
[0315] The memory 902 is used to store the software program that executes the solution of this application, and is controlled by the processor 901 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.
[0316] Optionally, the memory 902 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 902 may be integrated with the processor 901 or exist independently, and may be connected via the interface circuit of the communication device 900. Figure 9 (Not shown in the image) is coupled to the processor 901, but this embodiment does not specifically limit this.
[0317] Transceiver 903 is used for communication with other communication devices. For example, if communication device 900 is a terminal, transceiver 903 can be used to communicate with a network device or with another terminal device. As another example, if communication device 900 is a network device, transceiver 903 can be used to communicate with a terminal or with another network device.
[0318] Alternatively, transceiver 903 may include a receiver and a transmitter. (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.
[0319] Optionally, the transceiver 903 can be integrated with the processor 901, or it can exist independently and be connected via the interface circuit of the communication device 900. (Not shown in the image) is coupled to the processor 901, but this embodiment does not specifically limit this.
[0320] Understandable The structure of the communication device 900 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0321] In addition, the technical effects of the communication apparatus 900 can refer to the technical effects of the methods described in the above method embodiments, which will not be repeated here.
[0322] It should be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and the processor can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.
[0323] It should also be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically EPROM (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM) used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM) and direct rambus RAM (DR RAM).
[0324] The above-described embodiments can be implemented in part or in whole through software, hardware (e.g., circuitry), firmware, or any combination thereof. When implemented in software, the above-described embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When loaded and executed by a computer, the computer instructions or computer programs can produce the processes or functions described above according to the embodiments of the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, e.g., from a website site, a computer, a server, or a data center to another website site, a computer, a server, or a data center through a wired (e.g., infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium or a collection of medium accessible by a computer or a data storage device such as a server, a data center, etc. containing one or more medium. The medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium. The semiconductor medium can be a solid state disk.
[0325] It should be understood that the term "and / or" in this document is merely used to describe an associated relationship between associated objects, and can represent three relationships, for example, A and / or B can represent three cases of A alone, A and B together, and B alone, where A and B can be singular or plural. In addition, the character " / " in this document generally represents an "or" relationship between the front and rear associated objects, but can also represent an "and / or" relationship, which can be understood according to the context before and after.
[0326] In the embodiments of the present application, "indication" can include direct indication and indirect indication, and can also include explicit indication and implicit indication. The information indicated by a certain information is referred to as to-be-indicated information, and there are many ways to indicate the to-be-indicated information in the specific implementation process, for example, but not limited to, the to-be-indicated information can be directly indicated, such as the to-be-indicated information itself or the index of the to-be-indicated information. The to-be-indicated information can also be indirectly indicated by indicating other information, where the other information and the to-be-indicated information have an associated relationship. The to-be-indicated information can also be indicated only by a part, and the other part of the to-be-indicated information is known or agreed in advance. For example, the indication of a specific information can also be achieved by means of the arrangement order of each information agreed in advance (for example, a protocol), thereby reducing the indication overhead to a certain extent. At the same time, the common part of each information can be identified and uniformly indicated, so as to reduce the indication overhead caused by separately indicating the same information.
[0327] In addition, the specific indication manner can also be various existing indication manners, for example but not limited to the indication manners and various combinations thereof. The specific details of the various indication manners can be referred to the prior art, and will not be described herein. As can be seen from the above, for example, when multiple information of the same type needs to be indicated, the indication manners of different information can be different. In the specific implementation process, the required indication manner can be selected according to the specific needs, and the selected indication manner is not limited by the embodiments of the application. In this way, the indication manners involved in the embodiments of the application should be understood as covering various methods that can enable the to-be-indicated party to know the to-be-indicated information.
[0328] It should be understood that the to-be-indicated information can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and / or sending occasion of the sub-information can be the same or different. The specific sending method is not limited by the embodiments of the application. The sending period and / or sending occasion of the sub-information can be predefined, for example, predefined according to a protocol, or configured by the sending end device through sending configuration information to the receiving end device.
[0329] In the present application, "sending information" can be understood as a device sending information to another device, or a logical module in a device sending information to another logical module. For example, "network device sending information" can be understood as the network device sending information to another device (such as a terminal or another network device), or the logical module 1 in the network device sending information to the logical module 2 in the network device.
[0330] In the present application, "receiving information" can be understood as a device receiving information from another device, or a logical module in a device receiving information from another logical module. For example, "network device receiving information" can be understood as the network device receiving information from another device (such as a terminal or another network device), or the logical module 1 in the network device receiving information from the logical module 2 in the network device.
[0331] In the present application, "sending information to (for example, a terminal)" or related illustrations in the drawings can be understood as that the destination of the information is the terminal. It can include directly or indirectly sending information to the terminal. "Receiving information from (for example, a terminal)" or "receiving information sent by (for example, a terminal)" or "receiving information from (for example, a terminal)", or related illustrations in the drawings can be understood as that the source of the information is the terminal, which can include directly or indirectly receiving information from the terminal. The information can be processed as necessary between the source and the destination of the information, for example, format change, etc., but the destination can understand the valid information from the source. Similar expressions in the present application can be understood similarly, and will not be described herein.
[0332] The predefinition or pre-configuration can be realized by pre-storing corresponding codes, tables or other means for indicating relevant information in the device, and the embodiments of the present application do not limit the specific implementation manner. The storage can be in one or more memories. The one or more memories can be separately arranged or integrated in the encoder or decoder, processor or communication device. The one or more memories can be partially separately arranged and partially integrated in the decoder, processor or communication device. The memory can be any form of storage medium, and the embodiments of the present application do not limit the same.
[0333] The protocol referred to in the embodiments of the present application can refer to a protocol family in the communication field, a standard protocol similar to the protocol family frame structure, or a relevant protocol applied to a future communication system, and the embodiments of the present application do not limit the same.
[0334] In the embodiments of the present application, the descriptions such as "when", "in the case of", "if" and the like refer to that the device will make corresponding processing under certain objective conditions, and are not limited in time, and do not require the device to have a judgment action when implemented, nor mean that there are other limitations.
[0335] In the description of the embodiments of the present application, unless otherwise specified, " / " means that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the embodiments of the present application is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent: A exists alone, A and B exist simultaneously, and B exists alone, where A and B can be singular or plural. And in the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more than two. "At least one of the following" or the like means any combination of the items, including any combination of single or multiple items. For example, at least one of a, b or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple. In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, "first", "second", etc. are used to distinguish the same items or similar items with basically the same function and role. Those skilled in the art can understand that "first", "second", etc. do not limit the quantity and execution order, and "first", "second", etc. also do not necessarily mean different. At the same time, in the embodiments of the present application, "exemplary" or "for example" means to serve as an example, illustration or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as more preferred or more advantageous than other embodiments or design schemes. Rather, the use of "exemplary" or "for example" is intended to present the relevant concept in a specific manner, for understanding.
[0336] In the present application, "at least one" means one or more, and "multiple" means two or more than two. "At least one of the following" or the like means any combination of the items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, and c can be single or multiple.
[0337] It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of the processes should be determined by its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0338] Those skilled in the art can clearly understand that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be realized by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.
[0339] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.
[0340] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the above-described device embodiments are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.
[0341] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.
[0342] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit.
[0343] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application essentially or the parts that contribute to the prior art or parts of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.
[0344] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.
Claims
1. A communication method, characterized in that, The method, applied to L-SMF network elements for local session management functions, includes: Obtain the location information of the terminal; the location information of the terminal is used to identify the location of the terminal; Determine the Domain Name System (DNS) processing rules associated with the location information of the terminal; Send a first request, including the DNS processing rules, to the Session Management Function (SMF) network element; the first request is used to request updates related to the DNS processing rules.
2. The method according to claim 1, characterized in that, The method further includes: A subscription request is sent to the first network element; the subscription request is used to subscribe to the location information of the terminal. The step of obtaining the location information of the terminal includes: receiving a response from the first network element, the response including the location information of the terminal.
3. The method according to claim 1, characterized in that, The method further includes: Send a first message to the first network element, the first message indicating that: if the location of the terminal is not within the service range of the User Plane Function (UPF) network element connected to the terminal, then send the terminal's location information to the L-SMF network element; and / or, if the location of the terminal is within the service range of the UPF network element connected to the terminal, then do not send the terminal's location information to the L-SMF network element. The step of obtaining the location information of the terminal includes: receiving the location information of the terminal from the first network element, wherein the location of the terminal is not within the service range of the UPF network element.
4. The method according to claim 3, characterized in that, The first message includes the service range of the UPF network element connected to the terminal.
5. The method according to claim 1, characterized in that, The method further includes: A context establishment request is received from the SMF network element, the context establishment request including the location information of the terminal; the context establishment request is used to request the establishment of the terminal's context.
6. The method according to any one of claims 1-5, characterized in that, The method further includes: Send the DNS processing rules corresponding to all fully qualified domain names (FQDNs) supported by the L-SMF network element to the SMF network element; The first request is used to request an update related to the DNS processing rules, the update related to the DNS processing rules including: updating all DNS processing rules associated with the location information of the terminal.
7. The method according to any one of claims 1-6, characterized in that, The L-SMF network element sends a first request, including the DNS processing rules, to the SMF network element, including: When the distance between the terminal and the Edge Application Server (EAS) is greater than a distance threshold, the L-SMF network element sends a first request, including the DNS processing rules, to the SMF network element. The EAS is used to provide services corresponding to all FQDNs supported by the L-SMF network element.
8. The method according to any one of claims 1-7, characterized in that, The DNS processing rules include the EDNS Client Subnet Option (ECS option), which is used to indicate the location information of the terminal.
9. The method according to any one of claims 1-8, characterized in that, The L-SMF network element supports one or more FQDNs; Each of the one or more FQDNs corresponds to a different DNS processing rule.
10. A communication method, characterized in that, The method, applied to the Session Management Function (SMF) network element, includes: A first request is received from the local session management function (L-SMF) network element, wherein the first request includes a new Domain Name System (DNS) processing rule associated with terminal location information; the first request is used to request an update related to the new DNS processing rule; In response to the first request, a second request is sent to the Edge Application Server Discovery Function (EASDF) network element; the second request includes a new Domain Name System (DNS) processing rule associated with the terminal location information; the second request is used to request an update related to the new DNS processing rule; the EASDF is used to process the DNS request of the terminal.
11. The method according to claim 10, characterized in that, The method further includes: Obtain the location information of the terminal; the location information of the terminal is used to identify the location of the terminal; Based on the L-SMF network element's subscription to the terminal's location information, the terminal's location information is sent to the L-SMF network element.
12. The method according to claim 10, characterized in that, The method further includes: The system receives a first message from the L-SMF network element, the first message indicating that: if the location of the terminal is not within the service range of the UPF network element connected to the terminal, the terminal's location information is sent to the L-SMF network element; and / or, if the location of the terminal is within the service range of the UPF network element connected to the terminal, the terminal's location information is not sent to the L-SMF network element. If the location of the terminal is outside the service range of the UPF network element connected to the terminal, the terminal's location information is sent to the L-SMF network element.
13. The method according to claim 10, characterized in that, The method further includes: Receive information from the L-SMF network element from the EASDF network element; A context establishment request is sent to the L-SMF, the context establishment request including the location information of the terminal.
14. The method according to any one of claims 10-13, characterized in that, The method further includes: Receive DNS processing rules corresponding to all FQDNs supported by the L-SMF network element from the L-SMF network element; The first request is used to request an update related to the DNS processing rules, the update related to the DNS processing rules including: updating all DNS processing rules associated with the location information of the terminal.
15. The method according to claim 10, characterized in that, The L-SMF network element supports one or more fully qualified domain names (FQDNs); Each FQDN in the one or more fully qualified domain names (FQDNs) corresponds to a different DNS processing rule.
16. The method according to any one of claims 10-15, characterized in that, The first request further includes: information about the SMF network element; the information about the SMF network element is used to identify the SMF network element; The second request also includes: information about the EASDF network element; the information about the EASDF network element is used to identify the EASDF network element.
17. A communication device, characterized in that, The communication device includes: A transceiver unit is used to acquire the location information of the terminal; the location information of the terminal is used to identify the location of the terminal. The processing unit is used to determine the Domain Name System (DNS) processing rules associated with the location information of the terminal; The transceiver unit is further configured to send a first request, including the DNS processing rules, to the Session Management Function (SMF) network element; the first request is used to request an update related to the DNS processing rules.
18. A communication device, characterized in that, The communication device includes: The transceiver unit is configured to receive a first request from a local session management function (L-SMF) network element, wherein the first request includes a new Domain Name System (DNS) processing rule associated with terminal location information; the first request is used to request an update related to the new DNS processing rule; The processing unit is configured to, in response to the first request, send a second request to the Edge Application Server Discovery Function (EASDF) network element; the second request includes a new Domain Name System (DNS) processing rule associated with the terminal location information; the second request is used to request an update related to the new DNS processing rule; the EASDF is used to process the DNS request of the terminal.
19. A communication device, characterized in that, The communication device includes a processor and a communication interface, the processor and the communication interface being configured to support the communication device in performing the communication method as described in any one of claims 1-9, or in performing the method as described in any one of claims 10-16.
20. A communication system, characterized in that, The communication system includes the communication device as described in claim 17 and the communication device as described in claim 18.
21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-9, or cause the computer to perform the method as described in any one of claims 10-16.
22. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-9, or cause the computer to perform the method as described in any one of claims 10-16.