Service node

Abstract

This service node comprises: a control unit for controlling communication with another service node connected to service nodes that are units for providing a service in a radio access network divided into units of the service; and a transmission unit for transmitting identifiers to the other service node. At least one of the service node and the other service node includes a control service node in which a control plane of a central device for centrally controlling the radio access network is divided into units. The transmission unit transmits, as the identifiers, a first identifier whereby the service node identifies a terminal and a second identifier whereby the other service node identifies the terminal.

Description

Service Node

[0001] The present disclosure relates to a service node that provides services in an SBA based RAN.

[0002] The 3rd Generation Partnership Project (3GPP (registered trademark)) has specified the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also working on specifications for next-generation mobile communication systems called Beyond 5G, 5G Evolution, or 6G.

[0003] The 5G core network (5GC) is based on a service-based architecture (SBA). That is, the 5GC network functions are divided into service units (e.g., Access and Mobility Management Function (AMF), Session Management Function (SMF)). This SBA allows the 5GC to flexibly change its configuration.

[0004] On the other hand, the 5G radio access network (5G RAN) is configured so that nodes are connected peer-to-peer (p2p) rather than SBA. In such a configuration, the network functions realized by the nodes tend to depend on the hardware configuration. Therefore, when adopting new network functions in the 5G RAN, it is necessary to maintain backward compatibility with existing network functions. This configuration has made the 5G RAN expensive and difficult to flexibly change its configuration. Therefore, the adoption of an SBA-based RAN for 6G is being considered (Non-Patent Document 1).

[0005] N. Li et al., “Micro-service-based radio access network”, China Communications, vol. 19, no. 3, pp. 1-15, March 2022

[0006] In SBA-based RAN, it is conceivable to divide at least some of the existing nodes (e.g., Distributed Unit (DU), Central Unit-Control Plane (CU-CP), Central Unit-User Plane (CU-UP)) constituting a base station (hereinafter also referred to as gNodeB (gNB)) into service units. Hereinafter, each unit into which a node is divided into service units is also referred to as a service node or entity. Note that when some existing nodes are divided into service nodes and other nodes are not divided, the other nodes may be interpreted as service nodes.

[0007] When an existing node is divided into multiple service nodes, for example, it becomes necessary to newly define an identifier (UE ID) for a terminal (hereinafter also referred to as user equipment (UE)) connected to the RAN between the service nodes. However, since the existing UE ID identifies the same UE between nodes and is included in messages for the node-to-node interface, it is difficult to reuse it for identifying UEs between service nodes. In particular, when the CU-CP is divided, it is expected that there will be a large number of service nodes due to the diversity of their functions, so identifying UEs between service nodes may become a priority issue in realizing 6G RAN.

[0008] Furthermore, when an existing node is divided into multiple service nodes, it is likely that new service instances between the service nodes will also need to be defined. A service instance is the entity that provides a service, and in this case, it refers to the protocol that realizes the service. For example, a service instance between nodes is an interface between nodes such as XnAP or F1AP. Information identifying a service instance between nodes (service instance ID) was also included in messages for the interface between nodes, making it difficult to use it to identify service instances between service nodes.

[0009] Furthermore, in RAN sharing, where RANs are shared among carriers, when a user changes carriers, the RAN must also recognize that the user is changing carriers. A carrier is identified by the identifier (PLMN ID) of the network (Public Land Mobile Network, PLMN) provided by the carrier. Therefore, changing a carrier in RAN sharing involves changing the PLMN ID. Therefore, the RAN must recognize the identifiers of the PLMNs from which the UE is moving (source PLMN ID) and the identifiers of the PLMNs to which the UE is moving (target PLMN ID).

[0010] Even in such a situation, when an existing node is divided into multiple service nodes, it becomes necessary to share the source PLMN ID and the target PLMN ID between the service nodes constituting the RAN. However, for the same reasons as those for identifying UEs and service instances described above, it has been difficult to reuse the mechanism for sharing the source PLMN ID and the target PLMN ID between nodes between service nodes.

[0011] Therefore, the present disclosure aims to provide a service node that can identify UEs, service instances, and networks provided by a telecommunications carrier between service nodes, even when an existing node is divided into multiple service nodes.

