WO2009043273A1 - Méthode, système et appareil d'identification d'un routeur mobile - Google Patents

Méthode, système et appareil d'identification d'un routeur mobile Download PDF

Info

Publication number
WO2009043273A1
WO2009043273A1 PCT/CN2008/072471 CN2008072471W WO2009043273A1 WO 2009043273 A1 WO2009043273 A1 WO 2009043273A1 CN 2008072471 W CN2008072471 W CN 2008072471W WO 2009043273 A1 WO2009043273 A1 WO 2009043273A1
Authority
WO
WIPO (PCT)
Prior art keywords
nemo
mobile router
end device
routing
identifying
Prior art date
Application number
PCT/CN2008/072471
Other languages
English (en)
Chinese (zh)
Inventor
Yuankui Zhao
Ke Lin
Wentao Zhong
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2009043273A1 publication Critical patent/WO2009043273A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W40/00Communication routing or communication path finding
    • H04W40/24Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246Connectivity information discovery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/005Moving wireless networks

Definitions

  • Embodiments of the present invention relate to the field of network communication technologies, and in particular, to a mobile router identification method, system, and apparatus. Background technique
  • Mobile Internet Internet Protocol
  • IETF Internet Engineering Task Force
  • Mobile IP establishes an address mapping and uses a special routing mechanism to ensure that the original IP communication connection of a single node is not interrupted during the mobile process.
  • NEMO Mobile Network, a network that moves the entire network as a unit
  • MR Mobile Router
  • NEMO provides mobile support for one or more subnets as it provides mobile support for a single node compared to the Mobile IP protocol.
  • MR also registers the maintenance network prefix information MNP (Mobile Network Pre-fix) with the home agent based on all the functions of mobile IPv6.
  • MNP Mobile Network Pre-fix
  • the home agent of MR After receiving the network registration of the MR, the home agent of MR maintains the reachability of the mobile network prefix in the home network, and is responsible for transmitting the data packet with the destination address of MNP to the MR in a tunnel encapsulation manner; on the other hand, MR will be in the network. All the packets of the node are transmitted to the home agent in the form of tunnel encapsulation, and are normally routed to the communication peers by the home agent.
  • Proxy Mobile IPv6 is also an extension of Mobile IPv6. It introduces two new network entities, MAG (Mobile Access Gateway) and LMA (Local Mobile Anchor). Provide mobility support for mobile nodes that do not have mobility management capabilities through the network side.
  • MAG Mobile Access Gateway
  • LMA Local Mobile Anchor
  • the network side announces the node before signing the network by advertising the node to the mobile node.
  • the suffix information is "forged" into the home network of the mobile node.
  • the network entity MAG replaces the mobile node with the registration binding specified by the MIPv6 protocol to the LMA, and the LMA coordinates the different MAGs. Processing, advertising the same network prefix to the mobile node, causing the mobile node to "always" in the same network without the need for mobility management operations.
  • NEMO introduces the concept of mobile routers. Because mobile routers are quite different from traditional fixed routers, if they are applied without distinction, there may be problems in the following application scenarios:
  • PMIPv6+NEMO scenario MR as the served node of PMIPv6 domain
  • the schematic diagram of the hybrid network of ⁇ and NEMO is shown in Figure 1.
  • the MAG in PMIPv6 is difficult to distinguish between MR and MN (Mobile Node), and does not understand ⁇ prefix.
  • MN Mobile Node
  • the MN may select the MR as the default router during the process of selecting the upper-layer router. As a result, the nested NEMO routes are not optimized, as shown in Figure 2. As shown in Figure 3.
  • the MN receives the route advertisement RA message of the mobile router MR and the fixed router FR at the same time. If you choose a mobile router as the default router, you will have more routing overhead and latency than choosing a fixed router as the default router.
  • NEMO generally does not optimize routes in nested scenarios. If you want to optimize, It is also necessary to determine the specific optimization mode through capability negotiation. The method used to optimize the route is to distinguish the mobile router from the fixed router.
  • each MR is not a router relationship, but a relationship between the access router and the served node.
  • the mobile IPv6 protocol is run between the MRs instead of the routing protocol.
  • Figure 4 MR2 uses MR1 as the default router, MR3 uses MR2 as the default router, and MR1 uses MR3 as the default router to form a loopback.
  • MR3 wants to send a packet to a node on the Internet, the packet is cyclically forwarded inside the loopback and cannot be forwarded outside the NEMO domain.
  • Mobile IPv6 nodes can implement mobility management themselves, while PMIPv6 and NEMO are nodes, which may not require ⁇ or NEMO services, or PMIPv6 and NEMO can capture different processing modes for different types of mobile nodes. Failure to distinguish the type of node may result in mandatory service and insufficient use of resources.
  • the inventors have found that the prior art has at least the following problems: The identity of the mobile router cannot be identified, and if the mobile router and the fixed router are applied indiscriminately, in the above six scenarios, normal operation cannot be performed. Or more optimized processing. Summary of the invention
  • Embodiments of the present invention provide a method, system, and device for identifying a mobile router, Realize the identity of the mobile router, make the network function normal and more optimal processing.
  • an embodiment of the present invention provides a method for identifying a mobile router, including:
  • the receiving end device receives a routing message sent by the sending end device, where the routing message includes
  • the receiving end device determines that the routing message includes NEMO capability information, identifying that the transmitting end device that sends the routing message has NEMO capability.
  • an embodiment of the present invention further provides an identification system for a mobile router, including:
  • a sending end device configured to send a routing message, where the routing message includes NEMO capability information
  • the receiving end device is configured to receive a routing message sent by the sending end device, and determine whether the routing message includes NEMO capability information, if Including, identifying that the source device has NEMO capability.
  • the embodiment of the present invention further provides a sending end device, including: an information setting module, configured to add and set NEMO capability information to a routing message; and a sending module, connected to the information setting module, for The routing message is sent to the receiving device, and the routing message includes NEMO capability information.
  • the embodiment of the present invention further provides a receiving end device, including: a receiving module, configured to receive a routing message sent by a sending end device, where the routing message includes NEMO capability information;
  • an identifying module configured to identify that the sending end device has NEMO capability if it is determined that the routing message received by the receiving module includes NEMO capability information.
  • DRAWINGS 1 is a schematic diagram of a hybrid network of a prior art PMIPv6 and NEMO;
  • FIG. 2 is a schematic diagram 1 of a default router selection of a NEMO nested scenario in the prior art;
  • FIG. 3 is a schematic diagram 2 of a default router selection of a NEMO nested scenario in the prior art;
  • FIG. 5 is a schematic diagram of route optimization of a prior art NEMO
  • FIG. 6 is a flowchart of a method for identifying a mobile router according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of operations of a mobile router according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of operation of a mobile access gateway [ProxyMIPv6-02] according to an embodiment of the present invention.
  • FIG. 9 is a structural diagram of an identification system of a mobile router according to an embodiment of the present invention. detailed description
  • An embodiment of the present invention provides a method for identifying a mobile router.
  • NEMO capability information is added to a routing message, for example: mobile router identification information, by which the receiving device can identify and send the route.
  • the device at the sending end of the message has the NEMO capability, thereby realizing the capability negotiation between the transmitting device and the receiving device, and ensuring the normal and more optimized implementation of the network function.
  • the mobile router is used as an example to describe the NEMO-capable transmitting device.
  • the embodiment of the present invention is not limited thereto, and any NEMO-capable transmitting device should fall within the protection scope of the embodiment of the present invention. .
  • a flowchart of a method for identifying a mobile router specifically includes the following steps:
  • Step S601 The receiving end device receives a routing message sent by the sending end device, where the routing message includes NEMO capability information.
  • the routing message includes a routing request message and a route advertisement message, and the NEMO capability information includes but is not limited to mobile router identification information.
  • the embodiment of the present invention modifies the route request message (RS) in the neighbor discovery protocol [RFC2461], and adds NEMO capability information, for example: mobile router identification information, indicating that the node that sends the message is a mobile router, and the modified message is as shown in the table. 1 is shown. Table 1
  • the R flag in Table 1 is the mobile router identification information.
  • the sender device that sends the route request message is the mobile router; otherwise, the R flag is set to 0.
  • the receiving device that does not support the solution provided by the embodiment of the present invention must ignore the flag.
  • the sending end device adds an R flag bit in the routing request message, sets the R flag bit, and then sends a routing request message carrying the R flag bit to the receiving end device.
  • the embodiment of the present invention modifies a route advertisement message (RA) defined by the neighbor discovery protocol [RFC2461] and improved by mobile IPv6 [RFC3775], by adding a NEMO capability information, for example: mobile router identification information, indicating that the The sender device of the route advertisement message is a mobile router, which can provide [RFC3963] and later NEMO related capability support.
  • RA route advertisement message
  • RRC2461 neighbor discovery protocol
  • RFID3775 mobile IPv6
  • the modified route advertisement message is shown in Table 2:
  • the R flag in Table 2 is the mobile router identification information.
  • the network side device that sends the route advertisement message is the mobile router; otherwise, the R flag is set to 0.
  • the receiving device that does not support the solution provided by the embodiment of the present invention must ignore the flag.
  • the sender device adds an R flag to the route advertisement message, sets the R flag, and then sends a route advertisement message carrying the R flag to the receiving device.
  • the NEMO capability information in the embodiment of the present invention is represented by DHCP (Dynamic Host) Configure Protocol, Dynamic Host West Protocol Protocol, or AAA (Authentication Authorization Accounting) messages are carried.
  • DHCP Dynamic Host
  • the sending end device that sends the routing request message is the requesting access node
  • the receiving end device that receives the routing request message is the network side device
  • the sending end device that sends the routing advertisement message is the network side device, and receives the route advertisement.
  • the receiving device of the message is an access node.
  • the network side device may be a mobile access gateway MAG, an authentication and authorization charging server, an AAA server, or the like.
  • Step S602 If the receiving device determines that the routing message includes NEMO capability information, it identifies that the transmitting device that sends the routing message has the NEMO capability.
  • the receiving device After receiving the routing message, the receiving device first performs legality detection and subsequent processing on the routing request message according to the [RFC2461], and then detects whether the routing message contains NEMO capability information. If included, the receiving device recognizes that the transmitting device transmitting the routing message has NEMO capability.
  • the mobile router is used as an example to describe the NEMO-capable transmitting device.
  • the embodiment of the present invention is not limited thereto, and any NEMO-capable transmitting device should fall within the protection scope of the embodiment of the present invention.
  • the received routing message includes NEMO capability information, for example: mobile router identification information
  • the receiving device identifies that the sending device that sends the routing message is a mobile router; if the NEMO capability information is not included, the receiving device identifies and sends the The sending device of the routing message is not a mobile router, for example: It may be a mobile host or a general fixed node.
  • the network side device When the routing message sent is a routing request message, the network side device identifies that the requesting access node that sends the routing request message is a mobile router, and after the network side device identifies that the requesting access node that sends the routing request message is the mobile router, The network side device provides a proxy mobility management mode and/or a route optimization method for the mobile router.
  • the access node When the route message sent is a route advertisement message, the access node identifies that the network side device that sends the route advertisement message is a mobile router.
  • the NEMO capability information is added and set in the routing message, so that the receiving device that receives the routing message can identify that the sending device that sends the routing message is a mobile router, thereby making up for the prior art.
  • Identification shift A defect in the identity of the mobile router.
  • FIG. 7 it is a schematic diagram of operations of a mobile router according to an embodiment of the present invention, which specifically includes the following processes:
  • a route request message should be sent in accordance with the provisions of [RFC2461];
  • the mobile router when the condition for transmitting a route request message specified in [RFC2461] is satisfied, the mobile router must transmit a route request message as shown in Table 1; the network side device identifies by the route request message When the identity of the mobile router is out, the network side device provides a proxy mobility management mode and/or a route optimization method for the mobile router.
  • a route advertisement message shall be sent in accordance with the provisions of [RFC2461];
  • the mobile router when the condition for transmitting a route advertisement message specified in [RFC2461] is satisfied, the mobile router must transmit a route advertisement message as shown in Table 2;
  • the mobile router After receiving the route request message, the mobile router first performs legality detection and subsequent processing on the route request message according to the provisions of [RFC2461];
  • the mobile router detects the mobile router identification information, for example: R flag: If the R flag is set, it indicates that the requesting access node that sends the routing request message is a mobile router, and if the routing request message is received, The router can provide [RFC3963] and later NEMO related capability support (such as NEMO route optimization), and then prepares to provide NEMO related capability support for the requesting access node; if not set, it indicates that the route request message is sent.
  • the nodes are mobile hosts or general fixed nodes and do not need to provide NEMO-related support.
  • the mobile router After receiving the route request message, the mobile router first follows [RFC2461] Provisioning for legality detection and related processing of route advertisement messages;
  • the mobile router detects the mobile router identification information, for example: R flag: If the R flag is set, it indicates that the network side device that sends the route advertisement message is a mobile router, and can provide the served access node. [RFC3963] and later support of NEMO related capabilities; if the R flag is not set, it means that the network side device that sends the route advertisement message is a fixed router, and the mobile router accessing the router should be a NEMO. The root of the mobile router is ready.
  • R flag If the R flag is set, it indicates that the network side device that sends the route advertisement message is a mobile router, and can provide the served access node. [RFC3963] and later support of NEMO related capabilities; if the R flag is not set, it means that the network side device that sends the route advertisement message is a fixed router, and the mobile router accessing the router should be a NEMO. The root of the mobile router is ready.
  • FIG. 8 it is an operation diagram of a mobile access gateway [ProxyMIPv6-02] according to an embodiment of the present invention.
  • the mobile access gateway MAG is a network entity of [ProxyMIPv6-02] defined by PMIPv6, which is equivalent to MIPv6 [RFC3775].
  • AR Access Router, Access Router).
  • the MAG first performs legality detection and subsequent processing on the routing request message in accordance with the provisions of [RFC2461];
  • the MAG checks the mobile router identification information in the route request message, for example: R flag bit:
  • the R flag bit indicates that the requesting access node is a mobile router, then when the MAG sends a proxy binding message to the home agent of the requesting access node on behalf of the requesting access node, it needs to add in the message.
  • Mobile network prefix MNP option indicates that the MAG cannot increase the MNP option, for example, does not understand NEMO's MAG, then the MAG should refuse to provide the node with the ⁇ service;
  • the operation of the mobile host is also modified.
  • MIPv6 [RFC3775]
  • the binding lifetime of the home registration is up to 420 seconds.
  • the mobile host remains relatively stationary relative to the mobile router for a longer period of time, such as: mobile routers on the aircraft and mobile terminals of the passengers. Then, the longest bound lifetime of 420 seconds will cause the mobile host to initiate home registration too much.
  • the mobile host After receiving the route advertisement message, the mobile host
  • the mobile host may choose to set the lifetime of the home registration and the peer registration to a larger value, and reduce the number of registrations;
  • R flag is not set, then identifying the general fixed router that sent the route advertisement message, the mobile host's lifetime selection for home registration and peer registration should follow [RFC3775].
  • RA message of the route advertisement. You can also set the RA message as follows: Make the RA message: With the R flag, clear the identity of the Router; With the Router level option, it is convenient for the lower MR to select the default Router. Avoid nesting; With the Root-MR-CoA option, it is convenient for the MR to prompt the HA for nesting optimization in the BU message; with the N flag, it indicates that the protocol definition of NEMO RFC3963 is supported, and the corresponding capability support is provided.
  • the routing request RS message can also be set as follows: the RS message: with the R flag, indicating that this is a mobile router supporting the RFC3963 or NEMO related protocol; with the N flag indicating the mobile router/mobile terminal requirements
  • the network side device provides RFC3963, which is related to NEMO protocol support.
  • the above settings for the RA message and the RS message can be used in combination even if they contain the N/R flag.
  • the above is only a few preferred ways to add the identifier bit to the RA message and the RS message. Any modification to the RA message and the RS message to identify the identity of the mobile router should fall within the protection scope of the embodiment of the present invention.
  • FIG. 9 it is a structural diagram of an identification system of a mobile router according to an embodiment of the present invention, including a transmitting end device 1 and a receiving end device 2.
  • the sender device 1 is configured to send a routing message, where the routing message includes NEMO capability information.
  • Receiver device 2 for receiving and transmitting Sending a routing message sent by the device 1 and determining whether the routing message contains NEMO capability information. If yes, the sender device is identified as a mobile router.
  • the sender device 1 includes an information setting module 11 and a sending module 12.
  • the information setting module 11 is configured to add and set NEMO capability information to the routing message.
  • the sending module 12 is connected to the information setting module 11 and is configured to send a routing message set by the information setting module 11 to the receiving device 2, where the routing message includes NEMO capability information.
  • the receiving device 2 includes a receiving module 21 and a determining module 22.
  • the receiving module 21 is configured to receive a routing message sent by the sending end device 1, where the routing message includes NEMO capability information.
  • the identification module 22 is configured to identify the sender device 1 as a mobile router if it is determined that the routing message received by the receiving module 21 includes NEMO capability information.
  • the transmitting device 1 adds and sets the NEMO capability information in the routing message, so that the receiving device 2 that receives the routing message can identify the transmitting device 1 that sends the routing message as the mobile router, thereby It compensates for the defect that the prior art cannot identify the identity of the mobile router.
  • the present invention can be implemented by hardware or by software plus a necessary general hardware platform.
  • the technical solution of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention porte sur une méthode, un système et un appareil d'identification. Ladite méthode comporte les étapes suivantes: un dispositif côté réception reçoit un message de routeur envoyé par le dispositif côté expédition contenant une information d'habilitation NEMO (S601); si le dispositif côté réception confirme que le message du routeur contient l'information d'habilitation NEMO, il identifie que le dispositif côté expédition ayant envoyé le message du routeur a bien l'habilitation NEMO (S602). Dans l'invention, l'information d'habilitation NEMO a été ajoutée au message du routeur. Ainsi, le dispositif côté réception recevant le message du routeur peut identifier si le dispositif côté expédition possède l'habilitation NEMO via l'information d'habilitation NEMO. L'invention comble une lacune de l'art antérieur selon laquelle le dispositif côté réception ne peut identifier si le dispositif côté expédition a ou non l'habilitation NEMO. Les fonctions du réseau peuvent ainsi être mises en oeuvre normalement et optimalement.
