Access method and device, communication equipment and storage medium

Abstract

The invention discloses an access method and device, communication equipment and a storage medium. The method comprises: a BRAS receiving a first request sent by a terminal device; the first request is used for requesting a first record of the first domain name; sending a second request to the domain name server, and receiving a second response corresponding to the second request sent by the domain name server; the second request comprises a first prefix identifier corresponding to the BRAS, the second request is used for requesting a second record of the first domain name, and the second response comprises the second record; the second record comprises an address translation prefix corresponding to the first prefix identifier; and a first response corresponding to the first request is sent to the terminal device, the first response comprises a first record, the first record comprises an address conversion prefix corresponding to the first prefix identifier, and the first record is used for modifying the IPv4 destination address into the IPv6 destination address by the terminal device so as to initiate access to the IPv6 destination address.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to an access method, an apparatus, a communication device and a storage medium. Background Art

[0002] With the continuous advancement of the Internet Protocol version 6 (IPv6) transformation and the continuous evolution of new IPv6 technologies, the global IPv6 traffic has increased significantly. Although IPv6 has been basically implemented end-to-end, there are still some content ends that have not completed the IPv6 transformation and can only provide Internet Protocol version 4 (IPv4) services. In this scenario, the Network Address Translation (NAT) method is needed to enable IPv6 terminals to access IPv4 servers.

[0003] At present, the existing network address translation method can be implemented by deploying NAT64 and Domain Name System (DNS) 64. However, in the existing network, in order to meet the needs of traffic diversion, security management and control, different users are required to obtain different NAT64 prefixes and different data access paths in many scenarios. However, in the existing technical solutions based on NAT64 / DNS64, the NAT64 prefix returned by DNS64 for all users who initiate domain name access and used for network address translation is the same. Therefore, the existing network address translation method cannot realize the access of IPv6 terminals to IPv4 servers in multiple access path scenarios. Summary of the invention

[0004] In order to solve the existing technical problems, the embodiments of the present invention provide an access method, an apparatus, a communication device and a storage medium.

[0005] To achieve the above object, the technical solution of the embodiment of the present invention is implemented as follows:

[0006] In a first aspect, an embodiment of the present invention provides an access method, which is applied to a broadband access server BRAS, and includes: receiving a first request sent by a terminal device; the first request is used to request a first record of a first domain name;

[0007] Sending a second request to a domain name server, and receiving a second response corresponding to the second request sent by the domain name server; the second request includes a first prefix identifier corresponding to the BRAS, the second request is used to request a second record of the first domain name, and the second response includes the second record; the second record includes an address translation prefix corresponding to the first prefix identifier;

[0008] A first response corresponding to the first request is sent to the terminal device, wherein the first response includes the first record, wherein the first record includes an address conversion prefix corresponding to the first prefix identifier, and the first record is used by the terminal device to modify an Internet Communication Protocol version 4 (IPv4) destination address to an Internet Communication Protocol version 6 (IPv6) destination address to initiate access to the IPv6 destination address.

[0009] In the above scheme, before receiving the first request sent by the terminal device, the method also includes: configuring a first policy, the first policy is used to indicate sending a corresponding address conversion prefix to the terminal device, and the first policy includes a prefix identifier corresponding to each BRAS.

[0010] In the above scheme, the first request includes the first domain name related to the IPv4 target address and the first type identifier representing the first record; and / or the second request includes the first prefix identifier, the second type identifier representing the second record and the first domain name.

[0011] In the above scheme, sending the second request to the domain name server includes: according to the first strategy, modifying the first type identifier in the first request to the second type identifier, adding the first prefix identifier, generating a second request, and sending the second request to the domain name server.

[0012] In the above solution, the second response also includes the first prefix identifier and the first domain name.

[0013] In the above scheme, sending the first response corresponding to the first request to the terminal device includes: modifying the second type identifier in the second response to the first type identifier, deleting the first prefix identifier, generating a first response corresponding to the first request, and sending the first response to the terminal device.

[0014] In a second aspect, an embodiment of the present invention provides an access method, which is applied to a domain name server, and the method includes: receiving a second request sent by a broadband access server BRAS, wherein the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of a first domain name;

[0015] Obtain a second record corresponding to the first prefix identifier, and send a second response to the BRAS, where the second response includes the second record; the second record includes the address conversion prefix corresponding to the first prefix identifier.

[0016] In the above solution, the second request includes the first prefix identifier, a second type identifier indicating the second record, and the first domain name; and / or,

[0017] The second response also includes the first prefix identifier and the first domain name.

[0018] In the above solution, before receiving the second request sent by the broadband access server BRAS, the method further includes: configuring a plurality of second records, wherein different second records correspond to different prefix identifiers.

[0019] In the above solution, obtaining the second record corresponding to the first prefix identifier includes: determining the second record corresponding to the first prefix identifier from among the multiple prefix identifiers according to the second request.

[0020] In a third aspect, an embodiment of the present invention provides an access method, which is applied to a terminal device, and includes: sending a first request to a broadband access server BRAS; the first request is used to request a first record of a first domain name;

[0021] receiving a first response corresponding to the first request sent by the broadband access server BRAS, wherein the first response includes the first record, and the first record includes an address prefix identifier corresponding to the first prefix identifier corresponding to the BRAS;

[0022] The IPv4 destination address is modified into an IPv6 destination address according to the address prefix identifier to initiate access to the IPv6 destination address.

[0023] In the above solution, the first request includes the first domain name related to the IPv4 target address and a first type identifier representing the first record.

[0024] In the above scheme, the first designated bit and the second designated bit of the first record are respectively the address conversion prefix and the first prefix identifier; modifying the IPv4 destination address to the IPv6 destination address according to the address conversion prefix includes: the terminal device extracts the first designated bit in the first record as the address conversion prefix; combining the network address conversion prefix and the IPv4 destination address to obtain the IPv6 destination address.

[0025] In a fourth aspect, an embodiment of the present invention further provides an access device, which is applied to a broadband access server BRAS, and comprises: a first receiving unit and a first sending unit; wherein,

[0026] The first receiving unit is used to receive a first request sent by a terminal device; the first request is used to request a first record of a first domain name;

[0027] The first sending unit is used to send a second request to the domain name server, where the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of the first domain name;

[0028] The first receiving unit is further configured to receive a second response corresponding to the second request sent by the domain name server; the second response includes the second record; the second record includes the address translation prefix corresponding to the first prefix identifier;

[0029] The first receiving unit is also used to send a first response corresponding to the first request to the terminal device, the first response includes the first record, the first record includes the address conversion prefix corresponding to the first prefix identifier, and the first record is used by the terminal device to modify the IPv4 destination address to the IPv6 destination address to initiate access to the IPv6 destination address.

[0030] In a fifth aspect, an embodiment of the present invention further provides an access device, which is applied to a domain name server, and comprises: a second receiving unit, a second processing unit, and a second sending unit; wherein,

[0031] The second receiving unit is used to receive a second request sent by a broadband access server BRAS, where the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of the first domain name;

[0032] The second processing unit is used to obtain a second record corresponding to the first prefix identifier;

[0033] The second sending unit is used to send a second response to the broadband access server BRAS, where the second response includes the second record; the second record includes an address prefix identifier corresponding to the first prefix identifier.

[0034] In a sixth aspect, an embodiment of the present invention further provides an access device, which is applied to a terminal device, and comprises: a communication unit and a third processing unit; wherein:

[0035] The communication unit is configured to send a first request to a broadband access server BRAS; the first request is used to request a first record of a first domain name; and is also configured to receive a first response corresponding to the first request sent by the broadband access server BRAS, the first response including the first record, and the first record including an address translation prefix corresponding to a first prefix identifier corresponding to the BRAS;

