Wireless communication apparatus, communication method, and information processing apparatus

Abstract

A wireless communication device according to the present disclosure provides a second wireless access link with other wireless communication devices based on a first wireless access link with a base station. The wireless communication device includes one or more network interfaces, a user interface of the wireless communication device for a user, and a processor. The processor sends, via one or more network interfaces, a registration request or a start request related to the provision of the second wireless access link to a server device managing the provision of the second wireless access link. The processor receives a notification from the server device regarding the provision of the second wireless access link. The processor outputs at least a portion of the notification to the user interface.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to a wireless communication device, a communication method, and an information processing device. BACKGROUND

[0002] The first standard of the fifth generation mobile communication system (so-called 5G) was formulated as Rel-15 in 2018. In addition, in March 2020, services compatible with 5G started in Japan. Since the introduction of 5G communication networks, the deployment of communication infrastructure is accelerating. In particular, the introduction of millimeter wave band communication that makes it difficult to secure coverage requires the deployment of many communication infrastructures.

[0003] LIST OF REFERENCES

[0004] NON-PATENT LITERATURE

[0005] Non-Patent Literature 1: SP-211636, “New SID on Study on Architecture Enhancements for Vehicle Mounted Relays”, Electronic Meeting, 3GPP TSG SA Meeting #SP-94E, December 2021. Internet <URL: https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / TSGS_94E_Electronic_2021_12 / Docs / SP-211636.zip> SUMMARY

[0006] TECHNICAL PROBLEM

[0007] In order to expand the communication infrastructure, a large investment cost is required. Therefore, infrastructure sharing has recently been accelerated. Infrastructure sharing makes it possible to suppress the introduction cost of communication infrastructure.

[0008] In this way, in order to develop next-generation networks such as Beyond 5G / 6G, it is important to deploy communication infrastructure at low cost.

[0009] Therefore, the present disclosure provides a mechanism that can deploy communication infrastructure at low cost.

[0010] Note that the above problem or object is only one of a plurality of problems or objects that a plurality of embodiments disclosed herein can solve or achieve.

[0011] SOLUTION TO THE PROBLEM

[0012] A wireless communication device of the present disclosure provides a second wireless access link with other wireless communication devices based on a first wireless access link with a base station. The wireless communication device includes one or more network interfaces, a user interface of the wireless communication device that is set for a user, and a processor. The processor sends, via the one or more network interfaces, a registration request or a start request related to the provision of the second wireless access link to a server device that manages the provision of the second wireless access link. The processor receives a notification from the server device regarding the provision of the second wireless access link. The processor outputs at least a portion of the notification to the user interface. BRIEF DESCRIPTION OF DRAWINGS

[0013] Figure 1 is a diagram showing an overview of a communication system according to an embodiment of the present disclosure.

[0014] Figure 2 is a diagram showing an example of a service model using a VaaNI service according to an embodiment of the present disclosure.

[0015] Figure 3 is a diagram showing an example of a network architecture of a communication system according to an embodiment of the present disclosure.

[0016] Figure 4 is a block diagram showing an exemplary configuration of an application server according to an embodiment of the present disclosure.

[0017] Figure 5 is a diagram showing an exemplary configuration of a base station according to an embodiment of the present disclosure.

[0018] Figure 6 is a diagram showing an exemplary configuration of a VaaNI terminal according to an embodiment of the present disclosure.

[0019] Figure 7 is a diagram showing an exemplary configuration of an end user terminal according to an embodiment of the present disclosure.

[0020] Figure 8 is a flowchart showing an exemplary process of a process for executing an operation of a VaaNI terminal according to an embodiment of the present disclosure.

[0021] Figure 9 is a sequence diagram showing an exemplary process of a service registration process according to a first embodiment of the present disclosure.

[0022] Figure 10 is a table showing an example of a vehicle DB according to the first embodiment of the present disclosure.

[0023] Figure 11 is a sequence diagram showing an exemplary process of a service standby process according to the first embodiment of the present disclosure.

[0024] Figure 12 is a table showing an example of a state management DB according to the first embodiment of the present disclosure.

[0025] Figure 13 is a sequence chart showing an exemplary procedure of a service implementation process according to the first embodiment of the present disclosure.

[0026] Figure 14 is a sequence chart showing another exemplary procedure of a service implementation process according to the first embodiment of the present disclosure.

[0027] Figure 15 is a sequence chart showing an exemplary procedure of a service implementation process according to the second embodiment of the present disclosure.

[0028] Figure 16 is a diagram showing an example of a presentation screen according to the second embodiment of the present disclosure.

[0029] Figure 17 is a diagram showing an example of a vehicle selection screen according to the second embodiment of the present disclosure.

[0030] Figure 18 is a diagram showing another example of a presentation screen according to the second embodiment of the present disclosure.

[0031] Figure 19 is a sequence chart showing an exemplary procedure of a service implementation process according to the third embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. Note that, in this specification and the drawings, constituent elements having substantially the same function are denoted with the same reference numerals, and description thereof will not be repeated.

[0033] In addition, in this specification and the drawings, similar constituent elements of the embodiments are distinguished by giving the same reference numerals followed by different letters or numbers in some cases. However, when it is not necessary to particularly distinguish between a plurality of similar constituent elements, the constituent elements are simply denoted with the same reference numerals.

[0034] One or more embodiments described below (including examples, modifications, and application examples) can be implemented independently. Meanwhile, at least some of a plurality of embodiments described below can be appropriately combined with at least some of other embodiments to be implemented. A plurality of embodiments can include novel features different from each other. Therefore, a plurality of embodiments can contribute to solving different purposes or problems, and thus have different effects.

[0035] <1. Introduction>

[0036] <1.1 Operation Scenario>

[0037] As described above, in order to deploy the next-generation network, it is necessary to deploy a communication infrastructure at low cost. In order to deploy the communication infrastructure, a technique of extending coverage by using satellite communication or the like is known.

[0038] When extending coverage by using satellite communication or the like, there is a method of directly providing communication from a satellite to a terminal device. In this method, due to a limitation of power and communication capacity, a small device such as a smartphone can not be able to maintain communication quality.

[0039] In this case, a ground station is deployed near a terminal device, satellite communication is performed by the ground station, and a small terminal device such as a smartphone communicates with the ground station, thereby ensuring communication quality. However, in some cases, it can be difficult to install the ground station from the viewpoint of deployment cost and operation cost.

[0040] Therefore, in the present embodiment, a network infrastructure using hardware performance of a car is introduced. For example, the communication system of the present embodiment uses hardware performance and mobility features of a car or the like of a general user to operate the car as a relay station. As a result, the communication system provides more abundant wireless communication.

[0041] Figure 1 is a diagram showing an outline of a communication system S1 according to an embodiment of the present disclosure. Figure 1 The communication system S1 shown in FIG. 1 includes a satellite base station 20A, a base station 20B, a car 30, and user equipments (UEs) 40A and 40B (terminal devices).

[0042] The car 30 provides a wireless access link between the UEs 40A and 40B based on a wireless backhaul link (an example of a first wireless access link) with the satellite base station 20A. The UEs 40A and 40B are terminal devices used by users different from a user of the car 30. Each of the UEs 40A and 40B can be a small device such as a smartphone or AR glasses.

[0043] In this way, the communication system S1 operates the car 30 as a relay station of the satellite base station 20A. With this configuration, the communication system S1 provides more abundant wireless communication for the UEs 40A and 40B.

[0044] Further, the communication system S1 according to the present embodiment is not limited to satellite communication, and can also be applied to relay communication using a generally used base station 20B. The communication system S1 according to the present embodiment also serves for relay communication using a generally used base station 20B, and can provide cell splitting gain, thereby extending communication capacity of the entire network.

[0045] The automobile 30 can be regarded as a device that can provide computing capability in addition to wireless communication. The automobile 30 is different in the size of the housing from a small device such as a smartphone. Therefore, it is considered that the automobile 30 can easily secure a space for accommodating a computing server.

[0046] Therefore, operating the automobile 30 as a dynamic edge computing server in addition to wireless communication can provide computing capability to an application that is executed around the automobile 30, for example, an application that is executed on the UE 40.

[0047] The communication system S1 is applied, for example, to providing communication and computing capability in an urban area. For example, the automobile (vehicle) 30 of the communication system S1 can be used to compensate for a coverage hole of the base station 20B.

[0048] The automobile 30 of the communication system S1 can also be used as an edge computing infrastructure to provide computing resources to a device with low computing capability, such as AR glasses, a terminal device, or the like. Even in a device with low computing capability such as AR glasses, using the computing capability of the automobile 30 makes it possible to perform distributed processing with low latency, and an application with a large processing amount, such as map display or guidance to a destination, can be executed. Therefore, it is not necessary to perform processing in a cloud server via a wireless backhaul link with the satellite base station 20A, and it is possible to reduce the load on the wireless backhaul link.

[0049] Further, the communication system S1 is applied, for example, to providing wireless communication in an infrastructure-deficient area. Examples of the infrastructure-deficient area include a rural area such as a mountainous area and a developing country.

[0050] Note that here, the number of the automobiles 30 included in the communication system S1 is one, but the number of the automobiles 30 included in the communication system S1 can be two or more. When providing computing resources, the communication system S1 can use cooperation of edge computing servers that are locally installed on a plurality of automobiles 30 to provide more powerful computing resources. In this way, a plurality of automobiles 30 can cooperate with each other to provide computing resources.

[0051] <1.2. Definitions of Terms>

[0052] Definitions of some terms used in the present disclosure will be described.

[0053] (Owning person)

[0054] In the present disclosure, the "owning person" means an owner of an automobile. The owning person is not necessarily a driver of the automobile. The owning person can be an individual who owns the automobile, or can be a company that owns the automobile, such as an automobile rental company, a bus company, or a taxi company.

[0055] (driver)

[0056] In the present disclosure, the "driver" refers to a driver of a car. The driver is not necessarily the owner of the car. The driver is the person who drives the car, regardless of whether the driver owns the car. The above owner can be the driver, or the owner and the driver can be different.

[0057] (telecommunication carrier)

[0058] In the present disclosure, the "telecommunication carrier" is a provider that provides a wireless communication service. The telecommunication carrier is not limited to a broadband carrier (Public Land Mobile Network (PLMN)), but also includes a private network carrier in a local area. Furthermore, the telecommunication carrier includes a satellite carrier. The telecommunication carrier can also include a ride-sharing company and a car rental agency. The telecommunication carrier can be a Mobile Network Operator (MNO).

[0059] (end user)

[0060] In the present disclosure, the "end user" is a service beneficiary who receives a communication service or a computing service and enjoys an application service. For example, the "end user" is a subscriber to a communication service of a telecommunication carrier. In addition, a service beneficiary who receives a service using an unlicensed band communication such as a wireless local area network (LAN) is also assumed to be an "end user".

[0061] (car and vehicle)

[0062] In the present disclosure, the "car" or "vehicle" is a device that provides a wireless access link and a computing capability to a small device (end user terminal 40) such as a smartphone.

[0063] In one aspect, in the present disclosure, the "car" or "vehicle" can operate as a user equipment (UE), or can operate as a base station. More specifically, when the wireless access link is an access link for cellular communication, the car 30 in the present disclosure can be a Radio Access Network (RAN) node conforming to the 3GPP (registered trademark) standard. Specifically, the car 30 can be a relay node (including a donor node), an Integrated Access and Backhaul (IAB) node (including an IAB donor node), or simply a gNB. In addition or alternatively, the car 30 in the present disclosure can be a Device-to-Device (D2D) UE (network-to-UE relay, UE-to-UE relay).

[0064] When the wireless access link is an access link for Wi-Fi (registered trademark) (IEEE 802.11) communication, the car 30 in the present disclosure can be a Wi-Fi (registered trademark) access point.

[0065] Further, the automobile 30 in the present disclosure can have a computing resource. When the automobile 30 in the present disclosure is used as a RAN node conforming to the 3GPP (registered trademark) standard, an edge computing server such as an edge application server can be installed on the automobile 30.

[0066] In this configuration, the computing resource can include a local user plane function (UPF) between the RAN and the edge computing server (local data network (DN)). Alternatively, the computing resource can also include at least one of 5GC (5G core) nodes (for example, an access and mobility management function (AMF), a session management function (SMF), and an application function (AF)) as a node that manages the local UPF.

[0067] In this way, the automobile 30 in the present disclosure can have a communication device and / or a computing resource (information processing device). Hereinafter, the configuration and operation of the automobile 30 described below can be replaced at least in part by the configuration and operation of the communication device and / or the computing resource. In other words, the automobile 30 in the following explanation can be replaced with the communication device and / or the information processing device.

[0068] (Final user terminal)

[0069] In the present disclosure, the "final user terminal" is a terminal device used by a final user (service beneficiary). The final user terminal corresponds to the above-described UE 40. Hereinafter, the UE 40 is also referred to as the final user terminal 40.

[0070] The final user terminal 40 in the present disclosure performs wireless communication upon receiving a wireless access link provided from the automobile 30. Further, the final user terminal 40 can receive a computing resource provided from the automobile to perform a predetermined computation (computation for a desired application) by using the resource.

[0071] (VaaNI (Vehicle-to-anything Network Infrastructure) service)

[0072] In the present disclosure, the "VaaNI service" is a service provided by the communication system S1 to the final user via the automobile 30. The VaaNI service includes providing a wireless access link and / or a computing resource by the automobile 30 to the final user terminal 40. Hereinafter, the automobile 30 that provides the VaaNI service to the final user terminal 40 is also described as the VaaNI terminal 30.

[0073] Hereinafter, an example of the VaaNI service provided when the automobile 30 is parked (stopped) will be described, but the VaaNI service can be provided even during movement (travel) of the automobile 30 unless otherwise stated.

[0074] <1.3. Example of wireless access link>

[0075] The wireless communication in the wireless access link provided by the VaaNI terminal 30 can use 3GPP (registered trademark) cellular communication as licensed band communication. Alternatively, unlicensed band communication such as Wi-Fi (registered trademark) can be used as the wireless communication.

