Communication method and device

Abstract

The invention provides a communication method and device, and the method comprises the steps: a network opening function determines first deployment information according to the service range of a session management network element, and the first deployment information comprises deployment information in the service range of the session management network element; and the network open function sends the first deployment information to the session management network element. Based on the scheme, the session management network element can obtain the deployment information within the service range of the session management network element, so that the load of the session management network element is reduced.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] In the EC deployment scenario, some services may be provided by multiple edge application servers (EAS) deployed at the edge of the network. These EAS provide the same services and content, but have different IP addresses. When the UE needs to access a certain service, the EC scenario requires it to access an available EAS that is closer to the UE. However, in the current EAS discovery process, the session management network element obtains all EAS deployment information related to the data network name (data network name, DNN) or single network slice selection support information (Single Network Slice Selection Assistance Information, S-NSSAI) it serves. However, due to the wide deployment of edge environments (for example, a large number of EAS are deployed), the amount of EAS deployment information will be large, and allowing all SMFs to obtain this EAS deployment information will generate a large load on the SMF.

[0003] Therefore, how to reduce the load on the session management network element caused by the data volume of EAS deployment information is a problem that needs to be solved urgently. Summary of the invention

[0004] The present application provides a communication method and device, whereby a session management network element can obtain deployment information within its own service range, thereby reducing the load of the session management network element.

[0005] In a first aspect, a communication method is provided, which can be executed by a network open function, where the network open function can refer to the network open function itself, or to a processor, module, chip, or chip system that implements the method in the network open function, and the present application does not limit this. The method includes:

[0006] The network open function determines first deployment information according to the service scope of the session management network element, where the first deployment information includes deployment information within the service scope of the session management network element; and the network open function sends the first deployment information to the session management network element.

[0007] It should be understood that the deployment information within the service scope of the SMF can also be understood as the deployment information corresponding to the service scope of the SMF, or the deployment information included in the service scope of the SMF.

[0008] In combination with the first aspect, in some implementations of the first aspect, the deployment information is edge application server (Edge Application Server, EAS) deployment information.

[0009] Based on the above solution, the network open function can determine and return the deployment information within the service scope of the session management network element to the session management network element based on the service scope of the session management network element, so that the session management network element can obtain the deployment information within its own service scope, thereby reducing the load of the session management network element.

[0010] In combination with the first aspect, in some implementations of the first aspect, the service scope of the session management network element includes at least one data network access identifier (data network access identifier, DNAI).

[0011] It should be understood that the first deployment information includes the at least one DNAI and the fully qualified domain name (FQDN), EAS IP, APP ID and other deployment information corresponding to the at least one DNAI.

[0012] In combination with the first aspect, in some implementations of the first aspect, before the network open function determines the first deployment information according to the service scope of the session management, the method further includes: the network open function obtains the service scope of the session management network element.

[0013] In combination with the first aspect, in some implementations of the first aspect, the network open function obtains the service scope of the session management network element, including: the network open function receives the identifier of the session management network element, the network open function sends the identifier of the session management network element to a first network element, and the network open function receives the service scope of the session management network element from the first network element; or, the network open function receives the identifier of the session management network element, and the network open function determines the service scope of the session management network element based on the correspondence between the identifier of the locally configured session management network element and the service scope of the session management network element; or, the network open function receives the service scope of the session management network element from the session management network element.

[0014] In combination with the first aspect, in some implementations of the first aspect, the network open function receives the identifier of the session management network element, including: the network open function receives the identifier of the session management network element from the session management network element.

[0015] It should be understood that the network open function receiving the identifier of the session management can be understood as the network open function receiving information including the identifier of the session management network element.

[0016] It should be understood that the network open function receiving the service scope of the session management network element can be understood as the network open function receiving information including the identifier of the session management network element.

[0017] It should be understood that the embodiments of the present application do not limit the specific indication method of the service scope of the SMF.

[0018] As an example and not limitation, the service scope of the SMF is indicated by at least one DNAI included in the service scope of the SMF.

[0019] As an example and not limitation, the service scope of the SMF is indicated by a specific field.

[0020] In combination with the first aspect, in certain implementations of the first aspect, the network open function determines the first deployment information based on the service scope of the session management network element, including: the network open function sends the service scope of the session management network element to the unified data repository network element; the network open function receives the deployment information corresponding to the service scope of the session management network element from the first network element.

[0021] It should be understood that the network open function sending the service scope of the session management network element to the unified database network element can be understood as the network open function sending information including the service scope of the session management network element to the unified database network element.

[0022] In combination with the first aspect, in some implementations of the first aspect, the first network element is one of the following: a unified data storage repository network element, a unified data management network element, a network storage function, an access management network element.

[0023] Based on the above solution, the network open function can obtain the deployment information within the service scope of the session management network element through the first network element according to the identifier of the session management network element or the service scope of the session management network element.

[0024] In combination with the first aspect, in certain implementations of the first aspect, when the network open function receives the identifier of the session management network element, the method also includes: the network open function receives first indication information, and the first indication information is used to instruct the network open function to obtain deployment information based on the service scope of the SMF; the network open function obtains the service scope of the session management network element based on the first indication information and the identifier of the session management network element.

[0025] It should be understood that the specific manner in which the network open function obtains the service scope of the session management network element can refer to the implementation manner of the first aspect above. Specifically, the session management network element determines the service scope of the session management network element according to the correspondence between the identifier of the locally configured session management network element and the service scope of the session management network element, or the session management network element obtains the service scope of the session management network element through the first network element.

[0026] In combination with the first aspect, in certain implementations of the first aspect, the network open function sends the identifier of the session management network element to the first network element, and the network open function receives the service scope of the session management network element or second indication information from the first network element, and the second indication information is used to instruct the network open function to obtain global deployment information, and the global deployment information includes deployment information within the service scope of at least one other session management network element.

[0027] It should be understood that if the network open function receives the service scope of the session management network element, the deployment information within the service scope of the session management network element is obtained, and if the second indication information is received, the global deployment information is obtained.

[0028] In combination with the first aspect, in certain implementations of the first aspect, the network open function determines the first deployment information based on the service scope of the session management network element, including: the network open function determines the deployment information corresponding to the service scope of the session management network element based on the service scope of the session management network element and local configuration.

[0029] Based on the above solution, the network open function can determine the deployment information within the service scope of the session management network element through local configuration according to the identifier of the session management network element or the service scope of the session management network element.

[0030] In a second aspect, a communication method is provided, which can be executed by a session management network element. The session management network element here can refer to the session management network element itself, or to a processor, module, chip, or chip system that implements the method in the session management network element, and the present application does not limit this. The method includes:

[0031] The session management network element sends information about the service scope of the session management network element to the second network element; the session management network element receives deployment information within the service scope of the session management network element; the session management network element sends a first message to the edge application server discovery function network element based on the deployment information, and the first message is used to configure the edge application server discovery network element's processing rules for domain name system messages related to user equipment.

[0032] In combination with the second aspect, in some implementations of the second aspect, the deployment information is edge application server EAS deployment information.

[0033] In combination with the second aspect, in certain implementations of the second aspect, the deployment information includes at least one full domain name and / or at least one EAS address, and the at least one full domain name and the at least one EAS address correspond to the service scope of the session management network element.

[0034] Based on the above solution, the session management network element can subscribe to the second network element for deployment information within the service scope of the session management network element, so that the session management network element can obtain the deployment information within its own service scope, thereby reducing the load of the session management network element.

[0035] In combination with the second aspect, in some implementations of the second aspect, the session management network element sends information about the service scope of the session management network element to the second network element, including: the session management network element sends the identifier of the session management network element to the second network element, and / or the service scope of the session management network element.

[0036] Based on the above solution, the session management network element can send the identifier of the session management network element or the service scope of the session management network element to the second network element to obtain deployment information within the service scope of the session management network element, thereby improving the flexibility of the solution.

[0037] In combination with the second aspect, in certain implementations of the second aspect, when the session management network element sends the service scope of the session management network element to the second network element, the method also includes: the session management network element determines the service scope of the session management network element according to the local configuration; or, the session management network element sends the identifier of the session management network element to the network storage function, and the session management network element receives the service scope of the session management network element from the network storage function.

[0038] Based on the above solution, the session management network element can send the identifier of the session management network element to the second network element, and determine the service scope of the session management network element according to the local configuration, or obtain the service scope of the session management network element through the network storage function.

[0039] In combination with the second aspect, in some implementations of the second aspect, the second network element is one of the following: a network open function, a unified data storage repository network element, a unified data management network element, a network storage function, an access management network element.

[0040] In combination with the second aspect, in some implementations of the second aspect, the service scope of the session management network element includes at least one data network access identifier.

[0041] In combination with the second aspect, in certain implementations of the second aspect, the method also includes: the session management network element receives a second message from the edge application server discovery function network element, the second message includes a first full domain name, and / or a first EAS address, wherein the first full domain name is included in the at least one full domain name, and the first EAS address is included in the at least one EAS address.

[0042] In combination with the second aspect, in certain implementations of the second aspect, when the second message includes the first EAS address, the method also includes: the session management network element inserts a first user plane network element according to the second message, and the first user plane network element has the same data network access identifier as the first EAS address.

[0043] In a third aspect, a communication method is provided, which can be executed by a network open function, where the network open function can refer to the network open function itself, or to a processor, module, chip, or chip system that implements the method in the network open function, and the present application does not limit this. The method includes:

[0044] The network open function receives deployment information from the application function; the network open function determines at least one session management network element corresponding to the deployment information based on the deployment information; the network open function sends the deployment information within the service scope of each session management network element in the at least one session management network element to the at least one session management network element.

[0045] Alternatively, the method includes: a network open function receives first information from an application function, the first information is used to indicate deployment information of N areas, the N areas are included in the service scope of M session management network elements, M≥N≥1; the network open function sends M second information to the M session management network elements, the M second information correspond one-to-one to the M session management network elements, and each second information is deployment information of an area included in the service scope of the corresponding session management network element.

[0046] In combination with the third aspect, in some implementations of the third aspect, the deployment information is edge application server EAS deployment information.

[0047] In combination with the third aspect, in some implementations of the third aspect, the deployment information includes at least one data network access identifier DNAI.

