JP7786853B2 - Terminal, wireless communication system, and wireless communication method - Google Patents

Description

The present disclosure relates to a terminal, a wireless communication system, and a wireless communication method that support slices in which a network is divided into specific units.

The 3rd Generation Partnership Project (3GPP) has specified Long Term Evolution (LTE) and the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also working on specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

In 3GPP Release 15 (NR) and later, the terminal (User Equipment, UE) has an Automatic Neighbor Relation (ANR) function, which allows it to automatically generate and update information about the UE's neighboring cells, specifically the Neighbor Relation Table (NRT). This enables appropriate handover of the UE.

In addition, 3GPP Release 17 is studying an architecture (RAN Slicing) that divides the radio access network (RAN) into slices based on service units such as use cases or business models (Non-Patent Document 1). For example, RAN Slicing considers cell reselection that takes slices into account and slice-specific random access channels (RACH).

"Enhancement of RAN slicing for NR", RP-211289, 3GPP TSG RAN meeting #92e, 3GPP, June 2021

However, the current 3GPP specifications make it difficult for UEs and networks to properly share slice information regarding RAN Slicing. This makes it difficult to build Self-Organizing Networks (SONs) that support slicing.

The following disclosure has been made in light of this situation and aims to provide a terminal, a wireless communication system, and a wireless communication method that can appropriately share slice information regarding RAN Slicing.

One aspect of the present disclosure is a terminal (UE200) having a control unit (control unit 240) that controls association of neighboring cells, and a transmission unit (slice-related information processing unit 230) that transmits neighboring cell information to the network, including information on slices into which the network is divided in specific units.

One aspect of the present disclosure is a wireless communication system including a terminal and a wireless base station, wherein the terminal:
The wireless communication system includes a control unit that controls the association of neighboring cells, and a transmitting unit that transmits neighboring cell information to the network, including information on slices into which the network is divided into specific units, and the wireless base station includes a receiving unit (ANR function unit 120) that receives the neighboring cell information.

One aspect of the present disclosure is a wireless communication method including a step in which a terminal controls association of neighboring cells, a step in which the terminal transmits neighboring cell information to the network, the neighboring cell information including information on slices into which the network is divided in specific units, and a step in which the network receives the neighboring cell information.

One aspect of the present disclosure is a terminal (UE200) that includes a control unit (control unit 240) that selects a cell that supports or does not support slices divided by a network in specific units, and a transmission unit (slice-related information processing unit 230) that transmits a report to the network that includes information related to the slice if the requested slice is not supported in the selected cell.

One aspect of the present disclosure is a wireless communication system including a terminal and a radio base station, wherein the terminal is equipped with a control unit that selects a cell that supports or does not support slices divided by a network in specific units, and a transmission unit that transmits a report to the network including information related to the slice if the requested slice is not supported in the selected cell, and the radio base station is equipped with a receiving unit (UE connection control unit 130) that receives the report.

One aspect of the present disclosure is a wireless communication method including a step in which a terminal selects a cell in which the network supports or does not support slices divided into specific units; a step in which the terminal transmits a report to the network including information related to the slice if the slice requested by the terminal is not supported in the selected cell; and a step in which the network receives the report.

One aspect of the present disclosure is a terminal (UE200) having a control unit (control unit 240) that executes a random access procedure specific to a slice into which a network is divided into specific units, and a transmission unit (slice-related information processing unit 230) that, if the random access procedure fails, transmits a report to the network including information related to the random access procedure.

One aspect of the present disclosure is a wireless communication system including a terminal and a radio base station, wherein the terminal is equipped with a control unit that executes a random access procedure specific to a slice into which a network is divided into specific units, and a transmission unit that, if the random access procedure fails, transmits a report to the network including information related to the random access procedure, and the radio base station is equipped with a receiving unit (UE connection control unit 130) that receives the report.

One aspect of the present disclosure is a wireless communication method including a step in which a terminal performs a random access procedure specific to a slice into which a network is divided in a specific unit; a step in which the terminal transmits a report to the network including information related to the random access procedure if the random access procedure fails; and a step in which the network receives the report.