[0076] For example, when the VaaNI terminal 30 provides a wireless access link based on satellite communication in a rural area, Wi-Fi (registered) can be used as the wireless access link. This is because service beneficiaries (end users) can not have rich terminals. For example, by using Wi-Fi (registered trademark) as the wireless communication in the wireless access link by the VaaNI terminal 30, even terminal devices (for example, tablet terminals, PCs, and the like) that cannot perform cellular communication can enjoy the VaaNI service.

[0077] Further, IAB communication defined in 3GPP (registered trademark) can be used for the wireless access link and the backhaul link.

[0078] <1.4. Examples of service models>

[0079] Next, an example of a service model using the VaaNI service will be described with reference to Figure 2

[0080] Figure 2 is a diagram illustrating an example of a service model using the VaaNI service according to an embodiment of the present disclosure.

[0081] Figure 2 The telecommunications carrier shown in FIG. 1 provides communication and computing capabilities to the end user terminal 40 used by the service beneficiaries (end users). For the communication and computing capabilities, the end users pay a fee to the telecommunications carrier.

[0082] Further, the telecommunications carrier provides a wireless backhaul for the vehicle owner so that the vehicle owner operates the vehicle as a communication infrastructure (base station (VaaNI terminal 30)). The vehicle owner provides communication and / or computing capabilities as part of the communication network to receive an incentive.

[0083] The vehicle owner establishes an infrastructure in order to operate the vehicle as a communication infrastructure (base station (VaaNI terminal 30)). For example, the vehicle owner pays a fee to an infrastructure provider, purchases an infrastructure device (for example, corresponding to the above communication device and / or information processing device) for operating the vehicle as a communication infrastructure (base station (VaaNI terminal 30)), and installs the infrastructure device in the vehicle. Alternatively, the vehicle owner can purchase a vehicle in which an infrastructure device is installed. ​

[0084] For example, when the car owner and the driver are different, the car owner lends the VaaNI terminal 30 to the driver. For example, the car owner causes the driver to park (move) the VaaNI terminal 30 at a place desired by the telecommunication carrier. The driver receives an incentive from the car owner to compensate for the space value.

[0085] (Examples of Incentives)

[0086] As described above, the car owner and / or the driver receives an incentive for providing the wireless access link to the end user terminal 40. Examples of the incentive include money, a coupon, a digital incentive, and the like.

[0087] Examples of the coupon include a discount coupon or a free coupon for parking at a place where the VaaNI terminal 30 is parked, a discount coupon for a facility next to the parking, and the like.

[0088] Examples of the digital incentive include virtual currency, a digital token, a non-fungible token (NFT), and the like. In addition, examples of the digital incentive include providing in-game content, an item, and the like.

[0089] <2. Example Configuration of Communication System S1>

[0090] <2.1. Example of Network Architecture>

[0091] Figure 3 is a diagram showing an example of a network architecture of a communication system S1 according to an embodiment of the present disclosure.

[0092] The telecommunication carrier of the communication system S1 has a base station (gNB in the example) 20, a core network CN, and an application server 10. Note that the base station 20 is connected to the core network CN and the application server 10 via a network N1. Figure 3 The example shows that the base station 20 includes a satellite station 20A and a ground station 20B. Figure 3

[0093] (Application Server 10)

[0094] The application server 10 is located on an external network, for example, and is connected to the core network CN via the external network. For example, the external network can be a service network of the telecommunication carrier, such as an IP Multimedia Subsystem (IMS) network. In addition, the external network can be a private network such as an intranet.

[0095] The application server 10 is connected to an application of a vehicle driver and an application of an end user, which will be described later, in an application layer (application layer). The application server 10 exchanges information with the application of the vehicle driver and the application of the end user in the application layer.

[0096] (Core Network CN)

[0097] ​The core network CN includes, for example, an evolved packet core (EPC) or a 5G core network (5GC). When the core network CN is an NR core network (5GC), the core network CN can include an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), and a unified data management (UDM).

[0098] The core network CN is connected to an external network via a gateway device (not shown). For example, the UPF, which is a network function that handles data of a user plane, is connected to an application server 10 via a network function called a data network (DN) that is identified by a data network name (DNN). Here, the DNN corresponds to an access point name (APN) used in systems prior to 4G.

[0099] (Base station 20)

[0100] Each base station 20 is a communication device that operates a cell and provides a wireless communication service to one or more VaaNI terminals 30 located within a coverage of the cell. The cell is operated in accordance with any wireless communication system such as long term evolution (LTE) or new radio (NR). The base station 20 is connected to the core network CN. In addition, the base station 20 operates a beam that is identifiable by a synchronization signal / PBCH block (SSB), and transmits and receives data to and from one or more VaaNI terminals 30 via one or more beams.

[0101] Furthermore, the base station 20 can include a collection of a plurality of physical or logical devices. For example, in the present embodiment of the present disclosure, the base station 20 can be divided into a plurality of devices of a baseband unit (BBU) and a radio unit (RU) so as to be considered as a collection of a plurality of devices. Additionally or alternatively, in an embodiment of the present disclosure, the base station 20 can be either or both of the BBU and the RU. The BBU and the RU can be connected through a predetermined interface (e.g., ePRI). Additionally or alternatively, the RU can be referred to as a remote radio unit (RRU) or a radio dot (RD). Additionally or alternatively, the RU can correspond to a gNB-DU described later. Additionally or alternatively, the BBU can correspond to a gNB-CU described later. Additionally or alternatively, the RU can correspond to a gNB-DU. Furthermore, the BBU can correspond to a combination of the gNB-CU and the gNB-DU, which is described later. Additionally or alternatively, the RU can be a device that is integrally formed with an antenna. The antenna of the base station 20 (e.g., an antenna integrally formed with the RU) can employ an advanced antenna system to support MIMO (e.g., FD-MIMO) or beamforming. In the advanced antenna system, the antenna of the base station 20 (e.g., an antenna integrally formed with the RU) can include, for example, 64 transmission antenna ports and 64 reception antenna ports.

[0102] Note that a plurality of base stations 20 can be connected to each other. One or more base stations 20 can be included in a radio access network (RAN). In other words, the base station 20 can be simply referred to as a RAN, a RAN node, an access network (AN), or an AN node. The RAN in LTE is called an enhanced general universal terrestrial RAN (EUTRAN). The RAN in NR is called an NGRAN. The RAN in W-CDMA (UMTS) is called a UTRAN. The base station 20 in LTE is called an evolved Node B (eNodeB) or eNB. In other words, the EUTRAN includes one or more eNodeBs (eNBs). Furthermore, the base station 20 in NR is called a gNodeB or gNB. In other words, the NGRAN includes one or more gNBs. Furthermore, the EUTRAN can include a gNB (en-gNB) connected to a core network (EPC) in a LTE communication system (EPS). Likewise, the NGRAN can include an ng-eNB connected to a core network 5GC in a 5G communication system (5GS). Additionally or alternatively, when the base station 20 is an eNB, a gNB, or the like, the base station can be referred to as a 3GPP access. Additionally or alternatively, when the base station 20 is a wireless access point (for example, a Wi-Fi (registered trademark) access point), the base station 20 can be referred to as a non-3GPP access. Additionally or alternatively, the base station 20 can be a small cell radio device called a remote radio head (RRH). Additionally or alternatively, when the base station 20 is a gNB, the base station 20 can be referred to as a combination of a gNB central unit (CU) and a gNB distributed unit (DU) or either of them. Here, the gNB CU hosts a plurality of upper layers of an access layer (for example, RRC, SDAP, and PDCP) for communication with a UE. Meanwhile, the gNB-DU hosts a plurality of lower layers of an access layer (for example, RLC, MAC, and PHY). In other words, in messages / information described later, RRC signaling (for example, MIB, various SIBs including SIB1, an RRCSetup (RRC setup) message, and an RRCReconfiguration (RRC reconfiguration) message) can be generated by the gNB CU, and downlink control information (DCI) and various physical channels (for example, PDCCH and PBCH) can be generated by the gNB-DU. Alternatively, in the RRC signaling, for example, part of the configuration (setting information) such as an IE: cellGroupConfig (cell group configuration) can be generated by the gNB-DU, and the remaining configuration can be generated by the gNB-CU. These configurations (setting information) can be transmitted and received through an F1 interface described later. Note that the base station 20 can be configured to be communicable with another base station 20. For example, when a plurality of base stations 20 are each an eNB or have a combination of an eNB and an EN-gNB, the base stations 20 can be connected through an X2 interface.Additionally or alternatively, when the plurality of base stations 20 are each a gNB or have a combination of gNB CU and gNB DU, the devices can be connected through an Fl interface. The messages / information (RRC signaling information or DCI information, or physical channels) described later can be transferred between the plurality of base stations 20 (for example, via an X2, Xn, or Fl interface). Furthermore, communication can be performed between the base stations 20 and the core network CN (using messages defined in an application protocol (for example, NGAP) on a base station-to-core network interface).

[0103] Furthermore, as described above, the base station 20 can be configured to manage a plurality of cells. Each cell provided by the base station 20 is referred to as a serving cell. The serving cell includes a primary cell (PCell) and a secondary cell (SCell). When a UE (for example, the VaaNI terminal 30) is provided with dual connectivity (for example, EUTRA-EUTRA dual connectivity, EUTRA-NR dual connectivity (ENDC), EUTRA-NR dual connectivity with 5GC, NR-EUTRA dual connectivity (NEDC), and NR-NR dual connectivity), a PCell provided by a master node (MN) and zero or one or more SCells are referred to as a master cell group. Furthermore, the serving cell can include a primary secondary cell or a primary SCG cell (PSCell). In other words, when a UE is provided with dual connectivity, a PSCell provided by a secondary node (SN) and zero or one or more SCells are referred to as a secondary cell group (SCG). Unless specifically set (for example, PUCCH on an SCell), a physical uplink control channel (PUCCH) is transmitted on the PCell and the PSCell, but not on the SCell. Furthermore, radio link failure is also detected on the PCell and the PSCell, but not detected (may not be detected) on the SCell. In this way, the PCell and the PSCell that play a special role on the serving cell are also referred to as special cells (SpCell). In one cell, one downlink component carrier and one uplink component carrier can be associated with each other. Furthermore, a system bandwidth corresponding to one cell can be divided into a plurality of bandwidth parts. In this configuration, one or more bandwidth parts (BWPs) can be set for a UE, and the UE can use one of the bandwidth parts as an active BWP. In addition, the radio resources (for example, frequency band, numerology (subcarrier spacing), and slot format (slot configuration)) used by the VaaNI terminal 30 can be different between cells, component carriers, or BWPs.

[0104] The base station 20 can be a ground station or a non-ground station. The non-ground station can be a satellite station or an aircraft station. If the non-ground station is a satellite station, the communication system S1 can be a bent-pipe (transparent) satellite mobile communication system.

[0105] Note that, in the present embodiment, a ground station (also referred to as a ground base station) refers to a base station 20 installed on the ground (including a relay station). Here, "ground" indicates not only a position on land but also positions on or under the ground, on or under water, and the like in a broad sense. Note that, in the following description, "ground station" can be replaced with "gateway".

[0106] The VaaNI terminal 30 is a communication device that performs wireless communication with the base station 20 based on control by the base station 20. For example, the VaaNI terminal 30 is connected to the base station 20 via a wireless backhaul link. The wireless backhaul link is, for example, a Uu link. Further, the VaaNI terminal 30 provides a wireless access link and / or a computing resource to the end user terminal 40.

[0107] For example, on the VaaNI terminal 30, an application of a vehicle driver is running. Alternatively, the application of the vehicle driver can be running on a device operated by the driver of the VaaNI terminal 30. The device operated by the driver of the VaaNI terminal 30 can be, for example, a terminal device such as a smartphone used by the driver, or can be an infotainment terminal installed in the vehicle.

[0108] The application of the vehicle driver performs registration with / exit from the VaaNI service, and receives location information and accompanying information about a provision place of the VaaNI service. Examples of the accompanying information include information about the provision place (presence or absence of a parking lot or a charging station), a supposed service provision time, a supposed battery consumption amount, a supposed incentive payment, and the like. In addition, the application of the vehicle driver transmits and receives signals related to the VaaNI service, such as acceptance of a request transmitted from the application server 10 or an application of an end user or a bid.

[0109] The end user terminal 40 is a communication device that performs wireless communication with the VaaNI terminal 30. For example, the end user terminal 40 is connected to the VaaNI terminal 30 via a wireless access link. The wireless access link is, for example, a Uu link or a Wi-Fi (registered trademark) link. The VaaNI service is provided to the end user terminal 40 by using the communication infrastructure and / or the computing infrastructure of the VaaNI terminal 30.

[0110] For example, on the end user terminal 40, an end user's application runs. The end user's application issues a request for the VaaNI service, and transmits accompanying information. Examples of the accompanying information include location information on a place where a service provision is desired, a required service provision time, a need for a computing resource, and the like.

[0111] <2.2. Exemplary Configuration of Application Server>

[0112] Figure 4 is a block diagram showing an exemplary configuration of the application server 10 according to an embodiment of the present disclosure.

[0113] The application server 10 is a device that implements a management function of the VaaNI service. The application server 10 is, for example, a server device. The application server 10 can be a device collectively called a cloud server or an edge server or the like.

[0114] As shown in Figure 4 The application server 10 includes a communication unit 11, a storage unit 12, and a control unit 13. Note that Figure 4 The configuration shown in

[0115] The communication unit 11 is a communication interface for communicating with other devices. The communication unit 11 can be a network interface or a device connection interface. For example, the communication unit 11 can be a LAN interface such as a network interface card (NIC), or can be a USB interface including a universal serial bus (USB) host controller, a USB port, and the like. Further, the communication unit 11 can be a wired interface or a wireless interface. The communication unit 11 functions as a communication means of the application server 10. The communication unit 11 communicates with the base station 20, other NF nodes, or AN nodes under the control of the control unit 13.

[0116] The storage unit 12 is a readable / writable data storage device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, or a hard disk. The storage unit 12 functions as a storage means of the application server 10.

[0117] The control unit 13 is a controller that controls the units of the application server 10. The control unit 13 is implemented by a processor such as a central processing unit (CPU), a micro processing unit (MPU), or a graphic processing unit (GPU). For example, the control unit 13 is implemented by the processor executing various programs stored in a storage device in the application server 10 with a random access memory (RAM) or the like as a work space. Note that the control unit 13 can be implemented by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). The CPU, MPU, GPU, ASIC, and FPGA can all be regarded as controllers.

