WO2024203907A1 - 通信装置、制御装置、及び通信方法 - Google Patents

通信装置、制御装置、及び通信方法 Download PDF

Info

Publication number
WO2024203907A1
WO2024203907A1 PCT/JP2024/011406 JP2024011406W WO2024203907A1 WO 2024203907 A1 WO2024203907 A1 WO 2024203907A1 JP 2024011406 W JP2024011406 W JP 2024011406W WO 2024203907 A1 WO2024203907 A1 WO 2024203907A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal
mld
communication
response
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2024/011406
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
悠介 田中
浩介 相尾
茂 菅谷
龍一 平田
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sony Group Corp
Original Assignee
Sony Group Corp
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 Sony Group Corp filed Critical Sony Group Corp
Priority to EP24780025.3A priority Critical patent/EP4694553A4/en
Priority to JP2025510748A priority patent/JPWO2024203907A1/ja
Priority to CN202480020650.4A priority patent/CN120917859A/zh
Publication of WO2024203907A1 publication Critical patent/WO2024203907A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/18—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection
    • H04W36/185—Performing reselection for specific purposes for allowing seamless reselection, e.g. soft reselection using make before break
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]

Definitions

  • This disclosure relates to a communication device, a control device, and a communication method.
  • a STA When a STA performs a roaming operation, it needs to perform connection processing for the new AP to which it will connect. In other words, it needs to re-associate with the new AP and exchange encryption keys using a 4-way handshake. These operations generally take about 10 ms and may cause communication delays. In addition, since the break-before-make method is used when reconnecting, the communication path to the STA is temporarily cut off, which may reduce the reliability of communications.
  • Non-patent document 1 presents Multi-Link Device (MLD)-based Multi-AP seamless roaming.
  • Multi-AP seamless roaming is a method in which multiple physically separated APs are grouped together by an AP MLD entity, which is a logical entity, and the APs in the group are operated virtually as a single AP MLD. STAs roam between these APs, allowing STAs to roam without interrupting data transmission to the STA.
  • MLD Multi-Link Device
  • the present disclosure aims to provide a communication device, a control device, and a communication method that reduce communication delays.
  • the communication device disclosed herein includes a communication unit that receives a connection request from a terminal that is wirelessly connected to multiple base stations via different links, and a control unit that acquires terminal information, which is information about the terminal that is required for communication with the terminal, from a control entity that controls the multiple base stations in response to the reception of the connection request or in response to the distance from the terminal, and the communication unit transmits a connection response indicating that the terminal information has been acquired.
  • FIG. 1 is a diagram showing an example of a system configuration according to an embodiment of the present invention.
  • FIG. 2 is a block diagram of an AP equipped with a communication device according to the embodiment. Block diagram of a Non-AP MLD equipped with a communication device of this embodiment. Block diagram of a configuration in which the AP MLD entity is realized by a device other than the AP.
  • FIG. 2 is a diagram showing a logical configuration of the system architecture according to the present embodiment.
  • FIG. 2 is a diagram showing an example of a physical configuration of a system architecture according to the present embodiment.
  • FIG. 1 is a block diagram of a configuration example of an AP equipped with a wired communication unit.
  • FIG. 13 is a diagram showing another example of the physical configuration of the system architecture in the present embodiment.
  • a diagram showing an example of a SAP connecting the MLD Upper MAC Sublayer and the MLD Lower MAC Sublayer. 1 shows a first example of a sequence in this embodiment.
  • 11 shows a second example of a sequence in this embodiment.
  • 11 shows a third example of a sequence in this embodiment.
  • 13 shows a fourth example of a sequence in this embodiment.
  • FIG. 1 is a block diagram showing a schematic configuration example of a smartphone to which the present embodiment is applied.
  • FIG. 1 is a block diagram showing an example of a schematic configuration of an in-vehicle device to which the present embodiment is applied.
  • FIG. 2 is a block diagram showing an example of a schematic configuration of a wireless AP to which the present embodiment is applied.
  • Figure 1 shows an example of a system configuration according to this embodiment.
  • the system in Figure 1 comprises an AP MLD (Multi Link Device) entity 300, AP1, AP2, AP3, and one or more Non-AP MLDs 200.
  • AP MLD Multi Link Device
  • AP1 to AP3 any AP will be referred to as AP100.
  • AP MLD entity 300 is a logical entity, and is physically realized by a central control device, a device on the cloud or an edge device, or any of APs AP1 to AP3.
  • a device that realizes AP MLD entity 300 is also referred to as a control device.
  • the control device is also the AP.
  • AP1 to AP3 are communication devices or wireless communication devices equivalent to base stations.
  • AP1 and AP2 have a connection relationship with AP MLD entity 300, and one AP MLD is virtually realized by AP1, AP2 and AP MLD entity 300.
  • AP MLD entity 300 is a control entity that controls AP1 and AP2.
  • AP1 and AP2 belong to a group of APs (AP MLD group) that make up the AP MLD.
  • the arcs centered on AP1, AP2 and AP3 indicate their respective coverages E1, E2 and E3.
  • the Non-AP MLD 200 is a communication device or wireless communication device equivalent to a terminal device (or STA) that supports Multi-Link Operation (MLO).
  • the Non-AP MLD 200 is connected to the AP MLD via AP1 and AP2.
  • the solid lines connecting the Non-AP MLD 200 to AP1 and AP2 indicate that the Non-AP MLD 200 is wirelessly connected to the AP MLD.
  • the Non-AP MLD 200 may be held by a user or mounted on a mobile device such as a robot or AGV, and moves as the user or robot moves. In the following explanation, it is assumed that the Non-AP MLD 200 can move while communicating with the AP MLD. Although only one Non-AP MLD 200 is shown in the figure, in reality there may be two or more Non-AP MLDs.
  • [Device configuration] 2 is a block diagram of the AP 100 (AP1 to AP3).
  • the AP 100 corresponds to a communication device, a wireless communication device, or a base station according to this embodiment, and will hereinafter also be referred to as a communication device 100.
  • the wireless communication device 100 mainly includes a communication unit 110, a control unit 130, a storage unit 140, and an antenna 150.
  • the communication unit 110 includes a communication control unit 111, a communication storage unit 112, a common data processing unit 113, a system R11, and a system R12.
  • the communication unit 110 can be realized by one or more LSIs.
  • System R11 and system R12 each include an individual data processing unit 121, a signal processing unit 122, a wireless interface unit 123, one or more amplifier units 124, and one or more antennas 150.
  • a system is composed of a set of the individual data processing unit 121, the signal processing unit 122, the wireless interface unit 123, the amplifier unit 124, and the antenna 150.
  • Each system functions as a transceiver, including a transmitter that transmits signals and a receiver that receives signals.
  • Each system performs wireless communication using a different link.
  • a link is a wireless transmission path that can transmit data between communication devices, and may be described as a wireless link.
  • the links used by each system may have different frequency bands or may be the same.
  • Each system may be provided with a memory unit.
  • the devices connected to the links used in each system may be different communication devices or may be the same communication device. For example, one link may be used to communicate with the Non-AP MLD 200, and the other link may be used to communicate with an AP MLD entity 300 that is realized as a control device separate from the AP 100.
  • One system may also be used to communicate with multiple communication devices.
  • one system may be used to communicate with the Non-AP MLD 200, and also with an AP MLD entity 300 that is realized as a device separate from the AP 100. It is also possible to configure one of the two systems to be used (active) and the other not to be used (inactive).
  • the communication control unit 111 controls the operation of each unit and the transmission of information between each unit. It also controls the transfer of control information and management information to be notified to other communication devices to the common data processing unit 113, system R11, and system R12.
  • the communication control unit 111 has the function of an MLD management entity.
  • the communication memory unit 112 holds information used by the communication control unit 111.
  • the communication memory unit 112 holds data to be transmitted and data received.
  • the communication memory unit 112 holds data to be transmitted to the Non-AP MLD 200 and data received from the Non-AP MLD 200.
  • the communication memory unit 112 holds data to be transmitted to the AP MLD entity 300 and data received from the AP MLD entity 300.
  • the common data processing unit 113 When transmitting, the common data processing unit 113 performs sequence management of the data stored in the communication memory unit 112 and the control information and management information received from the communication control unit 111, performs encryption processing, etc., and allocates the processed data to each individual data processing unit 121. When receiving, the common data processing unit 113 performs data decryption processing and reordering processing.
  • the common data processing unit 113 has the functions of Upper MAC (Higher MAC) and MLD entity.
  • the encryption processing may be performed using an encryption key obtained by a procedure such as a 4-way handshake performed with the Non-AP MLD 200.
  • each individual data processing unit 121 When transmitting, each individual data processing unit 121 performs channel access operations based on carrier sense, adds a MAC (Media Access Control) header to the data to be transmitted and an error detection code to generate a data unit, and performs processing to concatenate multiple data units.When receiving, it performs processing to deconcatenate the MAC header of the received data unit, analyze and detect errors, and request retransmission.
  • the individual data processing unit 121 is also called the Lower MAC.
  • each signal processing unit 122 When transmitting, each signal processing unit 122 performs encoding, interleaving, modulation, etc. on the data unit, adds a physical header, and generates a symbol stream. At this time, each signal processing unit 122 may perform spatial multiplexing processing for MIMO (Multiple Input Multiple Output). However, each signal processing unit 122 may not perform spatial multiplexing processing, and may apply an arbitrary delay amount (hereinafter, cyclic shift delay CSD: Cyclic Shift Delay) to each antenna 150.
  • cyclic shift delay CSD Cyclic Shift Delay
  • each signal processing unit 122 analyzes the physical header, and performs demodulation, deinterleaving, decoding, etc. on the symbol stream to generate a data unit. Furthermore, each signal processing unit 122 estimates complex channel characteristics and performs spatial separation processing as necessary.
  • each wireless interface unit 123 When transmitting, each wireless interface unit 123 performs digital-to-analog signal conversion, filtering, up-conversion, and phase control on the symbol stream to generate a transmission signal. When receiving, each wireless interface unit 123 performs down-conversion, filtering, and analog-to-digital signal conversion on the received signal to generate a symbol stream.
  • the amplifier unit 124 of each system amplifies the signal input from the wireless interface unit 123 or the antenna 150.
  • a part of the amplifier unit 124 may be a component outside the communication unit 110. Also, a part of the amplifier unit 124 may be included in the wireless interface unit 123.
  • the control unit 130 controls the communication unit 110 and the communication control unit 111.
  • the control unit 130 may also perform some of the operations of the communication control unit 111.
  • the communication control unit 111 and the control unit 130 may also be configured as a single block.
  • the control unit of the base station corresponds, as an example, to the communication control unit 111, or to at least one of the communication control unit 111 and the control unit 130.
  • the functions of the AP MLD entity 300 may be executed by the communication control unit 111, or a combination of the communication control unit 111 and the common data processing unit 113, or a combination of the communication control unit 111, the common data processing unit 113, and the control unit 130.
  • the memory unit 140 holds information used by the control unit 130 and the communication unit 110.
  • the memory unit 140 may also perform some of the operations of the communication memory unit 112.
  • the memory unit 140 and the communication memory unit 112 may be configured as a single block.
  • the individual data processing unit 121 and the signal processing unit 122 may be configured as one group, and multiple groups may be connected to one wireless interface unit 123. In other words, one wireless interface unit 123 may be shared by multiple systems. Also, the wireless interface unit 123, the amplifier unit 124, and the antenna 150 may be configured as one group, and multiple groups may be connected to one signal processing unit 122. In other words, the signal processing unit 122 may be shared by multiple systems. In this case, there may be one or more individual data processing units 121.
  • the communication control unit 111 may acquire terminal information, which is information about the Non-AP MLD 200, from the AP MLD entity 300 in response to the Non-AP MLD 200 (terminal device) selecting its own AP as the AP to which it will connect for roaming (handover) and receiving a connection request from the Non-AP MLD 200.
  • the communication control unit 111 may transmit a request to acquire terminal information to the AP MLD entity 300, and acquire the terminal information transmitted from the AP MLD entity 300 (control device) in response to the acquisition request.
  • the terminal information includes information about the capabilities of the Non-AP MLD 200 and information about security settings (encryption, etc.) as information necessary for communication with the Non-AP MLD 200.
  • the communication control unit 111 controls the transmission of a connection response to the Non-AP MLD 200 indicating that the terminal information has been acquired.
  • This connection response is also a notification that the connection process with the Non-AP MLD 200 has been completed. This allows subsequent processing (authentication processing) in the connection process to be omitted.
  • the communication control unit 111 needs to obtain information regarding security settings (encryption, etc.) by performing a procedure such as a 4-way handshake after connecting to the Non-AP MLD 200, but since the information has already been obtained from the AP MLD entity 300 (control device), this procedure can be omitted.
  • connection request received from the Non-AP MLD 200 does not need to include information regarding the capabilities of the Non-AP MLD 200. Since the communication control unit 111 obtains this information from the AP MLD entity 300 (control device), the frame length of the connection request can be shortened by not including information regarding the capabilities of the Non-AP MLD 200, which would normally need to be included in the connection request. This is expected to reduce the time required for connection (Re-association) with the new destination AP 100. Note that the communication control unit 111 may include the capabilities of the AP 100 in the connection response, or does not need to include the capabilities if the capabilities of the destination AP before the Non-AP MLD 200 roamed are to be inherited. In the latter case, the frame length of the connection response can be shortened.
  • Methods for acquiring the position of the Non-AP MLD 200 include, for example, measuring the strength of a signal received from the Non-AP MLD 200, and acquiring the position information of the Non-AP MLD 200 from a server that manages the position of the Non-AP MLD 200 or from the Non-AP MLD 200 itself. Alternatively, a method of measuring the position of the Non-AP MLD 200 using a sensor or beam, etc. is also possible.
  • communication control unit 111 may control to transmit a signal requesting that Non-AP MLD 200 extend the waiting time for receiving a connection response. In this case, communication control unit 111 may control to transmit a connection response to Non-AP MLD 200 within the extended waiting time. Specifically, communication control unit 111 performs control to acquire terminal information and transmit a connection response within the extended waiting time of Non-AP MLD 200. If communication control unit 111 is unable to transmit a connection response within the extended waiting time or is unable to acquire terminal information from AP MLD entity 300 (control device), communication control unit 111 may control to perform normal connection processing with Non-AP MLD 200.
  • Normal connection processing includes at least one or both of the following: exchange of information regarding capabilities with the Non-AP MLD 200 through the exchange of association request frames and association response frames (association processing), and exchange of information regarding security settings (encryption, etc.) through procedures such as a 4-way handshake (authentication processing).
  • Non-AP MLD 200 corresponds to a communication device, wireless communication device, terminal device or STA according to this embodiment, and will hereinafter also be referred to as communication device 200.
  • Communication device 200 mainly comprises a communication unit 210, a control unit 230, a memory unit 240 and an antenna 250.
  • Communication unit 210 comprises a communication control unit 211, a communication memory unit 212, a common data processing unit 213, system R21 and system R22.
  • Communication unit 210 can be realized by one or more LSIs.
  • System R21 and system R22 each include an individual data processing unit 221, a signal processing unit 222, a wireless interface unit 223, one or more amplifier units 224, and one or more antennas 250.
  • a system is composed of a set of the individual data processing unit 221, the signal processing unit 222, the wireless interface unit 223, the amplifier unit 224, and the antenna 250.
  • Each system functions as a transceiver including a transmitter unit that transmits signals and a receiver unit that receives signals.
  • Each system performs wireless communication using a different link.
  • a link is a wireless transmission path that allows data to be transmitted between two communication devices, and may also be described as a wireless link.
  • the links used by each system may have different frequency bands or may be the same.
  • Each system may be provided with a memory unit. For example, communication with AP100_2 is performed using one link, and communication with AP100_1 is performed using the other link. There may also be cases where communication with AP100_1 is performed using both links.
  • the communication control unit 211 controls the operation of each unit and the transmission of information between each unit. It also controls the transfer of control information and management information to be notified to other communication devices to the common data processing unit 213, system R21, and system R22.
  • the communication storage unit 212 holds information used by the communication control unit 211.
  • the communication storage unit 212 holds data to be transmitted and data received.
  • the communication storage unit 212 holds data to be transmitted to AP 100 and data received from AP 100.
  • the common data processing unit 213 When transmitting, the common data processing unit 213 performs sequence management of the data stored in the communication memory unit 212 and the control information and management information received from the communication control unit 211, performs encryption processing, etc., and allocates the processed data to each individual data processing unit 221. When receiving, the common data processing unit 213 performs data decryption processing and reordering processing.
  • the encryption processing may be performed using an encryption key obtained, for example, by a procedure such as a 4-way handshake performed with the AP 100, or with the AP MLD Entity 300 via the AP 100.
  • each individual data processing unit 221 When transmitting, each individual data processing unit 221 performs channel access operations based on carrier sense, adds a MAC (Media Access Control) header to the data to be transmitted, generates a data unit by adding an error detection code, and concatenates multiple data units.When receiving, it performs MAC header deconcatenation processing for the received data unit, analysis and error detection, and retransmission request operations.
  • MAC Media Access Control
  • each signal processing unit 222 When transmitting, each signal processing unit 222 performs encoding, interleaving, modulation, etc. on the data unit, adds a physical header, and generates a symbol stream. At this time, each signal processing unit 222 may perform spatial multiplexing processing for MIMO (Multiple Input Multiple Output). However, each signal processing unit 222 may not perform spatial multiplexing processing, and may apply an arbitrary delay amount (hereinafter, cyclic shift delay CSD: Cyclic Shift Delay) to each antenna 250.
  • cyclic shift delay CSD Cyclic Shift Delay
  • each signal processing unit 222 analyzes the physical header, and performs demodulation, deinterleaving, decoding, etc. on the symbol stream to generate a data unit. Furthermore, each signal processing unit 222 estimates complex channel characteristics and performs spatial separation processing as necessary.
  • each wireless interface unit 223 When transmitting, each wireless interface unit 223 performs digital-to-analog signal conversion, filtering, up-conversion, and phase control on the symbol stream to generate a transmission signal. When receiving, each wireless interface unit 223 performs down-conversion, filtering, and analog-to-digital signal conversion on the received signal to generate a symbol stream.
  • the amplifier unit 224 of each system amplifies the signal input from the wireless interface unit 223 or the antenna 250.
  • a part of the amplifier unit 224 may be a component outside the communication unit 210. Also, a part of the amplifier unit 224 may be included in the wireless interface unit 223.
  • the control unit 230 controls the communication unit 210 and the communication control unit 211.
  • the control unit 230 may also perform some of the operations of the communication control unit 211.
  • the communication control unit 211 and the control unit 230 may also be configured as a single block.
  • the control unit of the terminal corresponds, as an example, to the communication control unit 211, or to at least one of the communication control unit 211 and the control unit 230.
  • the memory unit 240 holds information used by the control unit 230 and the communication unit 210.
  • the memory unit 240 may also perform some of the operations of the communication memory unit 212.
  • the memory unit 240 and the communication memory unit 212 may be configured as a single block.
  • the individual data processing unit 221 and the signal processing unit 222 may be configured as one group, and multiple groups may be connected to one wireless interface unit 223. In other words, one wireless interface unit 223 may be shared by multiple systems. Also, the wireless interface unit 223, the amplifier unit 224, and the antenna 250 may be configured as one group, and multiple groups may be connected to one signal processing unit 222. In other words, the signal processing unit 222 may be shared by multiple systems. In this case, there may be one or more individual data processing units 221.
  • the Non-AP MLD 200 selects an AP that does not belong to an AP MLD group (an AP that is not subject to control by the AP MLD) as a roaming destination, the following operations may be performed.
  • the communication control unit 211 selects an AP that does not belong to the AP MLD group as the roaming destination AP (such as AP3 in FIG. 1), i.e., the new connection destination AP (target AP), and controls the device to send a connection request to the target AP.
  • the connection request does not need to include information regarding capabilities related to the Non-AP MLD 200.
  • the communication control unit 211 controls the target AP to omit execution of a procedure (e.g., a 4-way handshake) for acquiring the terminal information, and completes the connection process with the target AP.
  • the terminal information acquired by the target AP includes information about the capabilities of Non-AP MLD 200 and information about encryption (e.g., an encryption key) necessary for communication with Non-AP MLD 200.
  • Non-AP MLD 200 can omit performing a 4-way handshake with AP 100, or with AP MLD 300 via AP 100.
  • the communications control unit 211 would have to perform a procedure (authentication processing) such as a 4-way handshake to have the target AP or AP MLD 300 obtain encryption-related information (e.g., an encryption key) as terminal information, and would also need to obtain encryption-related information (e.g., an encryption key) itself; however, this procedure can be omitted because the target AP has already obtained the information from the AP MLD entity 300 (control device). Also, the Non-AP MLD 200 can continue to use the encryption information it was originally using. This reduces the execution of unnecessary processing, enables roaming to be completed quickly, and suppresses communication delays.
  • a procedure such as a 4-way handshake
  • the communication control unit 211 may extend the waiting time in response to receiving a response from the Non-AP MLD 200 requesting an extension of the waiting time for receiving a connection response, and may wait for the connection response until the waiting time has elapsed. This makes it possible to prevent a timeout occurring before the connection response is received when the time until the connection response is received is longer than the normal waiting time (set time).
  • FIG. 4 is a block diagram of a control device in the case where the AP MLD entity 300 is realized by a control device separate from the AP 100.
  • the control device 300 is represented using the same reference symbol as the AP MLD entity 300.
  • the control device 300 comprises a communication processing unit 320, a control unit 330, a memory unit 340, and a communication unit 310.
  • the communication processing unit 320 comprises a communication control unit 311, a communication memory unit 312, and a common data processing unit 313.
  • the control unit 330 controls and manages the subordinate APs (AP100_1 to AP100_3 in FIG. 1) through the network layer and application layer. For example, the control unit 330 collects information (information at Layer 3 and above) about the Non-AP MLD 200 connected to the subordinate APs, performance information such as throughput and delay of data transmission from the Non-AP MLD 200, and load information about the subordinate APs, and then optimizes network information related to the Non-AP MLD 200 and its connected APs. Roaming processing may also be performed via the control unit 330.
  • the communication control unit 311 controls and manages the APs (AP1, AP2 in the example of FIG. 1) in the group of APs (AP MLD group) that make up the AP MLD through the MAC layer.
  • the communication control unit 311 collects information (Layer 2 information) about the Non-AP MLD 200 connected to a subordinate AP, and notifies other APs of the information as necessary, thereby enabling cooperation at the MAC layer among APs in the same MLD group.
  • the communication control unit 311 may manage information such as terminal information (encryption keys, etc.) and sequence numbers, which are information about the Non-AP MLD 200 connected to the AP.
  • the encryption key may be common to AP1 and AP2 in the group. This embodiment is not limited to this configuration, and for example, the communication control unit 311 may also manage the success or failure of packet transmission in the Non-AP MLD 200.
  • the control unit 330 may perform some of the operations of the communication control unit 311.
  • the communication control unit 311 and the control unit 330 may also be configured as a single block.
  • the control unit of the control device corresponds, for example, to the communication control unit 311, or to at least one of the communication control unit 311 and the control unit 330.
  • the communication memory unit 312 holds information used by the communication control unit 311.
  • the communication memory unit 312 holds data to be transmitted and data received.
  • the communication memory unit 312 holds data to be transmitted to AP 100 and data received from AP 100.
  • the communication memory unit 312 may hold information (terminal information) relating to a Non-AP MLD for which connection processing has been completed with an AP in an AP MLD group.
  • the communication memory unit 312 may correspond to a holding unit that holds terminal information.
  • the common data processing unit 313 When transmitting, the common data processing unit 313 performs sequence management of the data stored in the communication memory unit 312 and the control information and management information received from the communication control unit 311, performs encryption processing, etc., and sends the processed data to the communication unit 310. When receiving, the common data processing unit 313 performs data decryption processing and reordering processing. For each AP MLD group, the common data processing unit 313 may manage the encryption key used by the AP and the encryption key used by the Non-AP MLD subordinate to the AP. The encryption key may be obtained, for example, by performing authentication processing including a 4-way handshake with the Non-AP MLD via an AP in the group.
  • the common data processing unit 313, or both the common data processing unit 313 and the communication control unit 311, have the MLD Upper MAC function.
  • the communication unit 310 has a transmitting unit that transmits signals and a receiving unit that receives signals, and performs wireless communication with each connected AP 100.
  • communication between the control device 300 and the AP 100 may be wireless communication (e.g., wireless communication according to the IEEE802.11 standard) or wired communication (e.g., Ethernet communication). Alternatively, both wired communication and wireless communication may be possible.
  • the communication unit 310 may be capable of communicating directly with the Non-AP MLD 200 (without going through the AP 100). When performing wireless communication, the communication unit 310 is equipped with an antenna.
  • the memory unit 340 holds information used by the control unit 330 and the communication processing unit 320.
  • the memory unit 340 may also perform some of the operations of the communication memory unit 312.
  • the memory unit 340 and the communication memory unit 312 may be configured as a single block.
  • control device 300 may perform the following operations when an AP (target AP) that does not belong to an AP MLD group performs connection processing with the Non-AP MLD 200.
  • a control unit (including at least one of the communication control unit 311 and the control unit 330) according to this embodiment receives a request to acquire terminal information, which is information relating to the Non-AP MLD 200, from the target AP, it controls the terminal information to be read from the communication memory unit 312 or the memory unit 340 and provided or transmitted to the target AP.
  • the control unit may add the target AP to the AP MLD group, i.e., add it to the control target of the control unit.
  • the control unit may add it to the AP MLD group (control target) only if the acquisition request includes a request to add it to the AP MLD group.
  • the control unit may control the control device 300 to transmit notification information in advance to the target AP indicating that it is possible to provide information about the Non-AP MLD under the AP group belonging to the AP MLD group by requesting the control device 300.
  • This allows the target AP to decide to request information about the Non-AP MLD 200 from the control device 300 when, for example, a connection request is received from the Non-AP MLD 200.
  • the notification information may include identification information of the Non-AP MLD under the AP group belonging to the AP MLD group.
  • the identification information may be, for example, a MAC address, or it may be an AID (Association ID).
  • the control unit may perform control so that when a target AP is added to an AP MLD group (control target), group information indicating the addition is sent to the target AP and other APs belonging to the AP MLD group.
  • AP MLD group control target
  • the control unit according to this embodiment may also remove from the AP MLD group those APs that belong to the AP MLD group and have not communicated with the Non-AP MLD 200 for a certain period of time or more.
  • the control unit may select an AP other than the target AP and remove the selected AP from the AP MLD group.
  • the AP to be removed may be an AP that was disconnected during roaming, or an AP may be selected based on other criteria.
  • the control unit may update information relating to security settings (e.g., encryption) required for communication with the Non-AP MLD 200. For example, the control unit may perform authentication processing via the Non-AP MLD 200 and an AP in the AP MLD group to generate new encryption keys to be used by the Non-AP MLD 200 and the APs in the AP MLD group, respectively.
  • security settings e.g., encryption
  • FIG. 5 shows a logical configuration of the system architecture in this embodiment.
  • the PHY Sublayer is a block that corresponds to the physical layer and corresponds to the signal processing section in the device configuration (see Figure 2).
  • the PHY Sublayer Management Entity is a block that controls the PHY Sublayer and corresponds to the communication control section and control section in the device configuration (see Figure 2 or Figure 4).
  • the MLD Lower MAC Sublayer is a block that corresponds to part of the MAC layer, and corresponds to the individual data processing section in the device configuration (see Figure 2).
  • the MLD Upper MAC Sublayer is a block that corresponds to part of the MAC layer, and corresponds to the common data processing unit in the device configuration (see Figure 2 or Figure 4), and also corresponds to the AP MLD entity.
  • the MAC Sublayer Management Entity is a block that controls the MLD Lower MAC Sublayer and the MLD Upper MAC Sublayer, and corresponds to the communication control unit and control unit in the device configuration (see Figure 2 or Figure 4).
  • IEEE 802.1X is a block that corresponds to the data link layer related to authentication.
  • IEEE 802.1X corresponds to the common data processing section or control section, or both, in the device configuration (see Figure 2 or Figure 4).
  • AP MLD entity Each SAP (Service Access Point) is an interface that connects each block, and exchanges specified commands in a specified manner. In addition, information is exchanged and controlled in any manner between the blocks indicated by the arrows.
  • FIG. 6 shows an example of a physical configuration of the system architecture in this embodiment.
  • this configuration includes two or more APs.
  • Each AP has a physical configuration corresponding to the logical configuration shown in Fig. 5.
  • the AP MLD group is composed of two APs, and AP1 on the left and AP2 or AP3 on the right are shown.
  • One of AP2 or AP3 is described as AP2/AP3.
  • AP1 has an AP MLD entity as the MLD Upper MAC Sublayer.
  • AP1 For communication with the Non-AP MLD 200, AP1 uses the PHY Sublayer, MLD Lower MAC Sublayer, MLD Upper MAC Sublayer, and corresponding Management entities on one side L1, and also uses IEEE802.1X.
  • the blocks on the other side L2, i.e., the PHY Sublayer, MLD Lower MAC Sublayer, MLD Upper MAC Sublayer, and corresponding Management entities, may be used for communication with other terminals, or may not be used (turned off).
  • AP2/AP3 use the PHY Sublayer, MLD Lower MAC Sublayer and corresponding Management entities on one side P1.
  • the MLD Upper MAC Sublayer and IEEE802.1X on one side P1 and the blocks indicated by diagonal lines on the other side P2 may be used for communication with other terminals, or may not be used (turned off).
  • each block in Figure 6 is the same as the explanation of the logical configuration, but the MLD Upper MAC Sublayer on one side L1 of AP1 is connected to the MLD Lower MAC Sublayer on one side P1 of AP2/AP3, and information is exchanged and controlled in any manner.
  • This communication is realized by wireless or wired communication. If realized by wireless communication, communication can occur between these blocks via other blocks, etc. That is, communication can occur from the MLD Upper MAC Sublayer on one side L1 of AP1, through the MLD Lower MAC Sublayer, PHY SAP, PHY Sublayer, RF, via Media (wireless medium), through the RF, PHY Sublayer, PHY SAP of one side P1 of AP2/AP3, to the MLD Lower MAC Sublayer on the right. If realized by wired communication, communication can occur by Ethernet, for example.
  • the AP 100 is provided with a wired communication unit 160, and the control unit 130 performs wired communication with other APs via the wired communication unit.
  • FIG. 7 is a block diagram of an example configuration of an AP 100 equipped with a wired communication unit 160.
  • the wired communication unit 160 is connected to the control unit 130.
  • the wired communication unit 160 is connected to a wired network such as Ethernet, and communicates with other APs via the wired network.
  • the wired communication unit 160 includes a transmitting unit that transmits signals and a receiving unit that receives signals.
  • the frequency that AP1 uses to communicate with Non-AP MLD 200 may be different from the frequency that AP2/AP3 uses to communicate with Non-AP MLD 200.
  • the frequency that AP2 uses to communicate with Non-AP MLD 200 may be different from the frequency that AP3 uses to communicate with Non-AP MLD 200.
  • FIG. 8 shows another example of the physical configuration of the system architecture in this embodiment.
  • This configuration includes two or more APs and a control device 300.
  • the control device 300 is, for example, a central control device, a device on a cloud, or an edge device.
  • AP1 and AP2/AP3 have physical configurations corresponding to the logical configuration shown in FIG.
  • the AP1 uses the PHY Sublayer, MLD Lower MAC Sublayer, and corresponding Management entity on one side L11.
  • the MLD Upper MAC Sublayer, IEEE802.1X on one side L11, and the blocks (PHY Sublayer, MLD Lower MAC Sublayer, MLD Upper MAC Sublayer, and corresponding Management entity) on the other side L12 may be used for communication with other terminals, or may not be used (turned off).
  • the control device 300 has an MLD Upper MAC Sublayer, a corresponding Management entity, and IEEE802.1X.
  • the explanation of each block is the same as the explanation of the logical configuration, but a connection is made between the MLD Upper MAC Sublayer of the control device 300 and the MLD Lower MAC Sublayer on one side P11 of AP2/AP3, and information is exchanged and controlled in any manner.
  • the explanation of AP2/AP3 is the same as in Figure 6. In other words, AP2/AP3 uses the PHY Sublayer, MLD Lower MAC Sublayer and corresponding Management entity of the one side P11.
  • the MLD Upper MAC Sublayer and IEEE802.1X on one side P11 and the blocks on the other side P12 may be used for communication with other terminals, or may not be used (turned off).
  • the frequency that AP1 uses to communicate with Non-AP MLD 200 may be different from the frequency that AP2/AP3 uses to communicate with Non-AP MLD 200.
  • the frequency that AP2 uses to communicate with Non-AP MLD 200 may be different from the frequency that AP3 uses to communicate with Non-AP MLD 200.
  • An SAP may be provided connecting the MLD Upper MAC Sublayer and the MLD Lower MAC Sublayer.
  • Figure 9 shows an example of an MLD MAC SAP that connects the MLD Upper MAC Sublayer and the MLD Lower MAC Sublayer.
  • specified commands are exchanged in a specified manner between the MLD Upper MAC Sublayer and the MLD Lower MAC Sublayer via the MLD MAC SAP.
  • the following signals are exchanged as a command to perform a scan.
  • MLME is a MAC Sublayer Management Entity.
  • the BSSType (BSS type, such as infrastructure BSS (Basic Service Set) or Mesh BSS) and BSSID (AP MAC address) contain information about the BSS to be scanned.
  • BSSType BSS type, such as infrastructure BSS (Basic Service Set) or Mesh BSS
  • BSSID AP MAC address
  • MLME is not limited to this one, and may be a name related to the Management Entity that controls the MLD Upper MAC Sublayer and MLD Lower MAC Sublayer.
  • [First Example of Sequence] 10 shows a first example of a sequence in this embodiment.
  • the AP 3 that has received a connection request from the Non-AP MLD 200 that has decided to perform roaming wirelessly requests information (terminal information) about the Non-AP MLD 200 from the AP 1 having the AP MLD entity, and receives information about the Non-AP MLD 200 from the AP 1.
  • the AP 3 completes the connection process with the Non-AP MLD 200 at this point, and transmits to the Non-AP MLD 200 a connection response indicating that information about the Non-AP MLD 200 has been acquired (in other words, a connection response indicating the completion of the connection process). Details of this sequence will be described below.
  • AP1 may also send to AP3 a signal (AP Group Information) indicating that AP1 has an AP MLD entity and has formed an AP MLD, and including information about the AP MLD.
  • AP Group Information includes, for example, information about APs included in the AP MLD group and information about Non-AP MLDs subordinate to the APs.
  • AP Group Information is also notification information indicating that by querying AP1, it is possible to provide information about Non-AP MLDs subordinate to APs that belong to the AP MLD group. Note that before this sequence starts, the AP MLD entity has added AP1 and AP2 to the AP MLD group, but has not added AP3.
  • Non-AP MLD 200 communicates with, for example, AP1 which has an AP MLD entity.
  • Non-AP MLD 200 transmits a UL signal 501 to AP1 and receives a response signal 502 from AP1.
  • Non-AP MLD 200 decides to roam from AP1 to AP3 (for example, it determines that the RSSI of the beacon signal from AP3 is higher than that of the beacon signal from AP1), and transmits an association request signal (Association Request) 503 to AP3.
  • AP3 which receives a connection request signal from Non-AP MLD200, transmits a request signal for information about Non-AP MLD200 (Non-AP Information Request) 504 to AP1, which has an AP MLD entity.
  • the request signal for information about Non-AP MLD200 may include a request to add the AP3 to the AP MLD group.
  • Non-AP Information Response a notification signal (Non-AP Information Response) 505 of the information about Non-AP MLD200.
  • the information about Non-AP MLD200 may include information about the capabilities of Non-AP MLD200, and information about security settings (e.g. encryption) between the AP MLD and Non-AP MLD200.
  • AP3 which has received a notification signal from AP1 containing information about Non-AP MLD200, completes the connection process with Non-AP MLD200 based on the information contained in the notification signal.
  • AP3 transmits an association response signal 506 indicating that it has acquired information about Non-AP MLD200, i.e., that the connection process has been completed.
  • Non-AP MLD 200 When Non-AP MLD 200 receives a connection response signal from AP 3, it knows that AP 3 has already acquired the information (terminal information) about Non-AP MLD 200 required for communication with Non-AP MLD 200, i.e., it knows that the connection process in AP 3 has been completed, and omits subsequent processes (e.g. authentication process including 4-way handshake). After that, Non-AP MLD 200 and AP 3 begin communication. In the example shown in the figure, Non-AP MLD 200 transmits UL signal 507 to AP 3 and receives response signal 508 from AP 3.
  • the frequency at which Non-AP MLD 200 communicates with AP1 may be different from the frequency at which Non-AP MLD 200 communicates with AP3.
  • AP1 may add AP3 to the AP MLD group (control target) in response to a request signal (Non-AP Information Request) 504 received from AP3.
  • request signal Non-AP Information Request
  • AP1 may also decide to remove from the AP MLD group an AP that has not communicated with Non-AP MLD 200 for a certain period of time, and remove that AP from the group.
  • AP1 may send a signal (AP Group Information) notifying of the change. For example, if AP1 adds AP3 to the AP MLD group, it may send a signal (AP Group Information) 509 to AP2 indicating that AP3 has been added. Signal 509 may also be sent to AP3.
  • AP Group Information AP Group Information
  • AP1 when it removes an AP from the AP MLD group because there has been no communication with Non-AP MLD 200 for a certain period of time, it may send a signal (AP Group Information) to other APs in the group (which may include the AP just added) indicating that the AP has been removed. For example, when AP1 is removed, AP1 may send a signal to AP2, or to both AP2 and AP3, indicating that AP1 has been removed. Note that the addition of an AP and the removal of an AP may be notified by the same signal, or by separate signals.
  • AP Group Information AP Group Information
  • [Second Example of Sequence] 11 shows a second example of a sequence in this embodiment.
  • the AP 3 that has received a connection request from the Non-AP MLD 200 requests information (terminal information) about the Non-AP MLD 200 from the central control device 300A having an AP MLD entity by wired communication, and receives information about the Non-AP MLD 200 from the central control device 300A. Based on the received information, the AP 3 completes the connection with the Non-AP MLD 200 and transmits a connection response to the Non-AP MLD 200 indicating that information about the Non-AP MLD 200 has been acquired (indicating connection completion). Details of this sequence will be described below.
  • Non-AP MLD 200 communicates with, for example, AP1.
  • Non-AP MLD 200 transmits UL signal 511 to AP1 and receives response signal 512 from AP1.
  • Non-AP MLD 200 decides to connect to AP3 by roaming at the timing indicated by the dashed line (for example, it determines that the RSSI of the beacon signal of AP3 is higher than that of the beacon signal of AP1), and transmits an association request signal (Association Request) 513 to AP3.
  • association Request association request
  • the AP 3 When the AP 3 receives a connection request signal from the Non-AP MLD 200, it transmits a request signal 514 for information about the Non-AP MLD 200 to the central control device 300A which has an AP MLD entity.
  • the request signal for information about the Non-AP MLD 200 may include a request to add the central control device 300A to the AP MLD group.
  • the central control device 300A receives a request for information about the Non-AP MLD 200 from the AP 3, it transmits a notification signal 515 including information about the Non-AP MLD 200.
  • the information about the Non-AP MLD 200 may be information about the capabilities of the Non-AP MLD 200, and information about security settings (e.g. encryption) between the AP MLD and the Non-AP MLD 200.
  • the request for information about the Non-AP MLD 200 and the response are transmitted and received via wired communication.
  • AP3 which has received a notification signal 515 of information relating to Non-AP MLD200 from central control device 300A, completes the connection process with Non-AP MLD200 and transmits an association response signal (Association Response) 516 indicating that information relating to Non-AP MLD200 has been acquired, i.e., that the connection process has been completed.
  • association Response association Response
  • Non-AP MLD 200 When Non-AP MLD 200 receives connection response signal 516 from AP 3, it understands that AP 3 has already acquired information about Non-AP MLD 200 (AP 3 has completed the connection process) and omits subsequent processing.
  • the frequency at which Non-AP MLD 200 communicates with AP 1 may be different from the frequency at which Non-AP MLD 200 communicates with AP 3.
  • a signal (AP Group Information) 519 is transmitted to notify the addition or removal.
  • AP1 when AP1 is removed, a signal 519 notifying the removal may be transmitted to AP1 and AP2.
  • AP3 When AP3 is added, a signal 519 notifying the addition of AP3 may be transmitted to AP1 and AP2.
  • Signal 519 may be transmitted to AP3.
  • [Third Example of Sequence] 12 shows a third example of the sequence in this embodiment.
  • the AP3 that has received a connection request from the Non-AP MLD200 returns a connection response 524 to the Non-AP MLD200 and waits temporarily, and then requests information (terminal information) related to the Non-AP MLD200 from the AP1 having the AP MLD entity via wireless communication.
  • the AP3 receives information related to the Non-AP MLD200 from the AP1, it completes the connection process and transmits a connection response 524 to the waiting AP3 indicating that information related to the Non-AP MLD200 has been acquired (AP3 has completed the connection process). Details of this sequence will be described below.
  • Non-AP MLD 200 communicates with, for example, AP1.
  • Non-AP MLD 200 transmits UL signal 521 to AP1 and receives response signal 522 from AP1.
  • Non-AP MLD 200 decides to connect to AP3 by roaming at the timing indicated by the dashed line (for example, it determines that the RSSI of the beacon signal of AP3 is higher than that of the beacon signal of AP1), and transmits an association request signal (Association Request) 523 to AP3.
  • association Request association request
  • Non-AP MLD 200 When the Non-AP MLD 200 receives a connection response signal 524 from the AP 3, it waits temporarily and extends the validity period until the connection is complete as necessary. By extending the validity period, it is possible to delay the time until the timeout.
  • AP3 transmits a request signal (Non-AP Information Request) 525 for information about Non-AP MLD 200 to AP1, which has an AP MLD entity.
  • AP1 transmits a notification signal (Non-AP Information Response) 526 for information about Non-AP MLD 200 to AP3.
  • AP3 completes the connection process with Non-AP MLD 200 and transmits an association response signal (Association Response) 527 indicating that information about Non-AP MLD 200 has been acquired (connection process has been completed).
  • Non-AP MLD 200 Having received association response signal 527 from AP3, Non-AP MLD 200 understands that AP3 has acquired information about Non-AP MLD 200 (AP3 has completed connection process) and omits subsequent processes. Non-AP MLD 200 and AP3 then begin communication. In the example shown in the figure, Non-AP MLD 200 transmits UL signal 528 to AP 3 and receives response signal 529 from AP 3.
  • a signal (AP Group Information) 530 is transmitted to notify the addition or removal. This operation is the same as in the sequence of Figure 10.
  • Signal 530 may be transmitted to AP3.
  • [Fourth Example of Sequence] 13 shows a fourth example of the sequence in this embodiment.
  • the AP3 which detects that the Non-AP MLD 200 approaches within a certain distance, wirelessly requests information (terminal information) about the Non-AP MLD 200 from the AP1 having the AP MLD entity, and receives information about the Non-AP MLD 200 from the AP1.
  • the AP3 subsequently receives a connection request from the Non-AP MLD 200, it completes the connection process based on the information acquired in advance, and transmits a connection response signal to the Non-AP MLD 200 indicating that the terminal information has been acquired (the connection process has been completed). Details of this sequence will be described below.
  • Non-AP MLD 200 communicates with, for example, AP1, which has an AP MLD entity.
  • AP1 which has an AP MLD entity.
  • Non-AP MLD 200 transmits UL signal 531 to AP1 and receives response signal 532 from AP1.
  • AP3 detects that Non-AP MLD 200 has approached AP3 to a specified distance.
  • AP3 detects that the distance to Non-AP MLD200 has fallen below a predetermined value when the RSSI of a signal received from Non-AP MLD200 exceeds a predetermined value.
  • AP3 obtains location information of Non-AP MLD200 from a location management server or Non-AP MLD200, and detects that the distance to Non-AP MLD200 has fallen below a predetermined value based on the location information.
  • AP3 measures the location of Non-AP MLD200 using a sensor or beam, etc., and detects that the distance to Non-AP MLD200 has fallen below a predetermined value based on the measured location.
  • Non-AP Information Request For information about Non-AP MLD 200 to AP1, which has an AP MLD entity.
  • the request signal for information about Non-AP MLD 200 may include a request to add the device to the AP MLD.
  • Non-AP Information Response a notification signal (Non-AP Information Response) 534 for information about the Non-AP MLD 200.
  • the information about the Non-AP MLD 200 may include information about the capabilities of the Non-AP MLD 200, and information about security settings (e.g. encryption) between the AP MLD and the Non-AP MLD 200.
  • AP3 which receives notification signal 534 of information regarding Non-AP MLD 200 from AP1, completes the connection process with Non-AP MLD 200 in advance (before receiving a connection request from Non-AP MLD 200).
  • Non-AP MLD 200 decides to connect to AP3 by roaming at the timing shown by the dashed line, and transmits an association request signal (Association Request) 535 to AP3.
  • Association Request an association request signal
  • association Response association response signal
  • Non-AP MLD 200 When Non-AP MLD 200 receives connection response signal 536 from AP 3, it understands that AP 3 has already acquired information about Non-AP MLD 200 (AP 3 has completed the connection process) and omits subsequent processing.
  • Non-AP MLD 200 and AP 3 start communication.
  • Non-AP MLD 200 transmits UL signal 537 to AP 3 and receives response signal 538 from AP 3.
  • the frequency at which Non-AP MLD 200 communicates with AP1 may be different from the frequency at which Non-AP MLD 200 communicates with AP3.
  • a signal (AP Group Information) 539 is transmitted to notify the addition or removal.
  • Signal 539 may also be transmitted to AP3.
  • FIG. 14 shows an example of the frame format of a request signal (signal 504 in Fig. 10, signal 514 in Fig. 11, signal 525 in Fig. 12, signal 533 in Fig. 13) requesting information about Non-AP MLD 200.
  • the format in Fig. 14 includes a MAC Header, Frame Body, and Frame Check Sequence (FCS).
  • the Frame Body includes Category and Action Details.
  • the Action Details include Non-AP MLD Address and Request Mode.
  • the MAC Header contains information such as the frame's destination and source, the Frame Body is the signal itself, and the FCS (Frame Check Sequence) contains information about error detection.
  • the Category contains information about the type of frame (Action Frame), and the Action Details are the main body of the Action Frame.
  • Non-AP MLD Address contains the MAC address of the Non-AP MLD for which information is being requested.
  • Request Mode contains the Non-AP information request bit and the request bit to be added to the AP MLD group. For example, if information about the Non-AP MLD is being requested, the Non-AP information request bit is "1", otherwise it is "0". If addition to the AP MLD group is being requested, the request bit to be added is "1", otherwise it is "0".
  • Figure 15 shows an example of the frame format of a signal (signal 505 in Figure 10, signal 515 in Figure 11, signal 526 in Figure 12, signal 534 in Figure 13) that notifies information (terminal information) related to Non-AP MLD.
  • signal 505 in Figure 10 signal 515 in Figure 11, signal 526 in Figure 12, signal 534 in Figure 13
  • terminal information information related to Non-AP MLD.
  • Action Details include Non-AP MLD Address, Capability, and Security.
  • Non-AP MLD Address includes the MAC address of the Non-AP MLD to which information is to be notified.
  • Capability includes information regarding the capability of the Non-AP MLD.
  • Security includes information regarding the security settings with the Non-AP MLD.
  • Figure 16 shows an example of a frame format that can handle both requests and notifications of information related to Non-AP MLD.
  • the following explanation focuses on the differences from the frame formats in Figures 14 and 15, and omits an explanation of the same parts.
  • Action Details includes Type, Non-AP MLD Address, Request Mode, Capability, and Security.
  • Type includes a value that identifies whether the signal is a request for information about Non-AP MLD or a notification signal for information about Non-AP MLD.
  • the other fields are the same as those described in Figures 14 and 15.
  • Figure 17 (A) shows an example frame format of an Association Response signal (signal 506 in Figure 10, signal 516 in Figure 11, signal 527 in Figure 12, and signal 536 in Figure 13). Explanations of fields that are the same as those in Figure 14 will be omitted as appropriate.
  • the format in Figure 17 includes a MAC Header, Association Response Body, and FCS.
  • the Association Response Body is the main body of the signal and includes one or more elements.
  • Elements shown include Element ID, Element ID Extension, Length, Connection Complete, Association Complete, and Authentication Complete.
  • the Element ID and Element ID Extension contain information about the type of the element.
  • 17B shows an example of a table that defines multiple elements that can be stored in an Association Response Body.
  • an element of Order 67 may be defined as one of the elements stored in the table.
  • "67" may be stored in the Element ID or Element ID Extension.
  • Connection Complete contains a notification that information about the Non-AP MLD has already been received and that the connection process with the Non-AP MLD has been completed.
  • Association Complete contains a notification that information about the Non-AP MLD that is related to association (e.g. capabilities) has been acquired, and is an option.
  • Authentication Complete contains a notification that information about the Non-AP MLD that is related to authentication (information about security settings (e.g. encryption)) has been acquired, and is an option.
  • the information about Non-AP MLD that Connection Complete targets includes information about association and information about authentication. If either one of the pieces of information has already been acquired, Association Complete or Authentication Complete may be used to notify that fact. If both pieces of information have been acquired, the connection is considered complete and this is notified by Connection Complete, and the optional Association Complete and Authentication Complete do not need to be used.
  • Figure 18 shows an example frame format of a signal (signal 509 in Figure 10, signal 519 in Figure 11, signal 530 in Figure 12, and signal 539 in Figure 13) that notifies information about the AP MLD group (AP group information). Explanations of fields that are the same as those in Figure 14 will be omitted as appropriate. Action Details include Grouping Type, AP MLD ID, AP MLD Info, and AP MAC Address.
  • Grouping Type contains a value that identifies whether the notification is for AP MLD group information, for addition to an AP MLD group, or for removal from an AP MLD group.
  • AP MLD group information is, for example, information about APs that belong to an AP MLD group.
  • the AP MLD ID includes the AP MLD identifier.
  • multiple AP MLD groups can be generated in parallel, and the AP MLD ID is an identifier (AP MLD group identifier) that identifies which of these AP MLD groups the AP MLD is formed from.
  • the combination of APs belonging to each AP MLD group may be different, and the same AP may belong to multiple AP MLD groups. Note that the AP MLD ID is different from the AP MLD MAC address.
  • AP MLD Info includes the AP MLD identifier (AP MLD MAC address), the MAC addresses and number of non-AP MLDs (STAs) connected to the AP MLD, and the AP MLD Capability.
  • AP MLD MAC address the AP MLD identifier
  • STAs non-AP MLDs
  • AP MAC Address contains the MAC address of the AP being added or removed from the AP MLD group.
  • AP MLD group which is a group of APs that virtually operate as a single AP MLD, with minimal processing.
  • FIG. 19 is a block diagram showing an example of the hardware configuration of a computer that executes the above-mentioned series of processes using a program.
  • the CPU Central Processing Unit
  • ROM Read Only Memory
  • RAM Random Access Memory
  • an input unit 806 consisting of a keyboard, mouse, etc.
  • an output unit 807 consisting of a display, speakers, etc.
  • a storage unit 808 consisting of a hard disk or non-volatile memory
  • a communication unit 809 consisting of a network interface, etc.
  • a drive 810 that drives removable media 811.
  • the CPU 801 for example, loads a program stored in the storage unit 808 into the RAM 803 via the input/output interface 805 and the bus 804, and executes the program, thereby performing the above-mentioned series of processes.
  • the programs executed by the CPU 801 are provided, for example, by being recorded on removable media 811, or via a wired or wireless transmission medium such as a local area network, the Internet, or digital broadcasting, and are installed in the storage unit 808.
  • the program executed by the computer may be a program in which processing is performed chronologically in the order described in this specification, or a program in which processing is performed in parallel or at the required timing, such as when called.
  • the base station (communication device) 100 in FIG. 2 and the terminal device (communication device) 200 in FIG. 3 may be realized as a mobile terminal such as a smartphone, a tablet PC (Personal Computer), a notebook PC, a portable game terminal, or a digital camera, a fixed terminal such as a television receiver, a printer, a digital scanner, or a network storage, or an in-vehicle terminal such as a car navigation device.
  • a mobile terminal such as a smartphone, a tablet PC (Personal Computer), a notebook PC, a portable game terminal, or a digital camera, a fixed terminal such as a television receiver, a printer, a digital scanner, or a network storage, or an in-vehicle terminal such as a car navigation device.
  • a mobile terminal such as a smartphone, a tablet PC (Personal Computer), a notebook PC, a portable game terminal, or a digital camera, a fixed terminal such as a television receiver, a printer, a digital scanner, or a network
  • the base station (communication device) 100 and the terminal device (communication device) 200 may be realized as an M2M (Machine To Machine Communication) terminal such as a smart meter, a vending machine, a remote monitoring device, or a POS (Point Of Sale) terminal.
  • M2M Machine To Machine Communication
  • the base station (communication device) 100 and the terminal device (communication device) 200 may be a wireless communication module (for example, an integrated circuit module configured on one die) mounted on these terminals.
  • the base station (communication device) 100 and the terminal device (communication device) 200 may be realized as a wireless LAN AP (wireless base station) with or without a router function.
  • the base station (communication device) 100 and the terminal device (communication device) 200 may be realized as a mobile wireless LAN router.
  • the base station (communication device) 100 and the terminal device (communication device) 200 may be a wireless communication module (for example, an integrated circuit module configured on a single die) mounted on these devices.
  • FIG. 20 is a block diagram showing a schematic configuration example of a smartphone to which the present technology is applied.
  • the smartphone 900 includes a processor 901, a memory 902, a storage 903, an external connection interface 904, a camera 906, a sensor 907, a microphone 908, an input device 909, and a display device 910.
  • the smartphone 900 also includes a speaker 911, a wireless communication interface 913, an antenna switch 914, an antenna 915, a bus 917, a battery 918, and an auxiliary controller 919.
  • the processor 901 may be, for example, a CPU or a SoC (System on Chip) and limits the functionality of the application layer and other layers of the smartphone 900.
  • SoC System on Chip
  • Memory 902 includes RAM and ROM, and stores programs and data executed by processor 901.
  • Storage 903 includes a storage medium such as a semiconductor memory or a hard disk.
  • the external connection interface 904 is an interface for connecting an external device such as a memory card or a USB (Universal Serial Bus) device to the smartphone 900.
  • an external device such as a memory card or a USB (Universal Serial Bus) device to the smartphone 900.
  • USB Universal Serial Bus
  • the camera 906 has an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor) and generates a captured image.
  • an imaging element such as a CCD (Charge Coupled Device) or a CMOS (Complementary Metal Oxide Semiconductor) and generates a captured image.
  • the sensor 907 includes a group of sensors such as a positioning sensor, a gyro sensor, a geomagnetic sensor, and an acceleration sensor.
  • the microphone 908 converts the audio input to the smartphone 900 into an audio signal.
  • the input device 909 includes, for example, a touch sensor that detects touches on the screen of the display device 910, a keypad, a keyboard, a button, or a switch, and accepts operations or information input from the user.
  • the display device 910 has a screen such as a liquid crystal display (LCD) or an organic light emitting diode (OLED) display, and converts the audio signal output from the smartphone 900 into audio.
  • LCD liquid crystal display
  • OLED organic light emitting diode
  • the wireless communication interface 913 supports one or more of the wireless LAN standards such as IEEE802.11a, 11b, 11g, 11ac, 11ad, 11ax, 11ay, and 11be, and performs wireless communication.
  • the wireless communication interface 913 communicates with other devices via a wireless LAN AP. In ad hoc mode or a direct communication mode such as Wi-Fi Direct, the wireless communication interface 913 communicates directly with other devices.
  • one of the two devices acts as an AP, but communication is carried out directly between the devices.
  • the wireless communication interface 913 typically includes a baseband processor, an RF (Radio Frequency) circuit, a power amplifier, and the like.
  • the wireless communication interface 913 may also be a one-chip module that integrates a memory that stores a communication control program, a processor that executes the program, and related circuits.
  • the antenna switch 914 switches the connection of the antenna 915 between multiple circuits (e.g., circuits for different wireless communication methods) included in the wireless communication interface 913.
  • the antenna 915 has a single or multiple antenna elements (e.g., multiple antenna elements constituting a MIMO (Multiple Input Multiple Output) antenna) and is used for transmitting and receiving wireless signals via the wireless communication interface 913.
  • MIMO Multiple Input Multiple Output
  • the smartphone 900 is not limited to the example in FIG. 20 and may include multiple antennas (for example, an antenna for wireless LAN and an antenna for a close-proximity wireless communication system).
  • the antenna switch 914 may be omitted from the configuration of the smartphone 900.
  • the bus 917 connects the processor 901, memory 902, storage 903, external connection interface 904, camera 906, sensor 907, microphone 908, input device 909, display device 910, speaker 911, wireless communication interface 913, and auxiliary controller 919 to each other.
  • the battery 918 supplies power to each block of the smartphone 900 shown in FIG. 20 via a power supply line partially indicated by a dashed line in the figure.
  • the auxiliary controller 919 operates the minimum necessary functions of the smartphone 900, for example, in sleep mode.
  • the communication unit 110, communication control unit 111, and control unit 130 in FIG. 2 and the communication unit 210, communication control unit 211, and control unit 230 in FIG. 3 may be implemented in the wireless communication interface 913.
  • at least some of these functions may be implemented in the processor 901 or the auxiliary controller 919.
  • the smartphone 900 may operate as a wireless AP (software AP) by having the processor 901 execute an AP function at the application level.
  • the wireless communication interface 913 may also have a wireless AP function.
  • the smartphone 900 may be equipped with a biometric authentication unit (fingerprint authentication, palm shape authentication, voice authentication, blood vessel authentication, face authentication, iris authentication, retina authentication).
  • a biometric authentication unit fingerprint authentication, palm shape authentication, voice authentication, blood vessel authentication, face authentication, iris authentication, retina authentication.
  • the wireless communication interface 913 in which the communication unit 110, communication control unit 111, and control unit 130 in FIG. 2 and the communication unit 210, communication control unit 211, and control unit 230 in FIG. 3 are implemented is configured to receive power from the same battery 918 as at least one of the display device 910, speaker 911, and biometric authentication unit.
  • information is displayed on at least one of the display device 910 and the speaker 911 based on communication with an external device via the wireless communication interface 913.
  • information relating to the present technology may be output from at least one of the display device 910 and the speaker 911.
  • FIG. 21 is a block diagram showing an example of a schematic configuration of an in-vehicle device 920 to which the present technology is applied.
  • the in-vehicle device 920 is configured to include a processor 921, a memory 922, a GNSS (Global Navigation Satellite System) module 924, a sensor 925, a data interface 926, a content player 927, and a storage medium interface 928.
  • the in-vehicle device 920 is also configured to include an input device 929, a display device 930, a speaker 931, a wireless communication interface 933, an antenna switch 934, an antenna 935, and a battery 938.
  • GNSS Global Navigation Satellite System
  • the processor 921 may be, for example, a CPU or SoC, and controls the navigation function and other functions of the in-vehicle device 920.
  • the processor 921 can also control the vehicle's drive system, such as the brakes, accelerator, or steering, based on information obtained through communication based on this technology.
  • Memory 922 includes RAM and ROM, and stores programs and data executed by processor 921.
  • the GNSS module 924 measures the position (e.g., latitude, longitude, and altitude) of the in-vehicle device 920 using GNSS signals received from GNSS satellites.
  • the sensor 925 includes a group of sensors such as a gyro sensor, a geomagnetic sensor, and an air pressure sensor.
  • the data interface 926 is connected to the in-vehicle network 941, for example, via a terminal not shown, and acquires data generated on the vehicle side, such as in-vehicle data.
  • the content player 927 plays content stored on a storage medium (e.g., a CD or DVD) inserted into the storage medium interface 928.
  • a storage medium e.g., a CD or DVD
  • the input device 929 includes, for example, a touch sensor, a button, or a switch that detects touches on the screen of the display device 930, and accepts operations or information input from the user.
  • the display device 930 has a screen such as an LCD or OLED display, and displays images of the navigation functions or the content being played.
  • Speaker 931 outputs audio for the navigation function or the content being played.
  • the navigation function and the function provided by the content player 927 are optional.
  • the navigation function and the content player 927 may be removed from the configuration of the in-vehicle device 920.
  • the wireless communication interface 933 supports one or more of the wireless LAN standards such as IEEE802.11a, 11b, 11g, 11n, 11ac, 11ad, 11ax, 11ay, and 11be, and performs wireless communication.
  • the wireless communication interface 933 communicates with other devices via a wireless LAN AP.
  • ad hoc mode or a direct communication mode such as Wi-Fi Direct, the wireless communication interface 933 communicates directly with other devices.
  • the wireless communication interface 933 typically includes a baseband processor, an RF circuit, a power amplifier, and the like.
  • the wireless communication interface 933 may be a one-chip module that integrates a memory that stores a communication control program, a processor that executes the program, or related circuits.
  • the wireless communication interface 933 may support other types of wireless communication systems, such as a short-range wireless communication system, a proximity wireless communication system, or a cellular communication system.
  • the antenna switch 934 switches the connection of the antenna 935 between multiple circuits included in the wireless communication interface 933.
  • the antenna 935 has a single or multiple antenna elements and is used for transmitting and receiving wireless signals via the wireless communication interface 933.
  • the in-vehicle device 920 is not limited to the example in FIG. 21 and may include multiple antennas 935. In that case, the antenna switch 934 may be omitted from the configuration of the in-vehicle device 920.
  • the battery 938 is connected via a power supply line partially shown by a dashed line in the figure.
  • the communication unit 110, communication control unit 111, and control unit 130 in FIG. 2 and the communication unit 210, communication control unit 211, and control unit 230 in FIG. 3 may be implemented in the wireless communication interface 933.
  • at least some of these functions may be implemented in the processor 921.
  • the wireless communication interface 933 may also operate as the base station (communication device) 100 or terminal device (communication device) 200 described above, and provide wireless connection to a terminal owned by a user in the vehicle.
  • the present technology may also be realized as an in-vehicle system (or vehicle) 940 including one or more blocks of the in-vehicle device 920 described above, an in-vehicle network 941, and a vehicle-side module 942.
  • vehicle-side module 942 generates vehicle-side data such as vehicle speed, engine RPM, or fault information, and outputs the generated data to the in-vehicle network 941.
  • FIG. 22 is a block diagram showing an example of a schematic configuration of a wireless AP 950 to which the present technology is applied.
  • the wireless AP 950 includes a controller 951, a memory 952, an input device 954, a display device 955, a network interface 957, a wireless communication interface 963, an antenna switch 964, and an antenna 965.
  • the controller 951 may be, for example, a CPU or a DSP (Digital Signal Processor) and operates various functions of the IP (Internet Protocol) layer and higher layers of the wireless AP 950 (e.g., access restriction, routing, encryption, firewall, and log management, etc.).
  • IP Internet Protocol
  • Memory 952 includes RAM and ROM, and stores programs executed by controller 951 and various control information (e.g., terminal lists, routing tables, encryption keys, security settings, and logs).
  • various control information e.g., terminal lists, routing tables, encryption keys, security settings, and logs.
  • the input device 954 includes, for example, buttons and switches, and accepts operations from the user.
  • the display device 955 includes an LED lamp or the like, and displays the operating status of the wireless AP 950.
  • the network interface 957 is a wired communication interface for connecting the wireless AP 950 to a wired communication network 958.
  • the network interface 957 may have multiple connection terminals.
  • the wired communication network 958 may be a LAN such as Ethernet (registered trademark), or may be a WAN (Wide Area Network).
  • the wireless communication interface 963 supports one or more of the wireless LAN standards such as IEEE802.11a, 11b, 11g, 11n, 11ac, 11ad, 11ax, 11ay, and 11be, and provides wireless connection as an AP to nearby terminals.
  • the wireless LAN standards such as IEEE802.11a, 11b, 11g, 11n, 11ac, 11ad, 11ax, 11ay, and 11be, and provides wireless connection as an AP to nearby terminals.
  • the wireless communication interface 963 typically includes a baseband processor, RF circuitry, a power amplifier, etc.
  • the wireless communication interface 963 may be a one-chip module that integrates a memory that stores a communication control program, a processor that executes the program, or related circuits.
  • the antenna switch 964 switches the connection of the antenna 965 between multiple circuits included in the wireless communication interface 963.
  • the antenna 965 has a single or multiple antenna elements and is used for transmitting and receiving wireless signals by the wireless communication interface 963.
  • the communication unit 110, communication control unit 111, and control unit 130 in FIG. 2 and the communication unit 210, communication control unit 211, and control unit 230 in FIG. 3 may also be implemented in the wireless communication interface 963. Furthermore, at least some of these functions may be implemented in the controller 951.
  • processing steps described in the above embodiments may be considered as a method having a series of steps, or as a program for causing the computer to execute the series of steps, or as a recording medium for storing the program.
  • Examples of the recording medium that can be used include a CD (Compact Disc), MD (MiniDisc), DVD (Digital Versatile Disc), memory card, and Blu-ray (registered trademark) Disc.
  • CD Compact Disc
  • MD MiniDisc
  • DVD Digital Versatile Disc
  • Blu-ray registered trademark
  • a system refers to a collection of multiple components (devices, modules (parts), etc.), regardless of whether all the components are in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device in which multiple modules are housed in a single housing, are both systems.
  • this technology can be configured as cloud computing, in which a single function is shared and processed collaboratively by multiple devices over a network.
  • each step described in the above flowchart can be executed by a single device, or can be shared and executed by multiple devices.
  • one step includes multiple processes
  • the multiple processes included in that one step can be executed by one device, or can be shared and executed by multiple devices.
  • This embodiment may also have the following configuration.
  • [Item 1] a communication unit that receives connection requests from terminals that are wirelessly connected to a plurality of base stations via different links;
  • a control unit that acquires terminal information, which is information about the terminal required for communication with the terminal, from a control entity that controls the plurality of base stations in response to the reception of the connection request or in response to a distance from the terminal; the communication unit transmits a connection response indicating that the terminal information has been acquired.
  • Communications equipment [Item 2] 2. The communication device according to item 1, wherein the terminal information includes at least one of information regarding capabilities of the terminal and information regarding security settings with the terminal.
  • the control unit determines to omit performing an authentication process with the terminal after the connection response is transmitted, 3.
  • the control unit acquires the terminal information from the control entity in response to a distance to the terminal becoming equal to or less than a predetermined value.
  • the control unit measures a strength of a signal received from the terminal, acquires location information of the terminal, or acquires a distance to the terminal by performing location measurement of the terminal.
  • a control unit that controls a plurality of base stations that are wirelessly connected to the terminal through different links; a storage unit for storing terminal information, which is information about the terminal required for the plurality of base stations to communicate with the terminal; the control unit, in response to receiving a request to acquire the terminal information from a target base station different from the plurality of base stations, provides the terminal information stored in the storage unit to the target base station.
  • Control device [Item 10] 10. The control device according to item 9, further comprising: the control unit providing the terminal information to the target base station and adding the target base station to a control target of the control unit. [Item 11] 11.
  • the control device according to item 9 or 10, further comprising: a communication unit configured to transmit notification information indicating that information regarding a terminal under the control of the plurality of base stations can be provided to the target base station.
  • a communication unit configured to transmit notification information indicating that information regarding a terminal under the control of the plurality of base stations can be provided to the target base station.
  • the notification information includes identification information of terminals under the control of the plurality of base stations.
  • a communication device comprising: a transmitter capable of communicating with a control entity that controls a plurality of base stations wirelessly connected to the communication device via different links, and that transmits a connection request to a target base station that is different from the plurality of base stations; a receiving unit for receiving a connection response corresponding to the connection request; a control unit that, in response to detecting notification information indicating that the target base station has already acquired terminal information, which is information about the communication device necessary for communication with the communication device, from the control entity, in the connection response, omits execution of a process for causing the target base station to acquire the terminal information;
  • a communication device comprising: [Item 19] Item 19.
  • the communication device wherein the control unit postpones the waiting time in response to receiving a signal requesting postponement of a waiting time for the connection response in response to the connection request, and waits for the connection response until the waiting time has elapsed.
  • the terminal information includes at least one of information regarding capabilities of the communication device and information regarding security settings with the communication device.
  • Terminal information which is information about the terminal required for communication with the terminal, from a control entity that controls the plurality of base stations; transmit a connection response indicating that the terminal information has been acquired; Communication methods.
  • a control entity capable of communicating with the communication device and controlling a plurality of base stations each wirelessly connected to the communication device via a different link, the control entity transmitting a connection request to a target base station different from the plurality of base stations; receiving a connection response corresponding to the connection request;
  • a communication method which omits a process of having the target base station acquire terminal information, which is information about the communication device necessary for communication with the communication device, in response to detecting notification information from the connection response indicating that the target base station has already acquired terminal information from the control entity.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/JP2024/011406 2023-03-29 2024-03-22 通信装置、制御装置、及び通信方法 Ceased WO2024203907A1 (ja)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP24780025.3A EP4694553A4 (en) 2023-03-29 2024-03-22 COMMUNICATION DEVICE, CONTROL DEVICE AND COMMUNICATION METHOD