[0012] One aspect of the disclosure is a service node that, in a radio access network divided into service units, comprises: a control unit (control unit 170) that controls communication with other service nodes connected to a service node that is a unit for providing the service; and a transmission unit (radio signal transmission / reception unit 110) that transmits an identifier to the other service node, wherein at least one of the service node and the other service node includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided into service units, and the transmission unit transmits, as the identifier, a first identifier by which the service node identifies a terminal and a second identifier by which the other service node identifies the terminal.

[0013] One aspect of the disclosure is a service node that, in a radio access network divided into service units, comprises a control unit (control unit 170) that controls communication with other service nodes connected to a service node that is a unit for providing the service, and a transmission unit (radio signal transmission / reception unit 110) that transmits an identifier to the other service node, wherein at least one of the service node and the other service node includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided into service units, and the transmission unit transmits, as the identifier, an identifier of an interface used for the communication.

[0014] One aspect of the disclosure is a service node that, in a radio access network divided on a service-by-service basis, comprises: a control unit (control unit 170) that controls communication with other service nodes connected to a service node that is a unit for providing the service; and a transmission unit (radio signal transmission / reception unit 110) that transmits an identifier to the other service node, wherein at least one of the service node and the other service node includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided on a service-by-service basis, and the transmission unit transmits, as the identifier, an identifier of a network provided by a telecommunications carrier from which a terminal is to be transferred and an identifier of a network provided by a telecommunications carrier to which the terminal is to be transferred.

[0015] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system. FIG. 2 is a diagram showing frequency ranges used in the wireless communication system. FIG. 3 is a diagram showing example configurations of radio frames, subframes, slots, and symbols used in the wireless communication system. FIG. 4 is a functional block diagram of a base station (service node). FIG. 5 is a functional block diagram of a terminal. FIG. 6 is a diagram showing example configurations of an SBA-based RAN and CN. FIG. 7 is a diagram showing another example configuration of an SBA-based RAN and CN. FIG. 8 is a diagram showing transmission and reception of a terminal identifier between service nodes (entities). FIG. 9 is a diagram showing transmission and reception of a communication interface identifier between service nodes (entities). FIG. 10 is a diagram showing transmission and reception of a PLMN identifier between service nodes (entities). FIG. 11 is a diagram showing an example hardware configuration of a base station and a terminal. FIG. 12 is a diagram showing an example configuration of a vehicle.

[0016] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0017] (1) Configuration of Wireless Communication System The wireless communication system 10 shown in Fig. 1 is a wireless communication system conforming to a method called 5G. Alternatively, the wireless communication system 10 may be a wireless communication system conforming to a method called Beyond 5G, 5G Evolution, or 6G.

[0018] The wireless communication system 10 can support Massive Multiple-Input Multiple-Output (Massive MIMO), which generates more directional beams by controlling wireless signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which uses multiple component carriers (CCs) as a bundle, and Dual Connectivity (DC), which enables simultaneous communication with two base stations.

[0019] As shown in FIG. 1 , the wireless communication system 10 includes a Radio Access Network (RAN) 20, a base station 100 (hereinafter also referred to as a gNodeB (gNB) 100) connected to the RAN 20, and a terminal 200 (hereinafter also referred to as a user equipment (UE) 200) that performs wireless communication with the gNB 100. The RAN 20 is connected to a core network (CN) 30. The RAN 20 and the CN 30 may be simply referred to as a "network." The gNB 100 may also be considered to be included in the RAN 20. Note that the specific configuration of the wireless communication system 10, for example, the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG. 1 .

[0020] The gNB 100 may be a base station in a Centralized-Radio Access Network (C-RAN) configuration that includes a distributed unit (DU) having a function for connecting to the UE 200 and a central unit (CU) having a function for connecting to the network. In this case, the CU may be further divided into a control plane (CU-CP) and a user plane (CU-UP).

[0021] The RAN 20 (specifically, the gNB 100 constituting the RAN 20) may be divided into service units provided by the RAN 20. For example, if the gNB 100 is composed of the existing nodes of the above-mentioned DU, CU-CP, and CU-UP, the CU-CP may be divided into N service units, resulting in CU-CP 1, CU-CP 2, ..., CU-CP N (see Figures 6 and 7). Furthermore, the node divided into service units is not limited to the CU-CP, but may also be a CU-UP or a DU. In this case, each service unit may be called a service node.

[0022] In addition, when some existing nodes are divided into service nodes but other nodes are not divided, the other nodes may be interpreted as service nodes. For example, when a CU-CP is divided into N service nodes, CU-CP 1, CU-CP 2, ..., CU-CP N, the DU and CU-UP may be existing nodes and service nodes at the same time.