[0048] It should be understood that the at least one session management network element corresponding to the deployment information can be understood as the service scope of the session management network element corresponding to the deployment information. Specifically, the deployment information includes at least one DNAI, and the service scope of the session management network element includes at least one of the DNAIs, that is, the session management network element can be regarded as corresponding to the deployment information.

[0049] Based on the above scheme, after receiving the deployment information from the application function, the network open function can obtain at least one session management network element corresponding to the deployment information, and send the deployment information within the service scope of the corresponding session management network element to the at least one session management network element, so that the session management network element can obtain the deployment information within its own service scope, thereby reducing the load of the session management network element.

[0050] In combination with the third aspect, in certain implementations of the third aspect, before the network open function sends the deployment information within the service scope of each session management network element in the at least one session management network element to the at least one session management network element, the method also includes: the network open function determines at least one session management network element corresponding to each DNAI based on the at least one DNAI and a preset first correspondence, wherein the first correspondence includes a correspondence between the at least one DNAI and the service scope of the at least one session management network element, and the at least one first session management network element belongs to the at least one session management network element.

[0051] It should be understood that the first corresponding relationship may be locally configured by the network open function, or may be obtained from other network elements storing the first corresponding relationship, and the embodiments of the present application are not limited to this.

[0052] Based on the above solution, the network open function can determine at least one session management network element corresponding to each DNAI included in the deployment information according to at least one DNAI in the deployment information and a preset first corresponding relationship.

[0053] In combination with the third aspect, in certain implementations of the third aspect, before the network open function sends the deployment information within the service scope of each session management network element in the at least one session management network element to the at least one session management network element, the method also includes: the network open function sends one or more of the DNAIs to a third network element, and the third network element is used to store the correspondence between the at least one DNAI and the service scope of the at least one session management network element; the network open function receives the identifier of at least one second session management network element from the third network element, the service scope of the at least one second session management network element corresponds to the at least one DNAI, and the at least one second session management network element belongs to the at least one session management network element.

[0054] In combination with the third aspect, in certain implementations of the third aspect, the third network element is one of the following: a unified data storage network element, a unified data management network element, an access management network element, and a network storage function.

[0055] Based on the above solution, the network open function can obtain at least one session management network element corresponding to each DNAI in at least one DNAI in the deployment information through the third network element.

[0056] In a fourth aspect, a communication method is provided, which can be performed by a unified data repository network element, where the unified data repository network element can refer to the unified data repository network element itself, or to a processor, module, chip, or chip system that implements the method in the unified data repository network element, and the present application does not limit this. The method includes:

[0057] The unified data repository network element receives the service scope information of the session management network element; the unified data repository network element determines the deployment information within the service scope information of the session management network element according to the service scope information of the session management network element; the unified data repository network element sends the deployment information within the service scope information of the session management network element to the session management network element.

[0058] In combination with the fourth aspect, in certain implementations of the fourth aspect, the service scope of the session management network element includes at least one DNAI.

[0059] In combination with the fourth aspect, in some implementations of the fourth aspect, the deployment information is edge application server EAS deployment information.

[0060] In combination with the fourth aspect, in certain implementations of the fourth aspect, the unified data storage repository network element sends the deployment information within the service scope information of the session management network element to the session management network element through the network open function network element.

[0061] In combination with the fourth aspect, in some implementations of the fourth aspect, the service scope information of the session management network element includes: an identifier of the session management network element, and / or a service scope of the session management network element.

[0062] In combination with the fourth aspect, in certain implementations of the fourth aspect, the service scope of the session management network element includes at least one data network access identifier.

[0063] In a fifth aspect, a communication device is provided, which includes a transceiver unit and a processing unit. The processing unit is used to determine first deployment information based on a service scope of a first session management network element, and the first deployment information includes deployment information within the service scope of the first session management network element; the transceiver unit is used to send the first deployment information to the session management network element.

[0064] It should be understood that the fifth aspect is an implementation method on the device side corresponding to the first aspect, and the supplement, explanation and beneficial effects of the first aspect are also applicable to the fourth aspect and will not be repeated here.

[0065] In a sixth aspect, a communication device is provided, which includes a transceiver unit and a processing unit, wherein the transceiver unit is used to send information about the service scope of the session management network element to the second network element; the transceiver unit is also used to receive deployment information within the service scope of the session management network element; the processing unit is used to send a first message to the edge application server discovery function network element based on the deployment information, and the first message is used to configure the edge application server discovery network element's processing rules for domain name system messages related to user equipment.

[0066] It should be understood that the sixth aspect is an implementation method on the device side corresponding to the second aspect, and the supplement, explanation and beneficial effects of the second aspect are also applicable to the fifth aspect and will not be repeated here.

[0067] In the seventh aspect, a communication device is provided, which includes a transceiver unit and a processing unit, the transceiver unit is used to receive deployment information from an application function; the processing unit is used to determine at least one session management network element corresponding to the deployment information based on the deployment information; the transceiver unit is also used to send the deployment information within the service scope of each session management network element in the at least one session management network element to the at least one session management network element.

[0068] It should be understood that the seventh aspect is an implementation method on the device side corresponding to the third aspect, and the supplement, explanation and beneficial effects of the third aspect are also applicable to the sixth aspect and will not be repeated here.

[0069] In an eighth aspect, a communication device is provided, which includes a transceiver unit and a processing unit, the transceiver unit being used to receive service scope information of a session management network element; the processing unit being used to determine deployment information within the service scope information of the session management network element based on the service scope information of the session management network element; the transceiver unit being further used to send the deployment information within the service scope information of the session management network element to the session management network element.

[0070] It should be understood that the eighth aspect is an implementation method on the device side corresponding to the fourth aspect, and the supplement, explanation and beneficial effects of the fourth aspect are also applicable to the eighth aspect and will not be repeated here.

[0071] In a ninth aspect, the present application provides a communication device, the communication device comprising a processor, configured to implement the method described in any one of the first to eighth aspects or the first to eighth aspects. The processor is coupled to a memory, the memory is configured to store instructions and data, and when the processor executes the instructions stored in the memory, the method described in any one of the first to eighth aspects or the first to eighth aspects can be implemented.

[0072] Optionally, the communication device may further include a memory. Optionally, the memory may be coupled to the processor. Optionally, the communication device may further include a communication interface, which is used for the device to communicate with other devices. Exemplarily, the communication interface may be a transceiver, a hardware circuit, a bus, a module, a pin or other types of communication interfaces.

[0073] In an example, the communication device may be a network open function, or may be a device, module, chip, etc. provided in the network open function, or may be a device that can be used in conjunction with the network open function.

[0074] In another example, the communication device may be a session management network element, or may be a device, a module, a chip, etc. disposed in the session management network element, or a device that can be used in conjunction with the session management network element.

[0075] In a tenth aspect, the present application provides a communication system, including a network open function, a session management network element, and a unified data storage network element. The network open function is used to perform the network open function as described in the first aspect or the third aspect, or any implementation of the first aspect or the third aspect, the session management network element is the session management network element as described in the second aspect or any implementation of the second aspect, and the unified data storage network element is the session management network element as described in the fourth aspect or any implementation of the fourth aspect.

[0076] In the eleventh aspect, the present application also provides a computer program, which, when executed on a computer, enables the computer to execute the method described in any one of the implementations of the first to eighth aspects or the first to eighth aspects.

[0077] In the twelfth aspect, the present application also provides a computer program product, comprising instructions, which, when executed on a computer, enable the computer to execute the method described in any one of the implementations of the first to eighth aspects or the first to eighth aspects.

[0078] In the thirteenth aspect, the present application also provides a computer-readable storage medium, in which a computer program or instruction is stored. When the computer program or instruction is run on a computer, the computer executes the method described in any one of the implementations of the first to eighth aspects or the first to eighth aspects.

[0079] In the fourteenth aspect, the present application also provides a chip, which is used to read a computer program stored in a memory and execute the method described in any implementation of the first to eighth aspects or the first to eighth aspects; or, the chip includes a chip for executing the method described in any implementation of the first to eighth aspects or the first to eighth aspects.

[0080] In a fifteenth aspect, the present application further provides a chip system, which includes a processor for supporting a device to implement the method described in any one of the first to eighth aspects or the first to eighth aspects. In a possible design, the chip system also includes a memory, which is used to store programs and data necessary for the device. The chip system can be composed of a chip, or it can include a chip and other discrete devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] Figure 1 is a schematic block diagram of an example of a wireless communication system architecture applicable to the present application;

[0082] Figure 2 It is a schematic diagram of the system architecture or scenario of the application of the embodiment of the present application;

[0083] Figure 3 It is a schematic flow chart of an EDI storage method;

[0084] Figure 4 A schematic flow chart of a method for EDI subscription is shown;

[0085] Figure 5 A schematic diagram of a system architecture or scenario for application of an embodiment of the present application is shown;

[0086] Figure 6 is a schematic flow chart of a communication method 600 provided in an embodiment of the present application;

[0087] Figure 7 is a schematic flow chart of a communication 700 provided in an embodiment of the present application;

[0088] Figure 8 is a schematic flow chart of a communication method 800 provided in an embodiment of the present application;

[0089] Fig. 9 is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of the present application;

[0090] Fig.10 is a schematic diagram of the structure of a communication device 2000 provided in an embodiment of the present application;

[0091] Fig.11It is a structural diagram of a chip system 3000 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0092] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0093] The technical solution provided in this application can be applied to various communication systems, such as: fifth generation (5G) or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, wireless local area network (WLAN) system, satellite communication system, future communication system, such as the sixth generation mobile communication system, or a fusion system of multiple systems.

[0094] The technical solution provided in the present application can also be applied to machine type communication (MTC), long term evolution technology for machine-to-machine communication (LTE-M), device to device (D2D) network, machine to machine (M2M) network, Internet of things (IoT) network or other networks. Among them, IoT network can include vehicle networking, for example. Among them, the communication mode in the vehicle networking system is collectively referred to as vehicle to other devices (vehicle to X, V2X, X can represent anything), for example, the V2X can include: vehicle to vehicle (V2V) communication, vehicle to infrastructure (V2I) communication, vehicle to pedestrian communication (V2P) or vehicle to network (V2N) communication, etc.