[0036] The third processing unit is used to modify the IPv4 destination address into an IPv6 destination address according to the address translation prefix, so as to initiate access to the IPv6 destination address.

[0037] In the seventh aspect, an embodiment of the present invention further provides a communication device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps of the method described in the first aspect, the second aspect, or the third aspect of the embodiment of the present invention are implemented.

[0038] In an eighth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect, the second aspect or the third aspect of the embodiment of the present invention.

[0039] In a ninth aspect, an embodiment of the present invention further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the method described in the first aspect, the second aspect or the third aspect of the embodiment of the present invention.

[0040] An access method, apparatus, communication equipment and storage medium provided by an embodiment of the present invention receive a first request for a first record of a first domain name sent by a terminal device through a BRAS, and obtain a second response including a second record by sending a second request to a domain name server, wherein the second record includes an address conversion prefix corresponding to a first prefix identifier corresponding to the BRAS; and then send a first response including the first record to the terminal device, wherein the first record includes an address conversion prefix corresponding to the first prefix identifier, so that the terminal device can modify an IPv4 destination address to an IPv6 destination address, thereby initiating access to the IPv6 destination address, thereby realizing access of the IPv6 terminal to the IPv4 server in a multi-access path scenario. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 A schematic diagram of the system architecture of the existing access method;

[0042] Figure 2 It is a schematic diagram of the interaction process of the relevant access technology;

[0043] Figure 3is a schematic diagram of a multi-access path scenario;

[0044] Figure 4 The access method of the embodiment of the present invention is shown in FIG. Figure 1 ;

[0045] Figure 5 Format of OPT RR extended by the embodiment of the present invention Figure 1 ;

[0046] Figure 6 The access method of the embodiment of the present invention is shown in FIG. Figure 2 ;

[0047] Figure 7 Format of OPT RR extended by the embodiment of the present invention Figure 2 ;

[0048] Figure 8 A schematic diagram of the format of the second record for implementing the present invention;

[0049] Fig. 9 A schematic diagram of a flow chart of an access method according to an embodiment of the present invention;

[0050] Fig.10 A schematic diagram of an interactive process of an access method according to an embodiment of the present invention;

[0051] Fig.11 The structure diagram of the access device according to the embodiment of the present invention is shown in FIG. Figure 1 ;

[0052] Fig.12 The structure diagram of the access device according to the embodiment of the present invention is shown in FIG. Figure 2 ;

[0053] Fig.13 The structure diagram of the access device according to the embodiment of the present invention is shown in FIG. Figure 3 ;

[0054] Fig.14 The figure is a schematic diagram of the hardware structure of the communication device according to the embodiment of the present invention. DETAILED DESCRIPTION

[0055] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0056] The technical solution of the embodiment of the present invention can be applied to various communication systems, for example: a global system of mobile communication (GSM) system, a long term evolution (LTE) system or a 5G system, etc. Optionally, the 5G system or 5G network may also be referred to as a new radio (NR) system or NR network.

[0057] Exemplarily, the communication system applied in the embodiment of the present invention may include a network device and a terminal device (also referred to as a terminal, a communication terminal, etc.); the network device may be a device that communicates with the terminal device. Among them, the network device can provide communication coverage within a certain area, and can communicate with terminals located in the area. Optionally, the network device may be a base station in each communication system, such as an evolved base station (eNB, Evolutional Node B) in an LTE system, and a base station (gNB) in a 5G system or an NR system.

[0058] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. The communication device may include a network device and a terminal with communication function, and the network device and the terminal device may be the specific devices described above, which will not be repeated here; the communication device may also include other devices in the communication system, such as a network controller, a mobile management entity and other network entities, which are not limited in the embodiment of the present invention.

[0059] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0060] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and need not be used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable in appropriate circumstances, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, the process, method, system, product or equipment comprising a series of steps or units need not be limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0061] Before describing the access method according to the embodiment of the present invention in detail, the related technology is briefly described first.

[0062] With the rapid growth of Internet users and Internet devices such as smartphones and personal computers around the world, IPv4 addresses are rapidly consumed, resulting in the exhaustion of IPv4 addresses, which restricts the development of the Internet. IPv6 is the next generation Internet protocol designed to replace the current version of IPv4 protocol. The launch of IPv6 solves the problem of IPv4 address exhaustion.

[0063] However, in recent years, with the continuous advancement of IPv6 transformation and the continuous evolution of new IPv6 technologies, the global IPv6 traffic has increased significantly. Although IPv6 has been basically implemented end-to-end, there are still some content terminals that have not completed IPv6 transformation and can only provide IPv4 services. In this scenario where IPv6 terminals need to access IPv4 servers, the existing related technologies need to be implemented by deploying NAT64 and DNS64.