[0023] The service node may be called an entity. Also, the service node may be called a subnode, in consideration of the fact that it is a lower node when each of the DU, CU-CP, and CU-UP is considered as a node. Alternatively, the service node may be called a function or a network function, following the SBA in the 5G CN.

[0024] The wireless communication system 10 may also support multiple frequency ranges (FR). That is, as shown in Fig. 2, the wireless communication system 10 may support the following FRs: FR1: 410 MHz to 7.125 GHz FR2-1: 24.25 GHz to 52.6 GHz FR2-2: Over 52.6 GHz to 71 GHz

[0025] In FR1, a subcarrier spacing (SCS) of 15, 30, or 60 kHz and a bandwidth (BW) of 5 to 100 MHz may be used, while in FR2-1, an SCS of 60 or 120 kHz (including 240 kHz) and a BW of 50 to 400 MHz may be used.

[0026] In FR2-2, to avoid an increase in phase noise, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) or Discrete Fourier Transform-Spread-Orthogonal Frequency Division Multiplexing (DFT-S-OFDM) with a larger SCS may be applied.

[0027] 3, one slot in the wireless communication system 10 is composed of 14 symbols. If this configuration is maintained, the larger (wider) the SCS, the shorter the symbol period (and slot period). Note that the SCS is not limited to the frequencies shown in FIG. 3 and may be, for example, 480 kHz, 960 kHz, or other frequencies.

[0028] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14, but may be, for example, 28 or 56. Furthermore, the number of slots per subframe may differ depending on the SCS.

[0029] (2) Functional block configuration of wireless communication system (2.1) Functional block configuration of base station As shown in Figure 4, the gNB 100 includes a wireless signal transceiver unit 110, an amplifier unit 120, a modulation / demodulation unit 130, a control signal / reference signal processing unit 140, an encoding / decoding unit 150, a data transceiver unit 160, and a control unit 170.

[0030] In the following description, each component of the gNB100 is assumed to be a component of a service node obtained by dividing the nodes constituting the gNB100, such as the DU, CU-CP, and CU-UP, on a service-by-service basis. Hereinafter, as an example, the control plane of the CU-CP, i.e., the central device that centrally controls the RAN20, is assumed to be divided on a service-by-service basis, and the DU and CU-UP are not divided. Furthermore, a service node obtained by dividing a CU-CP is also referred to as a control service node. As described above, if only some of the nodes constituting the gNB100 are divided on a service-by-service basis, the other nodes can be considered service nodes, and so the service nodes constituting the gNB100 are the DU, CU-CP 1, CU-CP 2, ..., CU-CP N, and CU-UP.

[0031] As described above, one service node constituting the gNB 100 may or may not include a control service node. In the latter case, one of the other service nodes constituting the gNB 100 becomes the control service node. That is, at least one of the service node or the other service node includes a control service node.

[0032] The radio signal transmitting / receiving unit 110 transmits and receives radio signals to and from the UE 200. The radio signal transmitting / receiving unit 110 may be configured with a transmitting unit that transmits radio signals to the UE 200 and a receiving unit that receives radio signals from the UE 200. The radio signals may include data or may be interpreted as data. Transmission may be interpreted as configuration, instruction, notification, etc. Reception may be interpreted as (reported), notification, etc. Note that configuration may be realized by configuration information (information element (IE)) of a radio resource control (RRC) layer, and instruction may be realized by a control element (CE) or downlink control information (DCI) of a medium access control (MAC) layer.

[0033] The radio signal transmitting / receiving unit 110 of the embodiment may transmit an identifier to another service node. The identifier may be a UE ID that identifies the UE 200 within the service node. That is, the radio signal transmitting / receiving unit 110 may transmit, as the identifier, an identifier by which the service node configured by the radio signal transmitting / receiving unit 110 identifies the UE 200 (hereinafter also referred to as a first identifier) ​​and an identifier by which the other service node identifies the UE 200 (hereinafter also referred to as a second identifier).

[0034] The wireless signal transceiver 110 of the embodiment may transmit another identifier to another service node. In this case, the identifier may be an identifier of an interface used for communication with another service node or the CN 30 (specifically, a function in the CN 30, such as an AMF). The interface identifier may refer to a protocol used for communication. The interface identifier may also be called a service instance identifier.