FIG. 1 is a diagram showing the overall configuration of a wireless communication system 10. Figure 2 is a functional block diagram of gNB100. FIG. 3 is a functional block diagram of the UE 200. FIG. 4 is a diagram showing an example of the configuration of the ANR function unit 120. FIG. 5 is a diagram showing an example of the configuration of a slice group. FIG. 6 is a diagram illustrating an example of a reporting sequence of a slice group ID according to the first operation example. FIG. 7 is a diagram illustrating an example of signaling of slice-related information between nodes according to the first operation example. FIG. 8 is a diagram illustrating an example of a communication sequence according to the second operation example. FIG. 9 is a diagram illustrating an example of a communication sequence according to the third operation example. FIG. 10 is a diagram showing an example of a slice remapping sequence according to Operation Example 4 (Slice re-mapping decided by T-gNB (Example 1)). FIG. 11 is a diagram showing an example of a slice remapping sequence according to Operation Example 4 (Slice re-mapping decided by T-gNB (Example 2)). FIG. 12 is a diagram showing an example of a slice remapping sequence according to Operation Example 4 (Slice re-mapping decided by AMF and T-gNB). FIG. 13 is a diagram showing an example of a sequence of slice remapping (Slice re-mapping decided by SN) according to the fourth operation example. FIG. 14 is a diagram illustrating an example of a communication sequence according to the fifth operation example. Figure 15 is a diagram showing an example of the hardware configuration of gNB100 and UE200. FIG. 16 is a diagram showing an example of the configuration of a vehicle 2001.

The following describes the embodiments based on the drawings. Note that identical or similar symbols are used to designate identical functions and configurations, and descriptions of these will be omitted where appropriate.

(1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (User Equipment 200, hereinafter, UE 200).

In addition, the wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G.

The NG-RAN 20 includes a radio base station 100 (hereinafter referred to as gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in Figure 1.

NG-RAN 20 actually includes multiple NG-RAN nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network 40 (which may also be referred to as 5GC). The NG-RAN 20 is connected to an Access and Mobility Management Function 50 (AMF50), which is included in the 5G system architecture and provides access and mobility management functions for UE 200. Network elements other than the wireless communication system 10 (e.g., a private network (NPN: Non-Public Network)) may also be connected to the core network 40.

The NG-RAN 20 and core network 40 may provide multiple slices 45 that can be configured on a service basis, such as a use case or business model. Multiple slices 45 may be grouped according to service content, etc. Slices 45 may also be configured only by the NG-RAN 20 (RAN Slicing). Slices 45 may be interpreted as logical networks in which the network is divided into specific units, such as services.

In RAN Slicing, slice 45-aware cell (re)selection and slice-specific random access channels (RACH) may be applied.

gNB100 is a radio base station conforming to NR, and performs radio communication conforming to NR with UE200. Note that gNB100 may be composed of a CU (Central Unit) and a DU (Distributed Unit), and the DU may be separated from the CU and installed in a different geographical location.

The gNB100 and UE200 are capable of supporting Massive MIMO, which generates more directional beams by controlling the radio signals transmitted from multiple antenna elements; Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs); and Dual Connectivity (DC), which enables simultaneous communication between the UE and multiple NG-RAN nodes.

The wireless communication system 10 may use an NRT (Neighbor Relation Table, also known as an NCRT (Neighbor Cell Relation Table)) that is applied to handover (HO) of the UE 200 to another cell and manages neighbor cell identification information (CGI: Cell Global Identifier). The contents of the NRT may be manually pre-configured, or an ANR (Automatic Neighbor Relation) function may be introduced that automatically associates neighbor cell information (CGI).

(2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

Figure 2 is a functional block diagram of gNB100. Figure 3 is a functional block diagram of UE200. Note that Figures 2 and 3 only show the main functional blocks relevant to the description of the embodiments, and that gNB100 and UE200 have other functional blocks (e.g., power supply units, etc.). Also, Figures 2 and 3 show the functional block configurations of gNB100 and UE200; for the hardware configuration, please refer to Figure 15.

(2.1) gNB100
As shown in FIG. 2, the gNB 100 includes a radio communication unit 110, an ANR function unit 120, a UE connection control unit 130, and a control unit 140.

The wireless communication unit 110 transmits downlink signals (DL signals) in accordance with NR. The wireless communication unit 110 also receives uplink signals (UL signals) in accordance with NR.

The ANR function unit 120 provides functions related to ANR (Automatic Neighbor Relation). Specifically, the ANR function unit 120 can automatically associate information about neighboring cells.

Figure 4 shows an example configuration of the ANR function unit 120. As shown in Figure 4, the ANR function unit (ANR function) may be composed of an NCRT Management Function, a Neighbor Removal Function, and a Neighbor Detection Function.

The Neighbor Cell Relation Table (NCRT) may consist of an NCR section (NCR, TCI (Transmission Configuration Indication)) and an O&M controlled attributes section (No Remove, No HO, No Xn). Note that such ANR functions may conform to the specifications in, for example, 3GPP TS38.300 Chapter 15.3.3.1.

The ANR function unit 120 can receive neighboring cell information from the UE 200. In this embodiment, the ANR function unit 120 may constitute a receiving unit that receives neighboring cell information. The neighboring cell information may include information about slice 45 (slice-related information). For example, the slice-related information may include identification information (Slice group ID) of the slice 45 or a group of slices 45.

The UE connection control unit 130 controls handover (which may also be called cell reselection, transition, etc.) from the serving cell of the UE 200 to another nearby cell. Specifically, the UE connection control unit 130 can perform handover to a nearby cell that meets handover conditions such as quality based on the NRT or ANR function.

In addition, the UE connection control unit 130 performs control regarding the random access procedure (RA procedure) with the UE 200.

The UE connection control unit 130 can receive a report including slice-related information. In this embodiment, the UE connection control unit 130 may configure a receiving unit that receives a report including slice-related information.

The slice-related information included in the report may include information indicating that the slice 45 corresponding to the service requested by UE200 is not supported in the cell selected (or reselected) by UE200 (or may be information about a supported slice).

The control unit 140 controls each functional block that constitutes the gNB 100. In particular, in this embodiment, the control unit 140 can manage (such as generate and update) the neighbor cell association (NCR) of the UE 200 and perform control related to the slice 45 used by the UE 200.

Specifically, the control unit 140 can manage the NCR taking into account the type of slice 45 supported by the cell based on slice-related information received by the ANR function unit 120 from the UE 200.

In addition, the control unit 140 may control handover to a cell that supports the slice 45 requested by the UE 200 based on slice-related information received by the UE connection control unit 130 from the UE 200.

The control unit 140 may exchange information about slices supported by the gNB100 with other radio base stations (gNBs). Specifically, the control unit 140 may share the slice-related information with nodes such as other radio base stations that constitute the NG-RAN20. Specific examples of sharing slice-related information will be described later.

Note that channels include control channels and data channels. Control channels may include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel, which may be Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI)), and Physical Broadcast Channel (PBCH).

