An access method and apparatus, a communication device, and a storage medium

Abstract

This invention discloses an access method, apparatus, communication device, and storage medium. The method includes: a BRAS receiving a first request sent by a terminal device; the first request being 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 including a first prefix identifier corresponding to the BRAS, the second request being used to request a second record of the first domain name, the second response including a second record; the second record including an address translation prefix corresponding to the first prefix identifier; sending a first response corresponding to the first request to the terminal device, the first response including a first record, the first record including an address translation prefix corresponding to the first prefix identifier, the first record being used by the terminal device to modify the IPv4 destination address to an IPv6 destination address to initiate access to the IPv6 destination address.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically to an access method, apparatus, communication device, and storage medium. Background Technology

[0002] With the ongoing progress of the Internet Protocol version 6 (IPv6) upgrade and the continuous evolution of new IPv6 technologies, global IPv6 traffic has increased significantly. Although IPv6 has been largely implemented end-to-end, some content providers have not yet completed the IPv6 upgrade and can only provide Internet Protocol version 4 (IPv4) services. In this scenario, Network Address Translation (NAT) is needed to enable IPv6 terminals to access IPv4 servers.

[0003] Currently, existing network address translation (NAT) methods can be implemented by deploying NAT64 and Domain Name System (DNS) 64. However, in live networks, to meet requirements such as traffic routing and security management, many scenarios require different NAT64 prefixes for different users and different paths for data access. However, in existing NAT64 / DNS64-based solutions, DNS64 returns the same NAT64 prefix for all users initiating domain name access. Therefore, existing NAT64 methods cannot handle IPv6 terminals accessing IPv4 servers in scenarios with multiple access paths. Summary of the Invention

[0004] To address the existing technical problems, embodiments of the present invention provide an access method, apparatus, communication device, and storage medium.

[0005] To achieve the above objectives, the technical solution of this invention is implemented as follows:

[0006] In a first aspect, embodiments of the present invention provide an access method applied to a Broadband Access Server (BRAS), the method comprising: receiving a first request sent by a terminal device; the first request being 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] Send a first response corresponding to the first request to the terminal device. The first response includes the first record, which includes an address translation prefix corresponding to the first prefix identifier. The first record is used by the terminal device to modify the Internet Protocol version 4 (IPv4) destination address to the Internet Protocol version 6 (IPv6) destination address in order 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 further includes: configuring a first strategy, the first strategy being used to instruct the terminal device to send a corresponding address translation prefix, the first strategy including a prefix identifier corresponding to each BRAS.

[0010] In the above scheme, 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.

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

[0012] In the above scheme, 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 the first response corresponding to the first request, and sending the first response to the terminal device.

[0014] Secondly, embodiments of the present invention provide an access method applied to a domain name server, the method comprising: receiving a second request sent by a Broadband Access Server (BRAS), the second request including a first prefix identifier corresponding to the BRAS, the second request being used to request a second record of a first domain name;

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

[0016] In the above scheme, the second request includes the first prefix identifier, a second type identifier representing 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 scheme, before receiving the second request sent by the Broadband Access Server (BRAS), the method further includes: configuring multiple second records, with different second records corresponding to different prefix identifiers.

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

[0020] Thirdly, embodiments of the present invention provide an access method applied to a terminal device, the method comprising: sending a first request to a Broadband Access Server (BRAS); the first request being used to request a first record of a first domain name;

[0021] Receive 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 the address prefix identifier corresponding to the first prefix identifier of the BRAS;

[0022] The IPv4 destination address is modified to an IPv6 destination address based on the address prefix identifier, so as to initiate access to the IPv6 destination address.

[0023] In the above scheme, the first request includes the first domain name associated with the IPv4 target address and a first type identifier representing the first record.

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

[0025] Fourthly, embodiments of the present invention also provide an access device, which is applied to a Broadband Access Server (BRAS). The device includes: a first receiving unit and a first transmitting unit; wherein,

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

[0027] The first sending unit is configured to send a second request to the domain name server, the second request including 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 an address translation prefix corresponding to the first prefix identifier;

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

[0030] Fifthly, embodiments of the present invention also provide an access device applied to a domain name server, the device comprising: 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), the second request including a first prefix identifier corresponding to the BRAS, and the second request being used to request a second record of a first domain name.

[0032] The second processing unit is used to obtain the 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), the second response including the second record; the second record includes an address prefix identifier corresponding to the first prefix identifier.

[0034] Sixthly, embodiments of the present invention also provide an access device, the device being applied to a terminal device, the device comprising: 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), wherein the first response includes the first record, and the first record includes an address translation prefix corresponding to a first prefix identifier of the BRAS.

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

[0037] In a seventh aspect, embodiments of the present invention also provide a communication device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the methods described in the first, second, or third aspects of the embodiments of the present invention.

[0038] Eighthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the methods described in the first, second, or third aspects of the embodiments of the present invention.

[0039] In a ninth aspect, embodiments of the present invention also provide a computer program product, including a computer program that, when executed by a processor, implements the methods described in the first, second, or third aspects of the embodiments of the present invention.