[0035] The radio signal transceiver 110 according to the embodiment may transmit other identifiers to other service nodes. In this case, the identifiers may be the identifier of the source PLMN of the UE 200 (source PLMN ID) and the identifier of the destination PLMN of the UE 200 (target PLMN ID).

[0036] The radio signal transmitting and receiving unit 110 of the embodiment may transmit the above-mentioned identifiers, that is, the first identifier and the second identifier, to the CN 30 connected to the RAN 20 .

[0037] The radio signal transceiver 110 according to the embodiment may transmit identifiers, i.e., the first identifier and the second identifier, used for scheduling configuration of the UE 200. In this case, the identifiers may be, for example, Configured Scheduling-Radio Network Temporary Identifiers (CS-RNTIs).

[0038] The amplifier unit 120 is configured by a power amplifier (PA) / low noise amplifier (LNA), etc. The amplifier unit 120 amplifies the radio signal output from the radio signal transmitting / receiving unit 110. The amplifier unit 120 also amplifies the radio signal output from the modulation / demodulation unit 130.

[0039] The modem unit 130 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (UE 200 or another UE). CP-OFDM / DFT-S-OFDM may be applied to the modem unit 130. Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0040] The control signal and reference signal processor 140 performs processing related to control signals transmitted and received between the UE 200, such as radio resource control (RRC) signaling.

[0041] The control signal / reference signal processing unit 140 performs processing related to reference signals transmitted and received between the UE 200, such as a Demodulation Reference Signal (DMRS), a Phase Tracking Reference Signal (PTRS), a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS).

[0042] The channels include control channels and data channels. The control channels include a physical uplink control channel (PUCCH), a physical downlink control channel (PDCCH), a physical random access channel (PRACH), a physical broadcast channel (PBCH), etc. The data channels include a physical uplink shared channel (PUSCH), a physical downlink shared channel (PDSCH), etc.

[0043] The encoding / decoding unit 150 performs division / concatenation and coding / decoding of data included in a radio signal for each predetermined communication destination (UE 200 or another UE).

[0044] Specifically, the encoding / decoding unit 150 decodes the data output from the modem unit 130 and concatenates the decoded data. In addition, the encoding / decoding unit 150 divides the data output from the data transmitter / receiver 160 into pieces of a predetermined size and performs coding on the divided data.

[0045] The data transmitter / receiver 160 assembles and disassembles data units (Protocol Data Units (PDUs) / Service Data Units (SDUs)) that make up data between each layer. The multiple layers include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer. The data transmitter / receiver 160 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (HARQ).

[0046] The control unit 170 controls the gNB 100. The control unit 170 controls, for example, the transmission and reception of radio signals by the radio signal transmission and reception unit 110, the amplification by the amplifier unit 120, the data modulation / demodulation by the modem unit 130, the signal processing by the control signal and reference signal processing unit 140, the coding / decoding by the encoding / decoding unit 150, and the assembly / disassembly of data units by the data transmission and reception unit 160. The control unit 170 also performs scheduling for the UE 200.

[0047] The control unit 170 of the embodiment controls communication with other service nodes connected to the service node that it configures in the RAN 20, which is divided into service units. Note that the service node and other service nodes may be considered as units that provide services in the RAN 20, which is divided into service units.

[0048] (2.2) Functional Block Configuration of Terminal As shown in FIG. 5, the UE 200 includes a radio signal transmitting / receiving unit 210 and a control unit 220.

[0049] The radio signal transceiver 210 transmits and receives radio signals to and from the gNB 100. The radio signal transceiver 210 may be configured with a transmitter that transmits radio signals to the gNB 100 and a receiver that receives radio signals from the gNB 100. The radio signals may include data or may be interpreted as data. Transmission may be interpreted as report, notification, etc. Reception may be interpreted as (configured), (instructed), (notified), etc. Note that configuration may be realized by configuration information (information element (IE)) of the radio resource control (RRC) layer, and instruction may be realized by a control element (CE) or downlink control information (DCI) of the medium access control (MAC) layer.

[0050] The control unit 220 controls the UE 200. The control unit 220 controls, for example, the transmission and reception of radio signals by the radio signal transmission and reception unit 210.

[0051] (2.3) Service-based architecture (SBA) As shown in Fig. 6, in SBA, the nodes (DU, CU-CP, CU-UP) constituting the RAN 20 may be divided into service units. Here, the CU-CP is divided into N service units, which are designated as CU-UP 1, CU-CP 2, ..., CU-CP N. On the other hand, the nodes divided into service units are not limited to CU-CPs, and may be CU-UPs or DUs.

