Communication equipment and communication methods
Patent Information
- Application Number
- JP2024574196
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-02-02
- Publication Date
- 2026-09-08
- Estimated Expiration
- 2043-02-02
Smart Images

Figure 0007917639000001 
Figure 0007917639000002 
Figure 0007917639000003
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to a communication apparatus and a communication method capable of performing wireless communication with a terminal (User Equipment, UE). [Background Art]
[0002] The 3rd Generation Partnership Project (3GPP: registered trademark) has standardized the 5th generation mobile communication system (5G, also referred to as New Radio (NR) or Next Generation (NG)), and is further推进 the standardization of next-generation systems called Beyond 5G, 5G Evolution or 6G.
[0003] For example, in a white paper regarding 6G (Non-Patent Document 1), more flexible network function arrangement and the like for network architecture have been studied. [Prior Art Documents] [Non-Patent Documents]
[0004] [Non-Patent Document 1] NTT DOCOMO, "DOCOMO 6G White Paper Version 5.0", [online], January 2023, Internet<URL:https: / / www.docomo.ne.jp / binary / pdf / corporate / technology / whitepaper_6g / DOCOMO_6G_White_PaperJP_20221116.pdf> [Summary of Invention]
[0005] In 6G, as a form of mobile communication network architecture, the introduction of Network Controlled Access Points (NCAP, tentative name) is planned, which are access points (communication devices) that can be installed under the mobile communication network and can be proactively controlled by the network operator.
[0006] In mobile communication networks including NCAP (which may also be called NCAP networks), the control plane (C-plane) functions of the core network (CN) for NCAP and UE are configured to be processed on the network operator's side.
[0007] In this configuration, if a failure occurs on the network operator's side, the authentication process for NCAP and UE cannot be completed, resulting in communication failures in the NCAP network.
[0008] Therefore, the following disclosure is made in light of these circumstances and aims to provide communication equipment and communication methods that can avoid the downtime of the NCAP network even if a failure or other issue occurs on the network operator's side.
[0009] One aspect of the present disclosure is a communication device (NCAP 100) comprising: a communication unit (first communication unit 110, second communication unit 120, third communication unit 130) that performs communication with a first communication network and a second communication network, and wireless communication with a terminal (UE 200); and a control unit (control unit 140) that performs a specific operation as a wireless base station (gNB 50) accommodating the terminal, without performing specific communication with the first communication network, based on whether or not specific conditions relating to the first communication network are met. [Brief explanation of the drawing]
[0010] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2]Figure 2 is a functional block diagram of NCAP100. [Figure 3] Figure 3 is a functional block diagram of the UE200. [Figure 4] Figure 4 shows an example of the arrangement of the C-plane and U-plane functions of the CN in a mobile communication network configured using NCAP100. [Figure 5] Figure 5 shows an example sequence (part 1) of the initiation of an exception by NCAP100. [Figure 6] Figure 6 shows an example sequence (part 2) of the initiation of an exception by NCAP100. [Figure 7] Figure 7 shows an example sequence (part 3) of the initiation of exception behavior by NCAP100. [Figure 8] Figure 8 shows an example sequence (part 1) of the termination of exception behavior by NCAP100. [Figure 9] Figure 9 shows an example sequence (part 2) of the termination of exception handling by NCAP100. [Figure 10] Figure 10 shows an example sequence (part 3) of the termination of exception behavior by NCAP100. [Figure 11] Figure 11 shows an example of the hardware configuration of NCAP100 and UE200. [Figure 12] Figure 12 shows an example of the configuration of vehicle 2001. [Modes for carrying out the invention]
[0011] The embodiments will be described below with reference to the drawings. Note that identical or similar reference numerals are used to denote the same functions and components, and their descriptions will be omitted as appropriate.
[0012] (1) Overall schematic configuration of the wireless communication system Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G (hereinafter referred to as 6G), and includes a wireless base station 50 (hereinafter referred to as gNB50) and a terminal 200 (hereinafter referred to as UE200, User Equipment, UE). Note that the wireless communication system 10 may also be a wireless communication system that conforms to specifications other than 6G, such as 5G New Radio (NR).
[0013] The gNB50 is a 6G-compliant radio base station that performs 6G-compliant wireless communication with the UE200. The NCAP100 and UE200 can support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional antenna beam by controlling radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication between the UE and two or more RAN Nodes.
[0014] The wireless communication system 10 includes a Network Controlled Access Point 100 (hereinafter referred to as NCAP100) in addition to the gNB50. The NCAP100 is a type of communication device called an access point (AP) and can provide similar functions to a wireless base station. NCAP is a provisional name and may be called by other similar names such as communication node, RAN node, or relay device.
[0015] NCAP100 may be installed by the operator of the wireless communication system 10 (mobile communication system) (which may also be called a network operator or mobile operator), but it may also be freely installed by the subscriber (Customer, Subscriber) of the communication services provided by the wireless communication system 10.
[0016] It should be noted that at least any one of the frequency band supported by NCAP100 (which may also include band combinations, etc.), the number of antenna beams, the number of MIMO layers, transmit power, etc. may be more restricted than that of gNB50. Since NCAP100 can provide substantially the same functions as gNB50, it can form cell C1 and accommodate UE200.
[0017] UE200 is typically a mobile terminal such as a smartphone, but may also be a device for Industrial Internet of Things (IIoT) or URLLC (Ultra-Reliable and Low Latency Communications).
[0018] The wireless communication system 10 may be configured by a radio access network (RAN) composed of a plurality of RAN Nodes such as gNB50 using 6G radio access technology (RAT), and a core network conforming to 6G. It should be noted that the RAN and the core network may be simply referred to as a "network".
[0019] The core network (CN) may be connected to the RAN, and is a network configured by an exchange, a subscriber information management device, and the like. UE200 can perform communication with the core network via the RAN.
[0020] In the wireless communication system 10, a control plane (C-plane) function and a user plane (U-plane) function (UPF: User Plane Function) are defined.
[0021] C-plane may mean a series of control processes that are mainly exchanged for establishing communication and the like. U-plane may mean transmission and reception processing of user data.
[0022] In core networks (and some RANs), the concept of CUPS (Control and User Plane Separation) may be introduced, where the functions of the C-plane and U-plane are clearly separated.
[0023] The core network's C-plane functionality may include the Access and Mobility Management Function (AMF), which provides access and mobility management functions for the UE200, and the Session Management Function (SMF), which provides session management functions. Note that AMF and SMF may be referred to by other names.
[0024] For NCAP100, the network operator may perform connections to the RAN and various controls via the C-plane function. At least a portion of such connections and / or controls may be implemented using the Self-Organizing Networks (SON) framework. SON can be interpreted as a self-optimization function for mobile communication networks, including automatic configuration and automatic parameter optimization during gNB50 installation.
[0025] The NCAP100 can connect to the gNB50 via the C-plane function in this way. The connection between the gNB50 and the NCAP100 may be via RAN (RAT) or via a wired network. Furthermore, the NCAP100 can provide the UE200 with a communication path to broadband internet and servers for MEC (Multiaccess Edge Computing) via a local area network (LAN). MEC is a mechanism in a mobile communication network that deploys servers and storage closer to the user (subscriber). It may also provide access to various cloud services via broadband internet.
[0026] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of NCAP100 and UE200 will be described. Figure 2 is a functional block configuration diagram of NCAP100. Figure 3 is a functional block configuration diagram of UE200.
[0027] (2.1) NCAP100 As shown in Figure 2, the NCAP 100 includes a first communication unit 110, a second communication unit 120, a third communication unit 130, and a control unit 140.
[0028] The first communication unit 110 performs communication with the network operator. Specifically, the first communication unit 110 performs communication with RAN nodes, including gNB50. Wireless access technology (RAT) may be used for connection with gNB50 (and other RAN nodes), or a wired network other than RAT may be used. The network on the network operator's side, which consists of RAN nodes including gNB50, may be called the first communication network. In other words, the first communication unit 110 performs communication with the first communication network using RAT. The network operator's side network may be interpreted as a concept that includes SON.
[0029] The second communication unit 120 performs communication with the local area network (LAN). Specifically, the second communication unit 120 performs communication with communication devices such as routers that constitute the LAN, and with the broadband internet (which may be simply abbreviated as the internet).
[0030] For connection to the LAN, a wireless LAN such as Wi-Fi (registered trademark) or a wired LAN such as Ethernet (registered trademark) may be used. The LAN-side network may also be called the second communication network. In other words, the second communication unit 120 performs communication with the second communication network using LAN technology.
[0031] Furthermore, the second communication unit 120 may communicate with the network operator via the LAN (second communication network) and the broadband internet. This communication may include not only U-plane functionality but also C-plane functionality.
[0032] The third communication unit 130 performs communication with the UE200. Specifically, the third communication unit 130 performs wireless communication with the UE200 using radio access technology (RAT). In this case, the NCAP 100 may provide the UE200 with the same functions as the gNB 50. In this embodiment, the third communication unit 130 constitutes a communication unit that performs wireless communication with the UE200.
[0033] The control unit 140 controls each functional block that constitutes the NCAP 100. In particular, in this embodiment, the control unit 140 can control the behavior of the communication device of the NCAP 100. Specifically, the control unit 140 can perform the operation of the NCAP 100 as a network device (NW device) that accommodates the UE 200 (hereinafter referred to as "specific operation").
[0034] The network device is not limited to any particular type of device, as long as it accommodates the UE200 (intended to connect to the UE200 and perform wireless communication). Here, it may refer to a network device such as a wireless base station (gNB50), and the control unit 140 may perform specific operations as a wireless base station accommodating the UE200.
[0035] The control unit 140 may perform a specific operation based on whether or not specific conditions regarding the network operator's network (first communication network) are met. In this case, it may operate as a network device without performing specific communication with the network operator's network. Such an operation may be specifically called an exceptional operation among the specific operations.
[0036] Certain communications during the operation, such as notifications allowing or terminating exceptional operations, may be performed, although these communications are not necessarily limited to specific communications between the network operator and the network.
[0037] The specific conditions may be conditions relating to the radio access network (RAN) or the core network (CN). The specific conditions may be conditions relating to the response to communications to the network operator's network (hereinafter referred to as the network operator as appropriate).
[0038] Specifically, the control unit 140 may perform the specified operation (exception operation) if there is no response to communication from the NCAP 100 or UE 200 to the network operator (first communication network).
[0039] Alternatively, the control unit 140 may perform a specific operation based on its response to a communication from the NCAP 100 or UE 200 to the network operator. Specifically, if the control unit 140 receives permission or instructions to perform a specific operation as a response to a communication from the NCAP 100 or UE 200 to the network operator, it can perform that specific operation.
[0040] Furthermore, when the control unit 140 is operating as a network device accommodating the UE200, it can execute a specific operation if it receives permission or instructions from the network operator to do so. The period when the NCAP 100 is operating as a network device accommodating the UE200 may refer to the period from the time when the NCAP 100 is set to operate as a network device accommodating the UE200 until the time when the setting is canceled, or it may refer to only a specific time frame within that period.
[0041] The control unit 140 can perform specific operations in at least one of the C-plane of the NCAP100 or UE200 relating to the CN, and the U-plane of the UE200 relating to the CN. The C-plane and U-plane functions of the CN may include the following processes.
[0042] • C-plane functions: Device registration / connection, subscriber management / retention / processing, subscriber authentication processing, billing-related control, mobility management, session management • U-plane: Connection to IP (Internet Protocol) network, authentication processing, IP packet routing, priority control. The control unit 140 may perform data communication (transmission and reception of user data) of the UE200 without performing operations on the C-plane of the NCAP100 or UE200 regarding the CN. Alternatively, the control unit 140 may perform operations on the C-plane of the NCAP100 or UE200 regarding the CN based on a notification from the network operator. The control unit 140 may proactively decide whether or not to perform operations on the C-plane of the NCAP100 or UE200 regarding the CN, and / or the content of the operations, depending on the status of the NCAP100, or it may decide based on a notification from the network operator. Furthermore, the possibility of performing such operations and / or the content of the operations may be predetermined by the 3GPP specification.
[0043] The control unit 140 may take the following actions regarding the termination of the specific operation. Specifically, the control unit 140 may terminate the specific operation based on notification from the network operator or the elapsed time since the start of the specific operation.
[0044] The control unit 140 may periodically (or irregularly) send an inquiry to the network operator asking whether or not to terminate the specific operation, and may terminate the specific operation based on the notification from the network operator in response to the inquiry. In this case, the control unit 140 may be required to always perform an action to receive a notification from the network operator. Alternatively, the control unit 140 may terminate the specific operation based on a determination by NCAP 100, without such notification or inquiry.
[0045] The control unit 140 may notify the network operator of the completion of the specific operation via the first communication unit 110 or the second communication unit 120. Alternatively, the control unit 140 may notify the UE 200 of the completion of the specific operation via the third communication unit 130.
[0046] (2.2)UE200 As shown in Figure 3, the UE200 comprises a wireless communication unit 210, a connection IF unit 220, and a control unit 230.
[0047] The wireless communication unit 210 transmits and receives wireless signals in accordance with 6G with gNB50 or NCAP100. Specifically, the wireless communication unit 210 transmits UL signals in accordance with 6G and receives DL signals in accordance with 6G. The wireless communication unit 210 supports Massive MIMO, CA using multiple CCs bundled together, and DC which enables simultaneous communication between the UE and each of the two NG-RAN Nodes.
[0048] The connection IF unit 220 can provide an interface (IF) function for connecting devices for IIoT or URLLC. The connection IF unit 220 is not mandatory and may not be provided depending on the specifications of the UE200. The IF provided by the connection IF unit 220 may be wired or wireless.
[0049] The control unit 230 controls the wireless communication unit 210 and the connection IF unit 220. In particular, in this embodiment, the control unit 230 can control the behavior of the UE200 during an exceptional operation in which the NCAP 100 performs a specific operation (operation as a network device accommodating the UE200) without performing communication with the network operator's network.
[0050] Specifically, the control unit 230 may suspend the execution of the UE200 corresponding to the C-plane of the CN if the NCAP100 is in an exceptional operation. This suspension of operation may be limited to the period during which the NCAP100 is in an exceptional operation, or it may be limited to the period of a specific operation in which the NCAP100 operates as a network device accommodating the UE200.
[0051] (3) Operation of the wireless communication system Next, the operation of the wireless communication system 10 will be described. Specifically, the operation of the NCAP 100 in the wireless communication system 10, including the NCAP 100, when a failure or other issue occurs in the network operator's network will be described.
[0052] (3.1) Premise In mobile communication networks (NCAP networks) including NCAP100, the control plane (C-plane) functions related to the core network (CN) for NCAP and UE are configured to be processed on the network operator's side.
[0053] Figure 4 shows an example of the arrangement of the CN's C-plane and U-plane functions in a mobile communication network configured using NCAP100.
[0054] In this configuration, if a failure occurs on the network operator's side, the CN's C-plane will not function, preventing the NCAP and UE authentication processes from being completed. This can lead to communication failures in the NCAP network as well.
[0055] Therefore, a mechanism is needed to prevent the NCAP network from shutting down and to ensure communication can continue even if a failure occurs on the network operator's side. Note that failures on the network operator's side may include events that make it impossible to provide the C-plane function, such as failures, overloads (congestion), or accidents of devices (nodes) that constitute the RAN or CN that make up the mobile communication network.
[0056] (3.2) Example of operation To resolve the aforementioned issues, NCAP100 may, when certain conditions are met (or not met), operate as a network device (NW device) accommodating UE200 without communicating with the network operator (or the network with the operator, hereinafter the same).
[0057] The interaction with the network operator may refer to communication with the network operator's network (first communication network) (for example, sending and receiving C-plane related signals), and the NCAP100 can perform its operations as a network device (referred to as exceptional operation) without performing the specific communication with the network operator as described above. The communication between the NCAP100 and the network operator may be wireless or wired, and the method is not limited.
[0058] The specified conditions are synonymous with the specific conditions described above, and these specific conditions may be events related to RAN or events related to CN.
[0059] (3.2.1) Regarding specific conditions Figure 5 shows an example sequence (part 1) for initiating an exception operation by NCAP100. As shown in Figure 5, if a failure occurs on the network operator side and there is no response to communication from NCAP100 or UE200 to the network operator side, NCAP100 may perform an exception operation. Note that the communication from NCAP100 or UE200 to the network operator side may be any communication, or may be limited to communication associated with the exception operation.
[0060] Specifically, if there is no response and no response is received for N communications at time T, NCAP100 may perform an exception. The values of N and T may be defined by the 3GPP specification or may be pre-set by a higher layer or the like.
[0061] By performing this operation, NCAP100 initiates an exception operation in the event of a failure on the network operator's side, preventing any communication between the network operator and NCAP100. This allows NCAP100 to accommodate UE200 and continue communication related to UE200.
[0062] Figure 6 shows an example sequence (part 2) for initiating an exception operation by NCAP100. As shown in Figure 6, NCAP100 may execute an exception operation if it receives an exception operation instruction (which may also be an authorization instruction; the same applies hereafter) as a response to communication from NCAP100 or UE200 to the network operator. In this case, the network operator has a mechanism in the CN or RAN to notify NCAP100 of the instruction. Note that the communication from NCAP100 or UE200 to the network operator may be any communication, or may be limited to communication associated with the exception operation.
[0063] By performing such actions, NCAP100 can control the exceptional behavior of NCAP100 at the initiative of the network operator.
[0064] Figure 7 shows an example sequence (part 3) of the initiation of an exception operation by NCAP100. As shown in Figure 7, NCAP100 may execute an exception operation if it receives an instruction for an exception operation from a network operator while performing an operation (specific operation) as a network device accommodating UE200.
[0065] In this case, NCAP100 does not need to receive any communication from NCAP100 or UE200 to the network operator regarding instructions for exceptional operation from the network operator, and may receive instructions for exceptional operation from the network operator while NCAP100 is operating as a network device accommodating UE200. In this case as well, the network operator has a mechanism in the CN or RAN to notify NCAP100 of such instructions.
[0066] The network operator's instruction for an exception may be issued per NCAP100 (unicast), per group of NCAP100s (groupcast / multicast), or for all NCAP100s (broadcast).
[0067] By performing such actions, NCAP100 can control the exceptional behavior of NCAP100 at the initiative of the network operator.
[0068] (3.2.2) Exceptions to NCAP100 as a network device Based on the specific conditions described above, the following exceptions may be applied. As mentioned above, the C-plane and U-plane functions of CN may include the following processing.
[0069] • C-plane functions: Device registration / connection, subscriber management / retention / processing, subscriber authentication processing, billing-related control, mobility management, session management • U-plane: Connection to IP (Internet Protocol) network, authentication processing, IP packet routing, priority control. NCAP100 may perform data communication with UE200 without performing the C-plane functions (which may also be called C-plane related operations) described above.
[0070] Alternatively, NCAP100 may execute the C-plane function based on a notification from the network operator. That is, the C-plane function may be executed by NCAP100 rather than by the network operator. In this case, the notification may be given in advance, or it may be given in conjunction with (associated with) the instructions for the exception operation shown in Figures 6 and 7. Furthermore, when NCAP100 executes a C-plane related operation, it may discard information related to the operation (for example, which UE performed the communication), and may report it to the network operator during or after the execution of the exception operation. The recipient of the report may be the network operator to which the UE200 connected to NCAP100 belongs.
[0071] Furthermore, whether or not to perform C-plane-related operations, and / or the content of those operations (e.g., the type of session to be set), may be determined by NCAP100 or defined by the 3GPP specification. Alternatively, NCAP100 may determine the content of such operations based on notifications from the network operator. Such notifications may be made in advance or in conjunction with (associated with) the instructions for exceptional operations shown in Figures 6 and 7.
[0072] When NCAP100 performs an exceptional operation, it may notify UE200 that an exceptional operation is in progress. This notification may be a predetermined operation instruction corresponding to the exceptional operation.
[0073] Any UE200 under any network operator may be able to connect to such an NCAP100. "Any network operator under any network operator" can be interpreted as all UE200s that can connect to the network of any network operator. That is, a UE200 may be able to connect to NCAP100 regardless of whether it belongs to the network operator or not. A UE200 may be notified that it can connect to NCAP100 regardless of which network operator it belongs to. Alternatively, the fact that a UE200 can connect to NCAP100 regardless of which network operator it belongs to may be notified as a designated mobile communication network (PLMN: Public Land Mobile Network). This notification may be the same as (or shared with) the notification that NCAP100 is in an exceptional operation. Note that the network operators that can be included in "any network operator" may be limited, in which case information for multiple PLMNs may be notified during the exceptional operation of NCAP100.
[0074] The various parameters (for example, various parameters related to SON) when NCAP100 performs exceptional operations (specific operations) as a network device may be handled as follows:
[0075] • Continue applying the parameters that were notified before the failure occurred.
[0076] • Continue to apply the parameters that were notified for the purpose of being applied in the event of a failure.
[0077] • Apply the parameters notified in association with the exceptional behavior instructions shown in Figures 6 and 7.
[0078] • Modify the applicable parameters based on the implementation of NCAP100 and / or the communication between NCAP100 instances.
[0079] According to the exceptional behavior of the NCAP100 as a network device as described above, even if a failure occurs on the network operator's side, communication using the NCAP network can continue.
[0080] (3.2.3) Operation of UE200 UE200 may abort the execution of the operation corresponding to the CN's C-plane if NCAP100 is in an exceptional operation. Specifically, UE200 does not need to perform the operation of UE200 that corresponds to the CN's C-plane function.
[0081] On the other hand, if NCAP100 is not in an exceptional operation, UE200 may perform an operation corresponding to the C-plane of CN. If NCAP100 is not in an exceptional operation, it may mean that NCAP100 is operating as a network device accommodating UE200 (a specific operation) without performing the exceptional operation described above, and this may include a state in which NCAP100 is operating as a network device accommodating UE200 while waiting for a response to communication from NCAP100 or UE200 to the network operator (first communication network).
[0082] (3.2.4) Termination of exceptional operation of NCAP100 as a network device Figure 8 shows an example sequence (part 1) of the termination of an exception operation by NCAP100. As shown in Figure 8, NCAP100 may continue to perform the exception operation from the start of the exception operation until it receives notification of the termination of the exception operation from the network operator.
[0083] Figure 9 shows an example sequence (part 2) for the termination of an exception operation by NCAP100. As shown in Figure 9, after the start of an exception operation, NCAP100 may periodically send queries to the network operator (for example, at regular time intervals) and continue the exception operation until it receives an instruction (or notification) from the network operator to terminate the exception operation in response to the queries. Note that the sending of queries may be irregular or at uneven intervals.
[0084] In the example sequences shown in Figures 8 and 9, the NCAP 100 may be constrained to always perform the action of receiving notifications from the network operator. The queries and / or notifications from the NCAP 100 may be lower-layer signals (e.g., SSB (Synchronization Signal / Physical Broadcast Channel blocks) / PRACH (Physical Random Access Channel)) or higher-layer signals (e.g., RRC (Radio Resource Control) or layers higher than RRC).
[0085] Figure 10 shows an example sequence (part 3) of the termination of an exception operation by NCAP100. As shown in Figure 10, NCAP100 may execute the exception operation until a time (t) has elapsed after the start of the exception operation. In this case, the time (t) may be defined by the 3GPP specification or may be set in advance by a higher layer or the like.
[0086] NCAP100 may terminate the exceptional operation by its own determination without such notification or inquiry. If NCAP100 terminates or has terminated the exceptional operation by any of the above procedures or other procedures, NCAP100 may notify UE200 and / or the network operator of the termination of the exceptional operation. Furthermore, if the exceptional operation is terminated, NCAP100 may start executing the specific operation (i.e., operation as a network device (NW device) housing UE200 while communicating with the network operator), or terminate operation as a network device housing UE200.
[0087] By performing this action, NCAP100 can be prevented from continuing its exceptional behavior (or specific behavior) indefinitely, and after the network operator's fault is resolved, NCAP100 can quickly return to the network operator's control.
[0088] (4) Action and Effects According to the embodiment described above, when a network failure occurs on the network operator's side, the NCAP 100 can perform its function as a network device accommodating the UE200 (exceptional operation) without performing specific communication with the network operator. This avoids the NCAP network being shut down and allows the UE200 to continue communicating.
[0089] (5) Other embodiments Although embodiments have been described above, it will be obvious to those skilled in the art that the invention is not limited to those embodiments described and that various modifications and improvements are possible.
[0090] For example, in the embodiment described above, it was explained that the system can connect to a server for MEC and the broadband internet via a LAN, but the LAN may be set up on the same segment, or it may be a different LAN that is physically or logically separated.
[0091] Furthermore, in the embodiment described above, the NCAP 100 was connected to both the network operator's network (first communication network) and the LAN (second communication network), but it may be connected to only one of the networks. Also, the UE 200 connected to the network configured by the NCAP 100 may or may not be separately connected to the network operator's wireless base station. The operation of the NCAP 100 and / or UE 200 may differ depending on whether or not such a connection is made. In addition, the network configured by the NCAP 100 may use either a licensed band or an unlicensed band.
[0092] Furthermore, the block diagrams (Figures 2 and 3) used in the description of the embodiments above show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Moreover, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.
[0093] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.
[0094] Furthermore, the NCAP100 and UE200 described above may function as computers that process the wireless communication method of this disclosure. Figure 11 shows an example of the hardware configuration of the NCAP100 and UE200. As shown in Figure 11, the NCAP100 and UE200 may be configured as computer devices including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.
[0095] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.
[0096] Each functional block of NCAP100 and UE200 (see Figures 2 and 3) is implemented by any hardware element of the computer device, or a combination of such hardware elements.
[0097] Furthermore, each function in the NCAP100 and UE200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.
[0098] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.
[0099] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one of the storage 1003 and the communication device 1004 into the memory 1002 and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may be transmitted from a network via a telecommunications line.
[0100] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software modules, etc., that can execute a method according to one embodiment of this disclosure.
[0101] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.
[0102] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc.
[0103] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD).
[0104] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0105] Furthermore, each device, such as the processor 1001 and the memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.
[0106] Furthermore, the device may include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), and a field-programmable gate array (FPGA), and some or all of each functional block may be implemented by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.
[0107] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.
[0108] Each aspect / embodiment described herein may be applied to at least one of systems utilizing Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (where x is, for example, an integer or decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).
[0109] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.
[0110] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).
[0111] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.
[0112] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be sent to other devices.
[0113] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).
[0114] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).
[0115] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.
[0116] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.
[0117] The information, signals, etc. described in this disclosure may be represented using any of the various different technologies. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.
[0118] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.
[0119] The terms “system” and “network” as used in this disclosure are interchangeable.
[0120] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.
[0121] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.
[0122] In this disclosure, terms such as "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.
[0123] A base station can house one or more (e.g., three) cells (also called sectors). If a base station houses multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).
[0124] The terms "cell" or "sector" refer to a portion or all of the coverage area of at least one of the base stations and base station subsystems that provide communication services in this coverage.
[0125] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.
[0126] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.
[0127] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term.
[0128] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.
[0129] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel (or side link).
[0130] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.
[0131] A wireless frame may consist of one or more frames in the time domain. Each of these one or more frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.
[0132] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.
[0133] A slot may consist of one or more symbols in the time domain (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol). A slot may also be a time unit based on neurology.
[0134] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.
[0135] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.
[0136] For example, one subframe may be called a Transmit Time Interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.
[0137] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.
[0138] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.
[0139] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit of scheduling may be controlled.
[0140] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.
[0141] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.
[0142] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.
[0143] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.
[0144] One or more RBs may also be called a Physical RB (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.
[0145] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.
[0146] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology on a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.
[0147] A BWP may include BWPs for UL (UL BWP) and BWPs for DL (DL BWP). One or more BWPs may be set within a single carrier for a UE.
[0148] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".
[0149] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.
[0150] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.
[0151] The reference signal can also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.
[0152] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."
[0153] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.
[0154] Any reference to elements using designations such as “First,” “Second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.
[0155] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.
[0156] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.
[0157] The terms “determining” and “determining” as used in this disclosure may encompass a wide variety of actions. “Determining” and “determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” and “determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having "judgmented" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having "judgmented" or "decided" about some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."
[0158] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."
[0159] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure may be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Accordingly, the descriptions in the present disclosure are for illustrative purposes only and are not intended to be restrictive in any way.
[0160] Figure 12 shows an example of the configuration of vehicle 2001. As shown in Figure 12, vehicle 2001 comprises a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.
[0161] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and rear wheels based on the operation of the steering wheel operated by the user. The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2027 provided in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).
[0162] Signals from various sensors 2021-2028 include current signals from the current sensor 2021 that senses motor current, front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.
[0163] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.
[0164] Information Services Section 2012 may include input devices that accept input from external sources (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) and output devices that perform output to external sources (e.g., displays, speakers, LED lamps, touch panels, etc.).
[0165] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.
[0166] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028 provided in the vehicle 2001.
[0167] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.
[0168] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021 to 2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021 to 2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.
[0169] The communication module 2013 receives various information (traffic information, signal information, vehicle-to-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 installed in the vehicle. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021-2028, etc., installed in the vehicle 2001.
[0170] (Note) The above disclosure may also be expressed as follows: The first feature is a communication device comprising a communication unit that performs communication with a first communication network and a second communication network, and wireless communication with a terminal, and a control unit that performs a specific operation as a wireless base station accommodating the terminal without performing communication with the first communication network, based on whether or not specific conditions relating to the first communication network are met.
[0171] The second feature is that, in the first feature, the control unit performs the specific operation if there is no response to communication from the communication device or the terminal to the first communication network.
[0172] The third feature is that, in the first or second feature, the control unit performs the specific operation based on the response to the communication from the communication device or the terminal to the first communication network.
[0173] The fourth feature is that, in the first to third features, the control unit performs the specific operation in at least one of the control plane of the communication device or terminal relating to the core network, and the user plane of the terminal relating to the core network.
[0174] The fifth feature is that, in the first to fourth features, the control unit terminates the specific operation based on a notification from the first communication network or the elapsed time since the start of the specific operation. [Explanation of Symbols]
[0175] 10 Wireless Communication Systems 50 gNB 100 NCAP 110 First Communications Department 120 Second Communications Department 130 Third Communications Department 140 Control Unit 200 UE Cell C1 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication Port
Claims
1. A communication unit that performs communication with the first communication network and the second communication network, and wireless communication with terminals, A control unit that performs a specific operation as a wireless base station accommodating the terminal, without performing specific communication with the first communication network, based on whether or not specific conditions relating to the first communication network are met. A communication device equipped with the following features.
2. The communication device according to claim 1, wherein the control unit performs the specific operation when there is no response to communication from the communication device or the terminal to the first communication network.
3. The communication device according to claim 1, wherein the control unit performs the specific operation based on a response to communication from the communication device or the terminal to the first communication network.
4. The communication device according to claim 1, wherein the control unit performs the specific operation in at least one of the control plane of the communication device or terminal relating to the core network, and the user plane of the terminal relating to the core network.
5. The communication device according to claim 1, wherein the control unit terminates the execution of the specific operation without performing the specific communication with the first communication network, based on a notification from the first communication network or the elapsed time since the start of the specific operation.
6. The steps include performing communication with the first communication network and the second communication network, and wireless communication with a terminal, A step of performing a specific operation as a wireless base station accommodating the terminal, without performing specific communication with the first communication network, based on whether or not specific conditions relating to the first communication network are met. A communication method that includes this.
Citation Information
Patent Citations
Integrated Small Cell and Handover within WiFi Network
JP2017510176A
A communication system to mitigate interference caused by coexistence.
JP2017520982A