[0095] Figure 1 This is a schematic block diagram of an example of a wireless communication system architecture applicable to the present application. As shown in the figure, the system architecture may specifically include the following network elements:

[0096] 1. User equipment (UE): can be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device.

[0097] The terminal device may be a device that provides voice / data to users, for example, a handheld device or a vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, wearable devices, terminal devices in 5G networks or future evolved public land mobile communication networks (public land mobile The embodiments of the present application do not limit this.

[0098] As an example but not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also powerful functions achieved through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and fully or partially independent of smartphones, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0099] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things.

[0100] It should be noted that the terminal device and the access network device can communicate with each other using a certain air interface technology (such as NR or LTE technology, etc.). The terminal devices can also communicate with each other using a certain air interface technology (such as NR or LTE technology, etc.).

[0101] In the embodiment of the present application, the device for realizing the function of the terminal device can be the terminal device, or it can be a device that can support the terminal device to realize the function, such as a chip system or a chip, which can be installed in the terminal device. In the embodiment of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0102] 2. (Radio) access network ((R)AN): It can provide the function of accessing the communication network for authorized users in a specific area. It can include wireless network equipment in the 3rd generation partnership project (3GPP) network and access points in non-3GPP networks. For the convenience of description, AN equipment is used below.

[0103] AN equipment can use different wireless access technologies. There are currently two types of wireless access technologies: 3GPP access technology (for example, the wireless access technology used in the third generation (3rd generation, 3G), fourth generation (4th generation, 4G) or 5G systems) and non-3GPP (non-3GPP) access technology. 3GPP access technology refers to access technology that complies with 3GPP standard specifications. For example, the access network equipment in the 5G system is called the next generation NodeBase station (gNB) or RAN equipment. Non-3GPP access technology may include air interface technology represented by access points (AP) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA), etc. AN equipment can allow terminal devices and 3GPP core networks to interconnect and communicate using non-3GPP technologies.

[0104] AN equipment can be responsible for functions such as wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side. AN equipment provides access services for terminal equipment, and then completes the control signals and user data between the terminal equipment and the core network. For example, AN equipment may include but is not limited to: macro base stations, micro base stations (also called small stations), radio network controllers (radio network controllers, RNC), node B (Node B, NB), base station controllers (base station controllers, BSC), base transceiver stations (base transceiver stations, BTS), home base stations (for example, home evolved NodeB, or home Node B, HNB), baseband units (baseband units, BBU), APs, wireless relay nodes, wireless backhaul nodes, transmission points (transmission points, TP) or transmission and reception points (transmission and reception points, TRP) in WiFi systems, etc., and can also be gNBs or transmission points (TRP or TP) in 5G (such as NR) systems, one or a group of (including multiple antenna panels) antenna panels of base stations in 5G systems, or, can also be network nodes constituting gNBs or transmission points, such as distributed units (distributed units, DU), or base stations in next-generation communication 6G systems, etc. The embodiments of the present application do not limit the specific technology and specific device form adopted by the AN device.

[0105] 3. User plane function (UPF): mainly used for receiving and forwarding user plane data. For example, UPF can receive user plane data from the data network (DN) and send the user plane data to the terminal device through the AN device. UPF can also receive user plane data from the terminal device through the AN device and forward it to the DN. The UPF directly connected to the DN through the N6 interface in the session can be called the protocol data unit (PDU) session anchor (PSA).

[0106] 4. Data network (DN): Operator network mainly used to provide data services to UE, such as the Internet, third-party service networks, IP multimedia service (IMS) networks, etc.

[0107] 5. Access and mobility management function (AMF): It is used for mobility management and access management, etc. It can be used to implement other functions of the mobility management entity (MME) except session management, such as lawful interception or access authorization / authentication.

[0108] 6. Session management function (SMF): It is mainly used for session management, allocation and management of Internet protocol (IP) addresses of terminal devices, selection of endpoints of manageable user plane functions, policy control and charging function interfaces, and downlink data notification.

[0109] 7. Network exposure function (NEF): mainly used to securely open the services and capabilities provided by the Third Generation Partnership Project (3GPP) network functions to the outside world.

[0110] 8. Policy control function (PCF): A unified policy framework used to guide network behavior and provide policy rule information to control plane functional network elements (such as AMF, SMF network elements, etc.).

[0111] 9. Application function (AF): used for data routing affected by applications, accessing network open function elements, and interacting with the policy framework for policy control.

[0112] In addition, the above network architecture also includes a network slice selection function network element (NSSF), which is used to manage information related to network slices; a network storage function network element (NRF), which is used to save descriptive information of network function entities and the services they provide, and support service discovery, network element entity discovery and other functions; a unified data repository (UDR), which is used to provide storage capabilities for contract data, policy data and capability exposure related data.

[0113] In this network architecture, the N2 interface is the interface between the RAN and AMF network elements, which is used for sending non-access stratum (NAS) messages, etc.; the N3 interface is the interface between the RAN and UPF network elements, which is used for transmitting user plane data, etc.; the N4 interface is the interface between the SMF network element and the UPF network element, which is used for transmitting information such as tunnel identification information of the N3 connection, data cache indication information, and downlink data notification messages.

[0114] It is understandable that the above-mentioned network elements or functions can be network elements in hardware devices, software functions running on dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform).

[0115] For the convenience of explanation, this application will be explained later using the access management function network element as the AMF network element, the session management network element as the SMF network element, and the policy control network element as the PCF network element as an example.

[0116] Furthermore, the AMF network element can be referred to as AMF, the SMF network element can be referred to as SMF, and the PCF network element can be referred to as PCF. That is, the AMF described later in this application can be replaced by an access management function network element, the SMF can be replaced by a session management network element, and the PCF can be replaced by a policy control network element.

[0117] For the convenience of explanation, this application takes the device as an AMF entity, an SMF entity, and a PCF entity as an example to illustrate the method for information transmission. For the implementation method where the device is a chip in an AMF entity, a chip in an SMF entity, or a chip in a PCF entity, please refer to the specific description that the devices are AMF entity, SMF entity, and PCF entity, respectively, and no repetitive introduction will be given.

[0118] exist Figure 1 In the network architecture shown, the UE is connected to the AMF through the N1 interface, the RAN is connected to the AMF through the N2 interface, and the RAN is connected to the UPF through the N3 interface.

[0119] UPFs are connected to each other through the N9 interface, and UPFs are interconnected with the data network (DN) through the N6 interface.

[0120] SMF controls UPF through N4 interface.

[0121] Figure 1 N1, N2, N3, N4, etc. are interface serial numbers. The meanings of these interface serial numbers can refer to the meanings defined in the current standard protocol and are not limited here.

[0122] It should be understood that the above-mentioned network architecture applied to the embodiments of the present application is merely an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture. The network architecture applicable to the embodiments of the present application is not limited to this. Any network architecture that can realize the functions of the above-mentioned network elements is applicable to the embodiments of the present application.

[0123] Figure 2 A system architecture or scenario diagram of an application embodiment of the present application is shown. The system can also be regarded as an introduction of support for edge computing (EC) in the above network architecture.

[0124] In order to facilitate understanding of the technical solution of the present application, a brief introduction to the protocol data unit (PDU) session is first given.

[0125] A PDU session refers to the process of communication between a user equipment UE and a data network DN. After the PDU session is established, a data transmission channel between the UE and the DN is established. Each PDU session supports a PDU session type (for example: IPv4, IPv6, IPv4v6, Ethernet, Unstructured).

[0126] In the traditional mobile network architecture and deployment before 4G, user plane devices are basically deployed in a tree topology. Uplink user messages pass through access network devices and backhaul networks, and finally access the data network through centrally deployed anchor gateways. These anchor gateways are generally deployed at higher positions in the network, such as regional center equipment rooms. This topology is relatively simple, which facilitates operators to centrally control services and process messages at anchor points. With the explosive growth of mobile service traffic, this deployment method is increasingly difficult to support the rapidly growing mobile service traffic model. On the one hand, in a network with centralized deployment of anchor gateways, the growing traffic is ultimately concentrated in the gateways and core equipment rooms, which puts higher and higher requirements on the backhaul network bandwidth, equipment room throughput, and gateway specifications; on the other hand, the long-distance backhaul network and complex transmission environment from the access point to the anchor gateway lead to large delays and jitters in user message transmission.

[0127] Based on the above background, the industry has proposed the concept of edge computing (EC). EC realizes local processing of distributed business traffic by moving UPF and business processing capabilities down to the edge of the network, avoiding excessive concentration of traffic, thereby greatly reducing the specification requirements for core computer rooms and centralized gateways, reducing the end-to-end (E2E) delay and jitter of user messages, and making the deployment of ultra-low latency services possible.

[0128] In the EC deployment scenario, some services may be provided by multiple edge application servers (EAS) deployed in the edge data network (EDN). EAS may also be referred to as application instance, edge application instance, MEC application (server), EAS function, etc. The edge application may specifically refer to an instance of a server application (e.g., social media software, augmented reality (AR), virtual reality (VR)) deployed and running on the EDN. An application may deploy one or more EAS in one or more EDNs. EAS deployed and running in different EDNs may be considered as different EAS of an application. They may share a domain name or use a different domain name from the application deployed on the cloud. The domain name may be a fully qualified domain name (FQDN), may use an arbitrary broadcast Internet protocol (IP) address, or may use different IP addresses.

[0129] The edge data network EDN can be a local data network. The local DN can also be understood as an access point of a data network that is closer to the user's attachment point. The data network refers to the service network of an operator or a third party, which can provide services such as operator services or Internet services to user devices. The local DN can be identified by a data network access identifier (DNAI) and a data network name (DNN).

[0130] The 3rd Generation Partnership Project (3GPP) standard TS23.548 defines EAS deployment information (EDI). EAS deployment information reflects the deployment of the network at the edge. Its content is shown in Table 1 below, including the address of the edge application server (EAS) deployed by the application service provider, the domain name system (DNS) server information, FQDN (full qualified domain name) and other information, as well as the 5GC (5G core network) identification of these edge services, such as DNAI, DNN corresponding to EAS, Single Network Slice Selection Assistance Information (S-NSSAI) and other information.