[0052] 7, in a 6G RAN based on SBA, the CU-CP may be included in the CN among the nodes constituting the RAN 20. Even in this case, the CU-CP may be divided into N service units.

[0053] (3) Operation of the wireless communication system (3.1) Issues (3.1.1) Issue 1 When an existing node is divided into multiple service nodes, for example, it becomes necessary to newly define an identifier (UE ID) for the UE connecting to the RAN between service nodes. However, since the existing UE ID identifies the same UE between nodes and is included in messages for the interface between nodes, it is difficult to reuse it for identifying UE between service nodes. In particular, when the CU-CP is divided, it is expected that there will be a large number of service nodes due to the diversity of their functions, so identifying UE between service nodes may become a priority issue in realizing 6G RAN.

[0054] (3.1.2) Issue 2: Furthermore, when an existing node is divided into multiple service nodes, it is likely that it will also be necessary to newly define service instances between service nodes. A service instance is the entity that provides a service, and in this case, it means the protocol that realizes the service. For example, a service instance between nodes is an interface between nodes such as XnAP or F1AP. Since information identifying a service instance between nodes (service instance ID) was also included in messages for the interface between nodes, it was difficult to use it to identify service instances between service nodes.

[0055] (3.1.3) Issue 3 Furthermore, in RAN sharing, where RANs are shared between carriers, when a user changes carriers, the RAN must also recognize that the user is changing carriers. A carrier is identified by the identifier (PLMN ID) of the network (Public Land Mobile Network, PLMN) provided by that carrier. Therefore, changing a carrier in RAN sharing involves changing the PLMN ID. Therefore, the RAN must recognize the identifiers of the PLMNs from which the UE is moving (source PLMN ID) and the identifiers of the PLMNs to which the UE is moving (target PLMN ID).

[0056] Even in such a situation, when an existing node is divided into multiple service nodes, it becomes necessary to share the source PLMN ID and the target PLMN ID between the service nodes constituting the RAN. However, for the same reasons as those for identifying UEs and service instances described above, it has been difficult to reuse the mechanism for sharing the source PLMN ID and the target PLMN ID between nodes between service nodes.

[0057] (3.2) Operational Examples (3.2.1) Operational Example 1 Operational example 1 will be described with reference to Fig. 8. In operation example 1, an identifier of UE 200 is transmitted and received between subnodes in the RAN or between a subnode in the RAN and a function in the CN (e.g., LMF). Note that, hereinafter, a subnode in the RAN or a function in the CN is also referred to as an entity.

[0058] As shown in Fig. 8, one entity (Entity 1 in the figure) transmits a service based interface (SBI) message to another entity (Entity 2 in the figure). The SBI message is, for example, a setup request message, a setup response message, a modification request message, or a modification response message of an xx (xx is an arbitrary name) interface. The SBI message may include one or more UE IDs in the header or message body.

[0059] <When UE ID is transmitted and received between subnodes within a RAN> The UE ID is, for example, a Cell-Radio Network Temporary Identifier (C-RNTI), a Configured Scheduling RNTI (CS-RNTI), a Subscription Permanent Identifier (SUPI), a UE context management entity ID, a mobility entity ID (RRM entity ID), an RRC entity ID, a radio bearer management entity ID, a paging entity ID, a Self-Organizing Network entity ID (SON entity ID), an Artificial Intelligence / Machine Learning entity ID (AIML entity ID), a CU-CP entity ID, a CU-UP entity ID, or a DU entity ID.

[0060] For example, when one entity is a mobility entity (RRM entity) and the other entity is a SON entity, the RRM entity may include an RRM entity ID, by which the RRM entity identifies UE 200, and a SON entity ID, by which the SON entity identifies UE 200, in the header or body of the above-mentioned SBI message and transmit the SBI message to the SON entity. Note that the SON entity may be read as a data collection entity.

[0061] <When transmitting and receiving a UE ID between a subnode in the RAN and a function in the CN> The UE ID is, for example, a C-RNTI, CS-RNTI, SUPI, UE context management entity ID, mobility entity ID (RRM entity ID), RRC entity ID, radio bearer management entity ID, paging entity ID, SON entity ID, AIML entity ID, CU-CP entity ID, CU-UP entity ID, DU entity ID, AMF ID, SMF ID, NWDAP ID, LMF ID, NEF ID, NRF ID, PCF ID, UDM ID, or UCMF ID.