[0064] Figure 1 A schematic diagram of the system architecture of the existing access method; Figure 1 As shown, IPv6 terminal ( Figure 1 The customer premise equipment (CPE) in the network accesses the IPv6 network through the broadband access server (BRAS). The domain name (i.e., source address) of the IPv6 terminal is, for example, 2001::1. Through the cooperation between the deployed DNS64 and NAT64, the destination IPv4 address (200.1.1.1) of the IPv4 server accessing the IPv4 network is converted, so that the IPv6 terminal can access the IPv4 server based on the destination IPv6 address obtained after the conversion.

[0065] However, the above technical solution relies on the IPv6 terminal to first initiate a DNS request for the domain name of the IPv4 server to obtain the destination IPv6 address (synthesized by the NAT64 prefix and the destination IPv4 address). However, in the current network, some applications directly access the destination IPv4 address without going through DNS. In this case, the above technical solution cannot be used to obtain the destination IPv6 address synthesized by the NAT64 prefix. In other words, in this scenario, the above NAT64 / DNS64 technical solution cannot be used.

[0066] For the above scenario, the improved technical solution is: first, the IPv6 terminal initiates a DNS request for an AAAA record with a universal special domain name of ipv4only.arpa., obtains the NAT64 prefix used for network address translation through the DNS64 response to the DNS request including the universal special domain name, and then synthesizes the NAT64 prefix with the destination IPv4 address to obtain the destination IPv6 address. Figure 2 As shown, the specific process includes:

[0067] Step 1: The IPv6 terminal sends a DNS request including an AAAA record of the universal special domain name ipv4only.arpa. to the DNS64 server;

[0068] Step 2: The DNS64 server performs DNS64 processing on the universal special domain name ipv4only.arpa. and obtains the A record of the domain name (for example Figure 2 192.0.0.170 and 192.0.0.171 in the URL);

[0069] Step 3: The DNS64 server combines the A record with one or more 64-bit NAT64 prefixes obtained after DNS64 processing to obtain an AAAA record, and returns it to the IPv6 terminal;

[0070] Step 4: After the IPv6 terminal obtains the AAAA record from the DNS64 server, if only one AAAA record is obtained, the IPv4 server is accessed directly based on the AAAA record; if the returned AAAA record is not unique, that is, multiple AAAA records (for example Figure 2 200:db8:42::192.0.0.170, 200:db8:43::192.0.0.170, 64:ff9b::192.0.0.170), the IPv4 server is accessed based on the first AAAA record.

[0071] Based on the above existing improved technical solutions, it can be seen that for all IPv6 terminals, the NAT64 prefix returned by the DNS64 server for network address translation is the same, but with the substantial increase in IPv6 traffic in the network, in order to meet the needs of traffic diversion, security control, etc., more and more scenarios require different IPv6 terminals to obtain different NAT64 prefixes and different data access paths. The current technical solution cannot meet the needs of multiple access paths in the existing network.

[0072] For example, Figure 3 is a schematic diagram of a multi-access path scenario; Figure 3As shown in the figure, a CPE1 with a source address of 1001::1 accesses the IPv6 network through BRAS1, and another CPE2 with a source address of 1002::1 accesses the IPv6 network through BRAS2. To meet the needs of traffic diversion, CPE1 is required to access the IPv4 server with a domain name of 200.1.1.1 through the NAT64 path of city B, and CPE2 is required to access the IPv4 server with a domain name of 200.1.1.1 through the NAT64 path of city A, that is, the IPv4 server accessing the IPv4 network is accessed through the NAT64 paths of multiple cities according to the needs. However, the current technical solution of returning the same NAT64 prefix to all CPEs can no longer meet the needs of this multi-access path scenario.

[0073] Based on this, an embodiment of the present invention proposes an access method. Figure 4 The access method of the embodiment of the present invention is shown in FIG. Figure 1 ;like Figure 4 As shown, the method is applied to a broadband access server (BRAS, Broadband Remote Access Server), and the method includes:

[0074] Step 101: receiving a first request sent by a terminal device; the first request is used to request a first record of a first domain name;

[0075] Step 102: Send a second request to a domain name server, and receive a second response corresponding to the second request sent by the domain name server; the second request includes a first prefix identifier corresponding to the BRAS, the second request is used to request a second record of the first domain name, and the second response includes the second record; the second record includes an address translation prefix corresponding to the first prefix identifier;

[0076] Step 103: Send a first response corresponding to the first request to the terminal device, where the first response includes the first record, where the first record includes an address conversion prefix corresponding to the first prefix identifier, and where the first record is used by the terminal device to modify the IPv4 destination address to an IPv6 destination address so as to initiate access to the IPv6 destination address.

[0077] The access method of the embodiment of the present invention is applied to BRAS. The BRAS is a new access gateway for broadband network applications and is a core network element device for broadband user access. It is used to provide basic access means and management functions of the broadband access network. The BRAS in the embodiment of the present invention can be used to provide access for IPv6 terminal devices.

[0078] In this embodiment, the terminal device can be a device that supports the IPv6 protocol, which can also be called an IPv6 terminal. This type of device can perform network communication through the IPv6 protocol to achieve connection with the Internet and data transmission. IPv6 terminal devices include but are not limited to user equipment (UE, User Equipment), computers, demodulators, customer premise equipment (CPE), etc.

[0079] In this embodiment, the BRAS receives a first request from a terminal device for requesting a first record of a first domain name. Exemplarily, the first request may be a DNS query (DNS Query), wherein the first record is used to point a host name (or domain name) to an IPv6 address, and in other optional embodiments, the first request is used to request resolution of the first domain name to an IPv6 address.

[0080] In an embodiment of the present invention, the first domain name may be a universal special domain name representing the requested first record. For example, in a scenario where an IPv6 terminal accesses an IPv4 destination address, the first domain name may be a universal special domain name ipv4only.arpa. used for reverse resolution of the IPv4 destination address.

[0081] In some implementations, the first request includes the first domain name associated with the IPv4 destination address and a first type identifier representing the first record.

[0082] For example, when an IPv6 terminal wants to access the IPv4 destination address 200.1.1.1, the first request sent by the IPv6 terminal and received by BRAS1 may be as follows:

[0083] DNS Query1(Name:ipv4only.arpa,Type:AAAA)

[0084] Among them, ipv4only.arpa is the first domain name used in the scenario where an IPv6 terminal accesses an IPv4 destination address, AAAA is a first type identifier representing a first record, and the first request (DNS Query1) is used to request that the first domain name be resolved to an IPv6 address.

[0085] In some implementations, before step 101, the method further includes: configuring a first policy, the first policy being used to instruct sending an address translation prefix to a terminal device, the first policy including a prefix identifier corresponding to each BRAS.

[0086] In this embodiment, before the BRAS receives a first request from a terminal device for requesting a first record of a first domain name, it is necessary to pre-configure a first policy for indicating that an address translation prefix is ​​sent to the terminal device. The address translation prefix may be a NAT64 prefix used in the NAT64 method. Compared with the NAT64 prefix in the prior art, the address translation prefix in this embodiment is a specific address translation prefix or a specific NAT64 prefix. Different specific address translation prefixes or specific NAT64 prefixes correspond to different prefix identifiers. Exemplarily, in an IPv6 scenario, the address translation prefix (or specific NAT64 prefix) may be set to 64 bits; the first policy may specifically include prefix identifiers corresponding to each BRAS, that is, in the first policy, different BRASs each correspond to a different prefix identifier.

[0087] It should be noted that in the embodiment of the present invention, each BRAS is configured with a corresponding first strategy, that is, for all terminal devices accessing the same BRAS, since the BRAS corresponds to a unique prefix identifier, the address conversion prefixes corresponding to all terminal devices accessing the same BRAS are the same.

[0088] For example, the first policy configured by BRAS1 includes: for a specific NAT64 prefix 2002:0:0:1 / 64, specifying the prefix identifier corresponding to the specific NAT64 prefix as 2; the first policy configured by BRAS2 includes: for a specific NAT64 prefix 2001:0:0:1 / 64, specifying the prefix identifier corresponding to the specific NAT64 prefix as 1.

[0089] In this embodiment, after receiving the first request sent by the terminal device, the BRAS determines that the corresponding address translation prefix needs to be sent to the terminal device according to the preconfigured first policy, and then the BRAS sends a second request for requesting a second record of the first domain name to the domain name server to request the address translation prefix corresponding to the first prefix identifier. In this embodiment of the present invention, the newly added second record carries the address translation prefix corresponding to the first prefix identifier, and feeds back the second record through a second response sent by the domain name server.

[0090] It should be noted that the domain name server is a server for converting a domain name (domain name) and its corresponding IP address (IP address). In the embodiment of the present invention, the domain name server may be a domain name server with special functions, such as a DNS64 server.

[0091] In an embodiment of the present invention, the BRAS and the domain name server can implement the second request and the second response through the extension mechanism of DNS (EDNS, Extension Mechanisms for DNS) and the extension of the DNS protocol, that is, requesting the second record of the first domain name, and obtaining the second record carrying the address conversion prefix corresponding to the first prefix identifier.

[0092] As an example, the BRAS may extend the option resource record (OPT RR, OPTION Resource Record) through an extended mechanism of DNS (EDNS) as the second record of the embodiment of the present invention. Figure 5 Format of OPT RR extended by the embodiment of the present invention Figure 1 ;like Figure 5 As shown in the left half of , the OPT RR may include the following fields: a name (Name) field, a type (TYPE) field, a TTL field, an RDLENGTH field, and an RDATA field.

[0093] Among them, the Name field is currently empty; the TYPE field indicates the type number of the OPT RR; RDLENGTH indicates the length of the variable part RDATA; RDATA is the variable part of the key-value pair (KV, Key-Value) type; the TTL field can store the return status code (RCODE) and flags in the extended DNS message header.

[0094] like Figure 5 As shown in the upper right part of , the existing TTL field includes an extended return status code (EXTENDED-RCODE) field, a version (VERSION) field, a Domain Name System Security Extensions (DNNSSEC) identifier (DO, DNSSEC OK) and a Z field, wherein the EXTENDED-RCODE field is in the most significant bit (MSB) of the binary system and is used to indicate the return status code; the VERSION field is in the least significant bit (LSB) of the binary system and is used to indicate the version of EDNS; DO is a status identifier used to verify the authenticity and integrity of the DNS response; the Z field is usually set to 0 by the sender and can be ignored by the receiver.

[0095] The embodiment of the present invention implements the second request in the embodiment of the present invention by extending the Z field in the TTL field. Figure 5As shown in the lower right part of the figure, by adding a 4-bit prefix identifier (PrefID) in the Z field, the first prefix identifier of the current BRAS is indicated, that is, PrefID can indicate that the corresponding message (such as the second request) is a specific NAT64 prefix requesting PrefID. In the second request, the first prefix identifier can be carried through the prefix identifier (PrefID) field, indicating that the address translation prefix (or specific NAT64 prefix) corresponding to the first prefix identifier is requested.

[0096] For example, based on the first policy configured in the above example, for BRAS1, PrefID=2 is set in the TTL field of its corresponding OPT RR; for BRAS2, PrefID=1 is set in the TTL field of its corresponding OPT RR.

[0097] In some implementations, the second request includes the first prefix identifier, a second type identifier indicating the second record, and the first domain name.

[0098] In this embodiment, the second request sent by the BRAS to the domain name server may include: the first prefix identifier, the second type identifier indicating the second record, and the first domain name.

[0099] For example, after receiving the first request in the above example, the second request sent by BRAS1 to the DNS64 server may be as follows:

[0100] DNS Query2(Name:ipv4only.arpa,Type:N,OPT:'PrefID=2')

[0101] Among them, ipv4only.arpa is the first domain name used in the scenario where an IPv6 terminal accesses an IPv4 destination address, N is the second type identifier representing the second record, OPT:'PrefID=2' represents the first prefix identifier, and the second request (DNSQuery2) is used to request the second record of the first domain name, that is, to request the address conversion prefix corresponding to the first prefix identifier for the first domain name.

[0102] In some implementations, sending the second request to the domain name server includes: according to a first policy, modifying the first type identifier in the first request to the second type identifier, adding the first prefix identifier, generating a second request, and sending the second request to the domain name server.

[0103] In this embodiment, after receiving the first request sent by the terminal device, the BRAS needs to determine the corresponding first prefix identifier according to the first policy configured by the BRAS, and based on the first request, modify the first type identifier in the first record of the request to the second type identifier in the second record that needs to be requested from the domain name server, and add the first prefix identifier to the request, thereby generating a second request, and sending the generated second request to the domain name server so that the domain name server can determine the second record corresponding to the first prefix identifier.

[0104] It can be understood that the second request is obtained based on the first request by modifying the type identifier of the requested record and adding the first prefix identifier in the first policy currently configured by the BRAS.

[0105] For example, after receiving the first request (DNS Query1) in the aforementioned example, BRAS1 modifies the first type identifier "Type:AAAA" in the first request to the second type identifier "Type:N", and adds the prefix identifier "OPT:'PrefID=2'", thereby generating a second request (DNS Query2), and sending the second request to the DNS64 server.

[0106] In this embodiment, after sending the second request including the first prefix identifier to the domain name server, BARS receives a second response fed back by the domain name server, thereby obtaining the address translation prefix corresponding to the first prefix identifier carried by the newly added second record.

[0107] As an example, Figure 6 Format of OPT RR extended by the embodiment of the present invention Figure 2 ;like Figure 6 As shown in the left half of , the OPT RR may include the following fields: a name (Name) field, a type (TYPE) field, a TTL field, an RDLENGTH field, and an RDATA field.

[0108] Among them, the Name field is currently empty; the TYPE field indicates the type number of the OPT RR; RDLENGTH indicates the length of the variable part RDATA; RDATA is the variable part of the key-value pair (KV, Key-Value) type; the TTL field can store the return status code (RCODE) and flags in the extended DNS message header.

[0109] like Figure 6As shown in the right half of , the existing TYPE field may include the definition of each TYPE field type, specifically including the value of each TYPE field type and the corresponding specific meaning (for example: the value of TYPE A type is 1, indicating a host address; the value of TYPE NS type is 2, indicating an authoritative name server; the value of TYPE MD type is 3, indicating a destination address; the value of TYPE MF type is 4, indicating a forwarder... and so on), and each TYPE field type is a subset of the TYPE field.

[0110] In the embodiment of the present invention, for different prefix identifiers, a corresponding second record (i.e., N record, i.e., TYPE N type) is added in the TYPE field, and the value of TYPE N type is defined as 20000, indicating that the N record is an IPv6 address (i.e., address translation prefix) composed of a NAT64 prefix and a prefix identifier. The format in the second record is as follows: Figure 7 As shown, the second record (N record) is a special IPv6 address, and its composition structure is the same as the IP address in the IPv6 protocol (consisting of a string of 128 bits). The first 64 bits from the highest bit are the NAT64 prefix, the last 4 bits are the prefix identifier, and the middle 60 bits are all 0. For example, when the prefix identifier is 1, the newly added corresponding N record is 2001:0:0:1::1; when the prefix identifier is 2, the newly added corresponding N record is 2002:0:0:1::2; when the prefix identifier is 3, the newly added corresponding N record is 2003:0:0:1::3.

[0111] It can be understood that, since different BRASs add prefix identifiers to corresponding fields of the message through the extended DNS protocol content when sending the second request, the domain name server searches and determines the corresponding second record according to the prefix identifier in the second request after receiving the second request. That is, the prefix identifiers extended by different BRASs and the second records extended by the domain name server are in a one-to-one correspondence.

[0112] In some implementations, the second response also includes the first prefix identifier and the first domain name.

[0113] In this embodiment, after the BRAS sends a second request for requesting a second record to the domain name server, it receives a second response from the domain name server; wherein the second response includes the first prefix identifier and the first domain name in addition to the second record. Figure 7 As shown, the second record includes the address conversion prefix and the first prefix identifier.

[0114] For example, based on the second request sent by BRAS1, the second response sent by the DNS64 server according to the second request and received by BRAS1 may be as follows:

[0115] DNS Response2(Name:ipv4only.arpa,N:2002:0:0:1::2,OPT:'PrefID=2')

[0116] Among them, ipv4only.arpa is the first domain name used in the scenario where the IPv6 terminal accesses the IPv4 destination address, N:2002:0:0:1::2 is the second record determined by the DNS64 server according to the first prefix identifier in the second request, that is, the address conversion prefix corresponding to the first prefix identifier, which includes the second type identifier "N" corresponding to the second record, OPT:'PrefID=2' represents the first prefix identifier, and BRAS1 obtains the second record according to the second response (DNS Response2).

[0117] In this embodiment, after receiving the second response including the second record from the domain name server, the BRAS sends a first response including the first record corresponding to the first request to the terminal device. The first record includes the address conversion prefix corresponding to the first prefix identifier, and the first record is used by the terminal device to modify the IPv4 destination address to the IPv6 destination address to initiate access to the IPv6 destination address.

[0118] For example, after receiving the second response sent by the DNS64 server in the above example, the first response including the first record corresponding to the first request sent by BRAS1 to the terminal device may be as follows:

[0119] DNS Response1(Name:ipv4only.arpa,AAAA:2002:0:0:1::2)

[0120] Among them, ipv4only.arpa is the first domain name used in the scenario where the IPv6 terminal accesses the IPv4 destination address, AAAA:2002:0:0:1::2 is the first record determined by BRAS1 according to the second record in the received second response, that is, the address conversion prefix corresponding to the first prefix identifier, which includes the first type identifier "AAAA" corresponding to the first record, and BRAS1 sends the first response (DNS Response1) to the first request to the IPv6 terminal, so that the IPv6 terminal modifies the IPv4 destination address to the IPv6 destination address, thereby initiating access to the IPv6 destination address.

[0121] In some implementations, the step 103 includes: modifying the second type identifier in the second response to the first type identifier, deleting the first prefix identifier, generating a first response corresponding to the first request, and sending the first response to the terminal device.

[0122] In this embodiment, after receiving the second response including the second record from the domain name server, the BRAS modifies the second type identifier to the first type identifier based on the second response and deletes the first prefix identifier, thereby generating a first response corresponding to the first request.

[0123] For example, based on the second response (DNSResponse2) including the second record received by BRAS1 in the above example, the corresponding second type identifier "N" in the second record is modified to the first type identifier "AAAA", and the first prefix identifier "OPT:'PrefID=2'" used by the DNS64 server to determine the second record is deleted, thereby obtaining a first response (DNS Response1) corresponding to the first request sent by the IPv6 terminal connected to BRAS1.

[0124] It is understandable that after receiving the second response including the second record, the BRAS modifies the second record in the second response to the first record, that is, modifies the second type identifier to the first type identifier, without modifying the address conversion prefix corresponding to the first prefix identifier spliced ​​with the type identifier.

[0125] The embodiment of the present invention proposes an access method. Figure 6 The access method of the embodiment of the present invention is shown in FIG. Figure 2 ;like Figure 6 As shown, the method is applied to a domain name server, and the method includes:

[0126] Step 201: receiving a second request sent by a BRAS, wherein the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of a first domain name;

[0127] Step 202: Obtain a second record corresponding to the first prefix identifier, and send a second response to the BRAS, where the second response includes the second record; the second record includes the address translation prefix corresponding to the first prefix identifier.

[0128] The access method of the embodiment of the present invention is applied to a domain name server, which is used as a server for converting a domain name and its corresponding IP address. In the embodiment of the present invention, the domain name server can be a domain name server with special functions, such as a DNS64 server.

[0129] In this embodiment, the domain name server receives a second request including a first prefix identifier corresponding to the BRAS and sent by the BRAS to request a second record of the first domain name. The first domain name may be a universal special domain name representing the first record requested by the terminal device to the BRAS, for example, in a scenario where an IPv6 terminal accesses an IPv4 destination address, the first domain name may be a universal special domain name ipv4only.arpa. for reverse resolution of the IPv4 destination address.

[0130] In some implementations, the second request includes the first prefix identifier, a second type identifier indicating the second record, and the first domain name.

[0131] In this embodiment, the second request sent by the BRAS and received by the domain name server may include: the first prefix identifier, the second type identifier indicating the second record, and the first domain name.

[0132] For example, the DNS64 server may receive the second request sent by BRAS1 as follows:

[0133] DNS Query2(Name:ipv4only.arpa,Type:N,OPT:'PrefID=2')

[0134] Among them, ipv4only.arpa is the first domain name used in the scenario where an IPv6 terminal accesses an IPv4 destination address, N is the second type identifier representing the second record, OPT:'PrefID=2' represents the first prefix identifier, and the request (DNSQuery2) is used to request the second record of the first domain name, that is, to request the address conversion prefix corresponding to the first prefix identifier for the first domain name.

[0135] In some implementations, before step 201, the method further includes: configuring multiple second records, where different second records correspond to different prefix identifiers.

[0136] In this embodiment, before receiving the second request sent by the BRAS, the domain name server needs to configure a different second record corresponding to each prefix identifier in the multiple prefix identifiers, so that when receiving the second request sent by the BRAS, the domain name server can know through the extended DNS protocol content that the second request is used to request the second record, and determine the corresponding second record according to the first prefix identifier in the second request, and fill the second record with the newly defined field after the extension.

[0137] Exemplarily, the multiple second records preconfigured by the domain name server may be as follows: N 2001:0:0:1::1; N 2002:0:0:1::2; N 2003:0:0:1::3.

[0138] In some optional embodiments, the second response also includes the first prefix identifier and the first domain name.

[0139] In this embodiment, after determining the second record corresponding to the first prefix identifier, the domain name server sends a second response to the BRAS that includes not only the second record but also: the first prefix identifier and the first domain name.

[0140] For example, based on the second request sent by BRAS1, after the DNS64 server determines that the corresponding second record is 2002:0:0:1::2 according to the second request including the first prefix identifier of 2, the second response sent to BRAS1 may be as follows:

[0141] DNS Response2(Name:ipv4only.arpa,N:2002:0:0:1::2,OPT:'PrefID=2')

[0142] Among them, ipv4only.arpa is the first domain name used in the scenario where the IPv6 terminal accesses the IPv4 destination address, N:2002:0:0:1::2 is the second record determined by the DNS64 server according to the first prefix identifier in the second request, that is, the address conversion prefix corresponding to the first prefix identifier, which includes the second type identifier "N" corresponding to the second record, OPT:'PrefID=2' represents the first prefix identifier, and the DNS64 server sends a second response including the second record to BRAS1, so that BRAS1 can determine the address conversion prefix corresponding to the first prefix identifier according to the second response (DNS Response2).

[0143] In this embodiment, after the domain name server receives the second request, it determines the second record corresponding to the first prefix identifier based on the second request, and sends a second response carrying the second record corresponding to the first prefix identifier to the BRAS, so that the BRAS can determine the address conversion prefix corresponding to the first prefix identifier.

[0144] It should be noted that the relevant description of filling the second record in the extension field of the present invention has been described above. Figure 6 and Figure 7 The corresponding text description is explained in detail and will not be elaborated here.

[0145] In some implementations, obtaining the second record corresponding to the first prefix identifier includes: determining, according to the second request, the second record corresponding to the first prefix identifier from among the multiple prefix identifiers.

[0146] In this embodiment, after receiving the second request including the first prefix identifier sent by the BRAS, the domain name server searches for the second record corresponding to the first prefix identifier in the configured multiple second records based on the first prefix identifier in the second request, thereby determining the second record corresponding to the first prefix identifier.

[0147] For example, when the first prefix identifier is 2, the second record corresponding to the prefix identifier 2 is searched in different second records configured for prefix identifiers corresponding to different BRASs and determined to be 2002:0:0:1::2.

[0148] In some implementations, before sending the second response to the BRAS, the method further includes: adding the second record to the second request, generating a second response corresponding to the second request, and sending the second response to the BRAS.

[0149] In this embodiment, after the domain name server determines the corresponding second record according to the first prefix identifier in the second request, it needs to add the second record to the second request, thereby generating a second response corresponding to the second request, and then sending the second response including the second record to the BRAS.

[0150] For example, based on the second request (DNS Query 2) sent by BRAS1 in the above example, the DNS64 server adds the determined second record "N:2002:0:0:1::2" to the "Type: N" field in the second request (see Figure 6 As shown), thereby obtaining the second response (DNSResponse2) in the above example.

[0151] The embodiment of the present invention proposes an access method. Fig. 9 The access method of the embodiment of the present invention is shown in FIG. Figure 3 ;like Fig. 9 As shown, the method is applied to a terminal device, and the method includes:

[0152] Step 301: Send a first request to a BRAS; the first request is used to request a first record of a first domain name;

[0153] Step 302: Receive a first response corresponding to the first request sent by the BRAS, where the first response includes the first record, and the first record includes an address conversion prefix corresponding to the first prefix identifier corresponding to the BRAS;

[0154] Step 303: Modify the IPv4 destination address to an IPv6 destination address according to the address translation prefix to initiate access to the IPv6 destination address.

[0155] The access method of an embodiment of the present invention is applied to a terminal device, which may be a device supporting the IPv6 protocol, also referred to as an IPv6 terminal. Such a device can perform network communications via the IPv6 protocol to achieve connection with the Internet and data transmission. The IPv6 terminal device includes but is not limited to user equipment (UE), computers, demodulators, customer premise equipment (CPE), etc.

[0156] In this embodiment, BRAS is a new access gateway for broadband network applications and is a core network element device for broadband user access. It is used to provide basic access means and management functions of the broadband access network. The BRAS in the embodiment of the present invention can be used to provide access for IPv6 terminal devices.

[0157] Here, the terminal device sends a first request to the BRAS for requesting a first record of a first domain name. In an embodiment of the present invention, the first record is used to point a host name (or domain name) to an IPv6 address; in other optional embodiments, the first request is used to request resolution of the first domain name to an IPv6 address.

[0158] In an embodiment of the present invention, the first domain name may be a universal special domain name representing the requested first record. For example, in a scenario where an IPv6 terminal accesses an IPv4 destination address, the first domain name may be a universal special domain name ipv4only.arpa. used for reverse resolution of the IPv4 destination address.

[0159] In some implementations, the first request includes the first domain name associated with the IPv4 target address and a first type identifier representing the first record.

[0160] For example, when the IPv6 terminal wants to access the IPv4 destination address 200.1.1.1, the first request sent by the IPv6 terminal to BRAS1 may be as follows:

[0161] DNS Query1(Name:ipv4only.arpa,Type:AAAA)

[0162] Among them, ipv4only.arpa is the first domain name used in the scenario where an IPv6 terminal accesses an IPv4 destination address, AAAA is a first type identifier representing a first record, and the first request (DNS Query1) is used to request that the first domain name be resolved to an IPv6 address.

[0163] In this embodiment, after the terminal device sends a first request to the BRAS for requesting a first record of a first domain name, the terminal device receives a first response from the BRAS corresponding to the first request and including a first record, wherein the first record includes an address conversion prefix corresponding to a first prefix identifier corresponding to the BRAS, and the terminal device converts the IPv4 destination address into an IPv6 destination address based on the first response.

[0164] For example, the first response including the first record received by the IPv6 terminal may be as follows:

[0165] DNS Response1(Name:ipv4only.arpa,AAAA:2002:0:0:1::2)

[0166] Among them, ipv4only.arpa is the first domain name used in the scenario where the IPv6 terminal accesses the IPv4 destination address, AAAA:2002:0:0:1::2 is the first record determined by BRAS1 based on the second record in the received second response, that is, the address conversion prefix corresponding to the first prefix identifier, which includes the first type identifier "AAAA" corresponding to the first record, and the IPv6 terminal determines the IPv6 destination address corresponding to the IPv4 destination address based on the first response (DNS Response1) sent by the DNS46 server to achieve access to the IPv6 destination address.

[0167] In this embodiment, after receiving the first response, the terminal device modifies the IPv4 destination address into an IPv6 destination address according to the address translation prefix in the first record, and can then initiate access to the IPv6 destination address.

[0168] In some embodiments, the first designated bit and the second designated bit of the first record are respectively an address conversion prefix and a first prefix identifier; modifying the IPv4 destination address to an IPv6 destination address according to the address conversion prefix includes: the terminal device extracts the first designated bit in the first record as the address conversion prefix; and combines the address conversion prefix and the IPv4 destination address to obtain an IPv6 destination address.

[0169] In this embodiment, after receiving the first response including the first record sent by the BRAS, the terminal device extracts the first designated bit in the first record as the address translation prefix, and then combines the extracted address translation prefix with the IPv4 destination address to obtain the IPv6 destination address of the requested first domain name.

[0170] For example, refer to Figure 7As shown, based on the first response (DNSResponse1) received in the above example, the IPv6 terminal extracts the first 64 bits of the first record 2002:0:0:1::2 as the address translation prefix, that is, the extracted address translation prefix is ​​2002:0:0:1, and the address translation prefix is ​​combined with the IPv4 destination address 200.1.1.1 to obtain the IPv6 destination address 2002:0:0:1::200.1.1.1. The IPv6 terminal can access the data of the IPv4 server through the IPv6 destination address 2002:0:0:1::200.1.1.1.

[0171] In this embodiment, after obtaining the IPv6 destination address according to the first response, the terminal device accesses the source IPv4 destination address through the NAT64 device.

[0172] It should be noted that before accessing the source IPv4 destination address, a prefix route needs to be configured in advance for the NAT64 devices in cities connected to different BRASs. The prefix route is the NAT64 prefix in the second record newly added to the domain name server. For example, the prefix route of city A connected to BRAS2 can be configured as 2001:0:0:1 / 64, and the prefix route of city B connected to BRAS1 can be configured as 2002:0:0:1 / 64. After the prefix route is configured, the prefix route can be published to the routing devices corresponding to each city through different dynamic routing protocols for subsequent access operations.

[0173] For example, when an IPv6 terminal with a source address of 100.1.1.1 initiates data access based on the obtained IPv6 destination address 2002:0:0:1::200.1.1.1, and the NAT64 device corresponding to city B publishes the 2002:0:0:1 / 64 prefix route, the relevant data packets initiated by the IPv6 terminal for data access will be routed to the NAT64 device in city B. The NAT64 device will perform stateful NAT64 conversion of the source address into a source IPv4 address, and then remove the NAT prefix of the IPv6 destination address to obtain the IPv4 destination address 200.1.1.1, thereby realizing IPv4 data access.

[0174] The access method of the embodiment of the present invention is described in detail below with reference to a specific example. In the following example, the terminal device is CPE1 and the domain name server is DNS64 server.

[0175] Fig.10 FIG. 1 is a schematic diagram of an interactive process of an access method according to an embodiment of the present invention; Fig.10As shown in the figure, the specific process of IPv6 terminal CPE1 initiating access to the IPv6 destination address corresponding to the IPv4 destination address through the BRAS1 and DNS64 server it accesses is as follows:

[0176] Step 401: BRAS1 pre-configures a first policy corresponding to a prefix identifier, and the DNS64 server pre-configures a second record corresponding to each prefix identifier among a plurality of prefix identifiers.

[0177] Specifically, the prefix identifier corresponding to BRAS1 is 2; the second record configured in the DNS64 server includes, for example: N 2001:0:0:1::1; N 2002:0:0:1::2; N 2003:0:0:1::3.

[0178] Step 402: CPE1 sends a DNSQuery to BRAS1 based on the IPv4 destination address 200.1.1.1 to be directly accessed.

[0179] Here, the DNS Query may be equivalent to the first request in the above embodiment; the DNS Query includes: Name: ipv4only.arpa, Type: AAAA.

[0180] Step 403: BRAS1 receives the first request and determines the corresponding prefix identifier 2 according to a pre-configured first policy.

[0181] Step 404: BRAS1 sends a DNS Query to the DNS64 server.

[0182] Here, the DNS Query may be equivalent to the second request in the above embodiment; the DNS Query includes: Name: ipv4only.arpa, Type: N, OPT: 'PrefID=2'.

[0183] Here, after receiving the first request, BRAS1 modifies the AAAA record into an N record, adds a prefix identifier OPT:'PrefID=2', and sends a second request.

[0184] Step 405: The DNS64 server receives the second request and determines the second record corresponding to the prefix identifier 2 according to the second records corresponding to the pre-configured plurality of prefix identifiers.

[0185] Step 406: The DNS64 server sends a DNS response (DNS Response) to BRAS1.

[0186] Here, the DNS response may be equivalent to the second response in the above embodiment; the DNS response includes: Name: ipv4only.arpa, N: 2002: 0: 0: 1:: 2, OPT: 'PrefID = 2'.

[0187] Step 407: BRAS1 receives the second response and sends a DNS response (DNS Response) to CPE1.

[0188] Here, the DNS response may be equivalent to the first response in the above embodiment; the DNS response includes: Name:ipv4only.arpa,AAAA:2002:0:0:1::2.

[0189] Here, BRAS1 modifies the N record in the second response into an AAAA record, deletes the prefix identifier OPT:'PrefID=2', and then sends the first response.

[0190] Step 408: CPE1 receives the first response, determines the IPv6 destination address according to the first response, and initiates data access to the IPv6 destination address.

[0191] Here, CPE1 extracts the first 64 bits of the AAAA record as the address translation prefix, combines it with the IPv4 destination address to obtain the IPv6 destination address, and initiates data access to the IPv6 destination address. The source address is: 1001::1, and the destination address is 2002:0:0:1::200.1.1.1.

[0192] Since the NAT64 in city B has sent the 2002:0:0:1 / 64 prefix route, the data packet of CPE1 is routed to the NAT64 device in city B, which will perform the NAT64 operation: convert the source address into a source IPv4 address (for example, 100.1.1.1) through stateful NAT64, and remove the NAT64 prefix from the destination address to obtain the destination IPv4 address (200.1.1.1); then perform IPv4 data plane access: the source address is 100.1.1.1, and the destination address is 200.1.1.1.

[0193] Based on the above embodiment, the embodiment of the present invention further provides an access device, which is applied to BRAS. Fig.11 The structure diagram of the access device according to the embodiment of the present invention is shown in FIG. Figure 1 ;like Fig.11 As shown, the device includes: a first receiving unit 51 and a first sending unit 52; wherein,

[0194] The first receiving unit 51 is used to receive a first request sent by a terminal device; the first request is used to request a first record of a first domain name;

[0195] The first sending unit 52 is used to send a second request to the domain name server, where the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of the first domain name;

[0196] The first receiving unit 51 is further configured to receive a second response corresponding to the second request sent by the domain name server; the second response includes the second record; the second record includes the address translation prefix corresponding to the first prefix identifier;

[0197] The first sending unit 52 is also used to send a first response corresponding to the first request to the terminal device, the first response includes the first record, the first record includes the address conversion prefix corresponding to the first prefix identifier, and the first record is used by the terminal device to modify the IPv4 destination address to the IPv6 destination address to initiate access to the IPv6 destination address.

[0198] In an optional embodiment of the present invention, the apparatus further comprises a first processing unit 53 for configuring a first policy, wherein the first policy is used to indicate sending a corresponding address translation prefix to a terminal device, and the first policy comprises a prefix identifier corresponding to each BRAS.

[0199] In an optional embodiment of the present invention, the first request includes the first domain name associated with the IPv4 target address and a first type identifier representing the first record; and / or the second request includes the first prefix identifier, a second type identifier representing the second record, and the first domain name.

[0200] In an optional embodiment of the present invention, the first processing unit 53 is further used to modify the first type identifier in the first request to the second type identifier according to the first strategy, add the first prefix identifier, generate a second request, and send the second request to the domain name server through the first sending unit 52.

[0201] In an optional embodiment of the present invention, the second response also includes the first prefix identifier and the first domain name.

[0202] In an optional embodiment of the present invention, the first processing unit 53 is also used to modify the second type identifier in the second response to the first type identifier, delete the first prefix identifier, generate a first response corresponding to the first request, and send the first response to the terminal device through the first sending unit 52.

[0203] In the implementation of the present invention, the first processing unit 53 in the device can be implemented by a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU) or a programmable gate array (FPGA) in the BRAS in actual applications; the first receiving unit 51 and the first sending unit 52 in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual applications.