Data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), etc. Data may refer to data transmitted via the data channel.

Layer 1 may also be interpreted as including lower layers such as the physical layer. Layer 3 is a layer higher than Layer 1. The higher layers may include at least one of the Radio Link Control layer (RLC), Packet Data Convergence Protocol layer (PDCP), and Radio Resource Control layer (RRC), and the Medium Access Control layer (MAC) may be positioned between the lower layer and the higher layer.

(2.2) UE200
As shown in FIG. 3 , the UE 200 includes a radio communication unit 210 , a connection execution unit 220 , a slice-related information processing unit 230 , and a control unit 240 .

The wireless communication unit 210 transmits uplink signals (UL signals) in accordance with NR. The wireless communication unit 210 also receives uplink signals (DL signals) in accordance with NR.

The connection execution unit 220 executes an RA procedure with the network (gNB100). The connection execution unit 220 also executes a handover from the serving cell to another nearby cell. Specifically, the connection execution unit 220 can execute a handover to a nearby cell that meets handover conditions such as quality based on the NRT or ANR function.

The slice-related information processing unit 230 processes information related to slice 45 (slice-related information).

Specifically, the slice-related information processing unit 230 can transmit neighboring cell information including information about slice 45 to the network. In this embodiment, the slice-related information processing unit 230 may constitute a transmitting unit that transmits neighboring cell information including information about slice 45.

For example, the slice-related information processing unit 230 may transmit neighboring cell information including identification information of a slice (NSSAI: Network Slice Selection Assistance Information) or a group of slices (Slice group ID).

In addition, if the requested slice 45 is not supported in the cell selected by the connection execution unit 220, the slice-related information processing unit 230 may transmit a report to the network including related information (slice-related information) for the slice. In this embodiment, the slice-related information processing unit 230 may constitute a transmitting unit that transmits a report including the slice-related information.

The slice-related information may simply indicate that the requested slice 45 is not supported, or it may indicate the identification information (or Slice group ID) of a supported slice 45.

Slice-related information may be included in a report such as a measurement report (e.g., a logged MDT (Minimization of Drive Test) measurement report, an Immediate MDT measurement report, or a measurement report). However, instead of a measurement report, other reports such as a Failure report (e.g., an RLF report, a connEstFailReport, or a RACH report) may also be used. Furthermore, slice-related information may be composed of, for example, identification information (or Slice group ID) of multiple slices 45 associated with priorities.