JP2025510748A JPWO2024203907A1 (cg-RX-API-DMAC7.html) 2023-03-29 2024-03-22
CN202480020650.4A CN120917859A (zh) 2023-03-29 2024-03-22 通信装置、控制装置和通信方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2023-054271 2023-03-29
JP2023054271 2023-03-29

Publications (1)

Publication Number Publication Date
WO2024203907A1 true WO2024203907A1 (ja) 2024-10-03

Family

ID=92906441

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2024/011406 Ceased WO2024203907A1 (ja) 2023-03-29 2024-03-22 通信装置、制御装置、及び通信方法

Country Status (4)

Country Link
EP (1) EP4694553A4 (cg-RX-API-DMAC7.html)
JP (1) JPWO2024203907A1 (cg-RX-API-DMAC7.html)
CN (1) CN120917859A (cg-RX-API-DMAC7.html)
WO (1) WO2024203907A1 (cg-RX-API-DMAC7.html)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004166277A (ja) * 2002-11-08 2004-06-10 Samsung Electronics Co Ltd 無線網におけるハンドオフ方法
JP2004222300A (ja) * 2003-01-14 2004-08-05 Samsung Electronics Co Ltd 無線ネットワークにおける高速ローミングサービス方法
EP4145947A1 (en) * 2020-05-27 2023-03-08 Huawei Technologies Co., Ltd. Multi-link tentative association method and related apparatus
US20230093547A1 (en) * 2020-02-28 2023-03-23 Lg Electronics Inc. Reuse of space in multi-ap system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9237514B2 (en) * 2003-02-28 2016-01-12 Apple Inc. System and method for filtering access points presented to a user and locking onto an access point
US11696129B2 (en) * 2019-09-13 2023-07-04 Samsung Electronics Co., Ltd. Systems, methods, and devices for association and authentication for multi access point coordination

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004166277A (ja) * 2002-11-08 2004-06-10 Samsung Electronics Co Ltd 無線網におけるハンドオフ方法
JP2004222300A (ja) * 2003-01-14 2004-08-05 Samsung Electronics Co Ltd 無線ネットワークにおける高速ローミングサービス方法
US20230093547A1 (en) * 2020-02-28 2023-03-23 Lg Electronics Inc. Reuse of space in multi-ap system
EP4145947A1 (en) * 2020-05-27 2023-03-08 Huawei Technologies Co., Ltd. Multi-link tentative association method and related apparatus

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
GUOGANG HUANG (HUAWEI): "Thoughts on Seamless Roaming Under the Non-collocated AP MLD Architecture", IEEE DRAFT; 11-23-0231-00-0UHR-THOUGHTS-ON-SEAMLESS-ROAMING-UNDER-THE-NON-COLLOCATED-AP-MLD-ARCHITECTURE, vol. 802.11 UHR, no. 0, 27 March 2023 (2023-03-27), Piscataway, NJ USA, pages 1 - 12, XP068201976 *
See also references of EP4694553A1 *