[0204] The embodiment of the present invention further provides an access device, which is applied to a domain name server. Fig.12 The structure diagram of the access device according to the embodiment of the present invention is shown in FIG. Figure 2 ;like Fig.12 As shown, the device includes: a second receiving unit 61, a second processing unit 62 and a second sending unit 63; wherein,

[0205] The second receiving unit 61 is configured to receive a second request sent by the BRAS, where the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of the first domain name;

[0206] The second processing unit 62 is used to obtain a second record corresponding to the first prefix identifier;

[0207] The second sending unit 63 is configured to send a second response to the BRAS, where the second response includes the second record; the second record includes the address conversion prefix corresponding to the first prefix identifier.

[0208] In an optional embodiment of the present invention, the second request includes the first prefix identifier, a second type identifier representing the second record, and the first domain name; and / or the second response also includes the first prefix identifier and the first domain name.

[0209] In an optional embodiment of the present invention, the second processing unit 62 is further configured to configure a plurality of second records before the second receiving unit 61 receives the second request sent by the BRAS, wherein different second records correspond to different prefix identifiers.

[0210] In an optional embodiment of the present invention, the second processing unit 62 is configured to determine, according to the second request, a second record corresponding to the first prefix identifier from among the multiple prefix identifiers.

[0211] In the implementation of the present invention, the second processing unit 62 in the device can be implemented by the CPU, DSP, MCU or FPGA in the domain name server in actual applications; the second receiving unit 61 and the second sending unit 63 in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual applications.