[0131] Table 1 EAS deployment information

[0132]

[0133]

[0134] The EAS deployment information reflects the correspondence between the above information. For example, one or more of the FQDN range, EASIP address range, and DNS server identifier corresponding to each DNAI. If the FQDN or EAS IP of a service is within the above range, it means that the service is deployed at the local edge. Any parameter in the above table is optional, that is, the EAS deployment information can have all of the above information, or only part of it, that is, a combination of any of the items. For details, please refer to 3GPP TS23.548.

[0135] When the EAS deployment information is stored in a UDR (unified data repository) network element, the SMF network element can obtain the EAS deployment information from the UDR network element. For example, the SMF provides a DNN and / or S-NSSAI to the UDR, thereby obtaining the EAS deployment information related to the DNN and / or S-NSSAI.

[0136] In the EC scenario, some services may be provided by multiple EAS deployed at the edge of the network. These EAS provide the same services and content, but have different IP addresses. When the UE needs to access a certain service, the EC scenario requires it to access an available EAS that is closer to the UE. Therefore, the UE needs to obtain the IP address of a suitable EAS. The standard also defines a new network element to assist in discovering EAS, the edge application server discovery function (EASDF), whose main function is to process domain name system (DNS) messages according to the instructions of SMF. It mainly includes: reporting DNS messages to SMF, adding DNS extended mechanisms for DNS-client-subnet option (ECS option) in DNS queries, forwarding DNS queries to DNS servers, forwarding DNS responses to UEs, etc.

[0137] Figure 3 A schematic flow chart of an EDI storage method is shown. Figure 3 As shown, the following steps are included:

[0138] S310, the AF sends an EAS deployment create / update / delete request (Nnef_EASDeployment_Create / Update / Delete Request) message to the NEF.

[0139] The request message includes the EAS deployment information shown in Table 1.

[0140] S320, the NEF processes the received EAS deployment information, for example, converts the external group identifier included in the request message into an internal group identifier.

[0141] S330, NEF sends a DM create / update / delete request (Nudr_DM_Create / Update / DeleteRequest) message to the UDR, where the request message is used to store the above EAS deployment information in the UDR.

[0142] S340, UDR returns a DM create / update / delete response (Nudr_DM_Create / Update / DeleteRequest) message to NEF.

[0143] S350, NEF returns an EAS deployment create / update / delete response (Nnef_EASDeployment_Create / Update / Delete Request) message to the AF.

[0144] Figure 4 A schematic flow chart of an EDI subscription method is shown. Figure 4 As shown, SMF can subscribe to EDI from NEF through the following steps:

[0145] S410, SMF sends an EAS deployment subscription request (Nnef_EASDeployment_SubscribeRequest) message to NEF, which is used for SMF to subscribe to EAS deployment information.

[0146] S420, NEF returns an EAS deployment subscription response (Nnef_EASDeployment_SubscribeResponse) message to SMF as NEF's response to the SMF subscription message.

[0147] S430, NEF sends an EAS deployment notification request (Nnef_EASDeployment_Notify Request) message to SMF. After NEF obtains EAS deployment information according to local configuration or from UDR, it notifies SMF of the EAS deployment information in this step.

[0148] S440, SMF returns an EAS deployment notification response (Nnef_EASDeployment_Notify Response) message to NEF as a response of SMF to the NEF notification message.

[0149] Figure 5 A schematic diagram of a system architecture or scenario for an application of an embodiment of the present application is shown. The system can be regarded as Figure 2 Based on the SMF service area, the SMF service area scenario is introduced. In this scenario, the SMF can serve one or more specific DNAIs within its service area, while for other DNAIs, the SMF cannot control the UPF in the DNAI.

[0150] like Figure 5As shown, SMF#1 and SMF#2 have different service scopes. As an example but not limitation, the service scope of SMF#1 includes DNAI#1, DNAI#2 and DNAI#3, then SMF#1 can control the UPF of DNAI#1, the UPF of DNAI#2 and the UPF of DNAI#3; the service scope of SMF#2 includes DNAI#2 and DNAI#4, then SMF#2 can control the UPF of DNAI#2 and the UPF of DNAI#4.

[0151] As an example but not limitation, the scenario can be an Enhanced Topology of SMF and UPF in 5G network (ETSUN) scenario.

[0152] Obviously, the existing MEC process relies on EAS deployment information, and SMF will obtain all EAS deployment information related to the DNN / S-NSSAI it serves. However, due to the wide deployment of edge environments (for example, a large number of EAS deployments), the amount of EAS deployment information will be large, and allowing all SMFs to obtain this EAS deployment information will generate a large load on the SMF.

[0153] In view of this, an embodiment of the present application proposes a communication method and a communication device, whereby the SMF can only obtain deployment information within its own service scope, and based on the deployment information, configure the EASDF to process the rules for DNS information related to the user device, so that each SMF only needs to serve its own area, thereby reducing the load on the SMF.

[0154] In order to facilitate understanding of the embodiments of the present application, the following points are explained:

[0155] First, in this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0156] Second, in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. In the text description of this application, the character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b and c can mean: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c. Where a, b and c can be single or multiple, respectively.