PCT/CN2008/072471 2007-09-28 2008-09-23 Méthode, système et appareil d'identification d'un routeur mobile WO2009043273A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2007101518874A CN101399752B (zh) 2007-09-28 2007-09-28 一种移动路由器的识别方法、系统和装置
CN200710151887.4 2007-09-28

Publications (1)

Publication Number Publication Date
WO2009043273A1 true WO2009043273A1 (fr) 2009-04-09

Family

ID=40518020

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/072471 WO2009043273A1 (fr) 2007-09-28 2008-09-23 Méthode, système et appareil d'identification d'un routeur mobile

Country Status (2)

Country Link
CN (1) CN101399752B (fr)
WO (1) WO2009043273A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1589538A (zh) * 2001-11-14 2005-03-02 诺基亚公司 支持ipv6的移动路由器
KR20050065990A (ko) * 2003-12-26 2005-06-30 한국전자통신연구원 망 이동성을 지원하는 인터넷 시스템 및 경로 최적화 방법
CN1745558A (zh) * 2003-02-11 2006-03-08 思科技术公司 在移动路由器和对端节点之间建立双向隧道的布置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100536471C (zh) * 2006-04-27 2009-09-02 北京交通大学 一种家乡代理信令消息有效保护方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1589538A (zh) * 2001-11-14 2005-03-02 诺基亚公司 支持ipv6的移动路由器
CN1745558A (zh) * 2003-02-11 2006-03-08 思科技术公司 在移动路由器和对端节点之间建立双向隧道的布置
KR20050065990A (ko) * 2003-12-26 2005-06-30 한국전자통신연구원 망 이동성을 지원하는 인터넷 시스템 및 경로 최적화 방법