[0212] The embodiment of the present invention further provides an access device, which is applied to a terminal device. Fig.13 The structure diagram of the access device according to the embodiment of the present invention is shown in FIG. Figure 3 ;like Fig.13 As shown, the device includes: a communication unit 71 and a third processing unit 72; wherein,

[0213] The communication unit 71 is configured to send a first request to a BRAS, wherein the first request is used to request a first record of a first domain name; and further configured to receive a first response corresponding to the first request sent by the BRAS, wherein the first response includes the first record, and the first record includes an address translation prefix corresponding to a first prefix identifier corresponding to the BRAS;

[0214] The third processing unit 72 is used to modify the IPv4 destination address into an IPv6 destination address according to the address translation prefix, so as to initiate access to the IPv6 destination address.

[0215] In an optional embodiment of the present invention, the first request includes the first domain name associated with the IPv4 target address and a first type identifier representing the first record.

[0216] In an optional embodiment of the present invention, the first designated bit and the second designated bit of the first record are respectively the address conversion prefix and the first prefix identifier; the third processing unit 72 is used to extract the first designated bit in the first record as the address conversion prefix; and combine the address conversion prefix and the IPv4 destination address to obtain the IPv6 destination address.

[0217] In the implementation of the present invention, the third processing unit 72 in the device can be implemented by the CPU, DSP, MCU or FPGA in the terminal device in actual applications; the communication unit 71 in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in actual applications.