[0157] Third, in the present application, "first", "second" and various numerical numbers (e.g., #1, #2, etc.) indicate distinctions made for ease of description and are not used to limit the scope of the embodiments of the present application. For example, to distinguish between different messages, etc., rather than to describe a specific order or sequence. It should be understood that the objects described in this way can be interchanged where appropriate so as to be able to describe solutions other than the embodiments of the present application.

[0158] Fourth, in this application, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products or apparatuses.

[0159] Fifth, in this application, "used for indication" may include being used for direct indication and being used for indirect indication. When describing that a certain indication information indicates A, it may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must carry A.

[0160] The indication method involved in the embodiments of the present application should be understood to include various methods that can enable the party to be indicated to know the information to be indicated. The information to be indicated can be sent as a whole or divided into multiple sub-information and sent separately, and the sending period and / or sending time of these sub-information can be the same or different. The present application does not limit the specific sending method.

[0161] The "indication information" in the embodiments of the present application may be an explicit indication, i.e., directly indicated by signaling, or obtained by combining other rules or other parameters or by deduction according to the parameters indicated by the signaling. It may also be an implicit indication, i.e., obtained by combining other rules or other parameters or by deduction according to a rule or relationship. The present application does not make any specific limitation on this.

[0162] Sixth, in this application, "protocol" may refer to a standard protocol in the field of communications, such as 5G protocol, NR protocol, and related protocols used in future communication systems, which are not limited in this application. "Predefined" may include pre-definition. For example, protocol definition. "Preconfiguration" can be implemented by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in the device, and this application does not limit its specific implementation method.

[0163] Seventh, in this application, "storage" may refer to storage in one or more memories. One or more memories may be separately set or integrated in an encoder or decoder, a processor, or a communication device. One or more memories may also be partially separately set and partially integrated in a decoder, a processor, or a communication device. The type of memory may be any form of storage medium, which is not limited in this application.

[0164] Eighth, in this application, if there is no logical conflict, "report", "feedback" and "send" can be interchangeable.

[0165] The communication method provided in the embodiment of the present application will be described in detail below with reference to the accompanying drawings, which can be applied to the above Figure 1 In the communication system shown.

[0166] Figure 6 600 is a schematic flow chart of a communication method 600 provided in an embodiment of the present application. As shown in the figure, the method 600 includes the following steps:

[0167] S610: The second network element determines first deployment information according to the service scope of the SMF, wherein the first deployment information includes deployment information within the service scope of the SMF, wherein the deployment information may be EAS deployment information.

[0168] It should be understood that the deployment information within the service scope of the SMF can also be understood as the deployment information corresponding to the service scope of the SMF, or the deployment information included in the service scope of the SMF.

[0169] In an embodiment of the present application, the service scope of the SMF can be indicated by one or more DNAIs that the SMF can provide services.

[0170] It should be understood that the second network element can be any one of a network open function, a unified data storage repository network element, a unified data management network element, a network storage function, and an access management network element. It only requires that the network element can obtain the deployment information corresponding to the service scope of the session management network element. This application does not limit this.

[0171] It should be understood that before the service scope of the SMF of the second network element determines the first deployment information, the second network element first needs to determine the service scope of the SMF.

[0172] Optionally, the service scope information of the SMF also includes an indication information, where the indication information is used to indicate that the deployment information is obtained according to the service scope of the SMF. If there is no indication information, all deployment information is obtained according to the existing technology.

[0173] In a possible manner, before the above step S610, the method 600 further includes the following steps:

[0174] S601, SMF sends the service scope information of the SMF to the second network element, and correspondingly, the second network element receives the service scope information of the SMF.

[0175] It should be understood that the embodiments of the present application do not limit the content of the information on the service scope of the SMF.

[0176] As an example but not limitation, the information on the service scope of the SMF includes the identifier of the SMF, and the second network element can determine the deployment information within the service scope of the SMF based on the identifier of the SMF.

[0177] Based on the identifier of the SMF, the second network element may determine the deployment information within the service scope of the SMF according to the local configuration, or the second network element may obtain the service scope of the SMF from the first network element.

[0178] Optionally, when the second network element sends the identifier of the SMF to the first network element, the first network element determines whether the SMF needs to obtain deployment information according to the service scope. If necessary, the first network element replies with the service scope of the SMF. If not, the reply of the first network element does not include the service scope of the SMF, for example, includes an indication information for obtaining all deployment information (i.e., the second indication information), and the NEF obtains all deployment information.

[0179] Optionally, the information of the service scope of the SMF also includes an indication information (i.e., first indication information), which is used to indicate that the deployment information is obtained according to the service scope of the SMF. If there is no such indication information, all deployment information is obtained according to the prior art. If the identifier and indication information of the SMF are received, the second network element determines the deployment information within the service scope of the SMF based on the identifier of the SMF according to the above example.

[0180] As an example but not limitation, the service scope information of the SMF includes the service scope of the SMF, and the second network element can determine the deployment information within the service scope of the SMF based on the service scope of the SMF.

[0181] It should be understood that the embodiments of the present application do not limit the specific indication method of the service scope of the SMF.

[0182] As an example and not limitation, the service scope of the SMF is indicated by at least one DNAI included in the service scope of the SMF.

[0183] As an example and not limitation, the service scope of the SMF is indicated by a specific field, such as an ID.

[0184] The specific method of indicating the service scope of the SMF will be explained in detail later and will not be elaborated here.

[0185] Furthermore, the second network element determines the first deployment information based on the service scope of the SMF.

[0186] In a possible implementation, the local configuration of the second network element includes a correspondence between a service scope and deployment information of at least one SMF, and the second network element can determine the deployment information within the service scope of the SMF according to the local configuration.

[0187] In another possible implementation, the second network element obtains the deployment information within the service scope of the SMF through the first network element, and the first network element is used to store the correspondence between the service scope and deployment information of at least one SMF.

[0188] In this implementation, the first network element can be any one of the unified data storage repository network element UDR, the unified data management network element UDM, the network storage function NRF, and the access management network element AMF. It only needs to store the deployment information, and the embodiments of the present application are not limited to this.

[0189] As an example but not limitation, the first network element may store the correspondence between the service scope information and the deployment information of at least one SMF, thereby determining the corresponding deployment information according to the service scope information of the SMF obtained from the second network element.

[0190] As an example but not limitation, the first network element may also only store deployment information, and retrieve the stored deployment information based on one or more DNAIs within the service scope of the SMF provided by the second network element as data keys. Since the deployment information includes DNAI, the deployment information corresponding to the SMF service scope can be retrieved through DNAI.

[0191] It should be understood that the specific process of the second network element obtaining the service scope of the SMF and the specific process of determining the first deployment information based on the service scope of the SMF will be described in Figure 6 and Figure 7 The details are described in detail in , and are not repeated here.

[0192] S620, the second network element returns the first deployment information to the SMF.

[0193] S630, the SMF sends a first message to the EASDF according to the first deployment information, where the first message is used to configure a processing rule of the EASDF for a DNS message related to the user equipment.

[0194] It should be understood that the first message includes information such as at least one FQDN and at least one EASIP corresponding to the service scope of the SMF.

[0195] It should be understood that the EASDF will configure the processing rules of the UE-related DNS message according to the first message.

[0196] It should be noted that in the embodiments of the present application, IP can be replaced by address, that is, it is applicable to IP address, Medium Access Control (MAC) address, etc.

[0197] Specifically, the rule enables the EASDF to perform the following steps only when the received DNS message includes the FQDN or EAS IP corresponding to the service scope of the SMF:

[0198] S640, EASDF sends a second message to SMF, and correspondingly, SMF receives the second message.

[0199] In a possible implementation, the second message includes a first FQDN, and the first FQDN is within at least one FQDN in the first deployment information, that is, the first FQDN is within the service scope of the SMF.

[0200] In another possible implementation manner, the second message includes a first EAS IP, and the first EAS IP is within at least one EAS IP in the first deployment information, that is, the first EAS IP is within the service scope of the SMF.

[0201] In this implementation, the method 600 further includes the following steps:

[0202] S650: The SMF inserts a first user plane network element according to the second message, wherein the first user plane network element and the first EAS IP correspond to the same DNAI.

[0203] The specific process of steps S630-650 may refer to 3GPP TS23.548, which will not be described in detail here.

[0204] Based on the above solution, SMF can obtain the deployment information within its own service scope through the second network element, and configure EASDF's processing rules for UE-related DNS messages according to the deployment information, so that SMF can only provide services within its own service scope, thereby reducing the load on SMF.

[0205] Figure 7 700 is a schematic flow chart of a communication method 700 provided in an embodiment of the present application. As shown in the figure, the method 700 includes the following steps:

[0206] S710, SMF sends a request message #1 to NEF, and correspondingly, NEF receives the request message #1.

[0207] Among them, the request message #1 can be a Nnef_EASDeployment_Subscribe message.

[0208] Specifically, the request message #1 includes DNN, S-NSSAI, and at least one of the information on the service scope of the session management network element and the identifier of the session management network element in the request message. The request message #1 is used to subscribe to the deployment information corresponding to the service scope of the session management network element from the NEF.

[0209] It should be understood that the embodiments of the present application do not limit the specific indication method of the service scope information of the SMF.

[0210] In a possible implementation, the service scope information of the SMF includes at least one data network identifier DNAI. In other words, the service scope information of the session management network element is indicated by the at least one DNAI.

[0211] In this implementation, the SMF adds a DNAI field in the request message #1, wherein the field may be one or more DNAIs, thereby subscribing to the EDI corresponding to the one or more DNAIs.

[0212] The structure of EDI includes DNAI and deployment information such as FQDN, EAS IP, and APP ID corresponding to DNAI, that is, each DNAI has its corresponding deployment information. As shown in Table 2 below, the FQDN corresponding to DNAI 1 includes FQDN 1, FQDN 2, etc., and the FQDN corresponding to DNAI2 includes FQDN 2, FQDN 3, etc.; the EAS IP corresponding to DNAI 1 includes EAS IP 1, EAS IP 2, etc., and the EAS IP corresponding to DNAI2 includes EAS IP 2, EAS IP 3, etc.

[0213] Table 2 Structure of an EDI

[0214]

[0215] As an example but not limitation, the above-mentioned subscription to the EDI corresponding to the one or more DNAIs can be achieved by the following operations: for each of the one or more DNAIs, subscribe to the EDI including all deployment information of the DNAI (for example, the FQDN, EAS IP, APP ID, etc. corresponding to the DNAI and the correspondence between the DNAI and the FQDN, EAS IP, APP ID), that is, the SMF will receive the union of the deployment information corresponding to all the DNAIs in the one or more DNAIs in the subscription reply message.

[0216] In conjunction with Table 1, if the service scope of SMF includes DNAI 1, SMF obtains the information corresponding to the row of DNAI 1. If the service scope of SMF includes DNAI 1 and DNAI 2, the information of the rows corresponding to DNAI 1 and DNAI 2 are both obtained.

[0217] It should be understood that when the item is multiple DNAIs, what SMF adds in the request message #1 may be a DNAI list (DNAIlist).

[0218] In another possible implementation, the service scope information of the SMF is indicated through a specific field.

[0219] In this implementation, the SMF adds a field of SMF service area in the request message #1, thereby subscribing to the EDI corresponding to the SMF service area.

[0220] In this implementation, EDI also needs to save one piece of information, that is, all the information corresponding to the SMF service area, as shown in Table 3 below. The FQDN corresponding to SMF service area 1 includes FQDN 1, FQDN 2, etc., and the FQDN corresponding to SMF servicearea 2 includes FQDN 2, FQDN 3, etc.; the EAS IP corresponding to SMF service area 1 includes EAS IP1, EAS IP 2, etc., and the EAS IP corresponding to SMF service area 2 includes EAS IP 2, EAS IP 3, etc.; the DNAI corresponding to SMFservice area 1 includes DNAI 1, DNAI 2, etc., and the DNAI corresponding to SMF service area 2 includes DNAI 2, DNAI 3, etc. In specific implementation, the SMF service area mentioned above can be an ID used to indicate the service scope of the SMF.

[0221] Table 3 Another EDI structure

[0222]

[0223] It should be understood that in this implementation, the method 700 further includes the following steps (not shown in the figure):

[0224] SMF sends configuration information #1 to UDR, and the configuration information #1 includes the correspondence between the field of the above-mentioned SMF service scope and at least one DNAI, and the at least one DNAI corresponds to the service scope of the SMF.

[0225] Based on the above configuration information #1, NEF can obtain the EDI corresponding to the SMF service scope through UDR.

[0226] Alternatively, the UDR locally configures the EDI corresponding to the SMF service scope, for example, configuring this information on the UDR during network deployment and planning.

[0227] In yet another possible implementation, the SMF provides an SMF identifier in the request message #1, thereby subscribing to the EDI corresponding to the SMF.

[0228] It should be understood that the specific indication method of the SMF identifier is not limited in the embodiment of the present application. Exemplarily, the SMF identifier is an SMF ID / FQDN, or the SMF identifier is the address of the SMF. The following description is taken as an example that the SMF identifier is an SMF ID.

[0229] As an example but not limitation, EDI needs to save one piece of information, namely, all information corresponding to the SMF identifier, as shown in Table 4 below. The FQDN corresponding to SMF 1 includes FQDN 1, FQDN 2, etc., and the FQDN corresponding to SMF service area 2 includes FQDN2, FQDN 3, etc.; the EAS IP corresponding to SMF service area 1 includes EAS IP 1, EAS IP 2, etc., and the EAS IP corresponding to SMF servicearea 2 includes EAS IP 2, EAS IP 3, etc.; the DNAI corresponding to SMF service area 1 includes DNAI 1, DNAI 2, etc., and the DNAI corresponding to SMF service area 2 includes DNAI 2, DNAI 3, etc.

[0230] Table 4 Another EDI structure

[0231]

[0232] It should be understood that in this implementation, the method 700 further includes the following steps (not shown in the figure):

[0233] The SMF sends configuration information #2 to the UDR, where the configuration information #2 includes the correspondence between the above-mentioned SMF identifier and at least one DNAI, where the at least one DNAI corresponds to the service scope of the SMF.

[0234] Based on the above configuration information #1', NEF can obtain the EDI corresponding to the SMF DI through UDR.

[0235] Alternatively, the UDR locally configures the EDI corresponding to the SMF ID, for example, configuring this information in the UDR during network deployment and planning.

[0236] It should be understood that when the SMF carries the service scope of the SMF in the request message #1, before step S710, the above method A00 further includes the following steps:

[0237] S701, SMF determines the information of its own service scope.

[0238] It should be understood that the embodiments of the present application do not limit the specific method by which the SMF determines its own service scope information.

[0239] As an example but not limitation, the local configuration of the SMF includes information about the service scope of the SMF. For example, this information is configured on the SMF during network deployment and planning, and the SMF can determine its own service scope information based on the local configuration.

[0240] As an example but not limitation, the SMF obtains information about the service scope of the SMF through the UDR, wherein the UDR stores information about the service scope of the SMF.

[0241] Furthermore, after receiving the request message #1, the NEF performs the following steps:

[0242] S720, NEF sends a request message #2 to UDR, and correspondingly, UDR receives the request message #2.

[0243] Among them, the request message #2 can be a Nudr_DM_Subscribe message.

[0244] Specifically, the request message #2 includes the service scope information of the SMF in the request message #1 (i.e., at least one of DNAI, SMF service area, or SMF ID), and the request message #2 is used to subscribe to the EDI corresponding to the service scope information of the SMF. The service scope information of the session management network element in the request message #2 can be used as a data key to instruct the UDR to obtain the information corresponding to the data key, for example, using the data key as an index to search and obtain the corresponding EDI.

[0245] Optionally, when the request message #1 includes the identifier of the SMF, the method 700 includes the following steps (not shown in the figure):

[0246] S721, NEF sends the SMF identifier or the SMF service range identifier (ie, SMF service area) to NRF.

[0247] In a possible implementation, the NRF locally stores the identifier of the SMF and one or more DNAIs within the service scope of the SMF, so that the NEF can obtain the one or more DNAIs within the service scope of the SMF.

[0248] In another possible implementation, the NRF locally stores the SMF service area and one or more DNAIs within the service range of the SMF, so that the NEF can obtain the one or more DNAIs within the service range of the SMF.

[0249] At this time, in S720, request message #2 includes one or more DNAIs within the service scope of the SMF.

[0250] S730, UDR returns a response message #2 to NEF, and correspondingly, NEF receives the response message #2.

[0251] Among them, the request message #2 can be a Nudr_DM_Notify message.

[0252] Specifically, the UDR responds to the request message #2, the UDR determines the EDI corresponding to the service scope of the SMF according to the local storage and returns it to the NEF through the response message #2.

[0253] As an example and not a limitation, when the request message #2 includes one or more DNAI fields, the UDR uses the one or more DNAIs as data keys to index the locally stored content and determine the EDI corresponding to the one or more DNAIs.

[0254] As an example but not limitation, when the request message #2 includes the SMF service scope field, the UDR uses the SMF service scope field as a data key to index the locally stored content (including the corresponding relationship received in step S702) to determine the EDI corresponding to the SMF service scope.

[0255] It should be understood that the EDI corresponding to the service scope of the SMF includes one or more FQDNs, one or more EAS addresses, etc.

[0256] It should be understood that the correspondence can be understood as at least one DNAI corresponding to the service scope of the SMF is included in the EDI, and the at least one DNAI corresponds to the above-mentioned FQDN and / or the address of the EAS. In other words, the scope of the at least one DNAI includes the FQDN and / or the EAS deployed with the address.

[0257] As an example and not a limitation, when the request message #2 includes an SMF ID, the UDR uses the SMF ID as a data key to index the locally stored content and determine the EDI corresponding to the SMF ID. The EDI corresponding to the SMF ID includes one or more FQDNs, one or more EAS IPs, one or more DNAIs, etc.

[0258] Optionally, the request object of the above-mentioned NEF can be replaced by any one of UDM, AMF, and NRF, that is, the above-mentioned EDI is stored by any one of the UDM, AMF, and NRF, so that NEF can obtain the deployment information corresponding to the at least one DNAI from any one of UDM, AMF, and NRF, or the deployment information corresponding to the service scope of the SMF, or the deployment information corresponding to the SMF ID.

[0259] S740, NEF sends a response message #1 to SMF, and correspondingly, SMF receives the response message #1.

[0260] Among them, the response message #1 can be a Nnef_EASDeployment_Notify message.

[0261] Specifically, the response message #1 includes the EDI corresponding to the service scope of the SMF requested by the SMF in step S702.

[0262] S750, select and discover EASDF. For the specific process, please refer to the relevant description of 3GPP 23.548, which will not be repeated here.

[0263] S751, SMF sends configuration information #2 to EASDF, and correspondingly, EASDF receives the configuration information #2.

[0264] The configuration information #2 may be included in a DNS context creation request (Neasdf_DNSContext_CreateRequest) or a DNS context update request (Neasdf_DNSContext_UpdateRequest) message.

[0265] Specifically, the configuration information #2 is used to configure the rule of the EASDF so that the EASDF processes the DNS message related to the UE according to the rule. Exemplarily, the rule can be a DNS handling rule, or a DNS message handling rule, or a baseline DNS pattern, which is not limited in the embodiment of the present application.

[0266] It should be understood that the rule includes at least one of the FQDN range corresponding to the service scope of the SMF and the EAS address range corresponding to the service scope of the SMF.

[0267] Optionally, when the service scope of the SMF changes, the SMF sends configuration information #3 to the EASDF, the configuration information #3 including rules determined according to the EDI corresponding to the updated service scope of the SMF, wherein the configuration information #3 is included in a DNS context update request (Neasdf_DNSContext_Update Request) message.

[0268] S752, the UE sends a DNS Query message to the EASDF. The DNS query message may include FQDN#1.

[0269] Further, EASDF matches the FQDN#1 contained in the DNS Query with the above FQDN range, wherein the above FQDN range is determined based on the above EASDF rules. Specifically, the above FQDN range corresponds to the service range of the SMF. In other words, EASDF will determine whether the FQDN#1 is within the service range of the SMF. If so, EASDF performs the following steps.

[0270] S753, EASDF sends a DNS message report to SMF by calling the DNS context notification request (Neasdf_DNSContext_Notify Request).

[0271] S754, SMF sends a DNS context notification response (Neasdf_DNSContext_NotifyResponse) to EASDF.

[0272] S755, EASDF obtains a DNS context update request (Neasdf_DNSContext_UpdateRequest) from the UE, which includes an ECS option.

[0273] S756, EASDF sends DNS query information to the DNS server.

[0274] S757, the DNS server returns a DNS response message (DNS Response) to the EASDF, wherein the DNS Response includes EAS IP#1, wherein the EAS IP#1 corresponds to the FQDN#1.

[0275] Further, EAS matches the EAS IP#1 contained in the DNS Response with the EAS IP range, wherein the EAS IP range is determined based on the EASDF rule. Specifically, the EAS IP range corresponds to the service range of the SMF. In other words, the EASDF determines whether the EAS is within the service range of the SMF. If so, the EASDF performs the following steps.

[0276] It should be noted that the EAS should be understood to be within the service scope of the SMF. The service scope of the EAS can be understood as that the address of the EAS is within the service scope of the SMF, or that at least one DNAI corresponding to the service scope of the SMF includes the EAS, or the address of the EAS.

[0277] S758, EASDF sends a DNS message report to SMF by calling a DNS context notification request (Neasdf_DNSContext_Notify Request), and the DNS message report includes the above-mentioned EAS IP#1.

[0278] S760, EASDF inserts UL CL / BP according to the DNS message report, and instructs EASDF to forward the DNS Response to the UE, thereby completing local service discovery. The UL CL / BP corresponds to the same DNAI as the EAS IP#1.

[0279] Based on the above solution, SMF can ensure that UEs within its service range implement MEC-related functions while obtaining less EDI.

[0280] Figure 8 800 is a schematic flow chart of a communication method 800 provided in an embodiment of the present application. As shown in the figure, the method 800 includes the following steps:

[0281] S810, NEF receives deployment information from the application function network element.

[0282] It should be understood that the above deployment information is EAS deployment information, which includes at least one DNAI and the FQDN, EAS IP, APP ID and other deployment information corresponding to the at least one DNAI. For the specific content of the EAS deployment information, please refer to Table 1, which will not be repeated here.

[0283] Among them, AF can send the above deployment information to NEF by calling EAS subscription creation / update / deletion (Nnef_EASDeployment_Create / Update / Delete) message.

[0284] S820, NEF determines at least one SMF corresponding to the deployment information.

[0285] Method 1

[0286] S821, NEF determines at least one SMF corresponding to the deployment information according to local configuration.

[0287] More specifically, the NEF determines at least one SMF corresponding to each DNAI in the at least one DNAI according to the local configuration, wherein the local configuration of the NEF includes a correspondence relationship between at least one DNAI and a service scope of the at least one SMF (hereinafter referred to as correspondence relationship #2).

[0288] As an example but not limitation, the deployment information received by NEF includes DNAI 1, DNAI 2 and DNAI 3 and the corresponding deployment information of the multiple DNAIs, as shown in Table 5 below. NEF determines that DNAI 1 is within the service scope of SMF 1 and SMF 2, determines that DNAI 2 is within the service scope of SMF 2 and SMF 3, and determines that DNAI 3 is within the service scope of SMF 3 based on the service scope of SMF in the local configuration.

[0289] Table 5 Example of SMF service scope

[0290]

[0291]

[0292] Method 2

[0293] NEF requests NRF for at least one SMF corresponding to the deployment information. More specifically, NEF requests NRF for at least one SMF corresponding to each DNAI in the at least one DANI. Specifically, the steps include:

[0294] S822, NEF sends a request message #3 to NRF, and correspondingly, NRF receives the request message #3. The request message #3 includes a first DNAI, and the first DNAI is all or part of the at least one DNAI.

[0295] It should be understood that the embodiments of the present application do not limit the specific content stored in the NRF.

[0296] In one possible implementation, the NRF is used to store the correspondence between at least one DNAI and at least one SMF (hereinafter referred to as correspondence #3). The NRF can respond to at least one DNAI in the request message #3 as a data key and index the DNAI corresponding to the SMF, or the SMF corresponding to the DNAI in the correspondence #3.

[0297] As an example but not limitation, as shown in Table 6 below, the NRF can determine SMF1 and SMF2 based on DNAI 1 in request message #3, determine SMF 1 and SMF 2 based on DNAI 2, and determine SMF 3 based on DNAI 3.

[0298] Table 6 Example of correspondence #3

[0299] SMF 1 DNAI 1… SMF 2 DNAI 1, DNAI 2… SMF 3 DNAI 2, DNAI 3…

[0300] In another possible implementation, the correspondence #3 is the correspondence between the at least one DNAI and the service scope of the at least one SMF (as shown in Table 4).

[0301] In another possible implementation, the NRF is used to store multiple SMFs and multiple DNAIs.

[0302] In this implementation, if the NRF receives the identification of the SMF, it can determine and return at least one DNAI corresponding to the service scope of the SMF based on its stored content.

[0303] In this implementation, after receiving the DNAI, the NRF can determine and return relevant information of the SMF whose service scope includes the DNAI based on its stored content.

[0304] It should be understood that the present application does not limit the specific content of the SMF related information. Exemplarily, the SMF related information includes at least one of the following: SMF ID, SMF address, SMF service area.

[0305] S823, NRF returns a response message #3 to NEF, and correspondingly, NEF receives the response message #3. The response message #3 includes the identifiers of one or more SMFs, and optionally, also includes the correspondence between the identifiers of the one or more SMFs and DNAI.

[0306] It should be understood that each of the above-mentioned first DNAIs corresponds to all or part of one or more SMFs.

[0307] As an example but not limitation, the above-mentioned request message #3 includes the first DNAI#1, the first DNAI#2, and the first DNAI#3, and the above-mentioned response message #3 includes the identifiers of SMF#1 and SMF#2, wherein the first DNAI#1, the first DNAI#2, and the first DNAI#3 correspond to SMF#1, and the first DNAI#2 and the first DNAI#3 correspond to SMF#2.

[0308] Optionally, the request object of the above-mentioned NEF can be replaced by any one of UDM, AMF, and UDR, that is, the EDI corresponding to the service scope of the SMF is stored by any one of UDM, AMF, and UDR, so that NEF can obtain the deployment information corresponding to the service scope of the SMF from any one of UDM, AMF, and UDR.

[0309] Optionally, before step S820, the method 800 further includes the following steps:

[0310] S811, SMF sends configuration information #5 to NRF, which includes the correspondence between one or more DNAIs and SMF as shown in Table 5, or the correspondence between one or more DNAIs and SMF service scope as shown in Table 4 (hereinafter referred to as correspondence #2).

[0311] The embodiment of the present application does not limit the timing when the SMF sends configuration information #5 to the NRF.

[0312] In one example, the SMF sends configuration information #5 to the NRF to provide the corresponding relationship #2, or the NRF locally configures the corresponding relationship #2 when establishing the network.

[0313] As another example, when the capability changes, the SMF sends configuration information #5 to the NRF to provide the corresponding relationship #2.

[0314] Based on the above two methods, the NEF obtains at least one SMF corresponding to the deployment information, and then performs the following steps:

[0315] S830, the NEF sends configuration information #6 to the at least one SMF, and correspondingly, the at least one SMF receives the configuration information #6. The configuration information #6 received by each SMF includes deployment information corresponding to the service scope of the SMF.

[0316] As an example but not limitation, the EDI received by NEF includes DNAI#1, DNAI#2 and DNAI#3, wherein DNAI#1 is within the service scope of SMF#1 and SMF#2, DNAI#2 is within the service scope of SMF#2, and DNAI#3 is within the service scope of SMF#1 and SMF#3. Then, the configuration information #6 received by SMF#1 includes the parts of EDI corresponding to the DNAI#1 and DNAI#3, the configuration information #6 received by SMF#2 includes the parts of EDI corresponding to the DNAI#2, and the configuration information #6 received by SMF#3 includes the parts of EDI corresponding to the DNAI#1 and DNAI#3.

[0317] Optionally, before the above step S820, the method 800 further includes the following steps (not shown in the figure):

[0318] S815, SMF#1 sends a request message #4 to NEF, and correspondingly, NEF receives the request message #4.

[0319] The request message #4 includes at least one of the following: the identifier of SMF#1, the address of SMF#1, and the service area of ​​SMF#1, so as to subscribe to the NEF for one or more DNAIs corresponding to the SMF.

[0320] It should be noted that, in response to the request message #4, the NEF executes the following steps instead of steps S820 to S830.

[0321] In a possible implementation, the request message #4 includes the service scope of SMF #1, and the NEF performs the following steps:

[0322] S816, NEF determines the deployment information corresponding to the service scope of SMF#1.

[0323] Specifically, the NEF matches at least one second DNAI included in the service scope of the SMF#1 with at least one DNAI included in the EDI, thereby determining a portion of the deployment information corresponding to the at least one second DNAI.

[0324] In another possible implementation, if the request message #4 does not include the service scope of SMF #1, the NEF performs the following steps:

[0325] S817, NEF sends a request message #5 to NRF, and correspondingly, NRF receives the request message #5. The request message #5 is used to query at least one second DNAI corresponding to the SMF #1.

[0326] S818, the NRF returns a response message #5 to the NEF, and the corresponding NEF receives the response message #5, wherein the response message #5 includes the at least one second DNAI.

[0327] Further, the NEF matches the deployment information received in step S810 with the at least one second DNAI, thereby determining a portion of the deployment information corresponding to the at least one second DNAI.

[0328] Based on the above two implementations, the NEF determines a portion of the deployment information corresponding to the at least one second DNAI.

[0329] S819, NEF returns a response message #4 to SMF#1, and correspondingly, SMF#1 receives the response message #4, wherein the response message #4 includes a portion of the deployment information corresponding to at least one second DNAI.

[0330] It should be noted that NEF can also receive request messages #4 from multiple SMFs, and the request message #4 sent by each SMF only includes its own relevant information (ie, the SMF identifier, the SMF address and at least one of the SMF's service areas).

[0331] It should be understood that the relevant information of the request message #4 of each SMF in the multiple SMFs may be the same or different, and this embodiment of the present application is not limited to this.

[0332] Exemplarily, the request message #4 sent by SMF#2 includes the identifier of SMF#2 and the address of SMF#2, the request message #4 sent by SMF#3 includes the service scope of SMF#3, and the request message #4 sent by SMF#4 includes only the identifier of SMF#4.

[0333] It should be understood that the response message #4 returned by the NEF to multiple SMFs only includes the part of the deployment information that corresponds to the service scope of each SMF.

[0334] S840, local service discovery process, the specific process can refer to steps SA50 to SA60, which will not be repeated here.

[0335] It should be understood that the Figures 6 to 8The specific examples shown are only to help those skilled in the art better understand the embodiments of the present application, and are not intended to limit the scope of the embodiments of the present application. It should also be understood that the sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0336] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0337] It should also be understood that in some of the above embodiments, network elements in the existing network architecture are mainly used as examples for exemplary description (such as NEF, SMF, NRF, UDR, etc.), and it should be understood that the specific form of the network element is not limited in the embodiments of the present application. For example, network elements that can achieve the same function in the future are applicable to the embodiments of the present application.

[0338] Combination of the above Figures 1 to 8 , describes in detail the communication method side embodiment of the present application, and will be combined with Figures 9 to 11 , describes in detail the communication device side embodiment of the present application. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0339] Fig. 9 1 is a schematic diagram of the structure of the communication device 1000 provided in the embodiment of the present application. Fig. 9 As shown, the device 1000 may include a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 may communicate with the outside, and the processing unit 1020 is used for data processing. The transceiver unit 1010 may also be called a communication interface or a transceiver unit.