[0062] For example, if one entity is a mobility entity (RRM entity) in the RAN and the other entity is an LMF entity in the CN, the RRM entity may include an RRM entity ID by which the RRM entity identifies UE 200 and an LMF entity ID by which the LMF entity identifies UE 200 in the header or body of the above-mentioned SBI message and transmit them to the LMF entity.

[0063] Furthermore, the above-mentioned UE ID may be transmitted from an entity in the CN to an entity in the RAN. In this case, the entity in the CN (e.g., the LMF entity) may assign a temporary identifier to the SUPI as the LMF ID and use the temporary identifier. This allows the LMF entity to avoid using the SUPI as the LMF ID, thereby reducing security risks compared to when the SUPI is transmitted to the RAN as the LMF ID.

[0064] Furthermore, an LMF entity may use, as an LMF ID, a combination of the temporary identifier assigned to the SUPI as described above and the ID of the LMF instance. For example, if an LMF instance that realizes an LMF entity fails and another LMF instance replaces this LMF instance (assuming that the LMF entity is implemented using multiple stateless instances and one data storage), the other LMF instance can use the ID of the failed LMF instance as a guide to find the context that was linked with the RAN before the failure.

[0065] (3.2.2) Operation Example 2 Operation Example 2 will be described with reference to Fig. 9. Operation Example 2 involves transmitting and receiving an identifier (service instance ID) of a service instance used between subnodes in the RAN or between a subnode in the RAN and a function in the CN, specifically, an identifier of a protocol (connection interface). Note that, hereinafter, a subnode in the RAN or a function in the CN is also referred to as an entity.

[0066] As shown in Fig. 9, one entity (Entity 1 in the figure) sends an SBI message to another entity (Entity 2 in the figure). The SBI message is, for example, a setup request message, a setup response message, a modification request message, or a modification response message for the xx (xx is an arbitrary name) interface. The SBI message may include a service instance ID in the header or message body.

[0067] <When a service instance ID is transmitted and received between subnodes in a RAN> The service instance ID may be, for example, an identifier that has a role similar to that of an XnAP ID or F1AP ID used in a 5G RAN.

[0068] <When transmitting and receiving a service instance ID between a subnode in a RAN and a function in a CN> The service instance ID may be, for example, an identifier that has a role similar to that of the NGAP ID used between a 5G RAN and a 5GC (e.g., an AMF).

[0069] (3.2.3) Operation Example 3 Operation Example 3 will be described with reference to Fig. 10. Operation Example 3 involves transmitting and receiving an identifier (PLMN ID) of a network (Public Land Mobile Network, PLMN) provided by a telecommunications carrier between subnodes in a RAN or between a subnode in a RAN and a function in a CN. Note that, hereinafter, a subnode in a RAN or a function in a CN is also referred to as an entity.

[0070] Operation example 3 is based on RAN sharing, in which multiple communication carriers share a network. When UE 200 changes communication carriers in the same network, the PLMN ID is changed. Accordingly, a subnode in RAN or a function in CN needs to recognize the identifier of the source PLMN ID of UE 200 and the identifier of the target PLMN ID of UE 200.

[0071] As shown in Fig. 10, one entity (Entity 1 in the figure) transmits an SBI message to another entity (Entity 2 in the figure). The SBI message is, for example, a setup request message, a setup response message, a modification request message, or a modification response message of the xx (xx is an arbitrary name) interface. The SBI message may include a source PLMN ID and a target PLMN ID in the header or message (body).

[0072] (4) Actions and Effects According to the above-described embodiment, even if an existing node is divided into multiple service nodes, it is possible to identify UEs, service instances, and networks provided by telecommunications carriers between the service nodes.

[0073] According to the above-described embodiment, the UE, the service instance, and the network provided by the communication carrier can be identified between the service node and the function in the CN. Furthermore, by using the identifier of the UE 200 to set the scheduling of the UE 200, the UE 200 can be identified in the 6G RAN without significantly changing the rules in the existing 5G RAN.

[0074] Furthermore, the service node may include sub-service nodes that are obtained by dividing the CU and CP. In this case, it is expected that there will be a large number of service nodes, but even in such a configuration, it is possible to reliably identify the UE 200 between each service node.

[0075] (5) Other Embodiments The contents of the present invention have been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0076] The above-described operation examples may be combined and applied in a composite manner, as long as no contradiction occurs.

[0077] The block diagrams used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. 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 directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

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