[0118] Further, an AF serving as a network function with a service-based interface can be implemented in the control unit 13 so that services provided by the base station 20, other NF nodes, or AN nodes are available via the communication unit 11. For services provided by nodes with a service-based interface, information can be exchanged between the nodes by request / response or subscription / notification.

[0119] <2.3. Exemplary Configuration of Base Station>

[0120] Figure 5 Fig. 1 is a diagram showing an exemplary configuration of the base station 20 according to an embodiment of the present disclosure. The base station 20 is a communication apparatus (wireless system) that performs wireless communication with the VaaNI terminal 30. The base station 20 is a type of information processing apparatus.

[0121] The base station 20 includes a signal processing unit 21, a storage unit 22, a network communication unit 23, and a control unit 24. Note that the base station 20 can include other units (not shown in the figure) as necessary. Figure 5 The configuration shown in Fig. 1 represents a functional configuration, and the base station 20 can have a hardware configuration different from the functional configuration. Further, the functions of the base station 20 can be distributed in a plurality of physically separate apparatuses for implementation. For example, as described above, the functions of the base station 20 are distributed to the CU and the DU, or the CU, the DU, and the RU.

[0122] The signal processing unit 21 is a wireless communication interface (communication unit) that performs wireless communication with other communication apparatuses (for example, the VaaNI terminal 30 and other base stations 20). The signal processing unit 21 is a wireless transceiver that operates under the control of the control unit 24. Note that the signal processing unit 21 can support a plurality of wireless access systems. For example, the signal processing unit 21 can support both NR and LTE. The signal processing unit 21 can support other cellular communication systems such as W-CDMA and CDMA2000. Further, the signal processing unit 21 can support a wireless LAN communication system in addition to the cellular communication systems. Of course, the signal processing unit 21 can support only one wireless access system.

[0123] The signal processing unit 21 includes a reception processing unit 211, a transmission processing unit 212, and an antenna 213. The signal processing unit 21 can include a plurality of reception processing units 211, transmission processing units 212, and antennas 213. Note that when the signal processing unit 21 supports a plurality of radio access systems, the units of the signal processing unit 21 can be configured individually for each radio access system. For example, when the base station 20 supports NR and LTE, the reception processing unit 211 and the transmission processing unit 212 can be configured individually for NR and LTE.

[0124] The reception processing unit 211 processes an uplink signal received via the antenna 213. The reception processing unit 211 includes a radio receiving unit 211a, a demultiplexing unit 211b, a demodulation unit 211c, and a decoding unit 211d.

[0125] The radio receiving unit 211a performs frequency down-conversion, removal of unnecessary frequency components, control of amplification levels, quadrature demodulation, conversion to a digital signal, removal of a guard interval, extraction of a frequency domain signal by a fast Fourier transform, and the like on an uplink signal. For example, assume that the radio access system of the base station 20 is a cellular communication system such as LTE. At this time, the demultiplexing unit 211b demultiplexes an uplink channel such as a physical uplink shared channel (PUSCH) and a physical uplink control channel (PUCCH) and an uplink reference signal from a signal output from the radio receiving unit 211a. The demodulation unit 211c performs demodulation of a reception signal on a modulation symbol on an uplink channel by using a modulation method such as binary phase shift keying (BPSK) or quadrature phase shift keying (QPSK). The modulation method used by the demodulation unit 211c can employ a multi-level QAM such as 16 quadrature amplitude modulation (QAM), 64 QAM, or 256 QAM. The decoding unit 211d performs decoding processing on encoded bits in a demodulated uplink channel. Decoded uplink data and uplink control information are output to the control unit 24.

[0126] The transmission processing unit 212 performs transmission processing of downlink control information and downlink data. The transmission processing unit 212 includes an encoding unit 212a, a modulation unit 212b, a multiplexing unit 212c, and a radio transmission unit 212d.

[0127] The coding section 212a encodes the downlink control information and the downlink data input from the control section 24 by using an encoding method such as block coding, convolution coding, Turbo coding. Note that, as the encoding, polar code encoding and low-density parity-check code (LDPC) encoding can be performed. The modulation section 212b modulates the encoded bits output from the coding section 212a by using a predetermined modulation method such as BPSK, QPSK, 16QAM, 64QAM, or 256QAM. The multiplexing section 212c allocates the modulation symbols and the downlink reference signal multiplexed for each channel to predetermined resource elements. The radio transmission section 212d performs various types of signal processing on the signal from the multiplexing section 212c. For example, the radio transmission section 212d performs processing such as conversion to the time domain by using a fast Fourier transform, addition of a guard interval, generation of a baseband digital signal, conversion to an analog signal, quadrature modulation, up-conversion of frequency, removal of unnecessary frequency components, amplification of power, and the like. The signal generated by the transmission processing section 212 is transmitted from the antenna 213.

[0128] The storage section 22 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, or a hard disk. The storage section 22 functions as a storage of the base station 20.

[0129] The network communication section 23 is a communication interface for communicating with other devices (for example, other base stations 20). For example, the network communication section 23 includes a LAN interface such as a NIC. The network communication section 23 can be a USB interface including a USB host controller, a USB port, and the like. In addition, the network communication section 23 can be a wired interface or a wireless interface. The network communication section 23 functions as a network communication of the base station 20. The network communication section 23 communicates with other devices under the control of the control section 24.

[0130] The control section 24 is a controller that controls the units of the base station 20. The control section 24 is implemented by a processor such as a CPU, an MPU, or a GPU. For example, the control section 24 is implemented by the processor executing various programs stored in a storage device inside the base station 20 with a RAM or the like as a work space. Note that the control section 24 can be implemented by an integrated circuit such as an ASIC or an FPGA. The CPU, the MPU, the GPU, the ASIC, and the FPGA can all be regarded as controllers.

[0131] <2.4. Exemplary Configuration of VaaN Terminal>

[0132] The VaaNI terminal 30 is a device that functions as a relay station of the base station 20. The VaaNI terminal 30 is a type of communication device. In addition, the VaaNI terminal 30 is a type of information processing device. The VaaNI terminal 30 can also be referred to as a relay base station. Furthermore, the VaaNI terminal 30 can be a device referred to as a repeater (for example, an RF repeater, a smart repeater, a network-controlled repeater, a smart surface).

[0133] The VaaNI terminal 30 is allowed to perform wireless communication, such as NOMA communication, with the end user terminal 40. The VaaNI terminal 30 relays communication between the base station 20 and the end user terminal 40. Note that the VaaNI terminal 30 can be configured to enable wireless communication with other VaaNI terminals 30 and the base station 20. The VaaNI terminal 30 can configure a radio access network RAN together with the base station 20.

[0134] Note that the VaaNI terminal 30 can have a configuration similar to that of the above-described base station 20. For example, the VaaNI terminal 30 can be a device installed at a mobile object or the mobile object itself. In addition, the mobile object can be a mobile object that moves on land (on the ground), or can be a mobile object that moves underground. Of course, the mobile object can be a mobile object that moves on water, or can be a mobile object that moves underwater.

[0135] Furthermore, the VaaNI terminal 30 can have a beamforming capability. In this case, the VaaNI terminal 30 can be configured so as to form a cell or a service area for each beam.

[0136] Figure 6 is a diagram illustrating an exemplary configuration of the VaaNI terminal 30 according to an embodiment of the present disclosure. The VaaNI terminal 30 includes a signal processing unit 31, a storage unit 32, a control unit 33, and an input / output unit 34. Note that the VaaNI terminal 30 can include a power supply unit (not shown) that supplies power to each unit. Figure 6 The configuration shown in FIG. 30 represents a functional configuration, and the VaaNI terminal 30 can have a hardware configuration different from this functional configuration. Furthermore, the functions of the VaaNI terminal 30 can be distributed in a plurality of physically separate configurations for implementation.

[0137] The signal processing unit 31 is a wireless communication interface that performs wireless communication with other wireless communication devices (e.g., the base station 20, the end user terminal 40, and other VaaNI terminals 30). The signal processing unit 31 supports one or more wireless access systems. For example, the signal processing unit 31 supports both NR and LTE. In addition to NR and LTE, the signal processing unit 31 can support W-CDMA or CDMA2000. The signal processing unit 31 includes a transmission processing unit 311, a reception processing unit 312, and an antenna 313. The signal processing unit 31 can include a plurality of transmission processing units 311, reception processing units 312, and antennas 313. Note that when the signal processing unit 31 supports a plurality of wireless access systems, the units of the signal processing unit 31 can be configured individually for each wireless access system. For example, the transmission processing unit 311 and the reception processing unit 312 can be configured individually for LTE and NR. The transmission processing unit 311, the reception processing unit 312, and the antenna 313 have similar configurations to the above configurations of the transmission processing unit 212, the reception processing unit 211, and the antenna 213. Note that the signal processing unit 31 can be configured to enable beamforming as in the signal processing unit 21.

[0138] The storage unit 32 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, or a hard disk. The storage unit 32 functions as a storage of the VaaNI terminal 30.

[0139] The control unit 33 is a controller that controls the units of the VaaNI terminal 30. The control unit 33 is implemented by a processor such as a CPU, an MPU, or a GPU. For example, the control unit 33 is implemented by a processor executing various programs stored in a storage device inside the VaaNI terminal 30 with a RAM or the like as a work space. Note that the control unit 33 can be implemented by an integrated circuit such as an ASIC or an FPGA. The CPU, the MPU, the GPU, the ASIC, and the FPGA can all be regarded as controllers. The operation of the control unit 33 can be the same as that of the control unit 24 of the base station 20.

[0140] The input / output unit 34 is a user interface for exchanging information with a user such as a driver. For example, the input / output unit 34 is an operation device for various operations of the user, such as a keyboard, a mouse, an operation key, or a touch screen. Alternatively, the input / output unit 34 is a display device such as a liquid crystal display or an organic electroluminescence (EL) display. The input / output unit 34 can be an acoustic device such as a speaker or a buzzer. Furthermore, the input / output unit 34 can be an illumination device such as a light emitting diode (LED) lamp. The input / output unit 34 functions as an input / output means (input means, output means, operation means, or reporting means) of the VaaNI terminal 30. The input / output unit 34 can be a car navigation device or an infotainment device mounted on a car (VaaNI terminal 30). Furthermore or alternatively, the input / output unit 34 can be a wireless communication device (for example, a smartphone) possessed by the driver, which is connected to the car (VaaNI terminal 30) in a wired or wireless manner. From this viewpoint, the input / output unit 34 can be an external device of the VaaNI terminal 30.

[0141] Note that the VaaNI terminal 30 can be an IAB relay node. The VaaNI terminal 30 operates as an IAB mobile terminal (MT) with respect to an IAB donor node that provides a backhaul, and operates as an IAB distributed unit (DU) with respect to an end user terminal 40 that provides access. The IAB donor node can be, for example, the base station 20, and operates as an IAB central unit (CU).

[0142] <2.5. Exemplary Configuration of End User Terminal>

[0143] The end user terminal 40 is a wireless communication device that performs wireless communication with other communication devices such as the base station 20 and the VaaNI terminal 30. The end user terminal 40 is, for example, a mobile phone, a smart device (a smartphone or a tablet), a personal digital assistant (PDA), or a personal computer. Furthermore, the end user terminal 40 can be a device provided with a communication function such as a service camera, or can be a motorcycle, a mobile relay vehicle, or the like, on which a communication device such as a field pickup unit (FPU) is installed. Furthermore, the end user terminal 40 can be a machine-to-machine (M2M) device or an Internet of Things (IoT) device.

[0144] Note that the end user terminal 40 can enable NOMA communication with the VaaNI terminal 30. Further, in the communication with the VaaNI terminal 30, the end user terminal 40 can enable the use of automatic retransmission technology such as HARQ. Further, the end user terminal 40 can enable sidelink communication with other end user terminals 40. The end user terminal 40 can enable the use of automatic retransmission technology such as HARQ when performing sidelink communication. Note that the end user terminal 40 can also enable NOMA communication in the communication (sidelink) with other end user terminals 40. Further, the end user terminal 40 can enable LPWA communication with other communication devices (e.g., the VaaNI terminal 30 and other end user terminals 40). In addition, the wireless communication used by the end user terminal 40 can be wireless communication using millimeter waves. Note that the wireless communication (including sidelink communication) used by the end user terminal 40 can be wireless communication using radio waves, or wireless communication using infrared or visible light (optical wireless communication).

[0145] Further, the end user terminal 40 can be a mobile device. Here, the mobile device is a wireless communication device that is movable. At this time, the end user terminal 40 can be a wireless communication device mounted on a mobile object or the mobile object itself. For example, the end user terminal 40 can be a vehicle (such as a car, a bus, a truck, or a motorcycle) moving on a road, or a wireless communication device mounted on the vehicle. Note that the mobile object can be a mobile terminal, or can be a mobile object moving on land (on the ground), under the ground, on water, or under water. Further, the mobile object can be a mobile object moving in the atmosphere (such as a drone or a helicopter), or can be a mobile object moving above the atmosphere (such as an artificial satellite).

[0146] The end user terminal 40 can be connected to multiple VaaNI terminals 30 or multiple cells at the same time to perform communication. For example, when one VaaNI terminal 30 supports a communication area via multiple cells (e.g., a pCell and an sCell), multiple cells can be combined by a carrier aggregation (CA) technology, a dual connectivity (DC) technology, or a multi-connectivity (MC) technology, thereby enabling communication between the VaaNI terminal 30 and the end user terminal 40. Alternatively, communication between the end user terminal 40 and multiple VaaNI terminals 30 can be performed via cells of different VaaNI terminals 30 by a coordinated multipoint transmission and reception (CoMP) technology.

[0147] Figure 7 is a diagram illustrating an exemplary configuration of the end user terminal 40 according to an embodiment of the present disclosure. The end user terminal 40 includes a signal processing unit 41, a storage unit 42, and a control unit 43. Note thatFigure 7 The configuration shown in FIG. 1 represents a functional configuration, and the end user terminal 40 can have a hardware configuration different from the functional configuration. Furthermore, the functions of the end user terminal 40 can be distributed in a plurality of physically separate configurations for implementation.