[0340] In one possible design, the device 1000 can implement steps or processes corresponding to the execution of the network open function in the above method embodiment, wherein the processing unit 1020 is used to execute operations related to the processing of the network open function in the above method embodiment, and the transceiver unit 1010 is used to execute operations related to the sending and receiving of the network open function in the above method embodiment.

[0341] In a possible implementation, the device 1000 may be used to perform the following actions:

[0342] As an example but not limitation, the processing unit 1020 is used to determine first deployment information according to the service scope of the session management network element, and the first deployment information includes deployment information within the service scope of the session management network element; the transceiver unit 1010 is used to send the first deployment information to the session management network element.

[0343] As an example and not limitation, the transceiver unit 1010 is used to receive deployment information from an application function; the processing unit 1020 is used to determine, based on the deployment information, at least one session management network element corresponding to the deployment information; the transceiver unit 1010 is also used to send deployment information within the service scope of each session management network element in the at least one session management network element to the at least one session management network element.

[0344] In another possible design, the device 1000 may implement steps or processes corresponding to those executed by the session management network element in the above method embodiment, wherein the transceiver unit 1010 is used to execute operations related to the sending and receiving of the session management network element in the above method embodiment, and the processing unit 1020 is used to execute operations related to the processing of the session management network element in the above method embodiment.

