WO2023078268A1 - Dns消息的发送方法、终端及网络侧设备 - Google Patents
Dns消息的发送方法、终端及网络侧设备 Download PDFInfo
- Publication number
- WO2023078268A1 WO2023078268A1 PCT/CN2022/129091 CN2022129091W WO2023078268A1 WO 2023078268 A1 WO2023078268 A1 WO 2023078268A1 CN 2022129091 W CN2022129091 W CN 2022129091W WO 2023078268 A1 WO2023078268 A1 WO 2023078268A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- dns server
- target
- terminal
- address information
- dns
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 126
- 230000006870 function Effects 0.000 claims description 35
- 230000004044 response Effects 0.000 claims description 32
- 238000013523 data management Methods 0.000 claims description 5
- 238000004891 communication Methods 0.000 abstract description 24
- 238000010586 diagram Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 11
- 238000007726 management method Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000004590 computer program Methods 0.000 description 4
- 238000013500 data storage Methods 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 241000699670 Mus sp. Species 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Definitions
- the present application belongs to the technical field of wireless communication, and in particular relates to a method for sending a DNS message, a terminal and a network side device.
- EASDF Edge Application Server Discovery Function
- DNS Domain Name System
- the embodiment of the present application provides a method for sending a DNS message, a terminal and a network side device, which can solve the problem that the terminal cannot guarantee that the DNS request sent can be sent to the network element designated by the operator.
- a method for sending a DNS message including: a terminal acquires a message to be sent; and in the case of determining that the message to be sent is a DNS query, sends the message to be sent to an operator specified The target DNS server.
- a device for sending a DNS message including: a first acquiring module, configured to acquire a message to be sent; a first transceiver module, configured to determine that the message to be sent is a DNS query , sending the to-be-sent message to the target DNS server designated by the operator.
- a method for configuring a DNS server including: a network-side device receives indication information sent by a terminal, wherein the indication information indicates that the terminal has a target capability; the network-side device acquires an operator-specified The address information of the target DNS server; the network side device sends the address information of the target DNS server to the terminal.
- a device for configuring a DNS server including: a second transceiver module, configured to receive indication information sent by a terminal, wherein the indication information indicates that the terminal has a target capability; a second acquisition module, It is used to obtain the address information of the target DNS server specified by the operator; the second transceiver module is also used to send the address information of the target DNS server to the terminal.
- a terminal includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor.
- the program or instruction is executed by the processor The steps of the method described in the first aspect are realized.
- a sixth aspect provides a terminal, including a processor and a communication interface, wherein the processor is configured to implement the steps of the method described in the first aspect, and the communication interface is configured to communicate with a network side device.
- a network-side device includes a processor, a memory, and a program or instruction stored in the memory and operable on the processor, and the program or instruction is executed by the The processor implements the steps of the method described in the third aspect when executing.
- An eighth aspect provides a network side device, including a processor and a communication interface, wherein the processor is configured to implement the steps of the method described in the third aspect, and the communication interface is configured to communicate with a terminal.
- a readable storage medium is provided, and programs or instructions are stored on the readable storage medium, and when the programs or instructions are executed by a processor, the steps of the method described in the first aspect are realized, or the steps of the method described in the first aspect are realized, or The steps of the method described in the third aspect.
- a chip in a tenth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect steps, or realize the steps of the method as described in the third aspect.
- a computer program/program product is provided, the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement the first aspect The steps of the method, or the steps of the method for realizing the third aspect.
- the terminal acquires the message to be sent, and when it is determined that the message to be sent is a DNS query message or a DNS request message, sends the message to be sent to the target DNS server designated by the operator, Therefore, it can be ensured that the DNS query message or DNS request message of the terminal is sent to the target DNS server designated by the operator, and the services provided by the target DNS server designated by the operator can be fully utilized.
- FIG. 1 shows a schematic diagram of a wireless communication system to which an embodiment of the present application is applicable
- FIG. 2 shows a schematic flowchart of a method for sending a DNS message provided by an embodiment of the present application
- FIG. 3 shows a schematic flow diagram of a DNS server configuration method provided by an embodiment of the present application
- FIG. 4 shows a schematic structural diagram of a device for sending a DNS message provided by an embodiment of the present application
- FIG. 5 shows a schematic structural diagram of a DNS server configuration device provided by an embodiment of the present application
- FIG. 6 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
- FIG. 7 shows a schematic diagram of a hardware structure of a terminal provided in an embodiment of the present application.
- FIG. 8 shows a schematic diagram of a hardware structure of a network side device provided by an embodiment of the present application.
- first, second and the like in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific sequence or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or described herein and that "first" and “second” distinguish objects. It is usually one category, and the number of objects is not limited. For example, there may be one or more first objects.
- “and/or” in the description and claims means at least one of the connected objects, and the character “/” generally means that the related objects are an "or” relationship.
- LTE Long Term Evolution
- LTE-Advanced LTE-Advanced
- LTE-A Long Term Evolution-Advanced
- CDMA Code Division Multiple Access
- TDMA Time Division Multiple Access
- FDMA Frequency Division Multiple Access
- OFDMA Orthogonal Frequency Division Multiple Access
- SC-FDMA Single-carrier Frequency-Division Multiple Access
- system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used for the above-mentioned system and radio technology, and can also be used for other systems and radio technologies.
- NR New Radio
- the following description describes the New Radio (NR) system for illustrative purposes, and uses NR terminology in most of the following descriptions, but these techniques can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.
- 6G 6th Generation
- Fig. 1 shows a schematic diagram of a wireless communication system to which this embodiment of the present application is applicable.
- the wireless communication system includes a terminal 11 and a network side device 12 .
- the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), Pedestrian Terminal (PUE) and other terminal-side devices, and wearable devices include: smart watches, bracelets, earphones, glasses, etc.
- UE User Equipment
- the network side device 12 may be a base station or a core network, where a base station may be called a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service Basic Service Set (BSS), Extended Service Set (ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN access point, WiFi node, transmission Receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiment of this application, only The base station in the NR system is taken as an example, but the specific type of the base station is not limited.
- FIG. 2 shows a schematic flowchart of a method for sending a DNS message in an embodiment of the present application, and the method 200 can be executed by a terminal.
- the method can be executed by software or hardware installed on the terminal.
- the method may include the following steps.
- the terminal obtains the message to be sent.
- the message to be sent may be a message to be sent by the terminal through an application (APP) on the application layer.
- APP application
- the message to be sent is a DNS query (also referred to as a DNS request, or a DNS query request)
- the message to be sent is sent to the target DNS specified by the operator. server, so as to ensure that the DNS query message or DNS request message of the terminal can be sent to the target DNS server specified by the operator, such as EASDF, so that the service provided by the target DNS server specified by the operator can be fully utilized.
- the message to be sent may carry a fully qualified domain name (FQDN).
- the terminal may generate a DNS query containing the fully qualified domain name, and send the generated DNS query to the operator The target DNS server specified by the provider.
- the operator refers to an operator that provides services for the terminal.
- the operator that provides the SIM card for the terminal is the operator that provides the SIM card for the terminal.
- the method may further include: receiving address information of the target DNS server from the network side device.
- the address information of the target DNS server can be sent to the terminal by the network side device, for example, the operator can send the IP address of the DNS server designated by the network side device (such as SMF, session management function) address to the terminal.
- the terminal may receive the address information of the target DNS server from the network side device through the PCO in the NAS message.
- the terminal may set the address information of the target DNS server as the highest priority DNS server address on the operating system of the terminal, Therefore, it can be ensured that the DNS query message or the DNS request message is sent to the target DNS server.
- setting the address information of the target DNS server as the DNS server address with the highest priority on the operating system (OS) of the terminal refers to: DNS queries sent by all APPs on the terminal messages or DNS request messages, are sent to the target DNS server. Or, when all APPs on the terminal send DNS query messages or DNS request messages in the above-mentioned PDU session (that is, the PDU session used to receive the address information of the target DNS server), the target DNS server has the highest priority, Or, all the DNS query messages or DNS request messages sent by all APPs on the terminal in the above PDU session are sent to the target DNS server. Wherein, the target DNS server has the highest priority compared with other DNS configurations sent by the network side device, or the configuration saved in the terminal OS, or the DNS configuration specified by the user, and the target DNS server has the highest priority .
- the terminal may bind the address information of the target DNS server with the PDU session, so that A DNS request message or a DNS query message sent on the PDU session may be sent to the target DNS server.
- the terminal may obtain the message to be sent from the first application, determine that the message to be sent is sent on the PDU session, and then in S212, after determining the message to be sent
- the terminal may use the address information of the target DNS server as the destination address of the message to be sent, and send the message to be sent; and/or the terminal Perform DNS query and/or resolution by using the address information of the target DNS server.
- the method further includes: forwarding the address information of the target DNS server to the second application on the application layer .
- the second application can use the address of the target DNS server as the destination IP when sending the DNS query message or DNS request message, so as to send the DNS query message or DNS request message to the target DNS server.
- the second application may be an application with target authority, where the target authority is capable of receiving the address of the DNS server specified by the operator Access to Information. That is to say, in this possible implementation manner, only the address information of the target DNS server can be sent to the application that has the authority to receive the address information of the DNS server specified by the operator.
- the second application may obtain the target authority by signing a contract with the operator, or the second application may also be an application specified by the operator.
- the terminal may obtain the identification information of the application with the target authority from the network side device, and then, after receiving the address information of the specified target DNS server from the network side device, transfer the target DNS The server sends the message to the second application in the terminal that has the target authority.
- the application identification information includes at least one of the following: application (application) ID, application descriptors (Application descriptors) (may include OSID, OSappID, etc.) and the like. Wherein, the application descriptor is used to identify the application on the UE OS. application ID is used to identify the application.
- the network side device may send the address information of the target DNS server to the terminal only when it is determined that the terminal has the target capability, so that the network side device can learn that the terminal Whether it has the target capability, in this possible implementation, before receiving the address information of the specified target DNS server from the network side device, the method further includes: the terminal sends indication information to the network side device, Wherein, the indication information indicates that the terminal has the target capability.
- the target capability includes but is not limited to at least one of the following:
- the terminal deploys a first functional entity, wherein the first functional entity can send a DNS query request to a DNS server designated by the operator; for example, the terminal is configured with an edge DNS client (Edge DNS client, EDC ) or edge DNS function, the EDC or edge DNS function can send DNS query to the target DNS server specified by the operator.
- edge DNS client Edge DNS client, EDC
- edge DNS function the EDC or edge DNS function can send DNS query to the target DNS server specified by the operator.
- the terminal supports obtaining the address information of the DNS server designated by the operator from the network side device.
- the terminal supports obtaining the address information of the DNS server specified by the operator from the network side device through the PDU session, and configuring the obtained address information of the DNS server to the PDU session, that is, the address information of the obtained DNS server and the The PDU session is bound.
- the terminal supports that after obtaining the DNS configuration specified by the operator, the DNS configuration will not be modified.
- the DNS configuration will not be manually modified by the user, or will not be modified by the APP on the terminal, etc., or the DNS configuration will not be lowered in priority because the user configures a private DNS configuration (cause the operator's DNS configuration is not used).
- the terminal supports forwarding the DNS configuration formulated by the operator to an application with a target authority, wherein the target authority is an authority capable of receiving address information of a DNS server specified by the operator.
- the terminal can indicate the network-side device the applications deployed on the current terminal (for example, the terminal reports the APP list on the current terminal through a NAS message), so that the network-side device can determine which applications have the target permissions, and indicate to the terminal.
- the terminal supports forwarding the DNS response received from the DNS server designated by the operator to the application. For example, forwarding of DNS responses to applications that sent DNS query messages or DNS request messages is supported.
- the method may further include: receiving a DNS response returned by the target DNS server, wherein the DNS The response carries the address information of the target server (for example, edge application server (EAS)), and the target server is the distance from the terminal obtained by analyzing the message to be sent by the DNS server designated by the operator. Topological distance to the closest server.
- EAS edge application server
- the terminal sends the DNS query message to the target DNS server (for example, EASDF), and then EASDF obtains the IP address of the server closest to the terminal topology according to the information such as the fully qualified domain name (Fully Qualified Domain Name, FQDN) of the DNS query message, Return the IP address of the server to the terminal through DNS response.
- the target DNS server for example, EASDF
- FQDN Fully Qualified Domain Name
- the method may further include: sending the DNS The response is forwarded to the first application on the application layer, where the first application is the application that sends the message to be sent.
- a new terminal capability is proposed.
- a terminal with this terminal capability at least one of the following operations can be performed:
- the terminal can send the DNS query request to the DNS server designated by the operator (for example, EASDF), and the DNS server can respond to the DNS query with a server IP address closest to the UE terminal topology (the The IP address is obtained after the DNS server resolves the FQDN in the DNS query);
- the operator for example, EASDF
- the DNS server can respond to the DNS query with a server IP address closest to the UE terminal topology (the The IP address is obtained after the DNS server resolves the FQDN in the DNS query);
- the terminal can indicate the capability of the terminal to the network side through the NAS message; after the network side obtains the capability indication, it can issue the DNS server IP address designated by the operator and capable of discovering the edge server to the terminal through the PDU session. After receiving the DNS server address, the terminal can set the server IP address as the highest priority for the PDU session and resolve the DNS query sent by the application.
- a terminal that does not have this terminal capability it may not be able to receive the DNS server IP address designated by the operator with the edge server discovery function from the 5G core network; or discard the address after receiving the address; or, the terminal cannot use the DNS address As the DNS server address with the highest priority; or, the terminal cannot send the DNS address to the application on the application layer, or cannot ensure that the DNS query sent in the PDU session can be sent to the DNS server designated by the operator.
- the terminal with the terminal capability receives the DNS server IP address sent by the operator from the network side, and performs at least one of the following:
- the UE When the application on the UE calls the API of the first function, or when the application on the UE does not expressly indicate that it will not use the service provided by the first function, the UE must send the DNS query to the DNS query sent by the application. Send to the DNS server designated by the operator;
- UE OS can forward the DNS server IP address to the application on the application layer.
- the first function may be: EDC (EDC: edge DNS client, or edge discovery client); or, a client supported by the UE, the client can send the DNS query on the UE to to the DNS server specified by the operator; or, the client can send the DNS server IP address issued by the operator to the application layer.
- EDC edge DNS client, or edge discovery client
- the application on the terminal can use the edge computing service of the operator (that is, provide an EAS closest to the topology or route of the terminal for the application on the terminal); it can also ensure that the application on the terminal can send The DNS query is sent to the operator's DNS server.
- an embodiment of the present application further provides a method for configuring a DNS server.
- FIG. 3 shows a flowchart of a method for configuring a DNS server provided by an embodiment of the present application, and the method 300 can be executed by a network side device.
- the method can be executed by software or hardware installed on the network side device.
- the method may include the following steps.
- the network side device receives indication information sent by the terminal, where the indication information indicates that the terminal has the target capability.
- the network side device may include a session management function entity (Session Management Function, SMF) or an access and mobility management function entity (Access and Mobility Management Function, AMF).
- SMF Session Management Function
- AMF Access and Mobility Management Function
- the terminal may send the indication information to the network side device through a NAS message (NAS message).
- NAS message NAS message
- the NAS message includes but is not limited to at least one of the following:
- PDU session establishment request PDU Session Establishment Request
- PDU session modification request PDU Session Modification Request.
- the target capability includes but is not limited to at least one of the following:
- the terminal deploys a first functional entity, wherein the first functional entity can send a DNS query request to a DNS server designated by the operator; for example, the terminal is configured with an edge DNS client (Edge DNS client, EDC ) or edge DNS function, the EDC or edge DNS function can send DNS query to the target DNS server specified by the operator.
- edge DNS client Edge DNS client, EDC
- edge DNS function the EDC or edge DNS function can send DNS query to the target DNS server specified by the operator.
- the terminal supports obtaining the address information of the DNS server designated by the operator from the network side device.
- the terminal supports obtaining the address information of the DNS server specified by the operator from the network side device through the PDU session, and configuring the obtained address information of the DNS server to the PDU session, that is, the address information of the obtained DNS server and the The PDU session is bound.
- the terminal supports that after obtaining the DNS configuration specified by the operator, the DNS configuration will not be modified.
- the DNS configuration will not be manually modified by the user, or will not be modified by the APP on the terminal, etc., or the DNS configuration will not be lowered in priority because the user configures a private DNS configuration (resulting in the operator's configuration not being use).
- the terminal supports forwarding the DNS configuration formulated by the operator to an application with a target authority, wherein the target authority is an authority capable of receiving address information of a DNS server specified by the operator.
- the terminal can indicate the network-side device the applications deployed on the current terminal (for example, the terminal reports the APP list on the current terminal through a NAS message), so that the network-side device can determine which applications have the target permissions, and indicate to the terminal.
- the terminal supports forwarding the DNS response received from the DNS server designated by the operator to the application. For example, forwarding of DNS responses to applications that sent DNS query messages or DNS request messages is supported.
- the network side device acquires the address information of the target DNS server specified by the operator.
- the network-side device may acquire the PDU session anchor (PDU session anchor, PSA) based on the subscription information of the terminal, the location information of the terminal, and the user plane PDU session anchor (PSA) to which the terminal is anchored. Describe the address information of the target DNS server.
- the SMF may send a Nnrf_NFDiscovery request to a network repository function (network repository function, NRF) network element to find a target DNS server, such as EASDF.
- NRF network repository function
- the network side device sends the address information of the target DNS server to the terminal.
- the network side device may also send the application identification information having the authority to receive the address information of the target DNS server to the terminal.
- the network side device may send the address information of the target DNS server to the terminal through Protocol Configuration Options (PCO).
- PCO Protocol Configuration Options
- the network-side device may determine the application identification information that has the authority to accept the address information of the target DNS server, specifically, it may be determined by one of the following:
- the network side device sends Nudm_SDM_Get request or Nudm_SDM_Subscribe request to the unified data management entity (Unified Data Management, UDM), requesting to obtain the subscription information in UDM, UDM feedbacks to AMF or SMF: sign with the operator APP identification information;
- UDM Unified Data Management
- SMF or UDM sends Nudr_DM_Query request or Nudr_DM_Subscribe request to Unified Data Repository (UDR), requesting to obtain the contract information in UDR, and UDR feeds back to SMF or UDM: the APP identification information signed with the operator; if it is If the UDM requests the UDR, the SMF may request the UDM to obtain the APP identification information signed with the operator from the UDR.
- UDR Unified Data Repository
- the SMF After receiving the APP identification information signed with the operator fed back by UDM or UDR, the SMF sends the receivable APP identification information to the terminal. For example, it is sent to the terminal through a NAS message.
- the network side device may also receive the first indication information sent by the terminal, where the first indication information indicates the application on the terminal, and then determine the application on the terminal according to the first indication information An application capable of obtaining the address information of the target DNS server. Then the network side device sends the determined application identifier of the application to the terminal.
- the APP identification information signed with the operator may be stored in the UDR.
- data set Application data
- Data Subset subscription application ID
- DataKey SUPI
- GPSI GPSI
- Internal Group Identifier External At least one or more of the above, such as Group Identifier or application ID.
- the APP identification information signed with the operator may also be stored in the UDM.
- the method may further include at least one of the following:
- the network side device indicates a function identifier to the terminal, wherein the function identifier is used to indicate that after the operating system or chip receives the address information of the target DNS server, it will send the address information to the a functional entity corresponding to the functional identifier;
- the network-side device indicates an application identifier to the terminal, where the application identifier is used to indicate an application that can obtain the address information of the target DNS server.
- the application identification may be the APP application identification information obtained from the UDM or UDR, or may also be the application identification of the application that can obtain the address information of the target DNS server among the current applications of the terminal.
- the network side device may indicate the function identifier and/or the application identifier while sending the address information of the target DNS server to the terminal, or may send the address information of the target DNS server
- the function identifier and/or the application identifier are indicated before or after the address information of the server, which is not limited in this embodiment of the present application.
- the network side device when the network side device knows that the terminal has the target capability, it will provide the application on the terminal with the address information of the DNS server closest to the terminal topology or route and send it to the terminal, so that the terminal can Use the DNS server to perform DNS query and/or resolution, so as to fully utilize the edge computing service provided by the operator.
- the DNS message sending method provided by the embodiment of the present application may be executed by the DNS message sending device, or a control module in the DNS message sending device for executing the DNS message sending method.
- the method for sending the DNS message performed by the device for sending the DNS message is taken as an example to illustrate the device for sending the DNS message provided in the embodiment of the present application.
- Fig. 4 shows a schematic structural diagram of a device for sending a DNS message provided by the present application.
- the device mainly includes: a first obtaining module 401 for obtaining a message to be sent; a first transceiving module 402, It is used for sending the message to be sent to the target DNS server designated by the operator when it is determined that the message to be sent is a DNS query.
- the first transceiving module 402 is further configured to receive address information of the specified target DNS server from the network side device before obtaining the message to be sent.
- the apparatus may further include: a first setting module 403, configured to set the address information of the target DNS server as the DNS server address with the highest priority on the operating system of the terminal.
- the first transceiver module 402 receives the address information of the specified target DNS server from the network side device, including:
- the address information of the specified target DNS server is received from the network side device through the PDU session.
- a second setting module 404 configured to bind the address information of the target DNS server with the PDU session.
- the first obtaining module 401 obtaining the message to be sent includes: obtaining the message to be sent from the first application, and determining that the message to be sent is sent on the PDU session;
- the first transceiver module 402 sends the message to be sent to a target DNS server designated by the operator, including at least one of the following:
- the first transceiving module 402 is further configured to forward the address information of the target DNS server to the second application on the application layer.
- the second application is an application with a target authority, where the target authority is an authority capable of receiving address information of a DNS server designated by an operator.
- the first obtaining module 401 is further configured to obtain, from the network side device, the identification information of the application with the target authority before obtaining the message to be sent.
- the first transceiver module 402 is further configured to send indication information to the network side device before receiving the address information of the designated target DNS server from the network side device, wherein the indication information Indicates that the terminal has the target capability.
- the target capability includes at least one of the following:
- the terminal deploys a first functional entity, wherein the first functional entity is capable of sending a DNS query request to a DNS server designated by an operator;
- the terminal supports obtaining address information of a DNS server designated by an operator from a network side device;
- the terminal supports obtaining the address information of the DNS server specified by the operator from the network side device through the PDU session, and configuring the obtained address information of the DNS server to the PDU session;
- the terminal supports that after obtaining the DNS configuration specified by the operator, the DNS configuration will not be modified;
- the terminal supports forwarding the DNS configuration formulated by the operator to an application with a target authority, wherein the target authority is an authority capable of receiving address information of a DNS server specified by the operator;
- the terminal supports forwarding the DNS response received from the DNS server designated by the operator to the application.
- the first transceiving module 402 is further configured to receive a DNS response returned by the target DNS server after sending the message to be sent to the target DNS server designated by the operator, wherein, The DNS response carries the address information of the target server, and the target server is the server with the closest topological distance to the terminal obtained by parsing the message to be sent.
- the first transceiving module 402 is further configured to forward the DNS response to the first application on the application layer after receiving the DNS response returned by the target DNS server, wherein the The first application is an application that sends the message to be sent.
- the device for sending the DNS message in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
- the device may be a mobile terminal or a non-mobile terminal.
- the mobile terminal may include but not limited to the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machines or self-service machines, etc., are not specifically limited in this embodiment of the present application.
- the device for sending the DNS message in the embodiment of the present application may be a device with an operating system.
- the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in this embodiment of the present application.
- the device for sending DNS messages provided by the embodiment of the present application can implement various processes implemented by the terminal in the method embodiments shown in FIG. 2 to FIG. 3 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
- the DNS server configuration method provided by the embodiment of the present application may be executed by a DNS server configuration device, or a control module in the DNS server configuration device for executing the DNS server configuration method.
- the DNS server configuration device provided in the embodiment of the present application is described by taking the DNS server configuration device executing the DNS server configuration method as an example.
- FIG. 5 shows a schematic structural diagram of an apparatus for configuring a DNS server provided by an embodiment of the present application.
- the apparatus mainly includes: a second transceiver module 501 and a second acquisition module 502 .
- the second transceiver module 501 is configured to receive indication information sent by the terminal, wherein the indication information indicates that the terminal has the target capability; the second acquisition module 502 is configured to acquire the information specified by the operator. address information of the target DNS server; the second transceiver module 501 is further configured to send the address information of the target DNS server to the terminal.
- the second obtaining module 502 obtains the address information of the target DNS server specified by the operator, including: based on the subscription information of the terminal, the location information of the terminal, and the terminal's anchored
- the user plane PSA of the user plane obtains the address information of the target DNS server.
- the second transceiving module 501 sending the address information of the target DNS server to the terminal includes: sending the address information of the target DNS server to the terminal through PCO.
- the second transceiver module 501 is also used for one of the following:
- the second obtaining module 502 is also used for one of the following:
- the target capability includes at least one of the following:
- the terminal deploys a first functional entity, wherein the first functional entity is capable of sending a DNS query request to a DNS server designated by an operator;
- the terminal supports obtaining address information of a DNS server designated by an operator from a network side device;
- the terminal supports obtaining the address information of the DNS server specified by the operator from the network side device through the PDU session, and configuring the obtained address information of the DNS server to the PDU session;
- the terminal supports that after obtaining the DNS configuration formulated by the operator, the DNS configuration will not be modified;
- the terminal supports forwarding the DNS configuration formulated by the operator to an application with a target authority, wherein the target authority is an authority capable of receiving address information of a DNS server specified by the operator;
- the terminal supports forwarding the DNS response received from the DNS server designated by the operator to the application.
- the device for configuring the DNS server in the embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a network side device.
- the device for configuring the DNS server in the embodiment of the present application may be a device with an operating system.
- the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in this embodiment of the present application.
- the DNS server configuration device provided in the embodiment of the present application can implement various processes implemented by the network side equipment in the method embodiments in FIGS. 2 to 3 and achieve the same technical effect. To avoid repetition, details are not repeated here.
- this embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, and programs or instructions stored in the memory 602 and operable on the processor 601,
- a communication device 600 including a processor 601, a memory 602, and programs or instructions stored in the memory 602 and operable on the processor 601
- the communication device 600 is a terminal
- the program or instruction is executed by the processor 601
- each process of the above-mentioned DNS message sending method embodiment can be realized, and the same technical effect can be achieved.
- the communication device 600 is a network-side device
- the program or instruction is executed by the processor 601
- each process of the above DNS server configuration method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
- the embodiment of the present application also provides a terminal, including a processor and a communication interface, the processor is used to implement each process of the above-mentioned DNS message sending method embodiment, and the communication interface is used to communicate with the network side device.
- This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
- FIG. 7 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
- the terminal 700 includes, but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710, etc. .
- the terminal 700 may also include a power supply (such as a battery) for supplying power to various components, and the power supply may be logically connected to the processor 710 through the power management system, so as to manage charging, discharging, and power consumption through the power management system. Management and other functions.
- a power supply such as a battery
- the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal.
- the terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components, which will not be repeated here.
- the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042, and the graphics processor 7041 is used for the image capture device (such as the image data of the still picture or video obtained by the camera) for processing.
- the display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
- the user input unit 707 includes a touch panel 7071 and other input devices 7072 .
- the touch panel 7071 is also called a touch screen.
- the touch panel 7071 may include two parts, a touch detection device and a touch controller.
- Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, and joysticks, which will not be repeated here.
- the radio frequency unit 701 receives the downlink data from the network side device, and processes it to the processor 710; in addition, sends the uplink data to the network side device.
- the radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
- the memory 709 can be used to store software programs or instructions as well as various data.
- the memory 709 may mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area may store an operating system, an application program or instructions required by at least one function (such as a sound playback function, an image playback function, etc.) and the like.
- the memory 709 may include a high-speed random access memory, and may also include a non-transitory memory, wherein the non-transitory memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
- ROM Read-Only Memory
- PROM programmable read-only memory
- PROM erasable programmable read-only memory
- Erasable PROM Erasable PROM
- EPROM electrically erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- flash memory for example at least one disk storage device, flash memory device, or other non-transitory solid state storage device.
- the processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs or instructions, etc., Modem processors mainly handle wireless communications, such as baseband processors. It can be understood that the foregoing modem processor may not be integrated into the processor 710 .
- the processor 710 is used for the terminal to obtain the message to be sent;
- the radio frequency unit 701 is configured to send the message to be sent to a target DNS server designated by the operator when it is determined that the message to be sent is a Domain Name System DNS query.
- the terminal acquires the message to be sent, and when it is determined that the message to be sent is a DNS query message or a DNS request message, sends the message to be sent to the target DNS server designated by the operator, Therefore, it can ensure that the DNS query message or DNS request message of the terminal is sent to the target DNS server specified by the operator, and fully utilize the services provided by the target DNS server specified by the operator
- the radio frequency unit 701 is further configured to receive the address information of the target DNS server from the network side device before the terminal obtains the message to be sent.
- the processor 710 is further configured to set the address information of the target DNS server as the DNS server address with the highest priority on the operating system of the terminal.
- the radio frequency unit 701 receives the address information of the target DNS server from the network side device through a protocol data unit PDU session.
- the processor 710 is further configured to bind the address information of the target DNS server with the PDU session.
- the processor 710 acquires the message to be sent from the first application, and determines that the message to be sent is sent on the PDU session; the radio frequency unit 701 uses the address information of the target DNS server as the message to be sent The destination address of the message to be sent, sending the message to be sent; and/or, using the address information of the target DNS server to perform DNS query and/or resolution.
- the radio frequency unit 701 is further configured to forward the address information of the target DNS server to the second application on the application layer.
- the second application is an application with a target authority, wherein the target authority is an authority capable of receiving address information of a DNS server designated by an operator.
- the radio frequency unit 701 is further configured to acquire the identification information of the application with the target authority from the network side device.
- the radio frequency unit 701 is further configured to send indication information to the network side device, where the indication information indicates that the terminal has the target capability.
- the target capability includes at least one of the following:
- the terminal deploys a first functional entity, wherein the first functional entity is capable of sending a DNS query request to a DNS server designated by an operator;
- the terminal supports obtaining address information of a DNS server designated by an operator from a network side device;
- the terminal supports obtaining the address information of the DNS server specified by the operator from the network side device through the PDU session, and configuring the obtained address information of the DNS server to the PDU session;
- the terminal supports that after obtaining the DNS configuration specified by the operator, the DNS configuration will not be modified;
- the terminal supports forwarding the DNS configuration formulated by the operator to an application with a target authority, wherein the target authority is an authority capable of receiving address information of a DNS server specified by the operator;
- the terminal supports forwarding the DNS response received from the DNS server designated by the operator to the application.
- the radio frequency unit 701 is further configured to receive a DNS response returned by the target DNS server after sending the message to be sent to the target DNS server designated by the operator, wherein the DNS response carries Address information of the target server, where the target server is the server with the closest topological distance to the terminal obtained by analyzing the message to be sent.
- the radio frequency unit 701 is further configured to, after receiving the DNS response returned by the target DNS server, forward the DNS response to a first application on the application layer, where the first application sends the The application of the message to be sent.
- the embodiment of the present application also provides a network side device, including a processor and a communication interface, the processor is used to implement the various processes in the above embodiment of the method for configuring the DNS server, and the communication interface is used to communicate with the terminal.
- the network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation mode of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
- the embodiment of the present application also provides a network side device.
- the network device 800 includes: an antenna 801 , a radio frequency device 802 , and a baseband device 803 .
- the antenna 801 is connected to the radio frequency device 802 .
- the radio frequency device 802 receives information through the antenna 801, and sends the received information to the baseband device 803 for processing.
- the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802
- the radio frequency device 802 processes the received information and sends it out through the antenna 801 .
- the foregoing frequency band processing device may be located in the baseband device 803 , and the method performed by the network side device in the above embodiments may be implemented in the baseband device 803 , and the baseband device 803 includes a processor 804 and a memory 805 .
- the baseband device 803 may include at least one baseband board, for example, a plurality of chips are arranged on the baseband board, as shown in FIG.
- the baseband device 803 may further include a network interface 806 for exchanging information with the radio frequency device 802, and the interface is, for example, a common public radio interface (CPRI for short).
- CPRI common public radio interface
- the network-side device in this embodiment of the present application also includes: instructions or programs stored in the memory 805 and operable on the processor 804, and the processor 804 calls the instructions or programs in the memory 805 to execute the modules shown in FIG. 5 To avoid duplication, the method of implementation and to achieve the same technical effect will not be repeated here.
- the embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by the processor, each process of the above-mentioned DNS message sending method embodiment is realized, or the Each process of the above embodiment of the DNS server configuration method can achieve the same technical effect, so in order to avoid repetition, it will not be repeated here.
- the processor is the processor in the terminal described in the foregoing embodiments.
- the readable storage medium includes computer readable storage medium, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk, etc.
- the embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the above method for sending DNS messages.
- the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.
- the embodiment of the present application also provides a computer program/program product, the computer program/program product is stored in a non-transitory storage medium, and the program/program product is executed by at least one processor to implement the above-mentioned DNS message
- the various processes of the embodiment of the sending method, or the various processes of the embodiment of the above-mentioned DNS server configuration method can achieve the same technical effect. In order to avoid repetition, details are not repeated here.
- the term “comprising”, “comprising” or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or apparatus comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or device. Without further limitations, an element defined by the phrase “comprising a " does not preclude the presence of additional identical elements in the process, method, article, or apparatus comprising that element.
- the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved. Functions are performed, for example, the described methods may be performed in an order different from that described, and various steps may also be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.
- the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
- the technical solution of the present application can be embodied in the form of computer software products, which are stored in a storage medium (such as ROM/RAM, magnetic disk, etc.) , CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请公开了一种DNS消息的发送方法、终端及网络侧设备,属于无线通信技术领域。本申请实施例的DNS消息的发送方法,包括:终端获取待发送的消息;在确定所述待发送的消息为DNS查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
Description
相关申请的交叉引用
本申请要求在2021年11月04日提交的中国专利申请第202111302509.8号的优先权,该中国专利申请的全部内容通过引用包含于此。
本申请属于无线通信技术领域,具体涉及一种DNS消息的发送方法、终端及网络侧设备。
边缘应用服务器发现功能(Edge Application Server Discovery Function,EASDF)为用于处理终端发送来的域名系统(Domain Name System,DNS)查询请求的核心网网元。在相关技术中,EASDF是由运营商控制的具有寻找边缘服务器的网元,终端并不能获知该网元的地址信息,因此不能保证发送的DNS请求能够发送到该网元,从而导致终端不能有效利用运营商提供的寻找边缘服务器的服务。
发明内容
本申请实施例提供一种DNS消息的发送方法、终端及网络侧设备,能够解决终端不能保证发送的DNS请求能够发送到运营商指定的网元的问题。
第一方面,提供了一种DNS消息的发送方法,包括:终端获取待发送的消息;在确定所述待发送的消息为DNS查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
第二方面,提供了一种DNS消息的发送装置,包括:第一获取模块,用于获取待发送的消息;第一收发模块,用于在确定所述待发送的消息为DNS 查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
第三方面,提供了一种DNS服务器的配置方法,包括:网络侧设备接收到终端发送的指示信息,其中,所述指示信息指示所述终端具备目标能力;所述网络侧设备获取运营商指定的目标DNS服务器的地址信息;所述网络侧设备将所述目标DNS服务器的地址信息发送给所述终端。
第四方面,提供了一种DNS服务器的配置装置,包括:第二收发模块,用于接收到终端发送的指示信息,其中,所述指示信息指示所述终端具备目标能力;第二获取模块,用于获取运营商指定的目标DNS服务器的地址信息;所述第二收发模块,还用于将所述目标DNS服务器的地址信息发送给所述终端。
第五方面,提供了一种终端,该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面,提供了一种终端,包括处理器及通信接口,其中,所述处理器用于实现如第一方面所述的方法的步骤,所述通信接口用于与网络侧设备进行通信。
第七方面,提供了一种网络侧设备,该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如第三方面所述的方法的步骤。
第八方面,提供了一种网络侧设备,包括处理器及通信接口,其中,所述处理器用于实现如第三方面所述的方法的步骤,所述通信接口用于与终端进行通信。
第九方面,提供了一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤,或者实现如第三方面所述的方法的步骤。
第十方面,提供了一种芯片,所述芯片包括处理器和通信接口,所述通 信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现如第一方面所述的方法的步骤,或者实现如第三方面所述的方法的步骤。
第十一方面,提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在非瞬态的存储介质中,所述程序/程序产品被至少一个处理器执行以实现第一方面所述的方法的步骤,或者实现如第三方面所述的方法的步骤。
在本申请实施例中,终端获取待发送的消息,在确定该待发送的消息为DNS查询消息或DNS请求消息的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器,从而可以确保终端的DNS查询消息或DNS请求消息发送到运营商指定的目标DNS服务器,充分利用运营商指定的目标DNS服务器提供的服务。
图1示出本申请实施例可应用的一种无线通信系统的示意图;
图2示出本申请实施例提供的DNS消息的发送方法的一种流程示意图;
图3示出本申请实施例提供的DNS服务器的配置方法的一种流程示意图;
图4示出本申请实施例提供的DNS消息的发送装置的一种结构示意图;
图5示出本申请实施例提供的DNS服务器的配置装置的一种结构示意图;
图6示出本申请实施例提供的一种通信设备的结构示意图;
图7示出本申请实施例提供的一种终端的硬件结构示意图;
图8示出本申请实施例提供的一种网络侧设备的硬件结构示意图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行清楚描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员所获得的所有其他实施例,都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象,而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换,以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施,且“第一”、“第二”所区别的对象通常为一类,并不限定对象的个数,例如第一对象可以是一个,也可以是多个。此外,说明书以及权利要求中“和/或”表示所连接对象的至少其中之一,字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是,本申请实施例所描述的技术不限于长期演进型(Long Term Evolution,LTE)/LTE的演进(LTE-Advanced,LTE-A)系统,还可用于其他无线通信系统,诸如码分多址(Code Division Multiple Access,CDMA)、时分多址(Time Division Multiple Access,TDMA)、频分多址(Frequency Division Multiple Access,FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access,OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access,SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用,所描述的技术既可用于以上提及的系统和无线电技术,也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio,NR)系统,并且在以下大部分描述中使用NR术语,但是这些技术也可应用于NR系统应用以外的应用,如第6代(6
th Generation,6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的示意图。无线通信系统包括终端11和网络侧设备12。其中,终端11也可以称作终端设备或者用户终端(User Equipment,UE),终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant,PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer,UMPC)、移动上网装置(Mobile Internet Device,MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、 行人终端(PUE)等终端侧设备,可穿戴式设备包括:智能手表、手环、耳机、眼镜等。需要说明的是,在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网,其中,基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station,BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set,BSS)、扩展服务集(Extended Service Set,ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point,TRP)或所述领域中其他某个合适的术语,只要达到相同的技术效果,所述基站不限于特定技术词汇,需要说明的是,在本申请实施例中仅以NR系统中的基站为例,但是并不限定基站的具体类型。
下面结合附图,通过一些实施例及其应用场景对本申请实施例提供的DNS消息的发送方案进行详细地说明。
图2示出本申请实施例中的DNS消息的发送方法的一种流程示意图,该方法200可以由终端执行。换言之,所述方法可以由安装在终端上的软件或硬件来执行。如图2所示,该方法可以包括以下步骤。
S210,终端获取待发送的消息。
在本申请实施例中,所述待发送的消息可以是终端通过其应用层上的应用(APP)发送的待发送消息。
S212,在确定所述待发送的消息为DNS查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
在本申请实施例中,在确定所述待发送的消息为DNS查询(也可以称为DNS请求,或DNS查询请求)的情况下,将所述待发送的消息发送到运营商指定的目标DNS服务器,从而可以确保终端的DNS查询消息或DNS请求消息能够发送运营商指定的目标DNS服务器,例如EASDF,从而可以充分利用运营商指定的目标DNS服务器提供的服务。
在一个可能的实现方式中,所述待发送的消息可能携带全限定域名 (FQDN),在这种情况下,终端可以生成包含所述全限定域名的DNS查询,将生成的DNS查询发送到运营商指定的目标DNS服务器。
在本申请实施例中,运营商是指为所述终端提供服务的运营商。例如,为所述终端提供SIM卡的运营商。
在本申请实施例的一个可能的实现方式中,在S210之前,该方法还可以包括:从网络侧设备接收所述目标DNS服务器的地址信息。在本申请实施例中,所述目标DNS服务器的地址信息可以由网络侧设备发送给终端,例如,运营商可以通过网络侧设备(比如,SMF,会话管理功能)发送其指定的DNS服务器的IP地址给终端。
在一个可能的实现方式中,终端可以通过NAS消息中的PCO,从网络侧设备接收所述目标DNS服务器的地址信息。
可选地,终端在从网络侧设备接收所述指定的目标DNS服务器的地址信息之后,可以将所述目标DNS服务器的地址信息设置为所述终端的操作系统上优先级最高的DNS服务器地址,从而可以保证将DNS查询消息或DNS请求消息发送到所述目标DNS服务器。
在上述可选的实现方式中,将所述目标DNS服务器的地址信息设置为所述终端的操作系统(OS)上优先级最高的DNS服务器地址是指:所述终端上所有APP发送的DNS查询消息或DNS请求消息,都发送至目标DNS服务器。或者,所述终端上的所有APP在上述PDU session(即接收所述目标DNS服务器的地址信息使用的PDU会话)发送的DNS查询消息或DNS请求消息时,所述目标DNS服务器为最高优先级,或,所述终端上的所有APP在上述PDU session发送的DNS查询消息或DNS请求消息都发送至目标DNS服务器。其中,所述目标DNS服务器为最高优先级的是与网络侧设备发送的其他DNS配置,或终端OS里保存的配置,再或者用户指定的DNS配置相比,所述目标DNS服务器的优先级最高。
在一个可能的实现方式中,在通过所述PDU会话,从网络侧设备接收所 述目标DNS服务器的地址信息之后,终端可以将所述目标DNS服务器的地址信息与所述PDU会话绑定,从而可以使得在所述PDU会话上发送的DNS请求消息或DNS查询消息可以发送到所述目标DNS服务器。
在一个可能的实现方式中,在S210中,终端可以从第一应用获取所述待发送的消息,确定所述待发送的消息在所述PDU会话上发送,然后在S212中,在确定所述待发送的消息为DNS查询消息或DNS请求消息的情况下,终端可以使用所述目标DNS服务器的地址信息作为所述待发送的消息的目的地址,发送所述待发送的消息;和/或终端使用所述目标DNS服务器的地址信息进行DNS查询和/或解析。
在一个可能的实现方式中,在从网络侧设备接收所述指定的目标DNS服务器的地址信息之后,所述方法还包括:将所述目标DNS服务器的地址信息转发给应用层上的第二应用。通过该可能的实现方式,可以使得第二应用在发送DNS查询消息或DNS请求消息时,将目标DNS服务器的地址作为目的IP,从而将DNS查询消息或DNS请求消息发送至目标DNS服务器。
在一个可能的实现方式中,为了保证目标DNS服务器的服务不被非法使用,所述第二应用可以为具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限。也就是说,在该可能的实现方式中,只能将目标DNS服务器的地址信息发送给具有接收运营商指定的DNS服务器的地址信息的权限的应用。
在具体应用中,第二应用可以通过与运营商签约获得所述目标权限,或者,第二应用也可以为运营商指定的应用。
在一个可能的实现方式中,终端可以从网络侧设备获取具有所述目标权限的应用的标识信息,然后在从网络侧设备接收所述指定的目标DNS服务器的地址信息之后,将所述目标DNS服务器发送给所述终端中具有所述目标权限的第二应用。所述应用的标识信息包括以下至少一项:应用(application)ID,应用描述符(Application descriptors)(可以包括OSID、OSappID等) 等。其中,所述application descriptor用于识别在UE OS上的应用。application ID用于识别应用。
在本申请实施例的一个可能的实现方式中,网络侧设备可以确定终端具备目标能力的情况下,才将所述目标DNS服务器的地址信息发送给所述终端,为了使得网络侧设备可以获知终端是否具备所述目标能力,在该可能的实现方式中,在从网络侧设备接收所述指定的目标DNS服务器的地址信息之前,所述方法还包括:所述终端向网络侧设备发送指示信息,其中,所述指示信息指示所述终端具备目标能力。
可选地,所述目标能力包括但不限定以下至少一项:
(1)所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;例如,终端配置了边缘DNS客户端(Edge DNS client,EDC)或边缘DNS功能,所述EDC或边缘DNS功能能够将DNS查询发送至运营商指定的目标DNS服务器。
(2)所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息。
(3)所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话,即将获取的DNS服务器的地址信息与该PDU会话绑定。
(4)所述终端支持在获取运营商指定的DNS配置后,该DNS配置不会被修改。例如,该DNS配置不会被用户手动修改,或者,不会被终端上的APP修改等,或者该DNS配置不会因为用户配置了私有DNS配置而被降低优先级(导致运营商的DNS配置不被使用)。
(5)所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限。在该可能的实现方式中,所述终端可以指示网络侧设备当前终端上部署的应用(比如,终端通过NAS消息,上报当前终端上的APP列表),以 便让网络侧设备确定哪些应用具备该目标权限,并指示给终端。
(6)所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。例如,支持将DNS响应转发给发送DNS查询消息或DNS请求消息的应用。
在一个可能的实现方式中,在将所述待发送的消息发送至运营商指定的目标DNS服务器之后,所述方法还可以包括:接收所述目标DNS服务器返回的DNS响应,其中,所述DNS响应中携带有目标服务器(例如,边缘应用服务器(edge application server,EAS))的地址信息,所述目标服务器为运营商所指定的DNS服务器解析所述待发送的消息得到的距离所述终端的拓扑距离最近的服务器。
例如,终端将DNS查询消息发送至目标DNS服务器(例如,EASDF),然后EASDF根据DNS查询消息的全域名(Fully Qualified Domain Name,FQDN)等信息,得到一个距离终端拓扑最近的服务器的IP地址,将该服务器的IP地址通过DNS响应返回给终端。
在上述可能的实现方式中,在所述待发送的消息为第一应用发送的消息的情况下,在接收所述目标DNS服务器返回的DNS响应之后,所述方法还可以包括:将所述DNS响应转发给应用层上的第一应用,其中,所述第一应用为发送所述待发送的消息的应用。
在本申请实施例中,提出一种新的终端能力。对于具有该终端能力的终端,可以执行以下至少之一的操作:
(1)使用该功能,终端能够将DNS查询请求,发送至运营商指定的DNS服务器(比如,EASDF),该DNS服务器能够为该DNS查询,响应一个距离UE终端拓扑最近的服务器IP地址(该IP地址为DNS服务器解析DNS查询中FQDN后所得到);
(2)终端可以通过NAS消息,向网络侧指示该终端能力;网络侧获得该能力指示后,可通过PDU会话向终端下发运营商指定的、具有边缘服务器 发现功能的DNS服务器IP地址。终端接收该DNS服务器地址后,可以将该服务器IP地址设定为优先级最高,用于该PDU会话,并解析应用发来的DNS查询。
而对于不具备该终端能力的终端,可能将无法从5G核心网接收运营商指定的具有边缘服务器发现功能的DNS服务器IP地址;或接收该地址后丢弃该地址;或,终端无法将该DNS地址作为优先级最高的DNS服务器地址;或,终端无法将该DNS地址发送给至应用层上的应用,或无法确保一定能够将该PDU会话中发送的DNS查询,发送至运营商指定的DNS服务器。
在本申请实施例中,具备该终端能力的终端(通过某PDU会话)从网络侧接收运营商发送的DNS服务器IP地址,并执行以下至少一项:
(1)将该DNS服务器地址设定为UE OS上最高优先级的DNS服务器地址;UE上的所有的DNS查询都使用该DNS服务器进行查询和/或解析;
(2)将该DNS服务器,与该PDU会话绑定;该PDU会话内的所有DNS查询(来自应用层)都将使用该DNS服务器地址进行DNS查询/解析;
(3)该PDU会话内的所有DNS查询(来自应用层),都被发送至该DNS服务器地址(比如,EASDF IP地址);
(4)当UE上的应用调用了第一功能的API,或当UE上的应用没有明确表示不使用该第一功能所提供的服务,对于该应用发送的DNS查询,UE一定将该DNS查询发送至运营商所指定的DNS服务器;
(5)UE OS能够将该DNS服务器IP地址,转发给应用层上的应用。
在一种实施方式中,第一功能可以是:EDC(EDC:edge DNS client,或edge discovery client);或者,一种UE支持的客户端,所述客户端能够将UE上的DNS查询,发送至运营商制定的DNS服务器;或,所述客户端,能够将运营商下发的DNS服务器IP地址发送至应用层。
通过本申请实施例提供的技术方案,保证终端上应用能够使用运营商的边缘计算服务(即:为终端上的应用提供一个距离终端拓扑或路由最近的 EAS);也能保证让终端上应用发出的DNS查询,被发送至运营商的DNS服务器。
与上述DNS消息的发送方法对应,本申请实施例还提供了一种DNS服务器的配置方法。
图3示出本申请实施例提供的DNS服务器的配置方法的一种流程图,该方法300可以由网络侧设备执行。换言之,所述方法可以由安装在网络侧设备上的软件或硬件来执行。如图3所示,该方法可以包括以下步骤。
S310,网络侧设备接收到终端发送的指示信息,其中,所述指示信息指示所述终端具备目标能力。
在本申请实施例中,网络侧设备可以包括会话管理功能实体(Session Management Function,SMF)或接入和移动管理功能实体(Access and Mobility Management Function,AMF)。
例如,终端可以通过NAS消息(NAS message)向所述网络侧设备发送所述指示信息。
其中,所述NAS消息包括但不局限于以下至少一项:
(1)PDU会话建立请求:PDU Session Establishment Request;
(2)PDU会话修改请求:PDU Session Modification Request。
在一个可能的实现方式中,与方法200相似,所述目标能力包括但不限定以下至少一项:
(1)所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;例如,终端配置了边缘DNS客户端(Edge DNS client,EDC)或边缘DNS功能,所述EDC或边缘DNS功能能够将DNS查询发送至运营商指定的目标DNS服务器。
(2)所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息。
(3)所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS 服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话,即将获取的DNS服务器的地址信息与该PDU会话绑定。
(4)所述终端支持在获取运营商指定的DNS配置后,该DNS配置不会被修改。例如,该DNS配置不会被用户手动修改,或者,不会被终端上的APP修改等,或者该DNS配置不会因为用户配置了私有DNS配置而被降低优先级(导致运营商的配置不被使用)。
(5)所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限。在该可能的实现方式中,所述终端可以指示网络侧设备当前终端上部署的应用(比如,终端通过NAS消息,上报当前终端上的APP列表),以便让网络侧设备确定哪些应用具备该目标权限,并指示给终端。
(6)所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。例如,支持将DNS响应转发给发送DNS查询消息或DNS请求消息的应用。
S312,所述网络侧设备获取运营商指定的目标DNS服务器的地址信息。
在一个可能的实现方式中,网络侧设备可以基于所述终端的签约信息、所述终端的位置信息以及所述终端所锚定的用户面PDU会话锚点(PDU session Anchor,PSA),获取所述目标DNS服务器的地址信息。例如,所述SMF收到终端的能力指示信息以后,可以发送Nnrf_NFDiscovery request到网络存储库功能(network repository function,NRF)网元,寻找目标DNS服务器,比如,EASDF。
S314,所述网络侧设备将所述目标DNS服务器的地址信息发送给所述终端。
在S314中,网络侧设备也可能将具有能够接收该目标DNS服务器地址信息的权限的应用标识信息,发给终端。
例如,网络侧设备可以通过协议配置选项(Protocol Configuration Options, PCO),将所述目标DNS服务器的地址信息发送给所述终端。
在一个可能的实现方式中,网络侧设备收到终端的指示信息以后,网络侧设备可以确定所述具有能够接受目标DNS服务器地址信息权限的应用标识信息,具体可以通过以下之一确定:
1、网络侧设备(例如,AMF或SMF)发送Nudm_SDM_Get request或Nudm_SDM_Subscribe request到统一数据管理实体(Unified Data Management,UDM),请求获得UDM中的签约信息,UDM向AMF或SMF反馈:与运营商签约的APP标识信息;
2、SMF或UDM发送Nudr_DM_Query request或Nudr_DM_Subscribe request到统一数据存储库(Unified Data Repository,UDR),请求获得UDR中的签约信息,UDR向SMF或UDM反馈:与运营商签约的APP标识信息;如果是UDM向UDR请求,则所述SMF可能请求UDM,从UDR中获得与运营商签约的APP标识信息。
SMF在接收到UDM或UDR反馈的与运营商签约的APP标识信息后,将可接收的APP标识信息,发给终端。例如,通过NAS消息发送给终端。
或者,网络侧设备也可以接收所述终端发送的第一指示信息,其中,所述第一指示信息指示所述终端上的应用,然后根据所述第一指示信息,确定所述终端上的应用中能够获得所述目标DNS服务器的地址信息的应用。然后网络侧设备将确定的所述应用的应用标识发送给终端。
其中,所述与运营商签约的APP标识信息,可能保存在UDR内,一种可能的情况为:data set=Application data,Data Subset=subscription application ID,DataKey=SUPI、GPSI、Internal Group Identifier、External Group Identifier或application ID等以上至少一项或多项。
或者,所述与运营商签约的APP标识信息,也可能保存在UDM内,在UDM里,这些数据保存方式可能为:Subscription data type=Session Management Subscription data中,Data Subset=subscription application ID, Data Key=SUPI、GPSI、Internal Group Identifier、External Group Identifier或application ID等以上至少一项或多项。
在一个可能的实现方式中,在所述网络侧设备获取运营商指定的目标DNS服务器的地址信息之后,所述方法还可以包括至少以下之一:
(1)所述网络侧设备向所述终端指示功能标识,其中,所述功能标识用于指示当操作系统或芯片接收到所述目标DNS服务器的地址信息后,将发送所述地址信息给与所述功能标识对应的功能实体;
(2)所述网络侧设备向所述终端指示应用标识,其中,所述应用标识用于指示能够获得所述目标DNS服务器的地址信息的应用。其中,该应用标识可以是上述从UDM或UDR中获取的APP应用标识信息,或者,也可以是确定终端当前应用中能够获得所述目标DNS服务器的地址信息的应用的应用标识。
在上述可能的实现方式中,网络侧设备可以在向所述终端发送所述目标DNS服务器的地址信息的同时,指示所述功能标识和/或所述应用标识,也可以在发送所述目标DNS服务器的地址信息之前或之后,指示所述功能标识和/或所述应用标识,具体本申请实施例不作限定。
在本申请实施例中,网络侧设备在获知终端具备所述目标能力的情况下,将为终端上的应用提供一个距离终端拓扑或路由最近的DNS服务器的地址信息发送给终端,从而使得终端可以使用该DNS服务器进行DNS查询和/或解析,以充分利用运营商提供的边缘计算服务。
需要说明的是,本申请实施例提供的DNS消息的发送方法,执行主体可以为DNS消息的发送装置,或者,该DNS消息的发送装置中的用于执行DNS消息的发送方法的控制模块。本申请实施例中以DNS消息的发送装置执行DNS消息的发送方法为例,说明本申请实施例提供的DNS消息的发送装置。
图4示出本申请提供的DNS消息的发送装置的一种结构示意图,如图4所示,该装置主要包括:第一获取模块401,用于获取待发送的消息;第一 收发模块402,用于在确定所述待发送的消息为DNS查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
在一个可能的实现方式中,所述第一收发模块402还用于在获取待发送的消息之前,从网络侧设备接收所述指定的目标DNS服务器的地址信息。
在一个可能的实现方式中,所述装置还可以包括:第一设置模块403,用于将所述目标DNS服务器的地址信息设置为所述终端的操作系统上优先级最高的DNS服务器地址。
在一个可能的实现方式中,所述第一收发模块402从网络侧设备接收所述指定的目标DNS服务器的地址信息,包括:
通过PDU会话,从网络侧设备接收所述指定的目标DNS服务器的地址信息。
在一个可能的实现方式中,还包括:第二设置模块404,用于将所述目标DNS服务器的地址信息与所述PDU会话绑定。
在一个可能的实现方式中,所述第一获取模块401获取待发送的消息,包括:从第一应用获取所述待发送的消息,确定所述待发送的消息在所述PDU会话上发送;
所述第一收发模块402将所述待发送的消息发送至运营商指定的目标DNS服务器,包括以下至少之一:
使用所述目标DNS服务器的地址信息作为所述待发送的消息的目的地址,发送所述待发送的消息;
使用所述目标DNS服务器的地址信息进行DNS查询和/或解析。
在一个可能的实现方式中,所述第一收发模块402还用于将所述目标DNS服务器的地址信息转发给应用层上的第二应用。
在一个可能的实现方式中,所述第二应用为具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限。
在一个可能的实现方式中,所述第一获取模块401还用于在获取待发送 的消息之前,从网络侧设备获取具有所述目标权限的应用的标识信息。
在一个可能的实现方式中,所述第一收发模块402还用于在从网络侧设备接收所述指定的目标DNS服务器的地址信息之前,向网络侧设备发送指示信息,其中,所述指示信息指示终端具备目标能力。
在一个可能的实现方式中,所述目标能力包括以下至少一项:
所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;
所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息;
所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话;
所述终端支持在获取运营商指定的DNS配置后,该DNS配置不会被修改;
所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限;
所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。
在一个可能的实现方式中,所述第一收发模块402还用于在将所述待发送的消息发送至运营商指定的目标DNS服务器之后,接收所述目标DNS服务器返回的DNS响应,其中,所述DNS响应中携带有目标服务器的地址信息,所述目标服务器为解析所述待发送的消息得到的距离所述终端的拓扑距离最近的服务器。
在一个可能的实现方式中,所述第一收发模块402还用于在接收所述目标DNS服务器返回的DNS响应之后,将所述DNS响应转发给应用层上的第一应用,其中,所述第一应用为发送所述待发送的消息的应用。
本申请实施例中的DNS消息的发送装置可以是装置,也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端,也可以为非移动终端。 示例性的,移动终端可以包括但不限于上述所列举的终端11的类型,非移动终端可以为服务器、网络附属存储器(Network Attached Storage,NAS)、个人计算机(personal computer,PC)、电视机(television,TV)、柜员机或者自助机等,本申请实施例不作具体限定。
本申请实施例中的DNS消息的发送装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统,可以为ios操作系统,还可以为其他可能的操作系统,本申请实施例不作具体限定。
本申请实施例提供的DNS消息的发送装置能够实现图2至图3的方法实施例中终端实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
需要说明的是,本申请实施例提供的DNS服务器的配置方法,执行主体可以为DNS服务器的配置装置,或者,该DNS服务器的配置装置中的用于执行DNS服务器的配置方法的控制模块。本申请实施例中以DNS服务器的配置装置执行DNS服务器的配置方法为例,说明本申请实施例提供的DNS服务器的配置装置。
图5示出本申请实施例提供的DNS服务器的配置装置的一种结构示意图,如图5所示,该装置主要包括:第二收发模块501和第二获取模块502。
在本申请实施例中,第二收发模块501,用于接收到终端发送的指示信息,其中,所述指示信息指示所述终端具备目标能力;第二获取模块502,用于获取运营商指定的目标DNS服务器的地址信息;所述第二收发模块501,还用于将所述目标DNS服务器的地址信息发送给所述终端。
在一个可能的实现方式中,所述第二获取模块502获取运营商指定的目标DNS服务器的地址信息,包括:基于所述终端的签约信息、所述终端的位置信息以及所述终端所锚定的用户面PSA,获取所述目标DNS服务器的地址信息。
在一个可能的实现方式中,所述第二收发模块501将所述目标DNS服务 器的地址信息发送给所述终端,包括:通过PCO,将所述目标DNS服务器的地址信息发送给所述终端。
在一个可能的实现方式中,所述第二收发模块501还用于以下之一:
向所述终端指示功能标识,其中,所述功能标识用于指示当操作系统或芯片接收到所述目标DNS服务器的地址信息后,将发送所述地址信息给与所述功能标识对应的功能实体;
向所述终端指示应用标识,其中,所述应用标识用于指示能够获得所述目标DNS服务器的地址信息的应用。
在一个可能的实现方式中,所述第二获取模块502还用于以下之一:
接收所述终端发送的第一指示信息,其中,所述第一指示信息指示所述终端上的应用;根据所述第一指示信息,确定所述终端上的应用中能够获得所述目标DNS服务器的地址信息的应用;
从统一数据管理实体UDM或统一数据存储库UDR获取与运营商签约的应用标识。
在一个可能的实现方式中,所述目标能力包括以下至少一项:
所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;
所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息;
所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话;
所述终端支持在获取运营商制定的DNS配置后,该DNS配置不会被修改;
所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限;
所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。
本申请实施例中的DNS服务器的配置装置可以是装置,也可以是网络侧设备中的部件、集成电路、或芯片。
本申请实施例中的DNS服务器的配置装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统,可以为ios操作系统,还可以为其他可能的操作系统,本申请实施例不作具体限定。
本申请实施例提供的DNS服务器的配置装置能够实现图2至图3的方法实施例中网络侧设备实现的各个过程,并达到相同的技术效果,为避免重复,这里不再赘述。
可选的,如图6所示,本申请实施例还提供一种通信设备600,包括处理器601,存储器602,存储在存储器602上并可在所述处理器601上运行的程序或指令,例如,该通信设备600为终端时,该程序或指令被处理器601执行时实现上述DNS消息的发送方法实施例的各个过程,且能达到相同的技术效果。该通信设备600为网络侧设备时,该程序或指令被处理器601执行时实现上述DNS服务器的配置方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
本申请实施例还提供一种终端,包括处理器和通信接口,处理器用于实现上述DNS消息的发送方法实施例的各个过程,通信接口用于与网络侧设备进行通信。该终端实施例是与上述终端侧方法实施例对应的,上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中,且能达到相同的技术效果。具体地,图7为实现本申请实施例的一种终端的硬件结构示意图。
该终端700包括但不限于:射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709、以及处理器710等部件。
本领域技术人员可以理解,终端700还可以包括给各个部件供电的电源(比如电池),电源可以通过电源管理系统与处理器710逻辑相连,从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终 端结构并不构成对终端的限定,终端可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置,在此不再赘述。
应理解的是,本申请实施例中,输入单元704可以包括图形处理器(Graphics Processing Unit,GPU)7041和麦克风7042,图形处理器7041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061,可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072。触控面板7071,也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆,在此不再赘述。
本申请实施例中,射频单元701将来自网络侧设备的下行数据接收后,给处理器710处理;另外,将上行的数据发送给网络侧设备。通常,射频单元701包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令区和存储数据区,其中,存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外,存储器709可以包括高速随机存取存储器,还可以包括非瞬态性存储器,其中,非瞬态性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非瞬态性固态存储器件。
处理器710可包括一个或多个处理单元;可选的,处理器710可集成应用处理器和调制解调处理器,其中,应用处理器主要处理操作系统、用户界 面和应用程序或指令等,调制解调处理器主要处理无线通信,如基带处理器。可以理解的是,上述调制解调处理器也可以不集成到处理器710中。
其中,处理器710,用于终端获取待发送的消息;
射频单元701,用于在确定所述待发送的消息为域名系统DNS查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
在本申请实施例中,终端获取待发送的消息,在确定该待发送的消息为DNS查询消息或DNS请求消息的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器,从而可以确保终端的DNS查询消息或DNS请求消息发送到运营商指定的目标DNS服务器,充分利用运营商指定的目标DNS服务器提供的服务
可选的,射频单元701,还用于在所述终端获取待发送的消息之前,从网络侧设备接收所述目标DNS服务器的地址信息。
可选的,处理器710,还用于将所述目标DNS服务器的地址信息设置为所述终端的操作系统上优先级最高的DNS服务器地址。
可选的,射频单元701通过协议数据单元PDU会话,从网络侧设备接收所述目标DNS服务器的地址信息。
可选的,处理器710,还用于将所述目标DNS服务器的地址信息与所述PDU会话绑定。
可选的,处理器710从第一应用获取所述待发送的消息,确定所述待发送的消息在所述PDU会话上发送;射频单元701使用所述目标DNS服务器的地址信息作为所述待发送的消息的目的地址,发送所述待发送的消息;和/或,使用所述目标DNS服务器的地址信息进行DNS查询和/或解析。
可选的,射频单元701,还用于将所述目标DNS服务器的地址信息转发给应用层上的第二应用。
可选的,所述第二应用为具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限。
可选的,射频单元701,还用于从网络侧设备获取具有所述目标权限的应用的标识信息。
可选的,射频单元701,还用于向网络侧设备发送指示信息,其中,所述指示信息指示所述终端具备目标能力。
可选的,所述目标能力包括以下至少一项:
所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;
所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息;
所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话;
所述终端支持在获取运营商指定的DNS配置后,该DNS配置不会被修改;
所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限;
所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。
可选的,射频单元701,还用于在将所述待发送的消息发送至运营商指定的目标DNS服务器之后,接收所述目标DNS服务器返回的DNS响应,其中,所述DNS响应中携带有目标服务器的地址信息,所述目标服务器为解析所述待发送的消息得到的距离所述终端的拓扑距离最近的服务器。
可选的,射频单元701,还用于在接收所述目标DNS服务器返回的DNS响应之后,将所述DNS响应转发给应用层上的第一应用,其中,所述第一应用为发送所述待发送的消息的应用。
本申请实施例还提供一种网络侧设备,包括处理器和通信接口,处理器用于实现上述DNS服务器的配置方法实施例的各个过程,通信接口用于与终端进行通信。该网络侧设备实施例是与上述网络侧设备方法实施例对应的, 上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中,且能达到相同的技术效果。
具体地,本申请实施例还提供了一种网络侧设备。如图8所示,该网络设备800包括:天线801、射频装置802、基带装置803。天线801与射频装置802连接。在上行方向上,射频装置802通过天线801接收信息,将接收的信息发送给基带装置803进行处理。在下行方向上,基带装置803对要发送的信息进行处理,并发送给射频装置802,射频装置802对收到的信息进行处理后经过天线801发送出去。
上述频带处理装置可以位于基带装置803中,以上实施例中网络侧设备执行的方法可以在基带装置803中实现,该基带装置803包括处理器804和存储器805。
基带装置803例如可以包括至少一个基带板,该基带板上设置有多个芯片,如图8所示,其中一个芯片例如为处理器804,与存储器805连接,以调用存储器805中的程序,执行以上方法实施例中所示的网络设备操作。
该基带装置803还可以包括网络接口806,用于与射频装置802交互信息,该接口例如为通用公共无线接口(common public radio interface,简称CPRI)。
具体地,本申请实施例的网络侧设备还包括:存储在存储器805上并可在处理器804上运行的指令或程序,处理器804调用存储器805中的指令或程序执行图5所示各模块执行的方法,并达到相同的技术效果,为避免重复,故不在此赘述。
本申请实施例还提供一种可读存储介质,所述可读存储介质上存储有程序或指令,该程序或指令被处理器执行时实现上述DNS消息的发送方法实施例的各个过程,或者实现上述DNS服务器的配置方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
其中,所述处理器为上述实施例中所述的终端中的处理器。所述可读存 储介质,包括计算机可读存储介质,如计算机只读存储器(Read-Only Memory,ROM)、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片,所述芯片包括处理器和通信接口,所述通信接口和所述处理器耦合,所述处理器用于运行程序或指令,实现上述DNS消息的发送方法实施例的各个过程,或者实现上述DNS服务器的配置方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
本申请实施例还提供了一种计算机程序/程序产品,所述计算机程序/程序产品被存储在非瞬态的存储介质中,所述程序/程序产品被至少一个处理器执行以实现上述DNS消息的发送方法实施例的各个过程,或者实现上述DNS服务器的配置方法实施例的各个过程,且能达到相同的技术效果,为避免重复,这里不再赘述。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外,需要指出的是,本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能,还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能,例如,可以按不同于所描述的次序来执行所描述的方法,并且还可以添加、省去、或组合各种步骤。另外,参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述,但是本申请并不局限于上述的具体实施方式,上述的具体实施方式仅仅是示意性的,而不是限制性的,本领域的普通技术人员在本申请的启示下,在不脱离本申请宗旨和权利要求所保护的范围情况下,还可做出很多形式,均属于本申请的保护之内。
Claims (39)
- 一种DNS消息的发送方法,包括:终端获取待发送的消息;在确定所述待发送的消息为域名系统DNS查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
- 根据权利要求1所述的方法,其中,在所述终端获取待发送的消息之前,所述方法还包括:从网络侧设备接收所述目标DNS服务器的地址信息。
- 根据权利要求2所述的方法,其中,在从网络侧设备接收所述指定的目标DNS服务器的地址信息之后,所述方法还包括:将所述目标DNS服务器的地址信息设置为所述终端的操作系统上优先级最高的DNS服务器地址。
- 根据权利要求2所述的方法,其中,从网络侧设备接收所述目标DNS服务器的地址信息,包括:所述终端通过协议数据单元PDU会话,从网络侧设备接收所述目标DNS服务器的地址信息。
- 根据权利要求4所述的方法,其中,在从网络侧设备接收所述目标DNS服务器的地址信息之后,所述方法还包括:将所述目标DNS服务器的地址信息与所述PDU会话绑定。
- 根据权利要求5所述的方法,其中,终端获取待发送的消息,包括:从第一应用获取所述待发送的消息,确定所述待发送的消息在所述PDU会话上发送;将所述待发送的消息发送至运营商指定的目标DNS服务器,包括以下至少之一:使用所述目标DNS服务器的地址信息作为所述待发送的消息的目的地址,发送所述待发送的消息;使用所述目标DNS服务器的地址信息进行DNS查询和/或解析。
- 根据权利要求2所述的方法,其中,在从网络侧设备接收所述指定的目标DNS服务器的地址信息之后,所述方法还包括:将所述目标DNS服务器的地址信息转发给应用层上的第二应用。
- 根据权利要求7所述的方法,其中,所述第二应用为具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限。
- 根据权利要求8所述的方法,其中,在所述终端获取待发送的消息之前,所述方法还包括:从网络侧设备获取具有所述目标权限的应用的标识信息。
- 根据权利要求2至9中任一项所述的方法,其中,在从网络侧设备接收所述指定的目标DNS服务器的地址信息之前,所述方法还包括:所述终端向网络侧设备发送指示信息,其中,所述指示信息指示所述终端具备目标能力,所述目标能力包括以下至少一项:所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息;所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话;所述终端支持在获取运营商指定的DNS配置后,该DNS配置不会被修改;所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限;所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。
- 根据权利要求1至9中任一项所述的方法,其中,在将所述待发送的消息发送至运营商指定的目标DNS服务器之后,所述方法还包括:接收所述目标DNS服务器返回的DNS响应,其中,所述DNS响应中携 带有目标服务器的地址信息,所述目标服务器为解析所述待发送的消息得到的距离所述终端的拓扑距离最近的服务器。
- 根据权利要求11所述的方法,其中,在接收所述目标DNS服务器返回的DNS响应之后,所述方法还包括:将所述DNS响应转发给应用层上的第一应用,其中,所述第一应用为发送所述待发送的消息的应用。
- 一种DNS服务器的配置方法,包括:网络侧设备接收到终端发送的指示信息,其中,所述指示信息指示所述终端具备目标能力;所述网络侧设备获取运营商指定的目标DNS服务器的地址信息;所述网络侧设备将所述目标DNS服务器的地址信息发送给所述终端。
- 根据权利要求13所述的方法,其中,所述网络侧设备获取运营商指定的目标DNS服务器的地址信息,包括:所述网络侧设备基于所述终端的签约信息、所述终端的位置信息以及所述终端所锚定的用户面PDU会话锚点PSA,获取所述目标DNS服务器的地址信息。
- 根据权利要求13所述的方法,其中,所述网络侧设备将所述目标DNS服务器的地址信息发送给所述终端,包括:所述网络侧设备通过协议配置选项PCO,将所述目标DNS服务器的地址信息发送给所述终端。
- 根据权利要求15所述的方法,其中,在所述网络侧设备获取运营商指定的目标DNS服务器的地址信息之后,所述方法还包括至少以下之一:所述网络侧设备向所述终端指示功能标识,其中,所述功能标识用于指示当操作系统或芯片接收到所述目标DNS服务器的地址信息后,将发送所述地址信息给与所述功能标识对应的功能实体;所述网络侧设备向所述终端指示应用标识,其中,所述应用标识用于指示能够获得所述目标DNS服务器的地址信息的应用。
- 根据权利要求16所述的方法,其中,在所述网络侧设备向所述终端指示应用标识之前,所述方法还包括以下之一:所述网络侧设备接收所述终端发送的第一指示信息,其中,所述第一指示信息指示所述终端上的应用;根据所述第一指示信息,确定所述终端上的应用中能够获得所述目标DNS服务器的地址信息的应用;所述网络侧设备从统一数据管理实体UDM或统一数据存储库UDR获取与运营商签约的应用标识。
- 根据权利要求13至17中任一项所述的方法,其中,所述目标能力包括以下至少一项:所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息;所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话;所述终端支持在获取运营商制定的DNS配置后,该DNS配置不会被修改;所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限;所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。
- 一种DNS消息的发送装置,包括:第一获取模块,用于获取待发送的消息;第一收发模块,用于在确定所述待发送的消息为DNS查询的情况下,将所述待发送的消息发送至运营商指定的目标DNS服务器。
- 根据权利要求19所述的装置,其中,所述第一收发模块还用于在获取待发送的消息之前,从网络侧设备接收所述指定的目标DNS服务器的地址信息。
- 根据权利要求20所述的装置,其中,所述装置还包括:第一设置模块,用于将所述目标DNS服务器的地址信息设置为所述终端的操作系统上优先级最高的DNS服务器地址。
- 根据权利要求20所述的装置,其中,所述第一收发模块从网络侧设备接收所述指定的目标DNS服务器的地址信息,包括:通过PDU会话,从网络侧设备接收所述指定的目标DNS服务器的地址信息。
- 根据权利要求22所述的装置,其中,还包括:第二设置模块,用于将所述目标DNS服务器的地址信息与所述PDU会话绑定。
- 根据权利要求23所述的装置,其中,所述第一获取模块获取待发送的消息,包括:从第一应用获取所述待发送的消息,确定所述待发送的消息在所述PDU会话上发送;所述第一收发模块将所述待发送的消息发送至运营商指定的目标DNS服务器,包括以下至少之一:使用所述目标DNS服务器的地址信息作为所述待发送的消息的目的地址,发送所述待发送的消息;使用所述目标DNS服务器的地址信息进行DNS查询和/或解析。
- 根据权利要求20所述的装置,其中,所述第一收发模块还用于将所述目标DNS服务器的地址信息转发给应用层上的第二应用。
- 根据权利要求25所述的装置,其中,所述第二应用为具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限。
- 根据权利要求26所述的装置,其中,所述第一获取模块还用于在获取待发送的消息之前,从网络侧设备获取具有所述目标权限的应用的标识信息。
- 根据权利要求20至27中任一项所述的装置,其中,所述第一收发 模块还用于在从网络侧设备接收所述指定的目标DNS服务器的地址信息之前,向网络侧设备发送指示信息,其中,所述指示信息指示终端具备目标能力,所述目标能力包括以下至少一项:所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息;所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话;所述终端支持在获取运营商指定的DNS配置后,该DNS配置不会被修改;所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限能够为接收运营商指定的DNS服务器的地址信息的权限;所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。
- 根据权利要求19至27中任一项所述的装置,其中,所述第一收发模块还用于在将所述待发送的消息发送至运营商指定的目标DNS服务器之后,接收所述目标DNS服务器返回的DNS响应,其中,所述DNS响应中携带有目标服务器的地址信息,所述目标服务器为解析所述待发送的消息得到的距离所述终端的拓扑距离最近的服务器。
- 根据权利要求29所述的装置,其中,所述第一收发模块还用于在接收所述目标DNS服务器返回的DNS响应之后,将所述DNS响应转发给应用层上的第一应用,其中,所述第一应用为发送所述待发送的消息的应用。
- 一种DNS服务器的配置装置,包括:第二收发模块,用于接收到终端发送的指示信息,其中,所述指示信息指示所述终端具备目标能力;第二获取模块,用于获取运营商指定的目标DNS服务器的地址信息;所述第二收发模块,还用于将所述目标DNS服务器的地址信息发送给所 述终端。
- 根据权利要求31所述的装置,其中,所述第二获取模块获取运营商指定的目标DNS服务器的地址信息,包括:基于所述终端的签约信息、所述终端的位置信息以及所述终端所锚定的用户面PSA,获取所述目标DNS服务器的地址信息。
- 根据权利要求31所述的装置,其中,所述第二收发模块将所述目标DNS服务器的地址信息发送给所述终端,包括:通过PCO,将所述目标DNS服务器的地址信息发送给所述终端。
- 根据权利要求33所述的装置,其中,所述第二收发模块还用于以下之一:向所述终端指示功能标识,其中,所述功能标识用于指示当操作系统或芯片接收到所述目标DNS服务器的地址信息后,将发送所述地址信息给与所述功能标识对应的功能实体;向所述终端指示应用标识,其中,所述应用标识用于指示能够获得所述目标DNS服务器的地址信息的应用。
- 根据权利要求34所述的装置,其中,所述第二获取模块还用于以下之一:接收所述终端发送的第一指示信息,其中,所述第一指示信息指示所述终端上的应用;根据所述第一指示信息,确定所述终端上的应用中能够获得所述目标DNS服务器的地址信息的应用;从统一数据管理实体UDM或统一数据存储库UDR获取与运营商签约的应用标识。
- 根据权利要求31至35中任一项所述的装置,其中,所述目标能力包括以下至少一项:所述终端部署了第一功能实体,其中,所述第一功能实体能够将DNS查询请求发送到运营商指定的DNS服务器;所述终端支持从网络侧设备获取运营商指定的DNS服务器的地址信息;所述终端支持通过PDU会话从网络侧设备获取运营商指定的DNS服务器的地址信息,并将获取的DNS服务器的地址信息配置给所述PDU会话;所述终端支持在获取运营商制定的DNS配置后,该DNS配置不会被修改;所述终端支持将运营商制定的DNS配置转发给具有目标权限的应用,其中,所述目标权限为能够接收运营商指定的DNS服务器的地址信息的权限;所述终端支持将从运营商指定的DNS服务器收到的DNS响应转发给应用。
- 一种终端,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求1至12任一项所述的DNS消息的发送方法的步骤。
- 一种网络侧设备,包括处理器,存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令,所述程序或指令被所述处理器执行时实现如权利要求13至18任一项所述的DNS服务器的配置方法的步骤。
- 一种可读存储介质,所述可读存储介质上存储程序或指令,所述程序或指令被处理器执行时实现如权利要求1至12任一项所述的DNS消息的发送方法的步骤,或者实现如权利要求13至18任一项所述的DNS服务器的配置方法的步骤。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202111302509.8 | 2021-11-04 | ||
CN202111302509.8A CN116074383A (zh) | 2021-11-04 | 2021-11-04 | Dns消息的发送方法、终端及网络侧设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023078268A1 true WO2023078268A1 (zh) | 2023-05-11 |
Family
ID=86170469
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/129091 WO2023078268A1 (zh) | 2021-11-04 | 2022-11-01 | Dns消息的发送方法、终端及网络侧设备 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN116074383A (zh) |
WO (1) | WO2023078268A1 (zh) |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112468604A (zh) * | 2019-09-06 | 2021-03-09 | 华为技术有限公司 | 域名系统服务器的确定方法、请求处理方法和装置、系统 |
CN113115480A (zh) * | 2021-04-02 | 2021-07-13 | 腾讯科技(深圳)有限公司 | 地址信息发送方法、获取方法、装置、设备及介质 |
CN113206894A (zh) * | 2021-05-08 | 2021-08-03 | 腾讯科技(深圳)有限公司 | Dns服务器的发现方法、装置、计算机设备及存储介质 |
-
2021
- 2021-11-04 CN CN202111302509.8A patent/CN116074383A/zh active Pending
-
2022
- 2022-11-01 WO PCT/CN2022/129091 patent/WO2023078268A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112468604A (zh) * | 2019-09-06 | 2021-03-09 | 华为技术有限公司 | 域名系统服务器的确定方法、请求处理方法和装置、系统 |
CN113115480A (zh) * | 2021-04-02 | 2021-07-13 | 腾讯科技(深圳)有限公司 | 地址信息发送方法、获取方法、装置、设备及介质 |
CN113206894A (zh) * | 2021-05-08 | 2021-08-03 | 腾讯科技(深圳)有限公司 | Dns服务器的发现方法、装置、计算机设备及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN116074383A (zh) | 2023-05-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10979887B2 (en) | Access method, network device, terminal device, and AMF device | |
US11297666B2 (en) | Electronic device and method for forming Wi-Fi direct group thereof | |
KR101785470B1 (ko) | 단말 검색 방법 및 장치 | |
WO2018228517A1 (zh) | 一种接入控制的方法、网络设备以及终端设备 | |
WO2023093609A1 (zh) | 物联网设备的会话建立方法及装置 | |
EP2842356B1 (en) | Updating subscription information | |
WO2022268067A1 (zh) | 定位方法、装置及相关设备 | |
WO2023025017A1 (zh) | 传输处理方法、装置及设备 | |
WO2022228438A1 (zh) | 信息处理方法、装置及通信设备 | |
WO2023078268A1 (zh) | Dns消息的发送方法、终端及网络侧设备 | |
WO2022213921A1 (zh) | Ntn场景下的波束测量方法、配置方法及相关设备 | |
WO2022068903A1 (zh) | 网络选择方法、信息发送方法、信息获取方法及装置 | |
WO2022127679A1 (zh) | 信息传输方法、装置、终端及网络侧设备 | |
WO2022247703A1 (zh) | 服务器地址的处理方法及装置 | |
WO2023005898A1 (zh) | 多终端联合会话管理方法、网络侧设备及终端 | |
WO2024022370A1 (zh) | 信息获取和发送方法、服务器访问和会话建立方法及设备 | |
WO2024120285A1 (zh) | 信息传输方法、装置、终端及网络侧设备 | |
WO2023280022A1 (zh) | 多路径通信方法和设备 | |
WO2023202603A1 (zh) | 条件切换的配置方法、终端及网络侧设备 | |
WO2023241614A1 (zh) | Ims服务获取方法、终端、网络侧设备及介质 | |
WO2024017167A1 (zh) | 规则处理方法、通信设备及网络侧设备 | |
WO2024032499A1 (zh) | Dns查询方法及通信设备 | |
WO2024022398A1 (zh) | 托管网络的选网信息的获取方法、终端及网络侧设备 | |
WO2023125856A1 (zh) | Ursp规则的监控和上报方法、装置、终端及网元 | |
WO2024061143A1 (zh) | 应用程序确定方法、装置、终端及服务器 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22889291 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2022889291 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2022889291 Country of ref document: EP Effective date: 20240604 |