[0148] The signal processing unit 41 is a signal processing unit for wireless communication with other wireless communication devices (e.g., the base station 20, the V2V terminal 30, and other end user terminals 40). The signal processing unit 41 operates under the control of the control unit 43. The signal processing unit 41 includes a transmission processing unit 411, a reception processing unit 412, and an antenna 413. The configuration of the signal processing unit 41, the transmission processing unit 411, the reception processing unit 412, and the antenna 413 can be similar to that of the signal processing unit 21, the transmission processing unit 212, the reception processing unit 211, and the antenna 213 of the base station 20. Furthermore, the signal processing unit 41 can be configured to enable beamforming as in the signal processing unit 21. Furthermore, the signal processing unit 41 can be configured to enable transmission and reception of spatially multiplexed signals as in the signal processing unit 21.

[0149] The storage unit 42 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, or a hard disk. The storage unit 42 serves as a storage of the end user terminal 40.

[0150] The control unit 43 is a controller that controls the units of the end user terminal 40. The control unit 43 is implemented by a processor such as a CPU or an MPU. For example, the control unit 43 is implemented by a processor executing various programs stored in a storage device inside the end user terminal 40 with a RAM or the like as a work space. Note that the control unit 43 can be implemented by an integrated circuit such as an ASIC or an FPGA. The CPU, the MPU, the ASIC, and the FPGA can all be regarded as controllers. Furthermore, the control unit 43 can be implemented by a GPU in addition to or instead of the CPU.

[0151] <3. Operation example of communication system>

[0152] The operation of the communication system S1 will be described below.

[0153] It is desirable to dynamically control the operation of the above-described V2V terminal 30 (vehicle infrastructure) (e.g., the operation of the V2V service) at a desired timing and at a desired place. The operation of the V2V terminal 30 requires a cost (vehicle battery consumption and incentive payment to the vehicle owner, etc.), and thus, it is desirable to perform the operation at a desired timing.

[0154] Figure 8is a flowchart showing an exemplary process of processing for performing the operation of the VaaNI terminal 30 according to the embodiment of the present disclosure. For example, the processing shown in Figure 8 is performed by the communication system S1.

[0155] As shown in Figure 8 , the communication system S1 provides and / or collects information to perform the operation of the VaaNI terminal 30 (step S11).

[0156] Next, the communication system S1 proceeds with performing determination to determine whether to perform the operation (step S12), and when the operation is performed, gives an instruction for performing the operation (step S13).

[0157] Specifically, examples of the person who determines the operation to determine the performance of the operation include an operator, a vehicle owner, and a service beneficiary (end user) in communication. The person who determines the operation performs the processing of Figure 8 via his / her own device. In the communication system S1, a system for performing the processing is constructed.

[0158] In this way, examples of the node that performs the processing for performing the operation include a device (for example, the application server 10, the VaaNI terminal 30, and the end user terminal 40, respectively) operated by the operator, the vehicle owner, and the service beneficiary (end user) in communication. The node determines whether the VaaNI terminal 30 provides a wireless access link. In other words, each node controls the on / off of the facility (vehicle infrastructure) that provides the wireless access link of the VaaNI terminal 30.

[0159] Although each node can perform the processing for performing the operation, the node needs different methods of providing / collecting information for performing the processing or an instruction for performing the processing. Therefore, hereinafter, examples of the operation method will be described for each person who determines the operation, in other words, for each node that performs the processing for performing the operation.

[0160] Note that the VaaNI terminal 30 provides a wireless access link for the inside and outside of the car. For example, the VaaNI terminal 30 has a communication providing function for providing a wireless access link to an end user terminal 40 (such as a smartphone) used by a driver. In addition, the VaaNI terminal 30 has a communication providing function for providing a wireless access link to an end user terminal 40 used by an end user (such as a pedestrian) outside the car.

[0161] Hereinafter, unless otherwise specified, it is assumed that the VaaNI terminal 30 provides a wireless access link to the outside of the car. The person who determines the operation (the node) determines whether to enable the communication providing function of the VaaNI terminal 30 for providing a wireless access link to the outside of the car.

[0162] In this way, the communication system S1 operates a car (the VaaNI terminal 30) used by a general user as a network communication infrastructure. As a result, the communication system S1 enables to increase the capacity of the entire communication network as needed and dynamically.

[0163] Further, operating the VaaNI terminal 30 as an edge computing infrastructure enables the communication system S1 to provide a local application with a computing capability.

[0164] Further, although details will be described later, the communication system S1 provides an owner of a car and a driver with information for operating the VaaNI terminal 30 as a communication infrastructure. Thus, the communication system S1 enables to perform a dynamic network deployment that satisfies a request from a telecommunication carrier and satisfies a request from an owner of a car.

[0165] <3.1. First Embodiment>

[0166] <3.1.1. Outline of the First Embodiment>

[0167] Here, execution of the operation of determining a VaaNI service by an operator, in other words, an instruction from the application server 10 for implementing a VaaNI service will be described.

[0168] As described above, the VaaNI terminal 30 provides a second wireless access link (an example of a wireless access link) with an end user terminal 40 (an example of another wireless communication device) based on a wireless backhaul link (an example of a first wireless access link) with the base station 20.

[0169] The VaaNI terminal 30 includes one or a plurality of signal processing units 31 (examples of a network interface). In addition, the VaaNI terminal 30 includes an input / output unit 34 (an example of a user interface).

[0170] The control unit 33 (an example of a processor) of the VaaNI terminal 30 transmits a registration request or a start request related to the provision of the wireless access link to the application server 10 that manages the provision of the wireless access link via the signal processing unit 31.

[0171] The control unit 33 of the VaaNI terminal 30 starts the provision of the wireless access link according to the instruction from the application server 10.

[0172] This configuration enables the VaaNI terminal 30 to provide a VaaNI service according to the instruction from the application server 10, and the communication system S1 can deploy a communication infrastructure at a low cost.

[0173] <3.1.2. Operation Execution Process>

[0174] In the communication system S1, operation execution processing is executed to provide the VaaNI service. The operation execution processing includes service registration processing, service standby processing, and service implementation processing.

[0175] The service registration processing is processing in which the VaaNI terminal 30 performs service registration to provide the VaaNI service. The service standby processing is processing in which the VaaNI terminal 30 prepares for provision of the VaaNI service. The service implementation processing is processing in which the VaaNI terminal 30 starts to provide the VaaNI service.

[0176] (Service registration processing)

[0177] Figure 9 is a sequence chart illustrating an exemplary procedure of the service registration processing according to the first embodiment of the present disclosure. Figure 9 The service registration processing of is executed between the VaaNI terminal 30 and the application server 10. For example, when the VaaNI terminal 30 is registered as a VaaNI service provision node, for example, when an operator and an owner conclude a contract for provision of the VaaNI service, the service registration processing can be executed.

[0178] As shown in Figure 9 , the VaaNI terminal 30 transmits a registration request to the application server 10 (step S101). The registration request can include, for example, at least one of identification information of an owner or a driver and identification information (vehicle ID) of a car (VaaNI terminal 30). In addition, the registration request can include, for example, at least one of communication capability information and computation (processing) capability information about the VaaNI terminal 30.

[0179] The application server 10 registers information about the VaaNI terminal 30 that has transmitted the registration request in a vehicle database (DB) (step S102). For example, the application server 10 registers information about the VaaNI terminal 30 in the vehicle DB based on the registration request.

[0180] Thereafter, the application server 10 transmits a registration completion notification to the VaaNI terminal 30 (step S103).

[0181] Figure 10 is a table illustrating an example of the vehicle DB according to the first embodiment of the present disclosure. The vehicle DB is provided in, for example, the storage unit 12 of the application server 10. Alternatively, for example, a database device on a data network can include the vehicle DB.

[0182] As shown in Figure 10 , the vehicle DB stores the vehicle ID, the communication capability, and the processing capability in association with each other. The vehicle ID is identification information of a car (VaaNI terminal 30) included in the registration request. In Figure 10In the example, the vehicle database stores "V1" as the vehicle ID.

[0183] Communication capabilities include, for example, information about the wireless access links that can be provided by the VaaNI terminal 30. Communication capabilities include, for example, the presence or absence of relay functionality, antenna gain information, corresponding frequency (band), modem information, etc. Figure 10 In the example, the vehicle database stores "CC1" as the communication capability of the vehicle ID "V1".

[0184] Processing capacity includes, for example, information about the computing resources that can be provided by the VaaNI terminal 30. Processing capacity includes, for example, information such as computing power (Flops (floats per second)) and processing latency. Figure 10 In the example, the vehicle DB stores "CP1" as the processing capability of the vehicle ID "V1".

[0185] When the VaaNI terminal 30 does not provide computing resources, the processing capacity space of the vehicle database can be left empty. Alternatively, the processing capacity of the vehicle database can store data for which no resources are provided, and can store "empty".

[0186] Notice, Figure 10 The vehicle database shown is merely an example, and the information stored in the vehicle database is not limited to... Figure 9 For example, a vehicle database could store information about contracts (e.g., the type of contract) or information about incentives (e.g., the type of incentive, the payment method, etc.).

[0187] In addition, Figure 11 In the service registration process shown above, VaaNI terminal 30 has sent a registration request, but the device sending the registration request is not limited to VaaNI terminal 30. For example, an information processing device used by the vehicle owner (e.g., a smartphone, PC, tablet, etc.) can send the registration request. Alternatively, the operator's information processing device can send the registration request to application server 10.

[0188] (Service in standby mode)

[0189] Figure 11 This is a sequence diagram illustrating an exemplary process for service standby processing according to a first embodiment of the present disclosure. Figure 11 The service standby process is executed between VaaNI terminal 30 and application server 10.

[0190] For example, when VaaNI terminal 30 determines that it will begin operating as a VaaNI service providing node, service standby processing is performed. For example, service standby processing can be performed based on the activation of the vehicle driver's application in VaaNI terminal 30.

[0191] As Figure 12 shown in FIG. 8, the VaaNI terminal 30 sends a start request to the application server 10 (step S201). The start request can include, for example, at least one of identification information of a car owner or a driver and identification information (vehicle ID) of the car (VaaNI terminal 30). In addition, the start request can include, for example, at least one of position information indicating a current position of the VaaNI terminal 30, a state of the VaaNI terminal 30 (for example, whether the vehicle is moving or parked, and the like), and a charging state. Note that details of the information included in the start request will be described later.

[0192] The application server 10 registers information on the VaaNI terminal 30 that has sent the start request in a state management database (DB) (step S202). The application server 10 registers information on the VaaNI terminal 30 in the state management DB based on, for example, the start request.

[0193] Thereafter, the application server 10 sends an acceptance to the VaaNI terminal 30 (step S203). The VaaNI terminal 30 that has received the acceptance shifts to standby (step S204), and waits for an instruction for starting the VaaNI service.

[0194] Figure 12 is a table showing an example of the state management DB according to the first embodiment of the present disclosure. The state management DB is provided, for example, in the storage unit 12 of the application server 10. Alternatively, for example, a database device on a data network can include the state management DB.

[0195] As Figure 12 shown in FIG. 8, the state management DB stores the vehicle ID, the current position, the state, and the charging state in association with each other. The vehicle ID is identification information of the car (VaaNI terminal 30) included in the registration request. The current position is information indicating a current position of the car (VaaNI terminal 30).

[0196] The state is information indicating a current state of the car. In the example of Figure 12 , the state is information indicating whether the vehicle is moving or parked. The charging state is information indicating a charging state of the car. The charging state is information indicating a percentage of the current charge to the full charge or indicating that the battery is charging.

[0197] In the example of Figure 12 , the VaaNI terminal 30 having the vehicle ID "V1" indicates the current position "place A", the state "moving", and the charging state "50%". In addition, the VaaNI terminal 30 having the vehicle ID "V2" indicates the current position "parking lot B", the state "parked", and the charging state "charging".

[0198] Note that, Figure 12 The state management DB shown in FIG. 6 is merely an example, and information stored in the state management DB is not limited to Figure 9 the example. The state management DB can store, for example, a prearranged parking time or the like. The state management DB can store, for example, information included in the start request described later.

[0199] Further, the state management DB can be updated in accordance with information from the VaaNI terminal 30. For example, the state management DB can be updated at a constant period. In other words, the VaaNI terminal 30 can notify the application server 10 of information about itself (state information for updating the state management DB) at a constant period.

[0200] Alternatively, the state management DB can be updated when the VaaNI terminal 30 has moved a certain distance or a greater distance. In this configuration, the VaaNI terminal 30 can notify the application server 10 of the state information when the moving distance becomes a certain distance or a greater distance.

[0201] Further, the state management DB can be updated when the state of the VaaNI terminal 30 changes, for example, when the state of the VaaNI terminal 30 changes from moving to parking. In this configuration, the VaaNI terminal 30 can notify the application server 10 of the state information, for example, based on the stop / start of the engine of the car, when the change in the state is detected.

[0202] Further, the state management DB can be updated when the charging state of the VaaNI terminal 30 changes, for example, when charging of the VaaNI terminal 30 starts or the charging percentage of the VaaNI terminal 30 exceeds a predetermined value. In this configuration, the VaaNI terminal 30 can notify the application server 10 of the state information when the start of charging is detected or when the charging percentage exceeds the predetermined value.

[0203] Note that the conditions for updating the state management DB are not limited to the above examples. The state management DB can be updated when there is a change in the state information described later.

[0204] Further, the notification of the state information can be performed by the VaaNI terminal 30 autonomously or can be performed in response to a request from the application server 10. Further, for the notification service of the state information via the service-based interface, the notification of the state information can be performed by request / response or by subscription / notification.

[0205] In addition, here, the service registration processing and the service standby processing are performed at different timings in the communication system S1, but the service registration processing and the service standby processing can be performed at the same timing. In this configuration, the service registration processing and the service standby processing can be executed as one processing. For example, the VaaNI terminal 30 can collect the registration request transmitted in step S101 of Figure 11 and the start request transmitted in step S201 of Figure 13 as one request to transmit.

[0206] In addition, here, the vehicle DB and the state management DB have been configured as different DBs, but the vehicle DB and the state management DB can be combined as one DB.