After the connection execution unit 220 selects a cell, if a connection is established with that cell or another cell, the slice-related information processing unit 230 may send a specific measurement report (e.g., a logged MDT) including slice-related information to the network.

In addition, the slice 45 requested in the selected cell may be determined based on the slice priority in UE 200.

If a random access procedure (RA procedure) fails, the slice-related information processing unit 230 may transmit a report to the network including information related to the RA procedure. In this embodiment, the slice-related information processing unit 230 may constitute a transmitting unit that transmits a report including information related to the RA procedure (RA procedure-related information).

The RA procedure-related information may include radio resources used to perform the RA procedure. The radio resources may include a 2-step slice-specific RACH resource or a 4-step slice-specific RACH resource. The RACH resource may be interpreted as a radio resource specific to a particular slice 45 (i.e., not used in other slices 45).

The RA procedure related information may also include a fallback from a slice 45-specific RA procedure (slice specific RACH) to a normal RA procedure, and/or a collision between the slice 45-specific RA procedure and the RA procedure of a specific service. Examples of specific services include MPS (Multimedia Priority Service) or MCS (Mission critical service).

The control unit 240 controls each functional block that constitutes the UE 200. In particular, in this embodiment, the control unit 240 controls the association of neighboring cells formed in the vicinity of the serving cell of the UE 200.

The control unit 240 can perform an RA procedure specific to the slice 45 (slice specific RACH). The slice specific RACH may include a two-step RACH and a four-step RACH, as well as a normal RACH.

In a two-step RACH, messages (MSG) A and B (Random Access Preamble, Contention Resolution/Random Access Response (RAR)) may be transmitted and received. In a four-step RACH, MSGs 1 to 4 (Random Access Preamble, Random Access Response, Scheduled Transmission, Contention Resolution) may be transmitted and received.

The control unit 240 can select a cell that supports or does not support slice 45. That is, the control unit 240 may select a cell that supports the type of slice 45 requested by UE 200, or may select a cell that does not support the type of slice 45 requested by UE 200. If the control unit 240 selects a cell that does not support the type of slice 45 requested by UE 200, slice-related information may be transmitted as described above.

In addition, if an RRC connection establishment failure occurs, the control unit 240 may transmit slice-related information about the slice 45 that was attempted to be accessed to the network. The slice-related information may be included in a ConnEstFailureReport, for example.

(3) Operation of the Wireless Communication System Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of an example of operation related to the construction of Self-Organizing Networks (SON) compatible with RAN Slicing.

(3.1) Premise
In RAN Slicing, it is preferable to realize cell reselection taking into account the slice 45 (see FIG. 1 ). Specifically, to support cell reselection taking into account the slice 45, it is necessary to broadcast the slices supported by the cell to the UE 200 in the idle state (RRC).

If the NSSAI is broadcast as is, there will be issues with the size of the system information (SIB: System Information Block) and security. Therefore, it is envisioned that multiple slices 45 of similar types will be managed as the same slice group, and the Slice group ID will be broadcast instead of the NSSAI.

Figure 5 shows an example of the configuration of a slice group. As shown in Figure 5, a slice group may be composed of multiple NSSAIs.

In addition, RAN Slicing assumes the application of slice-specific RACH. Slice-specific RACH reserves individual RACH resources for high-priority slices in a contention-based RACH, avoiding collisions with low-priority or legacy RACHs other than the slice-specific RACH.

For slice-specific RACH, it is desirable to reserve RACH resources in high-priority slices to connect to the network more quickly in URLLC (Ultra-Reliable and Low Latency Communications) services in factories, etc. Specifically, a portion of the contention-based RACH resources is reserved for high-priority slices. This may also be called RACH resource isolation.

Therefore, the following measures are being considered:

- Configure a RACH resource pool for each slice (or slice group) and notify UE200. - Set RACH parameters for each slice (or slice group) in UE200. For example, dedicated RACH parameters (scalingFactorBI and powerRampingStepHighPriority) may be set for high-priority slices.

(3.2) Operational Examples Below, operational examples 1 to 5 related to SON construction compatible with RAN Slicing will be described.

(3.2.1) Operation example 1
The existing ANR function has a problem in that the UE 200 cannot report information about slices supported by a cell. In this operation example, the UE 200 may include information about the slice group ID in a specific information element (e.g., CGIInfoNR) of the RRC layer.