[0218] It should be noted that: when the access device is accessing, only the division of the above program modules is used as an example. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device is divided into different program modules to complete all or part of the above-described processing. In addition, the access device and the access method embodiment provided in the above embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0219] The embodiment of the present invention further provides a communication device, Fig.14 FIG. 1 is a schematic diagram of the hardware structure of a communication device according to an embodiment of the present invention. Fig.14 As shown, the communication device includes a memory 82 , a processor 81 , and a computer program stored in the memory 82 and executable on the processor 81 .

[0220] Optionally, the communication device may specifically be a BRAS, a domain name server or a terminal device according to an embodiment of the present invention; when the processor 81 executes the program, the steps of the access method applied to the BRAS, the domain name server or the terminal device according to an embodiment of the present invention are implemented.

[0221] Optionally, the communication device further includes at least one communication component 84. The various components in the communication device can be coupled together via a bus system 83. It is understood that the bus system 83 is used to achieve connection and communication between these components. In addition to the data bus, the bus system 83 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.14 Various buses are labeled as bus system 83.

[0222] It can be understood that the memory 82 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disk, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAM bus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 82 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0223] The method disclosed in the above embodiment of the present invention can be applied to the processor 81, or implemented by the processor 81. The processor 81 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 81 or the instruction in the form of software. The above processor 81 can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 81 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present invention, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 82. The processor 81 reads the information in the memory 82 and completes the steps of the above method in combination with its hardware.