Also Published As

Publication number Publication date
EP4694553A4 (en) 2026-04-01
EP4694553A1 (en) 2026-02-11
CN120917859A (zh) 2025-11-07
JPWO2024203907A1 (cg-RX-API-DMAC7.html) 2024-10-03

Similar Documents

Publication Publication Date Title
US10667293B2 (en) Information processing device, information processing method, and program
US12356451B2 (en) Information processing apparatus, communication system, information processing method, and program
US20160255589A1 (en) Communication control device, communication control method, and information processing device
TW201618487A (zh) 資訊處理設備及資訊處理方法
US20180048350A1 (en) Multiband bluetooth
WO2016111085A1 (ja) 無線通信装置、無線通信方法及びプログラム
WO2024190715A1 (en) Wireless communication control device
US10397874B2 (en) Information processing device, communication system, information processing method, and program
US20250240055A1 (en) Communication control device and communication control method
WO2024262178A1 (ja) 通信装置および通信方法
US10897748B2 (en) Information processing apparatus, communication system, information processing method, and program
US20250358004A1 (en) Communication control device, communication control method, and program
US20250168741A1 (en) Wireless communication device
JP6950688B2 (ja) 無線通信装置および無線通信方法
EP4694553A1 (en) Communication device, control device, and communication method
WO2024195723A1 (ja) コントローラ装置、基地局、端末装置、通信方法及び制御方法
WO2025205071A1 (ja) 通信制御装置及び通信制御方法
WO2025187214A1 (ja) 通信制御装置
WO2025187486A1 (ja) 情報処理装置及び情報処理方法
WO2026014092A1 (ja) 無線通信制御装置
WO2025187373A1 (ja) 無線端末装置、無線通信装置、および無線通信方法
US20200288500A1 (en) Communication device, program, and communication method
WO2025182313A1 (ja) 通信制御装置
WO2025234227A1 (ja) 無線通信制御装置
WO2025204946A1 (ja) 通信制御装置及び通信制御方法

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: 24780025

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025510748

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025510748

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 202517084443

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: CN2024800206504

Country of ref document: CN

Ref document number: 202480020650.4

Country of ref document: CN

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112025020457

Country of ref document: BR

WWP Wipo information: published in national office

Ref document number: 202517084443

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2024780025

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202480020650.4

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

ENP Entry into the national phase

Ref document number: 2024780025

Country of ref document: EP

Effective date: 20251029

WWP Wipo information: published in national office

Ref document number: 2024780025

Country of ref document: EP