Figure 6 shows an example of a Slice group ID reporting sequence for operation example 1. As shown in Figure 6, UE200 is connected to cell A and can report neighboring cell information. Here, UE200 receives an SIB from cell B via BCCH (Broadcast Control Channel). Cell B may support RAN Slicing.

When UE200 receives an SIB from cell B containing an indication that it supports RAN Slicing, it may include the Slice group ID when reporting neighbor cell information of cell B to cell A (serving cell).

By incorporating the slice group ID into the NRT, it becomes possible to discover and select an appropriate destination cell to support slice 45 used in the source cell.

In addition, information about the slices supported by the cell (slice-related information) may be signaled between nodes that make up the network.

Figure 7 shows an example of signaling of slice-related information between nodes relating to operation example 1. As shown in Figure 7, under the same AMF50, information on the slices supported by each of gNB1 and gNB2, which do not have an Xn link, may be signaled.

Note that the messages used for signaling are just examples, and other messages may be used as long as they are sent and received between the nodes.

(3.2.2) Operation example 2
When UE 200 (re)selects a cell and requests connection, if the cell does not support the slice requested by UE 200, registration fails. In this operation example, such a failure is prevented in advance.

Figure 8 shows an example of a communication sequence related to operation example 2. As shown in Figure 8, UE200 may record that the slice it is attempting to access in the logged MDT is not supported by the cell.

When UE200 next enters the connected state, it may report the cell ID, unsupported slice information, and slice group IDs (or slice group information) supported by the cell to the network via a logged MDT measurement report. This information may be collectively referred to as slice-related information.

The slice to be accessed may be the slice (or list of slices) with the highest slice priority notified from the UE NAS (Non-Access Stratum) to the AS (Access Stratum). Alternatively, in slice-based cell reselection, it may be the slice (or list of slices) with the highest slice priority stored (held) by UE200, or a list of slices stored (held) by UE200.

Slice-based cell reselection may be performed, for example, according to the following procedure:

・Step 0: NAS layer at UE provides slice information to AS layer at UE, including slice priorities.
・Step 1: AS sorts slices in priority order starting with highest priority slice.
・Step 2: Select slices in priority order starting with the highest priority slice.
・Step 3: For the selected slice assign priority to frequencies received from network.
・Step 4: Starting with the highest priority frequency, perform measurements (same as legacy).
・Step 5: If the highest ranked cell is suitable (as defined in 38.304) and supports the selected slice in step 2 then camp on the cell and exit this sequence of operation.
・Step 6: If there are remaining frequencies then go back to step 4.
・Step 7: FFS: If the end of the slice list has not been reached go back to step 2.
・Step 8: Perform legacy cell reselection.

(3.2.3) Operation example 3
When the UE 200 executes the RRC setup, if a connection establishment failure (timer T300 expires) occurs, the UE 200 may be unable to report to the network information about the slice that the UE 200 is attempting to access in the cell. In this operation example, the UE 200 reports such slice information to the network.

Figure 9 shows an example of a communication sequence related to operation example 3. As shown in Figure 9, when a connection establishment failure occurs (timer T300 expires), UE200 may include information (NSSAI) of the slice to be accessed in ConnEstFailureReport.

Note that ConnEstFailureReport is just one example, and other reports (which may be dedicated reports or may be included in other reports such as Radio Link Failure (RLF)) can be used as long as they can report information about the slice in question.

For example, if UE200 attempts to access a high priority slice but a connection establishment failure occurs, this is an important event for the operator of the wireless communication system 10 and can be useful information for improving the quality of the area including the cell in question.

(3.2.4) Operation example 4
If the target cell at the handover destination cannot support the slice used in the source cell at the time of handover of UE 200, slice remapping may be considered.

Slice remapping may mean that during handover of UE200, the slice mapped by the source cell (source node) is mapped to a different slice because the slice is not supported by the target cell (target node).

However, if slice remapping fails (is impossible), there is a problem in that the reason (failure cause) cannot be notified to the source cell (source node) (the same applies to dual connectivity settings). In this operation example, the reason for the slice remapping failure may be notified to the source node using a specific message.

Figure 10 shows an example sequence of slice remapping related to operation example 4 (Slice re-mapping decided by T-gNB (example 1)).

Figure 11 shows an example sequence of slice remapping related to operation example 4 (Slice re-mapping decided by T-gNB (example 2)).