[0224] In an exemplary embodiment, the communication device may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), FPGA, general purpose processor, controller, MCU, microprocessor, or other electronic components to execute the aforementioned method.

[0225] An embodiment of the present invention further provides a computer-readable storage medium on which a computer program is stored.

[0226] Optionally, the computer-readable storage medium can be applied to the access device of the embodiment of the present invention; when the program is executed by the processor, the steps of the access method applied to BRAS, domain name server or terminal device in the embodiment of the present invention are implemented.

[0227] The embodiment of the present invention further provides a computer program product, including a computer program, and the computer program can be executed by the processor 81 of the communication device to complete the steps of the access method described in the embodiment of the present invention.

[0228] The methods disclosed in several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0229] The features disclosed in several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0230] The features disclosed in several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments or device embodiments.

[0231] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. 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 can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the devices or units can be electrical, mechanical or other forms.

[0232] The units described above as separate components may or may not be physically separated, and the components displayed 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 scheme of this embodiment.

[0233] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0234] A person skilled in the art can understand that: all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: mobile storage devices, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), disks or optical disks, etc. Various media that can store program codes.

[0235] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected 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 execute all or part of the methods described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

[0236] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. An access method, characterized in that: The method is applied to a broadband access server BRAS, and the method comprises: Receiving a first request sent by a terminal device; the first request is used to request a first record of a first domain name; Sending a second request to a domain name server, and receiving a second response corresponding to the second request sent by the domain name server; the second request includes a first prefix identifier corresponding to the BRAS, the second request is used to request a second record of the first domain name, and the second response includes the second record; the second record includes an address translation prefix corresponding to the first prefix identifier; A first response corresponding to the first request is sent to the terminal device, wherein the first response includes the first record, wherein the first record includes an address conversion prefix corresponding to the first prefix identifier, and the first record is used by the terminal device to modify an Internet Communication Protocol version 4 IPv4 destination address to an Internet Communication Protocol version 6 IPv6 destination address to initiate access to the IPv6 destination address.