[0207] (Service implementation processing)

[0208] Figure 13 is a sequence diagram showing an exemplary procedure of the service implementation processing according to the first embodiment of the present disclosure. Figure 13 The service implementation processing of

[0209] As shown in Figure 14 , the application server 10 receives a service start request for requesting the start of the VaaNI service from the end user terminal 40 (step S301). The service start request can include information about the end user (end user information). For example, the service start request can include location information of the end user terminal 40, a service provision time requested by the end user terminal 40, and a need for provision of computing resources.

[0210] The application server 10 that has received the service start request selects the VaaNI terminal 30 that provides the VaaNI service (step S302). The application server 10 selects the VaaNI terminal 30 based on, for example, static / quasi-static VaaNI information. The static / quasi-static VaaNI information includes, for example, information stored in the vehicle DB and the state management DB. The static / quasi-static VaaNI information will be described in detail below.

[0211] The application server 10 determines the service provision using the selected VaaNI terminal 30 (step S303). As described above, in the present embodiment, the application server 10 on the operation side determines the start of the VaaNI service (execution of the operation).

[0212] The application server 10 notifies the VaaNI terminal 30 of the start of the service (step S304).

[0213] Upon receiving the notification, the VaaNI terminal 30 starts the VaaNI service for the end user terminal 40 (step S305). For example, upon receiving the notification of the start of the service, the VaaNI terminal 30 transmits a discovery signal to the surrounding environment. The end user terminal 40 that has received the discovery signal notifies the VaaNI terminal 30 of a call-on request. Thus, the VaaNI terminal 30 operates as a cell (base station or relay station) and starts to provide the VaaNI service.

[0214] As for the end of the VaaNI service, the application server 10 notifies the VaaNI terminal 30 of the end of the VaaNI service (step S306). Thus, the VaaNI terminal 30 ends the provision of the VaaNI service.

[0215] Note that, for example, the application server 10 can determine the end of the VaaNI service when the scheduled service provision time has passed, or in response to a request from the VaaNI terminal 30, or the like.

[0216] Further, although the application server 10 determines the end of the VaaNI service here, the VaaNI terminal 30 can determine the end of the VaaNI service.

[0217] <3.1.3. Implementation Condition>

[0218] (Start Condition)

[0219] In the above service implementation process, the application server 10 determines the start of the VaaNI service in response to a request from the end user terminal 40, but the condition under which the application server 10 determines the start of the VaaNI service is not limited to this. Hereinafter, an example of the condition (start condition) under which the application server 10 determines the implementation of the VaaNI service will be described. For example, when at least one of the following start conditions is satisfied, the application server 10 activates the VaaNI terminal 30 to operate as a communication infrastructure (base station).

[0220] • The VaaNI terminal 30 is in an operation available area designated by an operator.

[0221] • The VaaNI terminal 30 is in a preset area.

[0222] • The number of end users that make requests is equal to or greater than a preset number of end users.

[0223] • The number of calculation processing requests that are made is equal to or greater than a preset number of calculation processing requests.

[0224] • A reward equal to or greater than a previously set reward is promised.

[0225] • The preset backhaul quality can be satisfied.

[0226] For example, the application server 10 determines implementation of the VaaNI service when the VaaNI terminal 30 is in an operation available area designated by an operator. The application server 10 can automatically activate the VaaNI terminal 30 when detecting that the VaaNI terminal 30 moves into the operation available area.

[0227] The operation available area designated by the operator is, for example, an operation available area of the VaaNI service. The operation available area is, for example, an area in which the base station 20 has poor communication quality (equal to or less than a predetermined threshold value). The operator determines the operation available area by using, for example, a minimization of drive test (MDT) function.

[0228] For example, the application server 10 refers to the state management DB to select the VaaNI terminal 30 located in the operation available area as a device that provides the VaaNI service.

[0229] Note that the area for determining implementation of the VaaNI service by the application server 10 is not limited to the operation available area designated by the operator, and can be, for example, a preset area. For example, the area in which the service is provided can be preset according to a request from an end user.

[0230] The application server 10 can also make a determination of implementation of the VaaNI service in a preset area, as in the operation available area designated by the operator.

[0231] In addition, the application server 10 activates the VaaNI function of the VaaNI terminal 30 when a connection request is issued to the network from a number of terminal users equal to or greater than a preset number of end users. The connection request is, for example, a VaaNI service start request.

[0232] In this case, each end user terminal 40 notifies the base station 20 of the connection request. At this time, the end user terminal 40 can give a notification of the connection request including location information of the end user terminal 40.

[0233] The base station 20 determines whether to deploy other base stations 20 (or relay stations) to a target area using at least one of the location of the end user and the number of connection requests. When it is determined that other base stations 20 are to be deployed, the base station 20 requests the application server 10 to add a vehicle-mounted base station as an other base station in the identified area.

[0234] The application server 10 selects the VaaNI terminal 30 located in the identified area, and determines to perform an operation using the selected VaaNI terminal 30. The application server 10 activates the selected VaaNI terminal 30, and starts the VaaNI service.

[0235] Note that here, the base station 20 requests the start of the VaaNI service according to the number of end users, but the base station 20 can request the start of the service according to a condition other than the number of end users.

[0236] For example, when an incoming / outgoing call rate decreases to or below a predetermined threshold, the base station 20 requests the start of the VaaNI service in an area including the base station 20. Alternatively, when congestion occurs or when admission control is performed, the base station 20 requests the start of the VaaNI service in an area including the base station 20. When a guaranteed flow bit rate (GFBR) cannot be satisfied, the base station 20 requests the start of the VaaNI service in an area including the base station 20.

[0237] In addition, although the base station 20 requests the start of the service here, a device other than the base station 20 can request the start of the service. For example, an NF or an AF of the core network CN can request the application server 10 to start the VaaNI service. In this case, the NF or the AF of the core network CN requests the start of the VaaNI service based on information acquired from the base station 20. Alternatively, the application server 10 can determine the start of the VaaNI service directly based on information acquired from the base station 20.

[0238] In addition, the application server 10 determines the start of the VaaNI service when the number of issued computation processing requests is equal to or greater than a predetermined number of computation processing requests.

[0239] The computation processing request is a request for operating the VaaNI terminal 30 as an edge computing server. The request can include request information indicating at least one of a required computation capacity and a required latency. The application server 10 notifies the VaaNI terminal 30 of the start of the VaaNI service and the request information.

[0240] Alternatively, the request information can be directly transmitted to the VaaNI terminal 30. In this configuration, the computation processing request is transmitted to the application server 10, and the request information is transmitted to the VaaNI terminal 30.

[0241] When the VaaNI terminal 30 operates as an edge computing server, the SMF of the core network CN establishes a session (e.g., a protocol data unit (PDU) session) in response to a session establishment request from the end user terminal 40, the session including a connection using local break out to the edge application server of the VaaNI terminal 30. The session is, for example, a session obtained by adding a connection using local break out to the edge application server to a session established with a DN of the core network CN, the DN corresponding to a DNN included in the session establishment request.

[0242] In the edge computing server, a UPF supporting an UL uplink classifier (CL) / branch point (BP) function and a PDU session anchor (PSA) UPF serving as a local break out destination anchor point are set, and are connected to the edge application server, as with the local UPF described above. The functions of the UPF include, for example, virtualization and containers, and are implemented in the edge computing server.

[0243] The SMF sets a forwarding destination of each QoS flow to the UPF supporting the UL CL / BP function, so that each QoS flow handled by the application server 10 or the edge application server is forwarded to the correct forwarding destination.

[0244] When the session establishment request from the end user terminal 40 is a session establishment request to handle a specific QoS flow, the SMF establishes a session including a connection using local break out to the edge application server. Examples of the specific QoS flow include a QoS flow having a 5G QoS identifier (5QI) with a resource type of delay critical GBR and / or a predetermined packet delay budget (PDB). In the established session, the specific QoS flow is transmitted and received between the end user terminal 40 and the edge application server.

[0245] In a session establishment request to handle other QoS flows, the SMF can establish a session with a DN of the core network CN via a wireless backhaul link with the base station 20.

[0246] In addition, the application server 10 determines the start of the VaaNI service when an incentive greater than a previously set incentive is promising. For example, the car owner sets a desired incentive in advance. The setting of the incentive can be performed by input to the input / output unit 34 provided in the vehicle (VaaNI terminal 30). In this case, the setting information (previously desired incentive) input to the input / output unit 34 can be provided to the application server 10 via the signal processing unit 31 or the like. The desired incentive is managed, for example, by a state management DB.

[0247] When it is promising that the incentive exceeds the expected incentive, the application server 10 determines the start of the VaaNI service of the VaaNI terminal 30 owned by the vehicle owner. Note that the application server 10 calculates the assumed incentive according to, for example, the assumed VaaNI service provision time.

[0248] In addition, when it is possible to satisfy the preset backhaul quality, the application server 10 determines the start of the VaaNI service. Examples of the backhaul quality include a reference signal received power (RSRP) and a reference signal received quality (RSRQ).

[0249] The backhaul quality changes, for example, according to the positional relationship between the VaaNI terminal 30 and the base station 20. For example, when the base station 20 is a satellite station 20A, the backhaul quality can also change according to the orbit of the satellite station 20A.

[0250] In the operation using low earth orbit (LEO) satellite communication and a vehicle base station (VaaNI terminal 30), the application server 10 can perform the operation using the orbit information of the satellite station 20A. For example, the application server 10 acquires the orbit information of the satellite station 20A, and activates the VaaNI terminal 30 located below the orbit of the satellite station 20A. Alternatively, the application server 10 can notify the satellite station 20A of the moving (driving) route of the VaaNI terminal 30 to change the route of the satellite station 20A. Alternatively, the application server 10 can give an instruction to the satellite station having the route above the vehicle base station (VaaNI terminal 30) to perform a handover connection using the route notification.

[0251] (End condition)

[0252] In the above service implementation processing, the application server 10 determines the end of the VaaNI service. Hereinafter, an example of the condition (end condition) in which the application server 10 determines the end of the VaaNI service will be described. For example, when at least one of the following end conditions is satisfied, the application server 10 deactivates the VaaNI terminal 30 operating as a communication infrastructure (base station).

[0253] • The connection of the end user terminal 40 cannot be confirmed for a certain period of time or longer.

[0254] • The preset service provision time has elapsed.

[0255] • The VaaNI terminal 30 has moved out of the preset area.

[0256] • The calculation processing is not performed for a certain period of time or longer.

[0257] • The preset backhaul quality cannot be satisfied.

[0258] When the end condition is satisfied, the application server 10 notifies the VaaNI terminal 30 of the end of the VaaNI service. Alternatively, the application server 10 can determine the end of the VaaNI service in response to a request from the VaaNI terminal 30.

[0259] <3.1.4. Examples of Static / Quasi-static VaaNI Information>

[0260] Next, examples of static / quasi-static VaaNI information will be described. Static / quasi-static VaaNI information includes, for example, information included in the registration request and the start request. Static / quasi-static VaaNI information includes, for example, state information. Static / quasi-static VaaNI information includes, for example, information acquired by the application server 10 for updating the state management DB. Static / quasi-static VaaNI information includes, for example, at least one of the following information.

[0261] • Identification information of the owner or the driver

[0262] • Identification information of the VaaNI terminal 30 (for example, vehicle ID)

[0263] • Permission performed by the owner on the VaaNI service

[0264] • Incentive value required by the owner (desired incentive)

[0265] • Presence or absence of registration in the infrastructure sharing service

[0266] • Amount of battery remaining in the automobile

[0267] • Position information of the automobile

[0268] • Prearranged travel route of the automobile

[0269] • Information on parking (stopping) of the automobile

[0270] • Retrieval result of the vehicle destination

[0271] • Communication quality of the backhaul

[0272] Note that here, it is assumed that the application server 10 directly notifies the VaaNI terminal 30 of the start of the service, in other words, the application server 10 activates the VaaNI terminal 30. However, the destination to which the application server 10 gives the notification of the start of the service is not limited to the VaaNI terminal 30.

[0273] For example, the application server 10 can notify the vehicle management company that manages the information processing device used by the owner and the VaaNI terminal 30 of the start of the service. In this case, the information processing device used by the owner or the vehicle management company notifies the VaaNI terminal 30 of the start of the service.

[0274] Note that when the VaaNI terminal 30 that has received the notification of the start of the service function functions as a gNB, the VaaNI terminal 30 transmits an NG setup request to an access and mobility management function (AMF) of the core network CN.

[0275] Note that here, it is assumed that the application server 10 activates the VaaNI terminal 30 based on the start condition. However, the VaaNI terminal 30 can be activated all the time regardless of the start condition, and the application server 10 can deactivate the VaaNI terminal 30 according to the end condition.

[0276] In this configuration, when at least one of the registration request and the start request is accepted, the VaaNI terminal 30 is activated to function as a communication infrastructure (base station) or a computing resource. In other words, the VaaNI terminal 30 is activated without shifting to the standby state.

[0277] According to an instruction from the application server 10, the VaaNI terminal 30 that is operating as a communication infrastructure (base station) or a computing resource is deactivated, and the operation as a communication infrastructure (base station) or a computing resource is completed.

[0278] When the VaaNI terminal 30 is operating as a communication infrastructure (base station) and a computing resource, the application server 10 can independently deactivate the communication infrastructure (base station) or the computing resource. For example, the application server 10 can deactivate only the operation of the computing resource of the VaaNI terminal 30 according to the end condition, to continue only the operation of the communication infrastructure (base station).

[0279] Further, here, at least a part of the information (end user information, state information, and the like) that the application server 10 acquires from the end user terminal 40 and the VaaNI terminal 30 can be acquired from, for example, the core network CN.

[0280] <3.1.5. Modification>

[0281] Here, it is assumed that the application server 10 is on the operator side, and the start of the VaaNI service is determined by the application server 10 on the operator side. In this configuration, the application server 10 can be a node (for example, an AF node) of the core network CN, or can be a node deployed in an external network as described above.

[0282] Alternatively, the application server 10 can be a device managed by a third party different from the operator. In this case, for example, the core network CN on the operator side can select the VaaNI terminal 30 to be operated as a communication infrastructure (base station).