[0040] This invention provides an access method, apparatus, communication device, and storage medium. It receives a first request from a terminal device via a BRAS (Branch-Based Access Server) requesting a first record for a first domain name, and obtains a second response including a second record by sending a second request to a domain name server. The second record includes an address translation prefix corresponding to a first prefix identifier corresponding to the BRAS. Then, it sends a first response including the first record to the terminal device, where the first record includes the address translation prefix corresponding to the first prefix identifier. This allows the terminal device to modify its IPv4 destination address to an IPv6 destination address, enabling access to the IPv6 destination address and facilitating access from an IPv6 terminal to an IPv4 server in multi-access path scenarios. Attached Figure Description

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

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

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

[0044] Figure 4 This is a flowchart illustrating the access method according to an embodiment of the present invention. Figure 1 ;

[0045] Figure 5 Schematic diagram of the extended OPT RR format for embodiments of the present invention Figure 1 ;

[0046] Figure 6 This is a flowchart illustrating the access method according to an embodiment of the present invention. Figure 2 ;

[0047] Figure 7 Schematic diagram of the extended OPT RR format for embodiments of the present invention Figure 2 ;

[0048] Figure 8 This is a schematic diagram illustrating the format of the second record in accordance with the present invention;

[0049] Figure 9 This is a flowchart illustrating the access method according to an embodiment of the present invention;

[0050] Figure 10 This is a schematic diagram of the interaction flow of the access method according to an embodiment of the present invention;

[0051] Figure 11 This is a schematic diagram of the composition structure of the access device according to an embodiment of the present invention. Figure 1 ;

[0052] Figure 12 This is a schematic diagram of the composition structure of the access device according to an embodiment of the present invention. Figure 2 ;

[0053] Figure 13 This is a schematic diagram of the composition structure of the access device according to an embodiment of the present invention. Figure 3 ;

[0054] Figure 14 This is a schematic diagram of the hardware composition structure of a communication device according to an embodiment of the present invention. Detailed Implementation

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

[0056] The technical solutions of this invention can be applied to various communication systems, such as GSM (Global System of Mobile communication), LTE (Long Term Evolution), or 5G systems. Optionally, a 5G system or 5G network can also be referred to as a New Radio (NR) system or NR network.

[0057] For example, the communication system used in this embodiment of the invention may include network devices and terminal devices (also referred to as terminals, communication terminals, etc.); the network device may be a device that communicates with the terminal device. The network device can provide communication coverage within a certain area and can communicate with terminals located within that area. Optionally, the network device may be a base station in various communication systems, such as an evolved Node B (eNB) in an LTE system, or a gNB in ​​a 5G or NR system.

[0058] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Communication devices may include network devices and terminals with communication functions. Network devices and terminal devices can be the specific devices described above, which will not be repeated here. Communication devices may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities. This embodiment of the present invention does not limit these.

[0059] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0060] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0061] Before providing a detailed description of the access method in the embodiments of the present invention, a brief description of the related technologies will be given first.

[0062] The rapid growth of internet users worldwide, along with the proliferation of internet-connected devices such as smartphones and personal computers, has quickly depleted IPv4 addresses, hindering network development. IPv6, designed to replace the current IPv4 protocol, is the next-generation internet protocol. The implementation of IPv6 has solved the problem of IPv4 address depletion.

[0063] However, in recent years, with the continuous advancement of IPv6 transformation and the evolution of new IPv6 technologies, global IPv6 traffic has increased significantly. Although IPv6 has been largely implemented end-to-end, some content providers have not yet completed the IPv6 transformation and can only provide IPv4 services. In scenarios where IPv6 terminals need to access IPv4 servers, existing technologies require the deployment of NAT64 and DNS64.