Also Published As

Publication number Publication date
CN101399752B (zh) 2011-07-06
CN101399752A (zh) 2009-04-01

Similar Documents

Publication Publication Date Title
JP4954219B2 (ja) Ipとセルラーモビリティとの組み合わせ
US7697930B2 (en) Method and apparatus for mobility management in wireless networks
RU2628486C2 (ru) Системы и способы доступа к сети
US7447182B2 (en) Discovering an address of a name server
JP5554342B2 (ja) アクセスネットワークへの接続又はハンドオーバの後のセキュアトンネルの確立
TWI357771B (en) Techniques to manage roaming
US7733824B2 (en) Fixed access point for a terminal device
US9516495B2 (en) Apparatus and methods of PMIPv6 route optimization protocol
JP4823233B2 (ja) 複数のpanaセッション
EP2401873B1 (fr) Fonctionnalité d'équilibrage de charge et de redirection à base d'envoi à la cantonade ipv6 pour pmipv6
US20060291426A1 (en) Method and apparatus for performing fast handover in wireless network
JP2009524275A5 (fr)
CA2637025A1 (fr) Procede et appareil permettant d'effectuer un transfert dans un systeme de communication utilisant un protocole internet mobile
JP2010532959A (ja) 移動ノード内に実装されたモビリティ機能の検知
TW201119296A (en) Method and apparatus for multicast mobility
WO2006124577A2 (fr) Utilisation d'un nom de point d'accès pour sélectionner un noeud passerelle d'accès
EP2168321A1 (fr) Réductions des tailles d'en-têtes de paquets de données
WO2010072074A1 (fr) Procédé, système et passerelle d'accès mobile destinés à optimiser un routage local
WO2010000174A1 (fr) PROCÉDÉ ET DISPOSITIF POUR L’ENREGISTREMENT, LA COMMUNICATION ET LE TRANSFERT INTERCELLULAIRE DE NœUDS MOBILES
KR20090020095A (ko) 이종망에서 인접 탐색 수행 방법 및 장치
WO2009097720A1 (fr) Procédé et appareil pour découvrir une liaison domestique dans un mip
WO2010072135A1 (fr) Procédé, dispositif et système de transfert de réseau
US7599345B2 (en) Method, network elements, a terminal, a network infrastructure, and a communication system for triggering events
US8634394B1 (en) Mechanism to verify packet data network support for internet protocol mobility
JP2002529021A (ja) 共通ipアドレス付きの移動端末および無線装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08800960

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08800960

Country of ref document: EP

Kind code of ref document: A1