[0345] In a possible implementation, the device 1000 may be used to perform the following actions:

[0346] As an example but not limitation, the transceiver unit 1010 is used to send information about the service scope of the session management network element to the second network element; the transceiver unit 1010 is also used to receive deployment information within the service scope of the session management network element; the processing unit 1020 is used to send a first message to the edge application server discovery function network element based on the deployment information, and the first message is used to configure the edge application server discovery network element's processing rules for domain name system messages related to user equipment.

[0347] In another possible design, the device 1000 may implement steps or processes corresponding to those executed by the unified data repository network element in the above method embodiments, wherein the transceiver unit 1010 is used to execute operations related to sending and receiving of the unified data repository network element in the above method embodiments, and the processing unit 1020 is used to execute operations related to processing of the unified data repository network element in the above method embodiments.

[0348] In a possible implementation, the device 1000 may be used to perform the following actions:

[0349] As an example but not limitation, the transceiver unit 1010 is used to receive service scope information of a session management network element; the processing unit 1020 is used to determine deployment information within the service scope information of the session management network element based on the service scope information of the session management network element; the transceiver unit 1010 is also used to send the deployment information within the service scope information of the session management network element to the session management network element.

[0350] It should be understood that the device 1000 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the device 1000 can be specifically the transmitting end in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the transmitting end in the above-mentioned method embodiment, or the device 1000 can be specifically the receiving end in the above-mentioned embodiment, and can be used to execute the various processes and / or steps corresponding to the receiving end in the above-mentioned method embodiment. To avoid repetition, it will not be repeated here.

[0351] The apparatus 1000 of each of the above-mentioned schemes has the function of implementing the corresponding steps executed by the transmitting end in the above-mentioned method, or the apparatus 1000 of each of the above-mentioned schemes has the function of implementing the corresponding steps executed by the receiving end in the above-mentioned method. The functions can be implemented by hardware, or can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor, respectively performing the transceiver operations and related processing operations in each method embodiment.