[0064] Figure 1 A schematic diagram of the system architecture for existing access methods; such as Figure 1 As shown, IPv6 terminal ( Figure 1 The Customer Premise Equipment (CPE) in the network accesses the IPv6 network through the Broadband Remote Access Server (BRAS). The domain name (i.e., source address) of the IPv6 terminal is, for example, 2001::1. Through the cooperation between deployed DNS64 and NAT64, the destination IPv4 address (200.1.1.1) of the IPv4 server accessing the IPv4 network is translated, so that the IPv6 terminal can access the IPv4 server based on the translated destination IPv6 address.

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

[0066] To address the above scenario, the improved technical solution is as follows: First, the IPv6 terminal initiates a DNS request for an AAAA record with the generic special domain name ipv4only.arpa. The response to the DNS request, which includes this generic special domain name, is used to obtain the NAT64 prefix for network address translation. Then, this NAT64 prefix is ​​combined with the destination IPv4 address to obtain the destination IPv6 address. Specifically, it can be done as follows: Figure 2 As shown, the specific process includes:

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

[0068] Step 2: The DNS64 server performs DNS64 processing on the generic special domain name ipv4only.arpa. to obtain the A record for that domain name (e.g., Figure 2 (192.0.0.170 and 192.0.0.171 in the original text);

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

[0070] Step 4: After receiving the AAAA record from the DNS64 server, if the IPv6 terminal receives only one AAAA record, it will directly access the IPv4 server based on that AAAA record; if the returned AAAA record is not unique, i.e., multiple AAAA records (e.g., ... Figure 2 If the records 200:db8:42::192.0.0.170, 200:db8:43::192.0.0.170, and 64:ff9b::192.0.0.170 are used, then the IPv4 server is accessed based on the first AAAA record.

[0071] Based on the aforementioned improved technical solutions, it is known that the NAT64 prefix returned by the DNS64 server for network address translation is the same for all IPv6 terminals. However, with the significant increase in IPv6 traffic on the network, in order to meet the needs of traffic routing and security management, more and more scenarios require different IPv6 terminals to obtain different NAT64 prefixes and access data through different paths. The current technical solutions cannot meet the needs of multiple access paths in the current network.

[0072] For example, Figure 3 This is a schematic diagram of a multi-access path scenario; such as Figure 3As shown, CPE1 with source address 1001::1 accesses the IPv6 network via BRAS1, and CPE2 with source address 1002::1 accesses the IPv6 network via BRAS2. To meet traffic routing requirements, CPE1 is required to access the IPv4 server with domain name 200.1.1.1 through the NAT64 path in city B, and CPE2 is required to access the IPv4 server with domain name 200.1.1.1 through the NAT64 path in city A. In other words, depending on the requirements, access to the IPv4 server via NAT64 paths in multiple different cities is necessary. However, the current technical solution of returning the same NAT64 prefix to all CPEs is no longer sufficient for this multi-access path scenario.

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

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

[0075] Step 102: Send a second request to the 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. The first response includes the first record, which includes an address translation prefix corresponding to the first prefix identifier. The first record is used by the terminal device to modify the IPv4 destination address to an IPv6 destination address in order to initiate access to the IPv6 destination address.

[0077] The access method of this invention is applied to a BRAS, which is a new type of access gateway for broadband network applications. The BRAS is a core network element device for broadband user access, used to provide basic access means and broadband access network management functions. The BRAS in this 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, also known as an IPv6 terminal. Such devices can communicate over a network via the IPv6 protocol to achieve connection and data transmission with the Internet. IPv6 terminal devices include, but are not limited to, user equipment (UE), computers, demodulators, customer front-end equipment (CPE), etc.

[0079] In this embodiment, the BRAS receives a first request from the terminal device for requesting a first record of a first domain name. For example, the first request may be a DNS query, where the first record is used to point a hostname (or domain name) to an IPv6 address. In other alternative embodiments, the first request may be used to request that the first domain name be resolved to an IPv6 address.

[0080] In this embodiment of the invention, the first domain name may be a general special domain name representing the requested first record. For example, in the scenario where an IPv6 terminal accesses an IPv4 destination address, the first domain name may be a general 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 received by BRAS1 can 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 of an IPv6 terminal accessing an IPv4 destination address, and AAAA is the first type identifier representing the first record. This first request (DNS Query1) is used to request that the first domain name be resolved to an IPv6 address.

[0085] In some implementations, prior to step 101, the method further includes: configuring a first policy, the first policy being used to instruct the sending of address translation prefixes for terminal devices, the first policy including prefix identifiers corresponding to each BRAS.

[0086] In this embodiment, before receiving a first request from a terminal device for a first record of a first domain name, the BRAS needs to pre-configure a first policy to instruct the BRAS to send an address translation prefix to the terminal device. The address translation prefix can be the NAT64 prefix used in the NAT64 method. Compared to NAT64 prefixes in existing technologies, the address translation prefix in this embodiment is a specific address translation prefix or a specific NAT64 prefix, with different specific address translation prefixes or specific NAT64 prefixes corresponding to different prefix identifiers. For example, in an IPv6 scenario, the address translation prefix (or specific NAT64 prefix) can be set to 64 bits. Specifically, the first policy may include a prefix identifier 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 this embodiment of the 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 translation prefixes of all terminal devices accessing the same BRAS are the same.

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

[0089] In this embodiment, after receiving the first request from the terminal device, the BRAS determines, according to a pre-configured first policy, that it needs to send the corresponding address translation prefix to the terminal device. The BRAS then sends a second request to the domain name server to request the second record for the first domain name, in order to request the address translation prefix corresponding to the first prefix identifier. This embodiment of the invention uses a newly added second record to carry the address translation prefix corresponding to the first prefix identifier, and the second record is fed back through a second response sent by the domain name server.

[0090] It should be noted that, as a server used to translate domain names into their corresponding IP addresses, in this embodiment of the invention, the domain name server can be a domain name server with special functions, such as a DNS64 server.

[0091] In this embodiment of the invention, the BRAS and the domain name server can achieve a second request and a second response through the extension mechanism for 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 translation prefix corresponding to the first prefix identifier.

[0092] As an example, BRAS can extend the Option Resource Record (OPT RR) as the second record in this embodiment of the invention through the DNS Extension Mechanism (EDNS). Figure 5 Schematic diagram of the extended OPT RR format for embodiments of the present invention Figure 1 ;like Figure 5 As shown in the left half, OPT RR can include the following fields: Name field, Type field, TTL field, RDLENGTH field, and RDATA field.

[0093] 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 a variable part of key-value pair (KV) type; the TTL field can store the return status code (RCODE) and flags from the extended DNS message header.

[0094] like Figure 5 As shown in the upper right part, the existing TTL fields include the Extended-RCODE field, the VERSION field, the DNSSEC OK identifier (DO), and the Z field. The Extended-RCODE field is located in the most significant bit (MSB) of the binary representation and is used to indicate the return status code. The VERSION field is located in the least significant bit (LSB) of the binary representation and is used to indicate the EDNS version. The 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] This embodiment of the invention extends the Z field in the TTL field to implement the second request in this embodiment. For example... Figure 5As shown in the lower right part, by adding a 4-bit prefix identifier (PrefID) to the Z field, the first prefix identifier of the current BRAS is represented. That is, the PrefID can indicate that the corresponding message (such as the second request) requests a specific NAT64 prefix of the PrefID. Then, in the second request, the first prefix identifier can be carried through the PrefID field to indicate that the address translation prefix (or specific NAT64 prefix) corresponding to the first prefix identifier is requested.

[0096] For example, based on the first strategy configured in the example above, for BRAS1, PrefID = 2 in the TTL field of its corresponding OPT RR; for BRAS2, PrefID = 1 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 representing 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: a first prefix identifier, a second type identifier representing the second record, and a first domain name.

[0099] For example, after receiving the first request in the example above, BRAS1 could send the following second request to the DNS64 server:

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

[0101] In this context, ipv4only.arpa is the first domain name used when an IPv6 terminal accesses an IPv4 destination address, N is the second type identifier for the second record, and OPT:'PrefID=2' represents the first prefix identifier. This second request (DNSQuery2) is used to request the second record for the first domain name, that is, to request the address translation prefix for the first domain name that corresponds to the first prefix identifier.

[0102] In some implementations, sending the second request to the domain name server includes: modifying the first type identifier in the first request to the second type identifier according to a first strategy, 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. Based on the first request, the first type identifier in the first record of the request is modified to the second type identifier in the second record that needs to be requested from the domain name server, and the first prefix identifier is added to the request to generate a second request. The generated second request is sent to the domain name server so that the domain name server can determine the second record corresponding to the first prefix identifier.

[0104] It is understandable that the second request is obtained by modifying the type identifier of the requested record and adding the first prefix identifier from the first policy configured in the current BRAS, based on the first request.

[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 the second request (DNS Query2) and sending the second request to the DNS64 server.

[0106] In this embodiment, after BARS sends a second request including the first prefix identifier to the domain name server, it receives a second response from 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 Schematic diagram of the extended OPT RR format for embodiments of the present invention Figure 2 ;like Figure 6 As shown in the left half, OPT RR can include the following fields: Name field, Type field, TTL field, RDLENGTH field, and RDATA field.

[0108] 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 a variable part of key-value pair (KV) type; the TTL field can store the return status code (RCODE) and flags from the extended DNS message header.

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

[0110] In this embodiment of the invention, for different prefix identifiers, a corresponding second record (i.e., an N record, or TYPE N type) will be added to the TYPE field, and the value of the TYPE N type will be defined as 20000, indicating that the N record consists of an IPv6 address (i.e., an address translation prefix) composed of a NAT64 prefix and a prefix identifier. The format of the second record is as follows: Figure 7 As shown, the second record (N record), as a special IPv6 address, has the same structure as an IP address in the IPv6 protocol (consisting of a 128-bit string). The first 64 bits from the most significant 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; and when the prefix identifier is 3, the newly added corresponding N record is 2003:0:0:1::3.

[0111] Understandably, because different BRASs add prefix identifiers to the corresponding fields of the message using the extended DNS protocol when sending the second request, the DNS server, upon receiving the second request, uses the prefix identifier in the second request to find and determine the corresponding second record. That is, there is a one-to-one correspondence between the extended prefix identifiers of different BRASs and the extended second records of the DNS server.

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

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

[0114] For example, based on the second request sent by BRAS1 above, the second response received by BRAS1 from the DNS64 server in accordance with the second request can 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 of IPv6 terminal accessing 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 translation 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 a second response from the domain name server that includes a second record, the BRAS sends a first response, which includes a first record, to the terminal device corresponding to the first request. The first record includes an address translation prefix corresponding to a first prefix identifier. This first record is used by the terminal device to modify the IPv4 destination address to an IPv6 destination address in order to initiate access to the IPv6 destination address.

[0118] For example, after receiving the second response from the DNS64 server in the example above, BRAS1 can send the first response, which includes the first record, to the terminal device in response to the first request, as follows:

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

[0120] Here, ipv4only.arpa is the first domain name used in the scenario where an IPv6 terminal accesses an IPv4 destination address, and 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 translation prefix corresponding to the first prefix identifier, which includes the first type identifier "AAAA" corresponding to the first record. BRAS1 sends the first response (DNS Response 1) of the first request to the IPv6 terminal so that the IPv6 terminal can modify the IPv4 destination address to the IPv6 destination address, thereby initiating access to the IPv6 destination address.

[0121] In some implementations, 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 a second response from the domain name server that includes a second record, the BRAS modifies the second type identifier in the second response to a first type identifier 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) received by BRAS1 in the above example, which includes the second record, the 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 the first response (DNS Response1) corresponding to the first request sent by the IPv6 terminal that has accessed BRAS1.

[0124] It is understandable that after receiving the second response which includes 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 translation prefix corresponding to the first prefix identifier concatenated with the type identifier.

[0125] This invention provides an access method. Figure 6 This is a flowchart illustrating the access method according to an embodiment of the present invention. Figure 2 ;like Figure 6 As shown, the method is applied to a domain name server, and the method includes:

[0126] Step 201: Receive a second request sent by the BRAS, the second request including the first prefix identifier corresponding to the BRAS, the second request being used to request the second record of the first domain name;

[0127] Step 202: Obtain the second record corresponding to the first prefix identifier, and send a second response to the BRAS, wherein 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 this invention is applied to a domain name server, which serves as a server for converting domain names to their corresponding IP addresses. In this 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 from the BRAS, including a first prefix identifier corresponding to the BRAS, to request a second record for the first domain name. The first domain name may be a generic special domain name representing the first record requested by the terminal device from the BRAS. For example, in a scenario where an IPv6 terminal accesses an IPv4 destination address, the first domain name may be the generic special domain name ipv4only.arpa. used for reverse lookup of the IPv4 destination address.

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

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

[0132] For example, the DNS64 server might receive the second request from BRAS1 as follows:

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

[0134] In this context, ipv4only.arpa is the first domain name used when an IPv6 terminal accesses an IPv4 destination address, N is the second type identifier for the second record, and OPT:'PrefID=2' represents the first prefix identifier. This request (DNSQuery2) is used to request the second record for the first domain name, that is, to request the address translation prefix for the first domain name that corresponds to the first prefix identifier.

[0135] In some implementations, prior to step 201, the method further includes configuring a plurality of second records, each of which corresponds to a different prefix identifier.

[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 of the multiple prefix identifiers. This is so that when the second request is received from the BRAS, the server can know that the second request is for requesting a second record through the extended DNS protocol content, find 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 fields after extension.

[0137] For example, multiple second records pre-configured by the domain name server may be as follows: N2001:0:0:1::1; N2002:0:0:1::2; N2003:0:0:1::3.

[0138] In some alternative embodiments, the second response may also include 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 second response sent by the domain name server to the BRAS includes the first prefix identifier and the first domain name, in addition to the second record.

[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 2, the second response sent to BRAS1 can be as follows:

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

[0142] In this context, ipv4only.arpa is the first domain name used when an IPv6 terminal accesses an IPv4 destination address. N:2002:0:0:1::2 is the second record determined by the DNS64 server based on the first prefix identifier in the second request, which is the address translation prefix corresponding to the first prefix identifier. It includes the second type identifier "N" corresponding to the second record. OPT:'PrefID=2' represents the first prefix identifier. The DNS64 server sends a second response including the second record to BRAS1 so that BRAS1 can determine the address translation prefix corresponding to the first prefix identifier based on 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 translation prefix corresponding to the first prefix identifier.

[0144] It should be noted that the relevant description of filling the second record in the extended field has been provided above. Figure 6 and Figure 7 The corresponding text descriptions will be explained in detail, and will not be elaborated on 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 plurality of prefix identifiers.

[0146] In this embodiment, after receiving a second request from the BRAS that includes a first prefix identifier, the domain name server searches for the second record corresponding to the first prefix identifier among 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 2002:0:0:1::2, which is found and determined in the different second records configured for the prefix identifiers corresponding to different BRAS.

[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 based on the first prefix identifier in the second request, it needs to add the second record to the second request to generate a second response corresponding to the second request, and then send a 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 aforementioned example, the DNS64 server, based on the second type identifier "N" included in the second request, adds the determined second record "N:2002:0:0:1::2" to the "Type:N" field of the second request (see reference). Figure 6 As shown in the figure, this yields the second response (DNSResponse2) in the example above.

[0151] This invention provides an access method. Figure 9 This is a flowchart illustrating the access method according to an embodiment of the present invention. Figure 3 ;like Figure 9 As shown, the method is applied to a terminal device, and the method includes:

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

[0153] Step 302: Receive the first response corresponding to the first request sent by the BRAS, wherein the first response includes the first record, and the first record includes the address translation prefix corresponding to the first prefix identifier of the BRAS;

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

[0155] The access method of this invention is applied to a terminal device, which may be a device that supports the IPv6 protocol, also known as an IPv6 terminal. Such devices can communicate over a network via the IPv6 protocol to achieve connection and data transmission with the Internet. IPv6 terminal devices include, but are not limited to, user equipment (UE), computers, demodulators, customer front-end equipment (CPE), etc.

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

[0157] Here, the terminal device sends a first request to the BRAS to request a first record for the first domain name. In this embodiment of the invention, the first record is used to point the hostname (or domain name) to an IPv6 address; in other alternative embodiments, the first request is used to request that the first domain name be resolved to an IPv6 address.

[0158] In this embodiment of the invention, the first domain name may be a general special domain name representing the requested first record. For example, in the scenario where an IPv6 terminal accesses an IPv4 destination address, the first domain name may be a general 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 an IPv6 terminal wants to access the IPv4 destination address 200.1.1.1, the first request sent by the IPv6 terminal to BRAS1 can 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 of an IPv6 terminal accessing an IPv4 destination address, and AAAA is the first type identifier representing the first record. This 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 to request a first record for the first domain name, it will receive a first response from the BRAS corresponding to the first request, which includes the first record. The first record includes the address translation prefix corresponding to the first prefix identifier of the BRAS. The terminal device will convert the IPv4 destination address to the IPv6 destination address according to the first response.

[0164] For example, the first response received by an IPv6 terminal, including the first record, can 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 of IPv6 terminal accessing IPv4 destination address, and 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 translation prefix corresponding to the first prefix identifier, which includes the first type identifier "AAAA" corresponding to the first record. The IPv6 terminal determines the IPv6 destination address corresponding to the IPv4 destination address according to the first response (DNS Response1) sent by the DNS46 server, so as to realize the access to the IPv6 destination address.

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

[0168] In some implementations, the first specified bit and the second specified bit of the first record are respectively the address translation prefix and the first prefix identifier; the step of modifying the IPv4 destination address to the IPv6 destination address according to the address translation prefix includes: the terminal device extracting the first specified bit in the first record as the address translation prefix; and combining the address translation prefix and the IPv4 destination address to obtain the IPv6 destination address.

[0169] In this embodiment, after receiving the first response from the BRAS that includes the first record, the terminal device extracts the first specified bit from the first record as an 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 example above, the IPv6 terminal extracts the first 64 bits of the first record 2002:0:0:1::2 as an address translation prefix, i.e., the extracted address translation prefix is ​​2002:0:0:1. This 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 data from the IPv4 server through this IPv6 destination address 2002:0:0:1::200.1.1.1.

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

[0172] It's important to note that before accessing the source IPv4 destination address, a prefix route needs to be configured for the NAT64 devices in the cities connected to different BRASs. This prefix route is the NAT64 prefix in the second record added by the domain name server. For example, the prefix route for city A connected to BRAS2 can be configured as 2001:0:0:1 / 64, and the prefix route for city B connected to BRAS1 can be configured as 2002:0:0:1 / 64. After configuring the prefix route, it can be advertised to the corresponding routing devices in each city using 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, if the NAT64 device corresponding to city B has published a 2002:0:0:1 / 64 prefix route, the relevant data packets of the IPv6 terminal initiating data access will be routed to the NAT64 device in city B. The NAT64 device will then perform stateful NAT64 translation of the source address into a source IPv4 address, and remove the NAT prefix from the IPv6 destination address to obtain the IPv4 destination address 200.1.1.1, thereby enabling IPv4 data access.

[0174] The access method of this invention will be 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 a DNS64 server.

[0175] Figure 10 This is a schematic diagram of the interaction flow of the access method according to an embodiment of the present invention; as shown below. Figure 10As shown, the specific process by which IPv6 terminal CPE1 initiates access to the IPv6 destination address corresponding to the IPv4 destination address through its connected BRAS1 and DNS64 server is as follows:

[0176] Step 401: BRAS1 is pre-configured with a first policy corresponding to its corresponding prefix identifier, and the DNS64 server is pre-configured with a second record corresponding to each of the multiple prefix identifiers.

[0177] Specifically, the prefix identifier corresponding to BRAS1 is 2; the second record configured in the DNS64 server includes, for example: N2001: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, DNS Query can be equivalent to the first request in the above embodiment; 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 the pre-configured first strategy.

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

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

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

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

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

[0186] Here, the DNS response can 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 to CPE1.

[0188] Here, the DNS response can 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 to an AAAA record, removes 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 based on 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 an address translation prefix, combines it with the IPv4 destination address to obtain the IPv6 destination address, and initiates data access to this IPv6 destination address. The source address is 1001::1, and the destination address is 2002:0:0:1::200.1.1.1.

[0192] Since City B's NAT64 has sent a 2002:0:0:1 / 64 prefix route, CPE1's data packet is routed to City B's NAT64 device, which will perform NAT64 operations: translate the source address into a source IPv4 address (e.g., 100.1.1.1) using 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: source address is 100.1.1.1, destination address is 200.1.1.1.

[0193] Based on the above embodiments, this invention also provides an access device applied to a BRAS. Figure 11 This is a schematic diagram of the composition structure of the access device according to an embodiment of the present invention. Figure 1 ;like Figure 11 As shown, the device includes: a first receiving unit 51 and a first transmitting unit 52; wherein,

[0194] The first receiving unit 51 is used to receive a first request sent by the 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. The second request includes a first prefix identifier corresponding to the BRAS. The second request is used to request the 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 an address translation prefix corresponding to the first prefix identifier;

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

[0198] In an optional embodiment of the present invention, the apparatus further includes a first processing unit 53, configured to configure a first strategy, the first strategy being configured to instruct the terminal device to send a corresponding address translation prefix, the first strategy including 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 configured 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 further 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 further configured 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 this invention, the first processing unit 53 in the device can be implemented in practical applications by a central processing unit (CPU), digital signal processor (DSP), microcontroller unit (MCU), or field-programmable gate array (FPGA) in the BRAS; the first receiving unit 51 and the first transmitting unit 52 in the device can be implemented in practical applications by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and transceiver antenna.

[0204] This invention also provides an access device applied to a domain name server. Figure 12 This is a schematic diagram of the composition structure of the access device according to an embodiment of the present invention. Figure 2 ;like Figure 12 As shown, the device includes: a second receiving unit 61, a second processing unit 62, and a second transmitting unit 63; wherein,

[0205] The second receiving unit 61 is used to receive a second request sent by the BRAS, the second request including 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 the second record corresponding to the first prefix identifier;

[0207] The second sending unit 63 is used to send a second response to the BRAS, the second response including the second record; the second record includes an address translation 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 further 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 among the plurality of prefix identifiers.

[0211] In this 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 practical applications; the second receiving unit 61 and the second transmitting 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 transceiver antenna in practical applications.

[0212] This invention also provides an access device, which is applied to a terminal device. Figure 13 This is a schematic diagram of the composition structure of the access device according to an embodiment of the present invention. Figure 3 ;like Figure 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 the 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 BRAS, wherein the first response includes the first record, and the first record includes an address translation prefix corresponding to the first prefix identifier of the BRAS.

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

[0215] In an alternative 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 translation 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 translation prefix; and combine the address translation prefix and the IPv4 destination address to obtain the IPv6 destination address.

[0217] In this invention, the third processing unit 72 in the device can be implemented by the CPU, DSP, MCU or FPGA in the terminal device in practical 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 transceiver antenna in practical applications.

[0218] It should be noted that the above-described access device is only illustrated by the division of the program modules. In practical applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. Furthermore, the access device and access method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0219] This invention also provides a communication device. Figure 14 This is a schematic diagram of the hardware composition structure of the communication device according to an embodiment of the present invention, such as... Figure 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 the embodiments of the present invention; when the processor 81 executes the program, it implements the steps of the access method applied to the BRAS, domain name server, or terminal device according to the embodiments of the present invention.

[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 implement communication between these components. In addition to a data bus, the bus system 83 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 14 The general labeled all buses as Bus System 83.

[0222] It is understood that memory 82 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (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), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).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 methods disclosed in the above embodiments of the present invention can be applied to processor 81, or implemented by processor 81. 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 integrated logic circuit of the hardware in processor 81 or by instructions in the form of software. The processor 81 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 81 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present invention can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory 82. Processor 81 reads the information in memory 82 and combines its hardware to complete the steps of the aforementioned method.

[0224] In an exemplary embodiment, the communication device may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0225] This invention also provides a computer-readable storage medium having a computer program stored thereon.

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

[0227] This invention also provides a computer program product, including a computer program that can be executed by a processor 81 of a communication device to complete the steps of the access method described in this invention.

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

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

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

[0231] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

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

[0233] In addition, in the various embodiments of the present invention, each functional unit can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0234] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0235] Alternatively, if the integrated units of this invention are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0236] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the 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 includes: Receive a first request sent by the terminal device; the first request is used to request the first record of the 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; 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 translation prefix corresponding to the first prefix identifier. The first record is used by the terminal device to modify the destination address of Internet Protocol version 4 (IPv4) to the destination address of Internet Protocol version 6 (IPv6) in order to initiate access to the IPv6 destination address. Prior to receiving the first request sent by the receiving terminal device, the method further includes: Configure a first policy, which is used to instruct the terminal device to send the corresponding address translation prefix, and the first policy includes a prefix identifier corresponding to each BRAS.