[0079] For example, the base station 100, the terminal 200, and the like according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 11 is a diagram illustrating an example of the hardware configuration of the base station 100 and the terminal 200 according to an embodiment of the present disclosure. The base station 100 and the terminal 200 described above may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0080] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of base station 100 and terminal 200 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0081] Each function in the base station 100 and the terminal 200 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the memory 1002, causing the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of reading and writing data in the memory 1002 and the storage 1003.

[0082] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc.

[0083] The processor 1001 also reads programs (program codes), 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 programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. While the above-described various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0084] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store executable programs (program codes), software modules, etc. for implementing a wireless communication method according to one embodiment of the present disclosure.

[0085] Storage 1003 is a computer-readable recording medium and may be, 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 disc), 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 storage medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0086] The communication device 1004 is hardware (transmission / reception 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, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0087] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an 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).

[0088] 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 may be configured using different buses between each device.

[0089] Furthermore, base station 100 and terminal 200 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 the hardware. For example, processor 1001 may be implemented using at least one of these pieces of hardware.

[0090] 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., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the 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, or the like.

[0091] Each aspect / embodiment described in this disclosure may apply to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), 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 any other suitable system, and next generation systems extended, modified, created, or defined based on these. In addition, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0092] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. 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.

[0093] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node in some cases. 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 (for example, an MME or an S-GW, etc., but are not limited to these). Although 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 (for example, an MME and an S-GW) may also be used.

[0094] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0095] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

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

[0097] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0098] 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.

[0099] Software, instructions, information, etc. may also be transmitted or received over 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), then these wired and / or wireless technologies are included within the definition of transmission media.

[0100] 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.

[0101] Note that terms described 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.

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

[0103] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0104] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions 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.

[0105] 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.

[0106] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station 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 term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or a base station subsystem that provides communication services within this coverage.

[0107] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

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

[0109] 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.

[0110] 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 object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be an autonomous mobile object operating based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 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.

[0111] Furthermore, the base station in the present disclosure may be read as a terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a terminal is replaced with communication between multiple terminals (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 200 may be configured to have the functions of the base station 100 described above. 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 an uplink channel and a downlink channel may be read as a side channel.

[0112] Similarly, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 100 may be configured to have the functions of the terminal 200 described above.

[0113] 12 shows an example of the configuration of a vehicle 2001. As shown in Fig. 12, the vehicle 2001 includes 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.

[0114] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0115] 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 the rear wheels based on the operation of the steering wheel operated by the user.

[0116] The electronic control unit 2010 is composed of a microprocessor 2031, a 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 Electronic Control Unit (ECU).

[0117] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels 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.

[0118] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired 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 2001.

[0119] The information service unit 2012 may include input devices (e.g., keyboards, mice, microphones, switches, buttons, sensors, touch panels, etc.) that accept input from the outside, and may also include output devices (e.g., displays, speakers, LED lamps, touch panels, etc.) that output to the outside.

[0120] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, Light Detection and Ranging (LiDAR), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., inertial measurement units (IMUs), inertial navigation systems (INSs), etc.), artificial intelligence (AI) 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.

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

[0122] 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, or the like.

[0123] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021 to 2029 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021 to 2029, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0124] 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 information service unit 2012 may also be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)).

[0125] Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the 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, axle 2009, sensors 2021 to 2029, and the like provided in the vehicle 2001.

[0126] 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, all of which are considered to be "judging" and "determining." "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory), all of which are considered to be "judging" and "determining." "Determining" and "determining" may also include resolving, selecting, choosing, establishing, comparing, and other actions, all of which are considered to be "judging" and "determining." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Also, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0127] 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.

[0128] The reference signal may also be abbreviated as RS, and may be called a pilot depending on the applicable standard.

[0129] 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."

[0130] 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 or that the first element must in some way precede the second element.

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

[0132] 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.

[0133] 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.

[0134] Numerology may be a communication parameter applied to the transmission and / or reception of a signal or channel, such as 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, specific windowing operations performed by the transceiver in the time domain, etc.

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

[0136] A slot may include multiple minislots. Each minislot may consist of one or multiple 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.

[0137] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0138] 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. That is, 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 to 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.

[0139] 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 terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each terminal) in TTI units. However, the definition of TTI is not limited to this.

[0140] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a 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 a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0141] In addition, when one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Furthermore, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0142] A TTI having a time length of 1 ms may be referred to as a regular TTI (TTI in LTE Rel. 8 to 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 or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0143] In addition, 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.