[0283] Figure 14is a sequence chart showing another exemplary process of service implementation processing according to the first embodiment of the present disclosure. Figure 15 The service implementation processing shown in FIG. 6 is executed among the end user terminal 40, the VaaNI terminal 30, the application server 10, and the core network CN.

[0284] First, the core network CN transmits a request (candidate request) for candidates of the VaaNI terminal 30 to be operated as a communication infrastructure (base station) to the application server 10 (step S401). The candidate request can include, for example, a service provision area, a service provision time, information on requested computing resources, and the like.

[0285] The application server 10 notifies the core network CN of the VaaNI terminal 30 as a candidate (step S402). For example, the application server 10 searches for the VaaNI terminal 30 satisfying the conditions included in the candidate request in the state management DB, and notifies the core network CN of the search result as a candidate.

[0286] The core network CN selects the VaaNI terminal 30 to be operated as a communication infrastructure (base station) from the candidates (step S403), and notifies the application server 10 of the selected VaaNI terminal 30 (selected terminal) (step S404).

[0287] The application server 10 determines to provide the VaaNI service using the selected terminal (step S405), and notifies the VaaNI terminal 30 of the start of the VaaNI service (step S406). Upon receiving the notification, the VaaNI terminal 30 starts the VaaNI service for the end user terminal 40 (step S407).

[0288] For example, when an end condition of the VaaNI service is satisfied, the core network CN requests the application server 10 to end the service (step S408). In response thereto, the application server 10 notifies the VaaNI terminal 30 of the end of the service (step S409).

[0289] Note that, although the application server 10 determines to provide (start) the VaaNI service here, the core network CN can determine to provide (start) the VaaNI service. In this configuration, the core network CN determines to start the VaaNI service using the selected terminal. The core network CN can give a notification of the start of the service via the application server 10, or can directly notify the VaaNI terminal 30 of the start of the service.

[0290] <3.2. Second Embodiment>

[0291] <3.2.1. Outline of Second Embodiment>

[0292] Here, the execution of the operation of determining the VaaNI service by the vehicle owner or the driver, in other words, the instruction from the VaaNI terminal 30 for implementing the VaaNI service will be described.

[0293] Depending on where or when the VaaNI terminal 30 is operated, in other words, depending on where or when the VaaNI terminal 30 provides the VaaNI service, the number of the accommodated end user terminals 40 and the incentive that the vehicle owner can receive are expected to greatly vary.

[0294] Meanwhile, the vehicle owner or the driver does not know how to determine where or when to execute the operation (determination of the implementation of the VaaNI service).

[0295] Therefore, in the present embodiment, the VaaNI terminal 30 presents to the vehicle owner or the driver (an example of the user) based on the information from the application server 10. The presentation is performed by the input / output unit 34 provided in (or externally mounted to) the VaaNI terminal 30. This configuration allows the vehicle owner or the driver to determine where and when to implement the VaaNI service, and the VaaNI service can be provided by using the VaaNI terminal 30.

[0296] Specifically, as described above, the VaaNI terminal 30 provides the second wireless access link (an example of a wireless access link) with the end user terminal 40 (an example of other wireless communication devices) based on the wireless backhaul link (an example of a first wireless access link) with the base station 20.

[0297] The VaaNI terminal 30 includes one or a plurality of signal processing units 31 (an example of a network interface). In addition, the VaaNI terminal 30 includes an input / output unit 34 (an example of a user interface).

[0298] The control unit 33 (an example of a processor) of the VaaNI terminal 30 transmits a registration request or a start request related to the provision of the wireless access link to the application server 10 that manages the provision of the wireless access link via the signal processing unit 31.

[0299] The control unit 33 of the VaaNI terminal 30 receives a notification related to the provision of the wireless access link from the application server 10, and outputs at least a part of the received notification to the input / output unit 34.

[0300] This configuration enables the VaaNI terminal 30 to provide the VaaNI service based on the notification from the application server 10, and the communication system S1 can deploy the communication infrastructure at a low cost.

[0301] <3.2.2. Operation execution processing>

[0302] In the communication system S1, operation execution processing is executed to provide the VaaNI service. The operation execution processing includes service registration processing, service standby processing, and service implementation processing.

[0303] Note that the service registration processing and the service standby processing are the same as those in the first embodiment, and the description thereof will not be repeated.

[0304] (Service implementation processing)

[0305] Figure 15 is a sequence chart showing an exemplary procedure of the service implementation processing according to the second embodiment of the present disclosure. Figure 13 The service implementation processing of is executed between the end user terminal 40, the VaaNI terminal 30, and the application server 10. For example, the service execution processing can be executed when the VaaNI service starts. Note that the processing steps in the service implementation processing shown in are the same as those in the service implementation processing in the first embodiment, and the description thereof will not be repeated. Figure 13 The processing steps in the service implementation processing shown in are the same as those in the service implementation processing in the first embodiment, and the description thereof will not be repeated.

[0306] The application server 10 that has received the service start request selects the VaaNI terminal 30 that satisfies the condition (step S501). The application server 10 selects the VaaNI terminal 30, for example, in accordance with the information included in the service start request and / or the start condition.

[0307] The application server 10 makes an inquiry (recommendation notification) to the selected VaaNI terminal 30 (step S502).

[0308] The VaaNI terminal 30 determines the service provision in accordance with the instruction from the car owner or the driver (the instruction from the car owner or the driver input to the input / output unit 34) (step S503), and transmits the acceptance to the application server 10 (step S504). Note that the subsequent processing steps are the same as those in the service implementation processing in Figure 16

[0309] <3.2.3. Example of recommendation notification>

[0310] As described above, the VaaNI terminal 30 determines the start of the VaaNI service in accordance with the instruction from the car owner or the driver. At this time, the VaaNI terminal 30 outputs at least a part of the information (recommendation notification) acquired from the application server 10 to the input / output unit 34 so as to present the presentation screen to the car owner or the driver.

[0311] Figure 16 is a diagram showing an example of the presentation screen according to the second embodiment of the present disclosure. Figure 16 The presentation screen shown in is displayed on the display provided in the input / output unit 34. Figure 16 ​The presentation screen shown in FIG. 6 includes, for example, map information and information about the VaaNI service. The map information includes, for example, information about the current position of the VaaNI terminal 30 and a provision site that provides the VaaNI service.

[0312] The information about the VaaNI service includes information about the provision site and provision information. The information about the provision site includes, for example, at least one of the following: detailed information (facility name, address, and the like) of the provision site that provides the VaaNI service, presence or absence of a parking lot, presence or absence of a charging station, and the like. The provision information includes, for example, at least one of the following: assumed service provision time, assumed battery consumption amount, assumed payment (incentive), and the like.

[0313] In addition, the presentation screen includes buttons (acceptance and rejection buttons) in Figure 16 to select whether to accept the proposal of the VaaNI service, in other words, whether to start the VaaNI service.

[0314] The VaaNI terminal 30 displays the presentation screen on a display (for example, a car navigation display) provided in the input / output unit 34 to present the recommendation notification to the car owner or the driver. Furthermore, the VaaNI terminal 30 can present the recommendation notification to the car owner or the driver by voice.

[0315] Note that, Figure 16 The presentation screen of FIG. 6 is merely an example, and the presentation screen can include information other than the information shown in Figure 17 For example, the presentation screen can include information about the VaaNI terminal 30. The information about the VaaNI terminal 30 can include, for example, a battery remaining amount and a battery consumption prediction value in the VaaNI terminal 30. For example, the battery consumption prediction value can include information indicating how the battery remaining amount will be when the VaaNI terminal 30 operates as a communication infrastructure (base station).

[0316] Note that the information about the VaaNI terminal 30 is not information including a notification from the application server 10, but information acquired by the VaaNI terminal 30 itself. As described above, the information presented to the car owner or the driver can include information acquired from the application server 10 and information acquired from the VaaNI terminal 30. The information acquired from the VaaNI terminal 30 can include information about the state of the VaaNI terminal 30 (car) and information about the state of a function (communication device) for wireless communication of the VaaNI terminal 30.

[0317] For example, the presentation screen can include the number of expected end user terminals 40, the amount of required computation tasks (processing), the amount of required traffic, and the like.

[0318] Further, for example, the presentation screen can include a desired time period (e.g., between 8:00 and 10:00) in which it is desired to operate as a communication infrastructure (base station).

[0319] The application server 10 can suggest (recommend) to the VaaNI terminal 30 (i.e., instruct the display provided in the input / output unit 34 to display) a parking lot that is most effective (e.g., has the largest number of accommodated end user terminals 40 or has the highest motivation) in a region around the VaaNI terminal 30.

[0320] Further, the VaaNI terminal 30 can present a display screen to the car owner or driver as auxiliary information for selecting a destination. In this configuration, the VaaNI terminal 30 presents the display screen as part of car navigation information to the car owner or driver via the display provided in the input / output unit 34.

[0321] For example, when the car owner or driver searches for a restaurant as a destination, the VaaNI terminal 30 can display presentation information on the display provided in the input / output unit 34 in association with the restaurant information.

[0322] As described above, operating the VaaNI terminal 30 as a communication infrastructure (e.g., base station) reduces the battery, which can affect the normal function (e.g., driving) of the VaaNI terminal 30. Therefore, the VaaNI terminal 30 needs to operate as a communication infrastructure within a range that does not affect the normal function.

[0323] Therefore, for example, a lower limit of the battery is set for the VaaNI terminal 30, and when the battery remaining amount is equal to or less than the lower limit (or the battery remaining amount is predicted to be equal to or less than the lower limit), the VaaNI terminal 30 is prevented from operating as a communication infrastructure. The lower limit can be a preset fixed value or a dynamically changing value. When the lower limit dynamically changes, the VaaNI terminal 30 can predict the battery consumption based on, for example, driving route information or destination information to determine the lower limit according to the prediction result.

[0324] When the operation as a communication infrastructure can reduce the battery remaining amount to the lower limit or less, the VaaNI terminal 30 can give attention to the car owner or driver via the display provided in the input / output unit 34, such as displaying a warning message indicating the reduction of the battery remaining amount.

[0325] Here, giving attention may be, for example, presenting the vehicle owner or driver with the possibility that the operation of the communication infrastructure may prevent the vehicle from reaching a pre-designated destination, or that battery charging may be required on the way. In this case, the VaaNI terminal 30 can present the vehicle owner or driver with information about candidate locations of charging stations that allow battery charging to be performed while attention is being given, via a display provided in the input / output unit 34.

[0326] Note that, attached to or replacing the option to start VaaNI service at the current time, vehicle owners or drivers can determine whether to start VaaNI service in the future. In other words, vehicle owners or drivers can make an appointment for VaaNI terminal 30 to function as a future communication infrastructure (base station).

[0327] For example, application server 10 queries whether VaaNI terminal 30 will operate as communication infrastructure (base station) for three to six hours starting from the current time. VaaNI terminal 30 determines the future operation of the communication infrastructure (base station) based on instructions from the vehicle owner or driver. In this way, communication system S1 can have a reservation function for operating VaaNI terminal 30 as communication infrastructure (base station) at a future time. If VaaNI terminal 30 cannot operate as communication infrastructure (base station) at the reserved time, VaaNI terminal 30 notifies application server 10 that VaaNI terminal is unavailable.

[0328] Furthermore, here, the vehicle owner or driver determines whether to activate the VaaNI service in response to a recommendation notification. However, for example, the VaaNI terminal 30 may determine whether to activate the service after the vehicle owner or driver has pre-set operating conditions for operating the VaaNI terminal 30 as a base station (communication infrastructure).

[0329] For example, the vehicle owner or driver pre-determines the time period, remaining battery level, and area as operating conditions. The VaaNI terminal 30 determines whether to start the VaaNI service based on the information and operating conditions included in the query from the application server 10. These operating conditions may be the same as or different from the start conditions described above.

[0330] Additionally, the VaaNI terminal 30 presents at least a portion of the notifications from the application server 10 to the vehicle owner or driver via a display provided in the input / output unit 34. However, the information presented to the vehicle owner or driver is not limited to the notifications from the application server 10. Attached to or replacing the information obtained from the application server 10, the VaaNI terminal 30 may present information about itself to the vehicle owner or driver via the display provided in the input / output unit 34.

[0331] In addition, the number of terminals of the VaaNI terminals 30 selected by the application server 10 to satisfy the condition is not limited to one. The application server 10 can select a plurality of VaaNI terminals 30. In this case, the application server 10 can transmit the inquiry to the plurality of VaaNI terminals 30 that have been selected. The application server 10 selects the VaaNI terminal 30 that actually operates as a communication infrastructure (base station) from the plurality of VaaNI terminals 30 using, for example, an auction method.

[0332] Specifically, for example, the application server 10 presents to the plurality of VaaNI terminals 30 a candidate place (area) in which the plurality of VaaNI terminals 30 operate as a communication infrastructure (for example, a base station) and the received incentive (upper limit). The presentation is performed by displaying on a display provided in the input / output unit 34 by each VaaNI terminal 30 that has received the instruction from the application server 10.

[0333] The VaaNI terminal 30 notifies the application server 10 of, for example, an area in which the VaaNI terminal 30 can operate as a communication infrastructure (base station) and a desired incentive payment. Here, the desired incentive payment can be selected from several options presented from the application server 10. Alternatively, the car owner or the driver can input the desired incentive payment by himself / herself. The selection or input can be an input from the car owner or the driver through a user interface (for example, a touch screen display) provided in the input / output unit 34.

[0334] The application server 10 determines the VaaNI terminal 30 to be operated as a communication infrastructure (base station) from among the VaaNI terminals 30 that have returned the response on the incentive payment and the like. When the response has been returned from a plurality of VaaNI terminals 30, the application server 10 can determine the VaaNI terminal 30 in the order of arrival of the response, or can determine the VaaNI terminal 30 in ascending order of the desired incentive payment.

[0335] When there is no response from the VaaNI terminal 30, the application server 10 can, for example, increase the incentive payment and again inquire the VaaNI terminal 30.

[0336] Note that the application server 10 can make an inquiry to the plurality of VaaNI terminals 30 on information other than the area and the incentive payment (for example, information included in the presentation screen and the like). Furthermore, in addition to or instead of the response order and the desired incentive payment order, the application server 10 can determine the VaaNI terminal 30 to be operated as a communication infrastructure by using information on the car or information on the car owner or the driver.