2. 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, the second type identifier representing the second record, and the first domain name.

3. The method according to claim 2, characterized in that, Sending the 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, which is then sent to the domain name server.

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

5. The method according to claim 2, characterized in that, Sending the first response corresponding to the first request to the terminal device includes: The second type identifier in the second response is modified to the first type identifier, and the first prefix identifier is deleted to generate the first response corresponding to the first request, and the first response is sent to the terminal device.

6. An access method, characterized in that, The method is applied to a domain name server, and the method includes: Receive a second request sent by a Broadband Access Server (BRAS); wherein the second request includes a first prefix identifier corresponding to the BRAS, the second request is used to request a second record of a first domain name, the first prefix identifier is included in a first policy configured in the Broadband Access Server (BRAS), the first policy includes a prefix identifier corresponding to each BRAS, and the first policy is used to instruct the terminal device to send the corresponding address translation prefix. Obtain the second record corresponding to the first prefix identifier, and send a second response to the Broadband Access Server (BRAS). The second response includes the second record; the second record includes the address translation prefix corresponding to the first prefix identifier.

7. The method according to claim 6, characterized in that, 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.

8. The method according to claim 6, characterized in that, Before receiving the second request sent by the Broadband Access Server (BRAS), the method further includes: Configure multiple second records, each corresponding to a different prefix identifier.