Figure 12 shows an example sequence of slice remapping for operation example 4 (Slice re-mapping decided by AMF and T-gNB).

Figure 13 shows an example sequence of slice remapping (Slice re-mapping decided by SN) for operation example 4.

In the case of Xn handover, if the target node cannot support some or all of the slices (or list of slices) in the PDU session resource to be setup list included in the HO request msg. sent from the source node and the target node (T-gNB) decides to perform slice remapping, the following information may be notified to the source node:

-If the slice (or list of slices) can be remapped to another slice (or list of slices), notify the source node of this.

-If slice remapping fails, notify the source node of the slice (or list of slices) that could not be remapped and the reason for the slice remapping failure.

-In the case of NG handover, if the source node cannot support some or all of the slices in the PDU Session Resource List included in the handover required msg. from the source node to the AMF and the AMF or target node decides to perform slice remapping, the following information may be notified to the source node:

- If the slice (or list of slices) can be remapped to another slice (or list of slices), notify the source node of the remapping.

-If slice remapping fails, notify the source node of the slice (or list of slices) that could not be remapped and the reason for the slice remapping failure.

-In the case of SN addition, if the MN cannot support some or all of the slices in the PDU session resource to be added list included in the SN addition request and the SN decides to perform slice remapping, the following information may be notified to the source node:

-If the slice (or list of slices) can be remapped to another slice (or list of slices), notify the MN of this.

-If slice remapping fails, notify the MN of the slice (or list of slices) that could not be remapped and the reason for the slice remapping failure.

The above-mentioned notification content may be included in the message for the source node (S-gNB) shown in Figures 10 to 13 (in Figures 10 to 13, potentially relevant messages are indicated with an *).

(3.2.5) Operational Example 5
If a slice-specific RACH fails, appropriate RA procedure-related information needs to be included in a RACH report and reported to the network. In this operation example, if a slice-specific RACH fails, a RACH report including RA procedure-related information associated with the failure may be reported to the network.

Figure 14 shows an example of a communication sequence related to operation example 5. As shown in Figure 14, if a slice-specific RACH fails, the RACH report may report RA procedure related information including at least any of the following:

・Used 2-step slice specific RACH resource
・Used 4-step slice specific RACH resource
- scalingFactorBI and slice specific powerRampingStepHighPriority setting value - Number of times power ramping has been performed For example, this may be the number of times PREAMBLE_POWER_RAMPING_COUNTER has been incremented.

- Slice ID (NSSAI) or Slice group ID that UE 200 is trying to access
Information about the slice groups supported by the cell may be included in the RACH report.

-Indication of whether or not fallback has occurred from the 2-step slice specific RACH to the Legacy 4-step common RACH
- Indication of whether there was a collision with MPS/MCS based RACH
In the event of a collision with MPS/MCS based RACH, indicates whether slice specific RACH or MPS/MCS based RACH is prioritized.

(4) Actions and Effects According to the above-described embodiment, the following actions and effects can be obtained. According to the gNB 100 and the UE 200, the following actions and effects can be obtained.

- By including the Slice group ID in the ANR function and incorporating slice information into the NRT, it is possible to select an appropriate destination cell according to the slice used on the source cell (source node) side.

- If the slice that UE200 is attempting to access is not supported by the serving cell, reporting this information to the network can help optimize slice support in the area.

- The occurrence of a connection establishment failure when UE200 attempts to access a high priority slice during RRC setup is an important event for the operator of the wireless communication system 10, and therefore provides useful information for improving the quality of the area including the cell in question.

- When UE200 is handed over, the target cell cannot support the slice used in the source cell, and information indicating whether slice remapping was possible is notified to the source node, which provides information that is useful for maintaining service continuity through handover.

- Helps optimize parameter settings for slice-specific RACH by reporting a RACH report to the network containing RA procedure-related information regarding slice-specific RACH failures.

(5) Other Embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and that various modifications and improvements are possible.

For example, in the above-described embodiment, the term "slice" was used, but as mentioned above, a slice is a logical (virtual) network divided into service units such as use cases or business models, and such a network may be called by a different name.

In addition, in the above description, the words configure, activate, update, indicate, enable, specify, and select may be read as interchangeable. Similarly, the words link, associate, correspond, and map may be read as interchangeable, and the words allocate, assign, monitor, and map may also be read as interchangeable.

Furthermore, specific, dedicated, UE-specific, and UE-individual may be read as interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be read as interchangeable.

In this disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," and "panel" may be used interchangeably.