2. The method according to claim 1, characterized in that Before receiving the first request sent by the terminal device, the method further includes: A first policy is configured, where the first policy is used to instruct to send a corresponding address translation prefix to a terminal device, and the first policy includes a prefix identifier corresponding to each BRAS.

3. The method according to claim 1, characterized in that The first request includes the first domain name associated with the IPv4 destination address and a first type identifier representing the first record; and / or, The second request includes the first prefix identifier, a second type identifier indicating the second record, and the first domain name.

4. The method according to claim 3, characterized in that The sending a second request to the domain name server includes: According to the first strategy, the first type identifier in the first request is modified to the second type identifier, and the first prefix identifier is added to generate a second request, and the second request is sent to the domain name server.

5. The method according to claim 1, characterized in that The second response also includes the first prefix identifier and the first domain name.

6. The method according to claim 3, characterized in that: The sending a first response corresponding to the first request to the terminal device includes: Modify the second type identifier in the second response to the first type identifier, delete the first prefix identifier, generate a first response corresponding to the first request, and send the first response to the terminal device.

7. An access method, characterized in that: The method is applied to a domain name server, and the method comprises: receiving a second request sent by a broadband access server BRAS, wherein the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of the first domain name; A second record corresponding to the first prefix identifier is obtained, and a second response is sent to the broadband access server BRAS, wherein the second response includes the second record; the second record includes the address conversion prefix corresponding to the first prefix identifier.

8. The method according to claim 7, characterized in that The second request includes the first prefix identifier, a second type identifier indicating the second record, and the first domain name; and / or, The second response also includes the first prefix identifier and the first domain name.

9. The method according to claim 7, characterized in that: Before receiving the second request sent by the broadband access server BRAS, the method further includes: Multiple second records are configured, and different second records correspond to different prefix identifiers respectively.

10. The method according to claim 9, characterized in that The obtaining the second record corresponding to the first prefix identifier includes: According to the second request, a second record corresponding to the first prefix identifier is determined from the multiple prefix identifiers.

11. An access method, characterized in that: The method is applied to a terminal device, and the method comprises: Sending a first request to a broadband access server BRAS; the first request is used to request a first record of a first domain name; receiving a first response corresponding to the first request sent by the broadband access server BRAS, wherein the first response includes the first record, and the first record includes an address conversion prefix corresponding to the first prefix identifier corresponding to the BRAS; The IPv4 destination address is modified into an IPv6 destination address according to the address translation prefix to initiate access to the IPv6 destination address.

12. The method according to claim 11, characterized in that The first request includes the first domain name associated with the IPv4 target address and a first type identifier representing the first record.

13. The method according to claim 11, characterized in that The first designated bit and the second designated bit of the first record are respectively an address translation prefix and a first prefix identifier; and the step of modifying the IPv4 destination address to an IPv6 destination address according to the address translation prefix comprises: The terminal device extracts the first designated bit in the first record as an address conversion prefix; The address translation prefix and the IPv4 destination address are combined to obtain an IPv6 destination address.

14. An access device, characterized in that: The device is applied to a broadband access server BRAS, and comprises: a first receiving unit and a first sending unit; wherein, The first receiving unit is used to receive a first request sent by a terminal device; the first request is used to request a first record of a first domain name; The first sending unit is used to send a second request to the domain name server, where the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of the first domain name; The first receiving unit is further configured to receive a second response corresponding to the second request sent by the domain name server; the second response includes the second record; the second record includes the address translation prefix corresponding to the first prefix identifier; The first sending unit is also used to send a first response corresponding to the first request to the terminal device, the first response includes the first record, the first record includes the address conversion prefix corresponding to the first prefix identifier, and the first record is used by the terminal device to modify the IPv4 destination address to an IPv6 destination address to initiate access to the IPv6 destination address.

15. An access device, characterized in that: The device is applied to a domain name server, and comprises: a second receiving unit, a second processing unit, and a second sending unit; wherein, The second receiving unit is used to receive a second request sent by a broadband access server BRAS, where the second request includes a first prefix identifier corresponding to the BRAS, and the second request is used to request a second record of the first domain name; The second processing unit is used to obtain a second record corresponding to the first prefix identifier; The second sending unit is used to send a second response to the broadband access server BRAS, where the second response includes the second record; the second record includes the address conversion prefix corresponding to the first prefix identifier.

16. An access device, characterized in that: The device is applied to a terminal device, and comprises: a communication unit and a third processing unit; wherein, The communication unit is configured to send a first request to a broadband access server BRAS; the first request is used to request a first record of a first domain name; and is also configured to receive a first response corresponding to the first request sent by the broadband access server BRAS, the first response including the first record, and the first record including an address translation prefix corresponding to a first prefix identifier corresponding to the BRAS; The third processing unit is used to modify the IPv4 destination address into an IPv6 destination address according to the address translation prefix, so as to initiate access to the IPv6 destination address.

17. A communication device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of the method according to any one of claims 1 to 6 are implemented, or; When the processor executes the program, the steps of the method according to any one of claims 7 to 10 are implemented, or; When the processor executes the program, the steps of the method according to any one of claims 11 to 13 are implemented.

18. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented, or; When the program is executed by a processor, the steps of the method according to any one of claims 7 to 10 are implemented, or; When the program is executed by a processor, the steps of the method according to any one of claims 11 to 13 are implemented.

19. A computer program product comprising a computer program, characterized in that The computer program implements the method according to any one of claims 1 to 6 when executed by a processor, or; The computer program implements the method according to any one of claims 7 to 10 when executed by a processor, or; The computer program implements the method according to any one of claims 11 to 13 when executed by a processor.

Images