9. The method according to claim 8, characterized in that, 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 plurality of prefix identifiers.

10. An access method, characterized in that, The method is applied to a terminal device, and the method includes: Send a first request to the Broadband Access Server (BRAS); the first request is used to request the first record of the first domain name; Receive a first response corresponding to the first request sent by the Broadband Access Server (BRAS); wherein the first response includes the first record, the first record includes the address translation prefix corresponding to the first prefix identifier of the BRAS, the first prefix identifier is included in the first policy configured by the Broadband Access Server (BRAS), the first policy includes the prefix identifier corresponding to each BRAS, and the first policy is used to indicate that the corresponding address translation prefix is ​​sent to the terminal device. The IPv4 destination address is modified to an IPv6 destination address based on the address translation prefix, so as to initiate access to the IPv6 destination address.

11. The method according to claim 10, 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.

12. The method according to claim 10, characterized in that, The first specified bit and the second specified bit of the first record are respectively the address translation prefix and the first prefix identifier; the step of modifying the IPv4 destination address to an IPv6 destination address according to the address translation prefix includes: The terminal device extracts the first designated bit from the first record as the address translation prefix; The address translation prefix and the IPv4 destination address are combined to obtain the IPv6 destination address.

13. An access device, characterized in that, The device is applied to a Broadband Access Server (BRAS), and the device includes: a first receiving unit, a first transmitting unit, and a first processing unit; wherein... The first receiving unit is configured to receive a first request sent by the terminal device; the first request is configured to request a first record of a first domain name; The first sending unit is configured to send a second request to the domain name server, the second request including 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 an address translation prefix corresponding to the first prefix identifier; The first sending unit is further configured to send a first response corresponding to the first request to the terminal device. The first response includes the first record, and the first record includes an address translation prefix corresponding to the first prefix identifier. The first record is used by the terminal device to modify the IPv4 destination address to an IPv6 destination address in order to initiate access to the IPv6 destination address. The first processing unit is configured to configure a first policy before the first receiving unit receives a first request sent by the terminal device. The first policy is used to instruct the terminal device to send a corresponding address translation prefix. The first policy includes a prefix identifier corresponding to each BRAS.