[0352] In addition, the above-mentioned transceiver unit can also be a transceiver circuit (for example, it can include a receiving circuit and a sending circuit), and the processing unit can be a processing circuit. In an embodiment of the present application, the device 1000 can be a receiving device or a sending device in the aforementioned embodiment, or a chip or a chip system in a receiving device or a sending device, for example: a system on chip (SoC). Among them, the transceiver unit can be an input and output circuit, a communication interface. The processing unit is a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0353] Fig.102 is a schematic diagram of the structure of the communication device 2000 provided in the embodiment of the present application. Fig.10 As shown, the device 2000 includes a processor 2010 and a transceiver 2020. The processor 2010 and the transceiver 2020 communicate with each other through an internal connection path, and the processor 2010 is used to execute instructions to control the transceiver 2020 to send signals and / or receive signals.

[0354] Optionally, the device 2000 may further include a memory 2030, and the memory 2030 communicates with the processor 2010 and the transceiver 2020 through an internal connection path. The memory 2030 is used to store instructions, and the processor 2010 may execute the instructions stored in the memory 2030.

[0355] In a possible implementation, the device 2000 is used to implement various processes and steps corresponding to the network opening function in the above method embodiment.

[0356] In another possible implementation manner, the device 2000 is used to implement various processes and steps corresponding to the session management network element in the above method embodiment.

[0357] In yet another possible implementation, the device 2000 is used to implement various processes and steps corresponding to the unified data storage repository network element in the above method embodiment.

[0358] It should be understood that the device 2000 can be specifically the transmitting end or receiving end in the above embodiment, or a chip or a chip system. Correspondingly, the transceiver 2020 can be a transceiver circuit of the chip, which is not limited here. Specifically, the device 2000 can be used to execute each step and / or process corresponding to the transmitting end or receiving end in the above method embodiment.

[0359] Optionally, the memory 2030 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 2010 may be used to execute instructions stored in the memory, and when the processor 2010 executes instructions stored in the memory, the processor 2010 is used to execute the various steps and / or processes of the above-mentioned method embodiment corresponding to the transmitting end or the receiving end.

[0360] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0361] It should be noted that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The processor in the embodiment of the present application can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or the hardware and software modules in the decoding processor can be combined to perform. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0362] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory, dynamic random access memory, synchronous dynamic random access memory, double data rate synchronous dynamic random access memory, enhanced synchronous dynamic random access memory, synchronously connected dynamic random access memory, and direct memory bus random access memory. It should be noted that the memory of the system and method described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0363] Fig.11 3 is a schematic diagram of the structure of a chip system 3000 provided in an embodiment of the present application. Fig.11 As shown, the chip system 3000 (or may also be called a processing system) includes a logic circuit 3010 and an input / output interface (input / output interface) 3020 .

[0364] Among them, the logic circuit 3010 can be a processing circuit in the chip system 3000. The logic circuit 3010 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 3000 can implement the methods and functions of each embodiment of the present application. The input / output interface 3020 can be an input / output circuit in the chip system 3000, outputting information processed by the chip system 3000, or inputting data or signaling information to be processed into the chip system 3000 for processing.

[0365] As a solution, the chip system 3000 is used to implement the operations performed by the network open function in the above method embodiments.

[0366] As a solution, the chip system 3000 is used to implement the operations performed by the session management network element in the above method embodiments.

[0367] As a solution, the chip system 3000 is used to implement the operations performed by the unified data storage repository network element in the above method embodiments.

[0368] The embodiment of the present application also provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the network open function and the session management network element in the above-mentioned method embodiments are stored.

[0369] An embodiment of the present application also provides a computer program product, comprising computer program code or instructions, which, when executed on a computer, enables the computer to implement the methods executed by the network open function and the session management network element in the above-mentioned method embodiments.

[0370] An embodiment of the present application also provides a communication system, including the aforementioned network opening function and session management network element.

[0371] The explanation and beneficial effects of the relevant contents in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, which will not be repeated here. Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0372] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0373] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0374] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0375] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0376] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0377] 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 who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A communication method, characterized in that: include: The network open function determines first deployment information according to a service scope of the session management network element, where the first deployment information includes deployment information within the service scope of the session management network element; The network openness function sends the first deployment information to the session management network element.

2. The method according to claim 1, characterized in that The deployment information is edge application server deployment information.

3. The method according to claim 1 or 2, characterized in that: The service scope of the session management network element includes at least one data network access identifier.

4. The method according to any one of claims 1 to 3, characterized in that Before the network open function determines the first deployment information according to the service scope of the session management, the method further includes: The network open function obtains the service scope of the session management network element.

5. The method according to claim 4, wherein the network open function obtains the service scope of the session management network element, comprising: The network open function receives the identifier of the session management network element, the network open function sends the identifier of the session management network element to a first network element, and the network open function receives the service scope of the session management network element from the first network element; or The network open function receives the identifier of the session management network element, and the network open function determines the service scope of the session management network element according to the correspondence between the identifier of the session management network element configured locally and the service scope of the session management network element; or The network open function receives a service scope of the session management network element from the session management network element.

6. The method according to claim 5, wherein the network open function receives the identifier of the session management network element, comprising: The network opening function receives an identifier of the session management network element from the session management network element.

7. The method according to any one of claims 1 to 6, characterized in that The network open function determines the first deployment information according to the service scope of the first session management network element, including: The network open function sends the service scope of the session management network element to the unified data repository network element; The network open function receives deployment information corresponding to the service scope of the session management network element from the first network element.

8. The method according to any one of claims 4 to 7, characterized in that The first network element is one of the following: Unified data storage repository network element, unified data management network element, network storage function, access management network element.

9. The method according to any one of claims 1 to 4, characterized in that The network open function determines the first deployment information according to the service scope of the session management network element, including: The network open function determines deployment information corresponding to the service scope of the session management network element according to the service scope of the session management network element and local configuration.

10. A communication method, characterized in that: include: The session management network element sends information about the service scope of the session management network element to the second network element; The session management network element receives deployment information within a service scope of the session management network element; The session management network element sends a first message to the edge application server discovery function network element according to the deployment information, where the first message is used to configure a processing rule of the edge application server discovery network element for a domain name system message related to a user equipment.

11. The method according to claim 10, characterized in that The deployment information is edge application server EAS deployment information.

12. The method according to claim 10 or 11, characterized in that: The deployment information includes at least one fully qualified domain name and / or at least one EAS address, and the at least one fully qualified domain name and the at least one EAS address correspond to the service scope of the session management network element.

13. The method according to any one of claims 10 to 12, characterized in that The session management network element sends information about the service scope of the session management network element to the second network element, including: The session management network element sends the identifier of the session management network element and / or the service scope of the session management network element to the second network element.

14. The method according to claim 13, characterized in that The session management network element sends a service range of the session management network element to the second network element, and the method further includes: The session management network element determines the service scope of the session management network element according to local configuration; or The session management network element sends the identifier of the session management network element to the network storage function; and The session management network element receives the service scope of the session management network element from the network storage function.

15. The method according to any one of claims 10 to 14, wherein the second network element is one of the following: Network opening function, unified data storage network element, unified data management network element, network storage function, access management network element.

16. The method according to any one of claims 10 to 15, characterized in that The service scope of the session management network element includes at least one data network access identifier.

17. The method according to any one of claims 10 to 16, characterized in that The method further comprises: The session management network element receives a second message from the edge application server discovery function network element, wherein the second message includes a first fully qualified domain name and / or a first EAS address, wherein the first fully qualified domain name is included in the at least one fully qualified domain name, and the first EAS address is included in the at least one EAS address.

18. The method according to claim 17, characterized in that When the second message includes the first EAS address, the method further includes: The session management network element inserts a first user plane network element according to the second message, where the first user plane network element corresponds to the same data network access identifier as the first EAS address.

19. A communication method, characterized in that: include: The network open function receives deployment information from the application function; The network open function determines, according to the deployment information, at least one session management network element corresponding to the deployment information; The network open function sends deployment information within a service scope of each session management network element in the at least one session management network element to the at least one session management network element.

20. The method according to claim 19, characterized in that The deployment information is edge application server EAS deployment information.

21. The method according to claim 19 or 20, characterized in that The deployment information includes at least one data network access identifier DNAI.

22. The method according to claim 21, characterized in that Before the network open function sends the deployment information within the service scope of each session management network element in the at least one session management network element to the at least one session management network element, the method further includes: The network open function determines at least one first session management network element corresponding to each DNAI based on the at least one DNAI and the first correspondence, wherein the first correspondence includes the correspondence between the at least one DNAI and the service scope of the at least one session management network element, and the at least one first session management network element belongs to the at least one session management network element.

23. The method according to claim 21, characterized in that Before the network open function sends the deployment information within the service scope of each session management network element in the at least one session management network element to the at least one session management network element, the method further includes: The network open function sends one or more of the DNAIs to a third network element, and the third network element is used to store the correspondence between the at least one DNAI and the service scope of the at least one session management network element; The network open function receives an identifier of at least one second session management network element from the third network element, the service scope of the at least one second session management network element corresponds to the at least one DNAI, and the at least one second session management network element belongs to the at least one session management network element.

24. The method according to claim 23, characterized in that The third network element is one of the following: Unified data storage network element, unified data management network element, access management network element, network storage function.

25. A communication device, characterized in that: The communication device comprises a unit or a module for executing the method as claimed in any one of claims 1-9, 10-18, 19-24.

26. A communication device, characterized in that: include: A processor, the processor being coupled to a memory, the processor being configured to call computer program instructions stored in the memory to execute the method according to any one of claims 1 to 9, or the method according to any one of claims 10 to 18, or the method according to any one of claims 19 to 24.

27. A chip, characterized in that: It includes a processor and a communication interface, wherein the communication interface is used to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information to execute the method as described in any one of claims 1 to 9, or the method as described in any one of claims 10 to 18, or the method as described in any one of claims 19 to 24.

28. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, which, when executed on a computer, cause the computer to execute the method as claimed in any one of claims 1 to 9, or cause the computer to execute the method as claimed in any one of claims 10 to 18, or cause the computer to execute the method as claimed in any one of claims 19 to 24.

29. A computer program product, characterized in that The computer-readable storage medium stores instructions, which, when executed on a computer, cause the computer to execute the method as claimed in any one of claims 1 to 9, or cause the computer to execute the method as claimed in any one of claims 10 to 18, or cause the computer to execute the method as claimed in any one of claims 19 to 24.

Images