[0337] <3.2.4. Exemplary operations>

[0338] Here, exemplary operations performed when the driver actually determines to perform the operation will be described.

[0339] First, the VaaNI provider (the car owner or the driver) pre-registers the car operable as a communication infrastructure (base station) to the operator (application server 10) on the application layer. At this time, the VaaNI provider notifies the application server 10 of the identification information of the car (VaaNI terminal 30), performance information about the communication device installed in the car (VaaNI terminal 30), performance information about the computing power, and the like. In addition, the VaaNI provider can notify the application server 10 of information about a period of time available for operation.

[0340] The application server 10 on the operator side, for example, monitors the communication network, and identifies a region in which the VaaNI terminal 30 is desired to be operated as a communication infrastructure (base station). The application server 10 transmits a request (recommendation notification) to a plurality of VaaNI terminals 30 located around the identified region and operable as a communication infrastructure (base station). The request can be presented to the VaaNI provider (car owner or driver) via the display as the input / output unit 34 provided in (or externally installed to) the VaaNI terminal 30. The request includes, for example, region information about the region in which operation is desired, information about the desired operation time, information about available incentives, the desired number of cars (number of VaaNI terminals 30), and the like.

[0341] The request from the application server 10 is notified to the VaaNI terminals 30 located around the region (place of service provision) identified by the application server 10. The VaaNI terminals 30 each display information about the given request notification on the car navigation display, that is, the input / output unit 34, for example, via the car application. In addition, the VaaNI terminal 30 can read out the information about the request as voice information.

[0342] The driver views the request displayed on the display, and determines to park the car in the desired region, and operate the vehicle as a communication infrastructure. The driver notifies the application server 10 of the approval (determination of the start of service provision) via the VaaNI terminal 30. More specifically, the driver inputs to the user interface (for example, a touch screen display) provided in the input / output unit 34. The input information is notified to the application server 10 via the signal processing unit 31 or the like.

[0343] Here, it is assumed that the application server 10 searches for the VaaNI terminal 30 operating as a communication infrastructure (e.g., a base station), for example, in the order of arrival of the responses. In addition, it is assumed that the number of VaaNI terminals 30 determined to be operating as a communication infrastructure has not reached the number of VaaNI terminals 30 specified by the application server 10 at the time of acceptance in response to the driver.

[0344] In this case, the acceptance of the driver is accepted by the application server 10, and the VaaNI terminal 30 driven by the driver is determined to be a VaaNI terminal 30 operating as a communication infrastructure (a base station).

[0345] Thereafter, the driver moves the VaaNI terminal 30 to the specified area (a place where the service is provided) and parks the car. After parking, the driver notifies the application server 10 that the VaaNI terminal 30 can operate as a communication infrastructure (a base station). More specifically, the driver inputs to a user interface (e.g., a touch screen display) provided in the input / output unit 34. The input information is notified to the application server 10 via the signal processing unit 31 or the like. The driver can then leave the VaaNI terminal 30.

[0346] The application server 10 notifies the VaaNI terminal 30 of the start of the service. When the application server 10 receives the notification of the start of the service, the VaaNI terminal 30 connects to the backhaul link, and performs a configuration for operating as a communication infrastructure (a base station).

[0347] The VaaNI terminal 30 starts providing a wireless access link, and provides wireless communication and computing capabilities to the surrounding end user terminals 40. After a specified time has elapsed, the VaaNI terminal 30 ends the provision of the VaaNI service, for example, according to an instruction from the application server 10.

[0348] For example, after several hours, when the driver who left the VaaNI terminal 30 returns, the VaaNI terminal 30 notifies the driver that the operation as a communication infrastructure (a base station) has been completed. At this time, the VaaNI terminal 30 can present information on the received incentives, the amount of battery consumed, and the like to the driver. For example, the driver accepts the reception of the incentives and resumes driving.

[0349] <3.2.5. Exemplary Application of Car Sharing>

[0350] In the above embodiments, it has been described that the end users (e.g., pedestrians, etc.) around the VaaNI terminal 30 receive the provision of the VaaNI service, but the end users riding on the VaaNI terminal 30 receive the provision of the VaaNI service. For example, in car sharing, the end users expect to obtain comfortable wireless communication and computing capabilities even in a car. Here, such end users are enabled to select the VaaNI terminal 30 that provides the VaaNI service.

[0351] For example, in selecting a vehicle as a car sharing candidate, the application server 10 also presents information on the VaaNI service to the end user.

[0352] Figure 17 is a diagram showing an example of a vehicle selection screen according to the second embodiment of the present disclosure. The presentation screen shown in Figure 17 is displayed on the display provided in the input / output unit 34. Figure 17 The vehicle selection screen shown in

[0353] When the VaaNI service is available, the vehicle information includes the available VaaNI service in addition to, for example, the arrival time and the payment of the vehicle. For example, Figure 18 It is shown that the VaaNI service is available in the car 4.

[0354] In addition to the available VaaNI service, the vehicle information can also include wireless communication capability information and computing capability information. For example, these capability information can be confirmed on the detailed screen of the car 4.

[0355] Further, on the vehicle selection screen, the plurality of vehicles to be selected can be filtered according to whether the VaaNI service is available, the capability, etc.

[0356] Further, although the recommendation notification is sent to the VaaNI terminal 30 that performs car sharing, the recommendation notification in this case includes information on a car sharing service provision route (e.g., the destination of the end user) rather than a service provision place. At least one of these information can be displayed on the display provided in the input / output unit 34.

[0357] Figure 18 is a diagram showing another example of a presentation screen according to the second embodiment of the present disclosure. Figure 18 The presentation screen shown in Figure 18 is displayed on the display provided in the input / output unit 34. is displayed on the display provided in the input / output unit 34.

[0358] The information about the VaaNI service includes, for example, information about a destination of the end user (a facility name, an address, etc.), a pickup location of the end user, a supposed service provision time, a supposed battery consumption amount, a supposed payment (incentive), and the like.