14. An access device, characterized in that, The device is applied to a domain name server, and the device includes: a second receiving unit, a second processing unit, and a second sending unit; wherein... The second receiving unit is configured to receive a second request sent by a Broadband Access Server (BRAS); wherein the second request includes a first prefix identifier corresponding to the BRAS, the second request is used to request a second record of a first domain name, the first prefix identifier is included in a first policy configured in the Broadband Access Server (BRAS), the first policy includes a prefix identifier corresponding to each BRAS, and the first policy is used to instruct the terminal device to send the corresponding address translation prefix. The second processing unit is used to obtain the second record corresponding to the first prefix identifier; The second sending unit is configured to send a second response to the Broadband Access Server (BRAS), the second response including the second record; the second record including an address translation prefix corresponding to the first prefix identifier.

15. An access device, characterized in that, The device is applied to a terminal equipment, and the device includes: 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); wherein the first response includes the first record, the first record includes an address translation prefix corresponding to a first prefix identifier of the BRAS, the first prefix identifier is included in a first policy configured in the Broadband Access Server (BRAS), the first policy includes a prefix identifier corresponding to each BRAS, and the first policy is used to instruct the terminal device to send the corresponding address translation prefix. The third processing unit is used to modify the IPv4 destination address to an IPv6 destination address according to the address translation prefix, so as to initiate access to the IPv6 destination address.

16. 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, it implements the steps of the method according to any one of claims 1 to 5, or; When the processor executes the program, it implements the steps of the method according to any one of claims 6 to 9, or; When the processor executes the program, it implements the steps of the method according to any one of claims 10 to 12.

17. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program performs the steps of the method according to any one of claims 1 to 5, or; When executed by a processor, the program performs the steps of the method according to any one of claims 6 to 9, or; When executed by a processor, the program performs the steps of the method according to any one of claims 10 to 12.

18. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method according to any one of claims 1 to 5, or; When executed by a processor, the computer program implements the method according to any one of claims 6 to 9, or; When the computer program is executed by a processor, it implements the method according to any one of claims 10 to 12.

Images