Furthermore, the block diagrams (Figures 2 and 3) used to explain the above-mentioned embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and/or software. Furthermore, there are no particular limitations on the method for realizing each functional block. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (e.g., using wires, wirelessly, etc.) and these multiple devices. A functional block may also be realized by combining software with the single device or multiple devices.

Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission functions is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

Furthermore, the above-mentioned gNB100 and UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 15 is a diagram showing an example of the hardware configuration of the device. As shown in Figure 15, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.

In the following explanation, the term "apparatus" can be interpreted as a circuit, device, unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the devices shown in the figure, or may be configured to exclude some of the devices.

Each functional block of the device (see Figure 2.3) is realized by any hardware element of the computer device or a combination of such hardware elements.

In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including interfaces with peripheral devices, a control unit, an arithmetic unit, registers, etc.

The processor 1001 also 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 in accordance with these. The program used is a program that causes a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above may be executed by a single processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

Memory 1002 is a computer-readable recording medium and may be composed of, for example, at least one of Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be referred to as a register, cache, main memory, etc. Memory 1002 can store a program (program code), software module, etc. that can execute a method according to one embodiment of the present disclosure.

Storage 1003 is a computer-readable recording medium and may be composed of, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray® disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

The communication device 1004 is hardware (transmitting/receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, network controller, network card, or communication module.

The communication device 1004 may be configured to include high-frequency switches, duplexers, filters, frequency synthesizers, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

The input device 1005 is an input device (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, speaker, LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

Furthermore, each device such as the processor 1001 and memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

Furthermore, the notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

Each aspect/embodiment described in this disclosure may be applied to at least one of systems using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, multiple systems may be combined (e.g., a combination of at least one of LTE and LTE-A with 5G).

The order of the procedures, sequences, flowcharts, etc. of each aspect/embodiment described in this disclosure may be changed unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

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 may be performed by at least one of the base station and another network node other than the base station (such as, but not limited to, an MME or S-GW). While the above example illustrates a case where there is one other network node other than the base station, a combination of multiple other network nodes (e.g., an MME and an S-GW) may also be used.

Information, signals (information, etc.) may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

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. Output information may be deleted. Input information may be sent to another device.

The determination may be made based on a value represented by a single bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched between depending on the implementation. Furthermore, notification of specified information (e.g., notification that "X is true") is not limited to being done explicitly, but may also be done implicitly (e.g., not notifying the specified information).

Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Software, instructions, information, etc. may also be transmitted or received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave), these wired and/or wireless technologies are included within the definition of transmission media.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

Furthermore, the information, parameters, etc. described in this disclosure may be expressed using absolute values, relative values from a predetermined value, or other corresponding information. For example, radio resources may be indicated by an index.

The names used for the parameters described above are not intended to be limiting in any way. Furthermore, the mathematical formulas, etc. using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

In this disclosure, terms such as "base station (BS)," "radio 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.

A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the base station's overall coverage area can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

The terms "cell" or "sector" refer to part or all of the coverage area of a base station and/or a base station subsystem that provides communication services within that coverage area.

In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

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 suitable terminology.

At least one of the base station and the mobile station may be referred to as 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, or the mobile body itself. 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 also be a device that does not necessarily move during communication operations. 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.

Furthermore, the base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, each aspect/embodiment of the present 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 be configured to have the functions possessed by a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as uplink channel and downlink channel may be read as side channel.

Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.
A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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.

Numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology may indicate, 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 structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on numerology.

A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Other names may also be used for radio frame, subframe, slot, minislot, and symbol.

For example, one subframe may be referred to as a transmission time interval (TTI), multiple consecutive subframes may be referred to as a TTI, or one slot or one minislot may be referred to as a TTI. In other words, at least one of the subframe and the 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 referred to as a slot, minislot, etc. instead of a subframe.

Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. However, the definition of TTI is not limited to this.

The TTI may be a transmission time unit for a channel-coded data packet (transport block), code block, code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which the transport block, code block, code word, etc. is actually mapped may be shorter than the TTI.

Note that when one slot or one minislot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the smallest time unit for scheduling. Furthermore, the number of slots (minislots) that make up the smallest time unit for scheduling may be controlled.

A TTI with a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be referred to as a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

Furthermore, the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each consist of one or more resource blocks.

In addition, one or more RBs may also be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

A resource block may also be composed of one or more resource elements (REs). For example, one RE may be a radio resource area of one subcarrier and one symbol.

A Bandwidth Part (BWP) (which may also be referred to as a partial bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point for that carrier. PRBs may be defined in a given BWP and numbered within that BWP.

BWPs may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.

At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside of the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

The above-described structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio 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, as well as the number of symbols within a TTI, symbol length, and cyclic prefix (CP) length can be varied in various ways.

The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and/or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

The reference signal may also be abbreviated as Reference Signal (RS) or may be called a pilot depending on the applicable standard.

As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

In this disclosure, where articles are added by translation, such as a, an, and the in English, this disclosure may include the noun following these articles being plural.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching a table, database, or other data structure), and ascertaining something that is considered a "determination." Also, "determining" and "determining" may include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and other actions that are considered a "determination." Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

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 "combined" may also be interpreted in the same way as "different."

Figure 16 shows an example configuration of vehicle 2001. As shown in Figure 16, vehicle 2001 is equipped with 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.

The drive unit 2002 is composed 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 is composed of a microprocessor 2031, memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2027 provided in the vehicle. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

Signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the motor current, a front and rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front and rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

The information service unit 2012 is composed of various devices, such as a car navigation system, audio system, speakers, television, and radio, that provide various types of information such as driving information, traffic information, and entertainment information, as well as one or more ECUs that control these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

The driving assistance system unit 2030 is composed of various devices that provide functions to prevent accidents and reduce the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the 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, axles 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, all of which are provided on the vehicle 2001.

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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, etc.

The communication module 2013 transmits, via wireless communication, current signals from the current sensors input to the electronic control unit 2010 to external devices. The communication module 2013 also transmits, via wireless communication, to external devices, signals input to the electronic control unit 2010, such as front and rear wheel rotation speed signals acquired by the rotation speed sensor 2022, front and rear wheel air pressure signals acquired by the air pressure sensor 2023, vehicle speed signals acquired by the vehicle speed sensor 2024, acceleration signals acquired by the acceleration sensor 2025, accelerator pedal depression amount signals acquired by the accelerator pedal sensor 2029, brake pedal depression amount signals acquired by the brake pedal sensor 2026, shift lever operation signals acquired by the shift lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by the object detection sensor 2028.

The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from external devices in memory 2032 that can be used by 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, and the like provided in the vehicle 2001.

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 can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

10. Wireless communication systems
20 NG-RAN
40 Core Network
45 slices
50 AMF
100 gNB
110 Radio Communication Department
120 ANR Functional Section
130 UE connection control unit
140 Control Unit
200 UE
210 Radio Communication Department
220 Connection Execution Unit
230 Slice-related information processing section
240 Control Unit
1001 processor
1002 memory
1003 Storage
1004 Communication equipment
1005 Input Device
1006 Output Device
1007 Bus
2001 Vehicle
2002 Drive unit
2003 Steering Section
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 RPM Sensor
2023 Air Pressure Sensor
2024 Vehicle speed sensor
2025 Acceleration Sensor
2026 Brake pedal sensor
2027 Shift lever sensor
2028 Object Detection Sensor
2029 Accelerator pedal sensor
2030 Driving Assistance Systems Department
2031 microprocessor
2032 memory (ROM, RAM)
2033 communication port

Claims (5)

a control unit that controls association of neighboring cells;
a transmitter that transmits, to the network, neighboring cell information including information on slices into which the network is divided in specific units;
The neighboring cell information includes, in cell selection, information on the cell and the slice that is not supported when the slice to be accessed is not supported by the cell. The terminal according to claim 1, wherein the transmitter transmits the neighboring cell information including identification information of the slice or the group of slices. A wireless communication system including a terminal and a wireless base station,
The terminal
a control unit that controls association of neighboring cells;
a transmitter that transmits, to the network, neighboring cell information including information on slices into which the network is divided in specific units;
the radio base station includes a receiving unit that receives the neighboring cell information,
A wireless communication system in which the neighboring cell information includes information on the cell and the slice that is not supported when the slice to be accessed is not supported by the cell during cell selection. The wireless communication system described in claim 3, wherein the wireless base station includes a control unit that exchanges information about the slices supported by the wireless base station with other wireless base stations. a terminal controlling association of neighboring cells;
A step in which the terminal transmits neighboring cell information to the network, the neighboring cell information including information on slices into which the network is divided in specific units;
the network receiving the neighboring cell information;
A wireless communication method in which the neighboring cell information includes information on the cell and the slice that is not supported when a slice to be accessed is not supported by the cell during cell selection.