[0359] In addition, the presentation screen includes buttons (accept" and "reject" buttons in Figure 18 to select whether to accept the suggestion of the ride-sharing service and the VaaNI service.

[0360] The VaaNI terminal 30 displays the presentation screen on a display (for example, a car navigation display) as an input / output unit 34 to present the recommendation notification to the car owner or the driver. Furthermore, the VaaNI terminal 30 can present the recommendation notification to the car owner or the driver through a voice (a voice output from a speaker as the input / output unit 34).

[0361] Note that, Figure 18 The presentation screen of Figure 19 is merely one example, and the presentation screen can include information other than the information shown in

[0362] Furthermore, although an example in which the communication system S1 is applied to the ride-sharing service is described here, the communication system S1 can be applied to services other than ride-sharing. For example, the communication system S1 can be applied to a ride-hailing service, a rental car service, and the like.

[0363] <3.3. Third Embodiment>

[0364] <3.3.1. Outline of Third Embodiment>

[0365] Here, the execution of the operation of determining the VaaNI service by the end user will be described, in other words, the instruction from the end user terminal 40 for implementing the VaaNI service.

[0366] When the end user terminal 40 gives the instruction to implement the VaaNI service, there is a possibility that there is no car owner or driver in the VaaNI terminal 30 at the timing of the instruction to implement. In other words, the timing at which the car owner or driver arrives at the destination (a place where the service is provided) does not always coincide with the timing at which the end user desires to use the VaaNI service.

[0367] For example, assume that the car owner or driver parks the car (VaaNI terminal 30) in a parking lot and uses a facility located next to the parking lot. Assume that an end user needs a VaaNI service around the VaaNI terminal 30 parked in the parking lot while the car owner or driver uses the facility. However, the car owner or driver is not at the VaaNI terminal 30 when the VaaNI service is needed. Even in such a case, a mechanism is needed to enable the end user terminal 40 to receive the VaaNI service.

[0368] Thus, in the present embodiment, the end user terminal 40 requests the VaaNI terminal 30 to provide the VaaNI service based on the provision information related to the provision of the VaaNI service. Thus, the VaaNI terminal 30 starts to provide the VaaNI service to the end user terminal 40. Note that the provision information is, for example, a discovery signal transmitted by the VaaNI terminal 30 to the surrounding environment.

[0369] Specifically, as described above, the VaaNI terminal 30 provides a second wireless access link (an example of a wireless access link) with the end user terminal 40 (an example of another wireless communication device) based on a wireless backhaul link (an example of a first wireless access link) with the base station 20.

[0370] The VaaNI terminal 30 includes one or more signal processing units 31 (examples of network interfaces). In addition, the VaaNI terminal 30 includes an input / output unit 34 (an example of a user interface).

[0371] The control unit 33 (an example of a processor) of the VaaNI terminal 30 transmits a registration request or a start request related to the provision of the wireless access link to the application server 10 that manages the provision of the wireless access link via the signal processing unit 31.

[0372] The control unit 33 of the VaaNI terminal 30 starts the provision of the wireless access link in response to the request from the end user terminal 40.

[0373] For example, the control unit 33 transmits a discovery signal related to the provision of the wireless access link to the surrounding environment. The end user terminal 40 requests the provision of the wireless access link in response to the discovery signal.

[0374] Here, the VaaNI terminal 30 or the application server 10 can confirm the permission of the car owner or driver to the request from the end user terminal 40 to provide the VaaNI service. For example, when the request to provide the VaaNI service is received from the end user terminal 40, the VaaNI terminal 30 or the application server 10 gives a notification to a wireless communication device (for example, a smartphone) owned by the car owner or driver for requesting the permission of the request. Assume that the wireless communication device is, for example, registered in advance.

[0375] For example, upon confirming a notification from the VaaNI terminal 30 or the application server 10 that is displayed on an input / output unit of a wireless communication device possessed by the vehicle owner or the driver, the vehicle owner or the driver determines approval or rejection of a request for providing the VaaNI service via the input / output unit.

[0376] This configuration enables the VaaNI terminal 30 to provide the VaaNI service based on a notification from the application server 10, and the communication system S1 can deploy a communication infrastructure at low cost.

[0377] <3.3.2. Operation execution processing>

[0378] In the communication system S1, operation execution processing is executed to provide the VaaNI service. The operation execution processing includes service registration processing, service standby processing, and service implementation processing.

[0379] Note that the service registration processing and the service standby processing are the same as those in the first embodiment, and the description thereof will not be repeated.

[0380] (Service implementation processing)

[0381] Figure 19 is a sequence chart showing an exemplary procedure of the service implementation processing according to the third embodiment of the present disclosure. Figure 19 The service implementation processing of The service implementation processing is executed between the end user terminal 40, the VaaNI terminal 30, and the application server 10. For example, the service implementation processing can be executed when the VaaNI service starts.

[0382] As shown in ​ The VaaNI terminal 30 transmits a discovery signal to the surrounding environment (the end user terminal 40) (step S601). The discovery signal can include, for example, identification information of the VaaNI terminal 30, a supposed service provision time, information on available communication quality, information on available computing capability, and the like.

[0383] The end user terminal 40 that has received the discovery signal determines to provide the VaaNI service (step S602). For example, when it is desired to provide the VaaNI service, the end user terminal 40 determines to start the VaaNI service.

[0384] The end user terminal 40 transmits a service start request to the VaaNI terminal 30 (step S603). Thus, the end user terminal 40 activates a function of the VaaNI terminal 30 to operate as a base station (communication infrastructure).

[0385] The VaaNI terminal 30 notifies the end user terminal 40 of the start of the service (step S604). In addition, the VaaNI terminal 30 notifies the application server 10 of the start of the service (step S605).

[0386] The VaaNI terminal 30 starts the VaaNI service for the end user terminal 40 (step S606).

[0387] The VaaNI terminal 30 notifies the end user terminal 40 of the end of the service based on the elapse of the service provision time or the like (step S607). The VaaNI terminal 30 notifies the application server 10 of the end of the service (step S608).

[0388] Here, it should be noted that the VaaNI terminal 30 gives the notification of the end of the service, in other words, the VaaNI terminal 30 determines the end of the service, but the determination of the end of the service can be performed by a device other than the VaaNI terminal 30. For example, the end user terminal 40 can determine the end of the service, or the application server 10 can determine the end of the service.

[0389] In addition, when there is no connection (no use of the wireless access link) from the end user terminal 40 for a certain period of time, the VaaNI terminal 30 can end the VaaNI service. In this case, the VaaNI terminal 30 can not notify the end user terminal 40 of the end of the service.

[0390] The VaaNI terminal 30 notifies the application server 10 of the start and end of the service, and thus the application server 10 can know the provision of the VaaNI service. Therefore, the application server 10 can pay an incentive to the owner or the driver.

[0391] In addition, here, the VaaNI terminal 30 transmits the discovery signal as the provision information, but the provision information is not limited thereto. For example, the application server 10 can transmit the provision information to the end user terminal 40.

[0392] In this configuration, the application server 10 can notify the end user terminal 40 of information on the VaaNI terminal 30 capable of providing the VaaNI service as the provision information. The provision information can include, for example, identification information of the VaaNI terminal 30, a service provision area, a supposed service provision time, information on available communication quality, information on available computing capability, and the like.

[0393] <4. Other Embodiments>

[0394] The above-described embodiments are merely examples, and various modifications and applications are possible. For example, some or all of the above-described several embodiments can be implemented in combination with some or all of the other embodiments.

[0395] The control device that controls the application server 10, the base station 20, the VaaNI terminal 30, or the end user terminal 40 of the present embodiment can be realized by a special-purpose computer system or a general-purpose computer system.

[0396] For example, a communication program for realizing the above-described operation is stored in a computer-readable recording medium such as an optical disc, a semiconductor memory, a magnetic tape, or a floppy disc, for distribution. Then, for example, the program is installed on a computer to execute the above-described processing, and thereby the control device is configured. At this time, the control device can be a device (for example, a personal computer) external to the application server 10, the base station 20, the VaaNI terminal 30, or the end user terminal 40. Further, the control device can be a device (for example, the control unit 13, the control unit 24, the control unit 33, or the control unit 43) internal to the application server 10, the base station 20, the VaaNI terminal 30, or the end user terminal 40.

[0397] Further, for example, each communication program can be stored in a disc device included in a server device on a network such as the Internet, so as to be downloaded to a computer. Further, the above-described functions can be realized by cooperation between an operating system (OS) and application software. In this configuration, a part other than the OS can be stored in a medium for distribution, or a part other than the OS can be stored in a server device, for example, for download to a computer.

[0398] Further, in the processing described in the above embodiments, all or some of the processing described as being automatically executed can be manually executed, or all or some of the processing described as being manually executed can be automatically executed by a known method. In addition, unless otherwise specified, the processing procedure, the specific names described in the above description, and the information including various data and parameters described in the above description or shown in the drawings can be changed as appropriate. For example, the various information shown in the drawings is not limited to the information shown.

[0399] Further, the constituent elements of the devices are shown as functional concepts, but do not necessarily need to be physically configured as illustrated. In other words, the specific form of distribution or integration of the devices is not limited to those shown, and all or some of the devices can be configured by being distributed or integrated in an appropriate unit in terms of functions or physicality, according to various loads or usage conditions. Note that the configuration obtained by the distribution or integration can be dynamically formed.

[0400] Further, the above-described embodiments can be appropriately combined within a range consistent with the processing content. Further, the order of the steps shown in the sequence charts of the above-described embodiments can be changed as appropriate.

[0401] Furthermore, for example, the present embodiment can be implemented as all configurations constituting a device or a system, such as a processor as a system large scale integration (LSI) or the like, a module using a plurality of processors, a unit using a plurality of modules, and a collection obtained by further adding other functions to the unit (that is, a configuration of a part of a device).

[0402] Note that, in the present embodiment, a system means a collection of a plurality of constituent elements (devices, modules (components), and the like), and whether all the constituent elements are in the same housing is irrelevant. Therefore, a plurality of devices housed in separate housings and connected via a network and one device including a plurality of modules housed in one housing are both systems.

[0403] Furthermore, for example, the present embodiment can employ a configuration of cloud computing in which one function is shared between a plurality of devices via a network to cooperatively execute processing by the plurality of devices.

[0404] <5. Conclusion>

[0405] Although the embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the above-described embodiments, and various changes can be made without departing from the spirit and scope of the present disclosure. Furthermore, the constituent elements of different embodiments and modifications can be appropriately combined with each other.

[0406] Furthermore, the effects in the embodiments described herein are merely examples and the present disclosure is not limited to the effects and can also provide other effects.

[0407] Note that the present technology can also have the following configurations. (1)

[0409] A wireless communication device that provides a second wireless access link with another wireless communication device based on a first wireless access link with a base station, the wireless communication device comprising:

[0410] one or more network interfaces;

[0411] a user interface of the wireless communication device, the user interface being provided for a user; and

[0412] a processor that transmits, via the one or more network interfaces, a registration request or a start request related to the provision of the second wireless access link to a server device that manages the provision of the second wireless access link,

[0413] receives a notification regarding the provision of the second wireless access link from the server device, and

[0414] outputs at least a part of the notification to the user interface. (2)

[0416] The wireless communication device according to (1), wherein the processor receives the notification from the server device when requesting provision of the second wireless access link from the other wireless communication device. (3)

[0418] The wireless communication device according to (1) or (2), wherein the registration request or the start request includes at least one of identification information for identifying the wireless communication device or the user and capability information about a capability of the wireless communication device. (4)

[0420] The wireless communication device according to any one of (1) to (3), wherein the notification includes at least one of information about a provision site related to a provision site of the second wireless access link, incentive information about an incentive obtained by the user through provision of the second wireless access link, and provision information about provision of the second wireless access link. (5)

[0422] The wireless communication device according to (4), wherein the information about a provision site includes at least one of position information of a provision site, parking lot information indicating whether there is a parking lot at the provision site, and charging information indicating whether the wireless communication device can be charged at the provision site. (6)

[0424] The wireless communication device according to (4) or (5), wherein the provision information includes at least one of time information about a time at which the second wireless access link can be provided, power information about power that can be consumed by providing the second wireless access link, and utilization rate information about a utilization rate of a computing resource that can be used by providing the second wireless access link. (7)

[0426] The wireless communication device according to any one of (1) to (6), wherein the processor outputs at least one of first state information about a state of the wireless communication device and second state information about a state of a device in which the wireless communication device is installed to the user interface. (8)

[0428] The wireless communication device according to (7), wherein the processor outputs at least a part of the notification and at least one of the first state information and the second state information to the user interface. (9)

[0430] The wireless communication device according to any one of (1) to (8), wherein the processor outputs at least a part of the notification and map information to the user interface. (10)

[0432] The wireless communication device according to any one of (1) to (9), wherein the processor transmits, to the server device, movement information about movement of the wireless communication device. (11)

[0434] The wireless communication device according to (10), wherein the movement information includes at least one of route information about a movement route of the wireless communication device and search information about search for a movement destination. (12)

[0436] The wireless communication device according to any one of (1) to (11), wherein the processor starts provision of the second wireless access link according to an instruction from the user. (13)

[0438] The wireless communication device according to any one of (1) to (11), wherein

[0439] the processor:

[0440] transmits, to the server device, an acceptance notification of provision of the second wireless access link according to an instruction from the user, and

[0441] starts provision of the second wireless access link when a start notification of the provision is received from the server device. (14)

[0443] The wireless communication device according to any one of (1) to (13), wherein the wireless communication device is mounted on a vehicle. (15)

[0445] A communication method of a wireless communication device that provides a second wireless access link with another wireless communication device based on a first wireless access link with a base station, the method comprising:

[0446] transmitting, to a server device that manages provision of the second wireless access link, a registration request or a start request related to provision of the second wireless access link via one or more network interfaces of the wireless communication device;

[0447] receiving a notification about provision of the second wireless access link from the server device; and

[0448] outputting at least a part of the notification to a user interface of the wireless communication device, the user interface being set for a user. (16)

[0450] An information processing device that manages a second wireless access link provided between a first wireless communication device and a second wireless communication device based on a first wireless access link with a base station, the information processing device comprising:

[0451] one or more network interfaces; and

[0452] a processor that receives, from the first wireless communication device via the one or more network interfaces, a registration request or a start request related to provision of the second wireless access link, and

[0453] sends a notification to the first wireless communication device regarding provision of the second wireless access link,

[0454] wherein the notification is output to a user interface of the first wireless communication device, the user interface being set for a user. (17)

[0456] The information processing device according to (16), wherein the processor causes a database to store device information regarding the first wireless communication device that has sent the registration request or the start request. (18)

[0458] The information processing device according to (17), wherein the device information includes at least one of: identification information for identifying the first wireless communication device or a user, location information regarding a location of the first wireless communication device, capability information regarding a capability of the first wireless communication device, and state information regarding a state of the first wireless communication device. (19)

[0460] The information processing device according to (17) or (18), wherein the processor updates the device information according to at least one of a predetermined period and movement of the first wireless communication device. (20)

[0462] The information processing device according to any one of (16) to (19), wherein the processor receives, from the second wireless communication device, a request to provide the second wireless access link. (21)

[0464] The information processing device according to (20), wherein the processor transmits the notification to the first wireless communication device when the request is received. (22)

[0466] A communication method of an information processing device,

[0467] The information processing device manages a second wireless access link provided between a first wireless communication device and a second wireless communication device based on a first wireless access link with a base station, the method comprising:

[0468] receiving, from the first wireless communication device via one or more network interfaces of the information processing device, a registration request or a start request relating to provision of the second wireless access link, and

[0469] transmitting, to the first wireless communication device, a notification regarding provision of the second wireless access link,

[0470] wherein the notification is output to a user interface of the first wireless communication device, the user interface being user-set. (23)

[0472] A wireless communication device providing a second wireless access link with another wireless communication device based on a first wireless access link with a base station, the wireless communication device comprising:

[0473] one or more network interfaces;

[0474] a user interface of the wireless communication device, the user interface being user-set; and

[0475] a processor that transmits, to a server device managing provision of the second wireless access link via the one or more network interfaces, a registration request or a start request relating to provision of the second wireless access link, and

[0476] starts provision of the second wireless access link according to an instruction from the server device. (24)

[0478] An information processing device managing a second wireless access link provided between a first wireless communication device and a second wireless communication device based on a first wireless access link with a base station, the information processing device comprising:

[0479] one or more network interfaces; and

[0480] a processor to receive, via the one or more network interfaces, a registration request or start request relating to the provision of the second wireless access link from the first wireless communication device, and

[0481] to instruct the first wireless communication device to start the provision of the second wireless access link. (25)

[0483] A wireless communication device providing a second wireless access link to a further wireless communication device based on a first wireless access link to a base station, the wireless communication device comprising:

[0484] one or more network interfaces;

[0485] a user interface of the wireless communication device, the user interface being set up for a user; and

[0486] a processor to send, via the one or more network interfaces, a registration request or start request relating to the provision of the second wireless access link to a server device managing the provision of the second wireless access link, and

[0487] to start the provision of the second wireless access link in response to a request from the further wireless communication device. (26)

[0489] The wireless communication device according to claim (25), wherein the processor sends provision information about the provision of the second wireless access link to the surrounding environment. (27)

[0491] A wireless communication device,

[0492] the wireless communication device receiving the provision of the second wireless access link from a further wireless communication device providing the second wireless access link based on a first wireless access link to a base station, the wireless communication device comprising:

[0493] a processor to receive provision information about the provision of the second wireless access link by a further wireless communication device having sent a registration request or start request relating to the provision of the second wireless access link to a server device managing the provision of the second wireless access link, and

[0494] to receive the provision of the second wireless access link by making a request to the further wireless communication device.

[0495] List of reference symbols

[0496] S1 communication system

[0497] 10 application server

[0498] 11 communication unit

[0499] 12, 22, 32, 42 storage unit

[0500] 13, 24, 33, 43 control unit

[0501] 20 base station

[0502] 21, 31, 41 signal processing unit

[0503] 23 network communication unit

[0504] 30 VaaNI terminal

[0505] 34 input / output unit

[0506] 40 end user terminal

Claims

1. A wireless communication device that provides a second wireless access link with another wireless communication device based on a first wireless access link with a base station, the wireless communication device comprising: one or more network interfaces; a user interface of the wireless communication device, the user interface being provided for a user; and a processor that transmits, to a server device that manages provision of the second wireless access link, a registration request or a start request related to provision of the second wireless access link via the one or more network interfaces, receives a notification from the server device regarding the provision of the second wireless access link, and outputs at least a part of the notification to the user interface.

2. The wireless communication device of claim 1, wherein, The processor receives the notification from the server device when the provision of the second wireless access link is requested from the other wireless communication device.

3. The wireless communication device of claim 1, wherein, The registration request or the start request includes at least one of identification information for identifying the wireless communication device or the user and capability information regarding a capability of the wireless communication device.

4. The wireless communication device of claim 1, wherein, The notification includes at least one of information regarding a provision site related to a provision site of the second wireless access link, incentive information regarding an incentive obtained by the user through the provision of the second wireless access link, and provision information regarding the provision of the second wireless access link.

5. The wireless communication device of claim 4, wherein, The information regarding a provision site includes at least one of location information of a provision site, parking lot information indicating whether there is a parking lot at the provision site, and charging information indicating whether the wireless communication device can be charged at the provision site.

6. The wireless communication device of claim 4, wherein, The provision information includes at least one of time information regarding a time at which the second wireless access link can be provided, power information regarding power that can be consumed by providing the second wireless access link, and utilization information regarding a utilization rate of a computing resource that can be used by providing the second wireless access link.

7. The wireless communication device of claim 1, wherein, The processor outputs at least one of first state information regarding a state of the wireless communication device and second state information regarding a state of a device on which the wireless communication device is installed to the user interface.

8. The wireless communication device of claim 7, wherein, The processor outputs at least a part of the notification and at least one of the first state information and the second state information to the user interface.

9. The wireless communication device of claim 1, wherein, The processor outputs at least a part of the notification and map information to the user interface.

10. The wireless communication device of claim 1, wherein, The processor transmits, to the server device, movement information regarding movement of the wireless communication device.

11. The wireless communication device of claim 10, wherein, The movement information includes at least one of route information regarding a movement route of the wireless communication device and search information regarding a search for a movement destination.

12. The wireless communication device of claim 1, wherein, The processor starts the provision of the second wireless access link according to an instruction from the user. 13.The wireless communication device according to claim 1, wherein the processor: transmits, to the server device, an acceptance notification of the provision of the second wireless access link according to an instruction from the user, and when receiving the start notification of the provision from the server device, starting the provision of the second wireless access link.

14. The wireless communication device of claim 1, wherein, The wireless communication device is mounted on a vehicle.

15. A communication method of a wireless communication device that provides a second wireless access link with another wireless communication device based on a first wireless access link with a base station, the method comprising: transmitting, via one or more network interfaces of the wireless communication device, a registration request or a start request related to the provision of the second wireless access link to a server device that manages the provision of the second wireless access link; receiving a notification regarding the provision of the second wireless access link from the server device; and outputting at least a part of the notification to a user interface of the wireless communication device, the user interface being arranged for a user.

16. An information processing device that manages a second wireless access link provided between a first wireless communication device and a second wireless communication device based on a first wireless access link with a base station, the information processing device comprising: one or more network interfaces; and a processor that receives, via the one or more network interfaces, a registration request or a start request related to the provision of the second wireless access link from the first wireless communication device, and transmits a notification regarding the provision of the second wireless access link to the first wireless communication device, wherein the notification is output to a user interface of the first wireless communication device, the user interface being arranged for a user.

17. The information processing device according to claim 16, wherein The processor causes a database to store device information regarding the first wireless communication device that has transmitted the registration request or the start request.

18. A communication method of an information processing device that manages a second wireless access link provided between a first wireless communication device and a second wireless communication device based on a first wireless access link with a base station, the method comprising: receiving, via one or more network interfaces of the information processing device, a registration request or a start request related to the provision of the second wireless access link from the first wireless communication device, and transmitting a notification regarding the provision of the second wireless access link to the first wireless communication device, wherein the notification is output to a user interface of the first wireless communication device, the user interface being arranged for a user. ​

Images