[0144] A resource block (RB) is a resource allocation unit in the time domain and the 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 be determined based on numerology.

[0145] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0146] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0147] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region 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 certain numerology in a certain carrier. Here, the common RBs may be identified by their indexes relative to the common reference point of the carrier. PRBs may be defined in a certain BWP and numbered within the BWP.

[0148] The BWP 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.

[0149] 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 the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0150] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various configurations, such as 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, the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length, can be changed.

[0151] The "maximum transmit power" in this disclosure may mean the maximum value of transmit power, the nominal UE maximum transmit power, or the rated UE maximum transmit power.

[0152] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0153] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0154] Although the present disclosure has been described in detail above, it is 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.

[0155] (Additional Note) The above disclosure may be expressed as follows.

[0156] A first feature is a service node comprising: a control unit that controls communication with other service nodes connected to a service node that is a unit for providing the service in a radio access network that is divided on a service-by-service basis; and a transmission unit that transmits an identifier to the other service node, wherein at least one of the service node and the other service node includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided on a service-by-service basis, and the transmission unit transmits, as the identifiers, a first identifier by which the service node identifies a terminal and a second identifier by which the other service node identifies the terminal.

[0157] A second feature is the service node based on the first feature, wherein the transmitter transmits the first identifier and the second identifier to a core network connected to the radio access network.

[0158] A third feature based on the first or second feature is that the transmission unit is a service node that transmits the first identifier and the second identifier used in scheduling configuration of the terminal.

[0159] A fourth feature is a service node according to any one of the first to third features, wherein the service node includes the control service node.

[0160] A fifth feature is a service node comprising: a control unit that controls communication with other service nodes connected to a service node that is a unit for providing the service, in a radio access network that is divided on a service-by-service basis; and a transmission unit that transmits an identifier to the other service node, wherein at least one of the service node and the other service node includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided on a service-by-service basis, and the transmission unit transmits, as the identifier, an identifier of an interface used for the communication.

[0161] A sixth feature is a service node comprising: a control unit that controls communication with other service nodes connected to a service node that is a unit for providing the service in a radio access network that is divided on a service-by-service basis; and a transmission unit that transmits an identifier to the other service node, wherein at least one of the service node and the other service node includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided on a service-by-service basis; and the transmission unit transmits, as the identifier, an identifier of a network provided by a telecommunications carrier from which the terminal is to be transferred and an identifier of a network provided by a telecommunications carrier to which the terminal is to be transferred.

[0162] 10 Wireless communication system 20 RAN 30 CN 100 Base station 110 Radio signal transmitting / receiving unit 120 Amplifier unit 130 Modulation / demodulation unit 140 Control signal / reference signal processing unit 150 Encoding / decoding unit 160 Data transmitting / receiving unit 170 Control unit 200 Terminal 210 Radio signal transmitting / receiving unit 220 Control unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 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 service unit 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 system section 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. In a radio access network divided into service units, a control unit that controls communication with other service nodes connected to a service node that is a unit for providing the service, and a transmission unit that transmits an identifier to the other service nodes. At least one of the service node or the other service nodes includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided into service units. The transmission unit transmits, as the identifier, a first identifier by which the service node identifies a terminal and a second identifier by which the other service node identifies the terminal. A service node.

2. The transmission unit transmits the first identifier and the second identifier to a core network connected to the radio access network. The service node according to claim 1.

3. The transmission unit transmits the first identifier and the second identifier used for scheduling setting of the terminal. The service node according to claim 1.

4. The service node includes the control service node. The service node according to claim 1.

5. In a radio access network divided into service units, a control unit that controls communication with other service nodes connected to a service node that is a unit for providing the service, and a transmission unit that transmits an identifier to the other service nodes. At least one of the service node or the other service nodes includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided into service units. The transmission unit transmits, as the identifier, an identifier of an interface used for the communication. A service node.

6. In a radio access network divided into service units, a control unit that controls communication with other service nodes connected to a service node that is a unit providing the service, and a transmission unit that transmits an identifier to the other service nodes. At least one of the service node or the other service nodes includes a control service node in which a control plane of a central device that centrally controls the radio access network is divided into service units. The transmission unit transmits, as the identifier, an identifier of a network provided by a communication carrier from which the terminal transitions and an identifier of a network provided by a communication carrier to which the terminal transitions. Service node.

Images