Communication control method, mobile communication system, user device, program and chipset

Abstract

The present invention provides a communication control method, a mobile communication system, user equipment, a program, and a chipset for appropriately recording logs for predetermined processes and transmitting them to a base station. [Solution] In a mobile communication system, the communication control method by the user device includes executing a slice-specific random access channel, which is a random access procedure using resources separated for each slice or slice group; recording first log information obtained when the slice-specific random access channel is executed in memory; and transmitting the first log information to the base station gNB.

Description

Technical Field

[0001] The present invention relates to a communication control method, a mobile communication system, a user device, a program, and a chipset used in a mobile communication system.

Background Art

[0002] In 3GPP (Third Generation Partnership Project), which is a standardization project for mobile communication systems, network slicing (or network slice) has been specified.

[0003] Network slicing is a concept that allows differentiated processing according to the requirements of each customer. Alternatively, network slicing is also a technology that efficiently provides a network according to the required conditions of the services used by customers by virtually slicing the network.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Summary of the Invention

[0005] The communication control method according to the first aspect is a communication control method in a mobile communication system having a user device and a base station and enabling wireless communication between the user device and the base station. The communication control method includes the user device executing a random access procedure using a resource associated with a slice group. The communication control method also includes the user device recording first log information obtained when executing the random access procedure in a memory. Further, the communication control method includes the user device transmitting the first log information to the base station.

[0006] The second aspect of the communication control method is a communication control method in a mobile communication system having a user device and a base station, and capable of wireless communication between the user device and the base station. The communication control method includes the user device performing slice-specific cell reselection using priority frequencies mapped for each slice group. The communication control method also includes the user device recording second log information acquired when performing slice-specific cell reselection in memory. Furthermore, the communication control method includes the user device transmitting the second log information to the base station. [Brief explanation of the drawing]

[0007] [Figure 1] Figure 1 is a diagram showing an example configuration of a mobile communication system according to one embodiment. [Figure 2] Figure 2 is a diagram showing an example configuration of a UE (User Equipment) according to one embodiment. [Figure 3] Figure 3 is a diagram showing an example configuration of a gNB (base station) according to one embodiment. [Figure 4] Figure 4 is a diagram showing an example of the configuration of a protocol stack for a user plane according to one embodiment. [Figure 5] Figure 5 is a diagram showing an example of the configuration of a protocol stack related to a control plane according to one embodiment. [Figure 6] Figure 6 is a diagram showing an example configuration of the mobile communication system 1 according to the first embodiment. [Figure 7] Figure 7 is a diagram illustrating an example of operation according to the first embodiment. [Figure 8] Figure 8 is a diagram illustrating an example of operation according to the second embodiment. [Modes for carrying out the invention]

[0008] This disclosure aims to provide a communication control method that can appropriately record logs for predetermined processes and transmit them to a base station.

[0009] A mobile communication system according to an embodiment will be described with reference to the drawings. In the drawings, identical or similar parts are denoted by the same or similar reference numerals.

[0010] (Mobile communication system) First, the configuration of a mobile communication system according to one embodiment will be described. The mobile communication system according to one embodiment is a 3GPP 5G system, but LTE may be applied to the mobile communication system at least partially. Furthermore, future mobile communication systems such as 6G may also be applied to the mobile communication system.

[0011] Figure 1 is a diagram showing an example configuration of a mobile communication system 1 according to one embodiment.

[0012] As shown in Figure 1, the mobile communication system 1 includes user equipment (UE) 100, a 5G radio access network (NG-RAN) 10, and a 5G core network (5GC) 20.

[0013] UE100 is a mobile device. UE100 can be any device used by a user, but examples include mobile phone terminals (including smartphones), tablet terminals, notebook PCs, communication modules (including communication cards or chipsets), sensors or devices attached to sensors, vehicles or devices attached to vehicles (Vehicle UE), and aircraft or devices attached to aircraft (Aerial UE).

[0014] NG-RAN10 includes base stations (called "gNBs" in 5G systems) 200. gNB200 is sometimes referred to as an NG-RAN node. gNB200s are interconnected via the Xn interface, which is an inter-base station interface. gNB200 manages one or more cells. gNB200 performs wireless communication with UE100s that have established a connection with its own cell. gNB200 has radio resource management (RRM) functions, user data routing functions (hereinafter simply referred to as "data"), and measurement and control functions for mobility control and scheduling. "Cell" is used as a term indicating the smallest unit of a wireless communication area. "Cell" is also used as a term indicating a function or resource that performs wireless communication with UE100s. One cell belongs to one carrier frequency.

[0015] Furthermore, the gNB200 may be connected to the EPC (Evolved Packet Core), which is the core network of LTE, or the LTE base station may be connected to the 5GC20. In addition, the LTE base station and the gNB200 may be connected via an inter-base station interface.

[0016] 5GC20 includes AMF (Access and Mobility Management Function) 301 (301-1, 301-2) and UPF (User Plane Function) 302 (302-1, 302-2). AMF301 performs various mobility controls for UE100. AMF301 manages information about the area where UE100 is located by communicating with UE100 using NAS (Non-Access Stratum) signaling. UPF302 controls data transfer. AMF301 and UPF302 are connected to gNB200 via the NG interface, which is the base station-core network interface. AMF301 and UPF302 are examples of core network devices connected to 5GC (core network) 20.

[0017] Figure 2 is a diagram showing an example configuration of UE100 (user device) according to one embodiment.

[0018] As shown in FIG. 2, the UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0019] The receiving unit 110 performs various receptions under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts (down-converts) the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 130.

[0020] The transmitting unit 120 performs various transmissions under the control of the control unit 130. The transmitting unit 120 includes an antenna and a transmitter. The transmitter converts (up-converts) the baseband signal (transmitted signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0021] The control unit 130 performs various controls in the UE 100. The control unit 130 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs executed by the processor and information used for the processing by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of the baseband signal, etc. The CPU executes the programs stored in the memory to perform various processes. The control unit 130 may perform various operations and various processes executed by the UE 100 in each of the embodiments shown below.

[0022] FIG. 3 is a diagram showing a configuration example of a gNB 200 (base station) according to an embodiment.

[0023] As shown in FIG. 3, the gNB 200 includes a transmitting unit 210, a receiving unit 220, a control unit 230, and a backhaul communication unit 240.

[0024] The transmitting unit 210 performs various types of transmissions under the control of the control unit 230. The transmitting unit 210 includes an antenna and a transmitter. The transmitter converts (upconverts) the baseband signal (transmission signal) output by the control unit 230 into a wireless signal and transmits it from the antenna.

[0025] The receiving unit 220 performs various types of reception under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts (downconverts) the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 230.

[0026] The control unit 230 performs various controls on the gNB200. The control unit 230 includes at least one processor and at least one memory electrically connected to the processor. The memory stores programs executed by the processor and information used for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation, demodulation, encoding, and decoding of baseband signals. The CPU executes programs stored in the memory and performs various processes. In each of the embodiments shown below, the control unit 230 may perform various operations and processes performed by the gNB200.

[0027] The backhaul communication unit 240 is connected to an adjacent base station via an inter-base station interface. The backhaul communication unit 240 is connected to the AMF301 and / or UPF302 via a base station-core network interface. The gNB200 may consist of a CU (Central Unit) and a DU (Distributed Unit), with the two units connected by an F1 interface.

[0028] Figure 4 is a diagram showing an example of the protocol stack configuration of a user plane wireless interface according to one embodiment.

[0029] As shown in Figure 4, the user plane's wireless interface protocol for handling data has a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, and an SDAP (Service Data Adaptation Protocol) layer.

[0030] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the UE100's PHY layer and the gNB200's PHY layer via a physical channel.

[0031] The MAC layer performs data priority control, retransmission processing using Hybrid ARQ (HARQ), and random access procedures. Data and control information are transmitted between the MAC layer of the UE100 and the MAC layer of the gNB200 via the transport channel. The MAC layer of the gNB200 includes a scheduler. The scheduler determines the transport format for the up and down links (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be allocated to the UE100.

[0032] The RLC layer transmits data to the receiving RLC layer using the functions of the MAC layer and PHY layer. Data and control information are transmitted between the UE100's RLC layer and the gNB200's RLC layer via a logical channel.

[0033] The PDCP layer performs header compression / decompression, and encryption / decryption. Data and control information are transmitted between the UE100's PDCP layer and the gNB200's PDCP layer via a wireless bearer.

[0034] The SDAP layer maps QoS flows, which are the units in which the core network performs QoS control, to wireless bearers, which are the units in which the AS (Access Stratum) performs QoS control. Note that if the RAN is connected to the EPC, the SDAP is not required.

[0035] Figure 5 is a diagram showing an example of the configuration of the protocol stack of the wireless interface of a control plane according to one embodiment.

[0036] As shown in Figure 5, the protocol stack of the control plane's wireless interface that handles signaling (control signals) has an RRC (Radio Resource Control) layer and a NAS layer instead of the SDAP layer shown in Figure 4.

[0037] RRC signaling for various settings is transmitted between the RRC layer of the UE100 and the RRC layer of the gNB200. The RRC layer controls the logical channel, transport channel, and physical channel in response to the establishment, re-establishment, and release of the radio bearer. If there is a connection (RRC connection) between the RRC of the UE100 and the RRC of the gNB200, the UE100 is in the RRC connected state. If there is no connection (RRC connection) between the RRC of the UE100 and the RRC of the gNB200, the UE100 is in the RRC idle state. Also, if the RRC connection is suspended, the UE100 is in the RRC inactive state.

[0038] The NAS (Non-Access Stratum) layer, located above the RRC layer, handles session management and mobility management, among other things. NAS signaling is transmitted between the UE100's NAS layer and the AMF301's NAS layer.

[0039] In addition to the wireless interface protocol, the UE100 also has an application layer and other components.

[0040] [First Embodiment] Next, the first embodiment will be described.

[0041] As mentioned above, network slicing enables the provision of various services that meet user requirements. In the following, network slicing may be referred to as "slicing." In network slicing, the portion supported by NG-RAN10 may be referred to as RAN slicing. Even when network slicing and RAN slicing are not distinguished, they may simply be referred to as "slicing" in the following.

[0042] A slice represents a logically divided core network and / or wireless access network. Identifiers for identifying a slice include NSSAI (Network Slice Selection Assistance Information) or S-NSSAI (Single-NSSAI).

[0043] Furthermore, a slice group is a group containing one or more slices, and such a group is assigned an identifier (ID). Slice groups may be created in the core network (e.g., AMF301) or in the wireless access network (e.g., gNB200). The created slice groups may be notified to the UE100.

[0044] In 3GPP, slice-specific cell reselection is being considered. In slice-specific cell reselection, frequencies are mapped (or associated) with each slice, and each frequency is assigned an absolute priority. The process of performing cell reselection using this setting is called slice-specific cell reselection. Slice-specific cell reselection makes it possible to provide frequency resources for each slice (or slice group), for example, and suppresses situations where frequency resources overlap between slices. Furthermore, by controlling the frequency priority of the cells (reselected cells) where the UE100 camps for each slice (or slice group), the UE100 can be positioned (distributed) to the appropriate frequency for each slice that the UE100 wishes to access. In addition, the UE100 can be camped (positioned) at different frequencies (or cells) from UEs that do not wish to access a slice (e.g., legacy UEs).

[0045] Regarding slice-specific cell reselection, 3GPP states that 1) Prioritized frequencies mapped for each slice are provided to the UE100. 2) "Slice" may also mean "slice group". 3) It was agreed that the prioritized frequencies mapped to each slice would be part of the “Slice info”.

[0046] Furthermore, 3GPP is also considering slice-specific random access channels (Random Access Channel(s)). Slice-specific random access channels (hereinafter sometimes referred to as "slice-specific RACH") use separate random access opportunities (RAH Occasions) and / or separate preambles for each slice or slice group. Random access procedures performed using RACH resources separated for each slice or slice group in this way are called slice-specific RACH. Slice-specific RACH can suppress situations where resources overlap, for example, between slices, between slice groups, or between access using slices and access not using slices. In addition, by avoiding such resource overlap, interference of RACH transmitted by multiple UE100s can be suppressed. Furthermore, access to a certain slice or slice group can be prioritized (by assigning resources that are less likely to cause interference).

[0047] Furthermore, 3GPP is also considering "intended slices." However, 3GPP has not yet reached an agreement on specific details, such as the definition of an "intended slice." In the first embodiment, an "intended slice" will refer to a slice that is likely to be used, a candidate slice, a desired slice, a slice to communicate with, a requested slice, an allowed slice, or an intended slice. For example, UE100 can receive the desired service from a cell that supports an "intended slice" by accessing that cell.

[0048] Meanwhile, in the field of wireless communication, there have traditionally been SON (Self Organizing / Optimizing Network) and MDT (Minimization of Drive Tests).

[0049] SON (Systems-on-Demand) is a technology that autonomously organizes or optimizes networks. Specifically, SON is a technology that enables continuous optimization in response to dynamic network changes, parameter optimization during troubleshooting, and optimization of coverage and capacity. By utilizing these functions of SON, processes such as network planning, configuration, and optimization can be automated, reducing the workload of operators (telecommunications carriers) and lowering operating costs.

[0050] Furthermore, MDT is a technology that supports the collection of measurement values ​​specific to the UE100. With MDT, measurement data that was previously collected through drive tests using an electronically measured vehicle can now be collected using the UE100, thus automating measurement and data collection and reducing man-hours and costs.

[0051] In the first embodiment, an example is described in which UE100 records information obtained by executing slice-specific RACH (attempt) as a log in memory, as a function of SON and MDT.

[0052] Specifically, firstly, the user device (e.g., UE100) executes a slice-specific random access channel, which is a random access procedure that uses resources separated for each slice or slice group. Secondly, the user device records the first log information obtained when executing the slice-specific random access channel into memory. Thirdly, the user device transmits the first log information to the base station (e.g., gNB200).

[0053] This allows, for example, the UE100 to properly record logs regarding slice-specific RACH and send them to the gNB200.

[0054] (Example of operation according to the first embodiment) Next, an example of operation according to the first embodiment will be described.

[0055] Figure 6 is a diagram showing an example configuration of the mobile communication system 1 according to the first embodiment. As shown in Figure 6, an example of operation of the first embodiment will be described as an example in which UE100 performs slice-specific RACH and connects to a cell in gNB200. Then, UE100 records first log information resulting from the execution of slice-specific RACH and transmits it to gNB200.

[0056] Figure 7 is a diagram illustrating an example of operation according to the first embodiment.

[0057] As shown in Figure 7, in step S10, UE100 starts processing.

[0058] In step S11, UE100 performs slice-specific RACH. For example, UE100 can perform slice-specific RACH by obtaining the parameters for slice-specific RACH from gNB200 via SIB (System Information Block) or individual signaling, and then executing a random access procedure using these parameters.

[0059] In step S12, UE100 records first log information in memory for the slice-specific RACH that was executed.

[0060] The first log information may include not only slice-specific RACH but also log information obtainable through the execution of a normal random access procedure. Examples of such log information include the following:

[0061] Firstly, this information may include the number of random access preambles sent from UE100, the total number of consecutive random access preambles sent from UE100, and at least one of the contention detections. This information is also sent from UE100 to gNB200 as part of the Connection Establishment Failure Report (ConnEstFailReport).

[0062] Secondly, the information may include at least one of the following: the cell ID of the cell on which slice-specific RACH was performed, the purpose of the random access, and the number of RACH opportunities. This information is also transmitted from the UE100 to the gNB200 as part of the Random Access Report (RA-Report) or the Wireless Link Failure Report (RLF-Report).

[0063] In the first embodiment, slice-specific RACH-specific logs are recorded in memory as first log information. That is, when UE100 performs a slice-specific RACH (RACH attempt), it records one of the following pieces of information as first log information.

[0064] (A1) The slice identifier associated with the Physical Random Access Channel (PRACH) resource that performed the RACH attempt.

[0065] (A2) Resource information or resource ID relating to the RO that performed the RACH attempt.

[0066] (A3) Resource information or resource ID related to the preamble on which the RACH attempt was made.

[0067] (A4) Information indicating that the purpose was to obtain priority access to a particular slice. UE100 may further record the identifier of the slice or slice group that was accessed via priority access.

[0068] The above (A1) and (A4) contain information about slices, for example, and can be considered logs specific to slice-specific RACH. Furthermore, since slice-specific RACH uses separate RACH resources for each slice group, (A2) and (A3) make it possible to record which RACH resources were used.

[0069] In step S13, UE100 sends the first log information recorded in memory to gNB200. For example, UE100 may send a UE Information Response message containing the first log information to gNB200. In this case, UE100 sends the UE Information Response message as a response message to the UE Information Request message received from gNB200. Alternatively, UE100 may send the above (A4) by sending a UE Information Response message with "Slice-specific RACH attempt" set in the IE "raPurpose" indicating the purpose of random access.

[0070] Then, in step S14, UE100 terminates the series of processes.

[0071] (Modified version of the first embodiment) In the first embodiment, an example was described in which information included in connection establishment failure reports, random access reports, or wireless link failure reports is recorded as log information obtainable through normal RACH execution. As a modification of the first embodiment, at least one of the following may be recorded as first log information obtainable through normal RACH execution: timestamp, location information (latitude, longitude, altitude, etc.), and wireless conditions (RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality), SINR (Signal to Interference plus Noise Ratio), etc.) and transmitted to the gNB200.

[0072] [Second Embodiment] Next, a second embodiment will be described.

[0073] As a function of SON and MDT, UE100 may report the cell IDs of visited cells to gNB200 as a Mobility History Report. However, there is no specification for reporting the results of cell re-selection by UE100 to gNB200.

[0074] On the other hand, if the aforementioned slice-specific cell reselection is introduced, it is expected that whether or not the UE100 was able to reselect a cell that supports the desired slice ("intended slice") will become one of the pieces of information for network optimization. For example, an operator will be able to newly place cells that support URLLC (Ultra-Reliable and Low Latency Communications) slices in areas where there are many UE100s that desire URLLC slices as their desired slice.

[0075] Therefore, in the second embodiment, an example of recording the execution result of slice-specific cell reselection as a log will be described. Specifically, firstly, the user device (e.g., UE100) performs slice-specific cell reselection using priority frequencies mapped to each slice. Secondly, the user device records the second log information obtained when the slice-specific cell reselection was performed into memory. Thirdly, the user device transmits the second log information to the base station (e.g., gNB200).

[0076] This makes it possible, for example, to properly record logs during slice-specific cell reselection. It also makes it possible to address network optimization, for example.

[0077] (Example of operation according to the second embodiment) Figure 8 is a diagram illustrating an example of operation according to the second embodiment.

[0078] As shown in Figure 8, in step S20, UE100 starts processing.

[0079] In step S21, UE100 performs slice-specific cell reselection. For example, UE100 can perform slice-specific cell reselection by obtaining the parameters for slice-specific cell reselection from gNB200 via SIB or individual signaling, and then using those parameters to perform cell reselection.

[0080] In step S22, UE100 completes slice-specific cell reselection. Whether or not slice-specific cell reselection is complete may be determined by whether or not predetermined completion conditions are met. The predetermined completion conditions are, for example, 1) prioritized frequencies (or cells) associated with the slice are reselected, 2) the highest priority frequency (or cell) is reselected, and 3) the reselected cell (or frequency) transmits a slice-specific RACH parameter corresponding to a slice identifier indicating "intended slice". UE100 may also determine completion conditions other than these predetermined conditions.

[0081] In step S23, if UE100 succeeds in re-selecting slice-specific cells, it records the first information as second log information in memory. Also in step S23, if UE100 fails to re-select slice-specific cells, it records the second information as second log information in memory. Whether or not slice-specific cell re-selection has succeeded or failed may be determined, for example, by whether or not the completion condition is met. If UE100 fails to re-select slice-specific cells, it will perform normal cell re-selection.

[0082] The first piece of information may be, for example, any of the following:

[0083] (B1) Identifier for the desired slice ("intended slice"). For example, S-NSSAI for "intended slice".

[0084] (B2) Information indicating that the re-selection of slice-specific cells has been completed.

[0085] (B3) Information indicating that the slice in question ("intended slice") is located in a cell that supports it.

[0086] (B4) Information indicating that the device is located in a cell that supports preferred access to the slice in question ("intended slice"). For example, if UE100 receives the parameters of the slice-specific RACH in the cell it is located in, it can be determined that the device is located in a cell that supports preferred access to the slice in question.

[0087] (B5) Information indicating which cell (or frequency) was reselected for the priority specified in the slice-specific cell reselection parameter.

[0088] (B6) Information about the re-selected cell (or frequency). This information may be represented by a cell ID or an ARFCN (Absolute radio-frequency channel number).

[0089] On the other hand, the second piece of information may be, for example, any of the following:

[0090] (C1) Identifier of the desired slice ("intended slice"). For example, the identifier of the desired slice if slice-specific cell reselection fails for a cell that supports the desired slice.

[0091] (C2) Information indicating that slice-specific cell reselection failed.

[0092] (C3) Information indicating that the cell in question ("intended slice") may not support it.

[0093] (C4) Information indicating that the user is located in a cell that does not support preferred access to the slice in question ("intended slice"). For example, if UE100 does not receive the slice-specific RACH parameter in the cell it is located in, it can be determined that the user is located in a cell that does not support preferred access to the slice in question.

[0094] (C5) Information about the re-selected cell (or frequency).

[0095] Furthermore, the UE100 may record at least one of the following as second log information: timestamp, location information (latitude, longitude, altitude, etc.), and radio conditions (RSRP, RSRQ, SINR, etc.).

[0096] In step S24, UE100 transitions to the RRC Connected state. After transitioning to the RRC Connected state, UE100 may notify gNB200 that it is logging slice-specific cell reselection. This notification may be made by UE100 sending an RRC Setup Complete message or an RRC Release Complete message that includes “Slice-specific cell reselection log available”.

[0097] In step S25, UE100 sends the log (second log information) recorded in memory to gNB200. For example, UE100 may include the log in a UE Information Response message, which is a response message to a UE Information Request message received from gNB200, and send it.

[0098] Then, in step S26, UE100 terminates the series of processes.

[0099] [Other embodiments] A program may be provided that causes a computer to perform each of the processes that UE100 or gNB200 performs. The program may be recorded on a computer-readable medium. Using a computer-readable medium, it is possible to install the program on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, but may be a recording medium such as a CD-ROM or DVD-ROM.

[0100] Alternatively, the circuits that perform each process carried out by the UE100 or gNB200 may be integrated, and at least a portion of the UE100 or gNB200 may be configured as a semiconductor integrated circuit (chipset, SoC).

[0101] The terms "based on" and "depending on" used in this disclosure do not mean "based solely on" or "depending solely on" unless otherwise specified. The term "based on" means both "based solely on" and "at least partially on." Similarly, the term "depending on" means both "at least partially on" and "at least partially on." Also, "obtain / acquire" may mean obtaining information from stored information, obtaining information from information received from other nodes, or obtaining information by generating it. The terms "include," "comprise," and their variations do not mean to include only the listed items, but may include only the listed items, or may include additional items in addition to the listed items. Also, the term "or" used in this disclosure is not intended to mean exclusive OR. Furthermore, any reference to elements using designations such as "first," "second," etc., used in this disclosure does not limit the quantity or order of those elements in general. These designations may be used herein as a convenient way to distinguish between two or more elements. Therefore, references to the first and second elements do not imply that only two elements may be employed therein, or that the first element must precede the second element in any way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall be plural unless it is clearly indicated otherwise by the context.

[0102] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to that described above, and various design changes can be made without departing from the gist of the work. Furthermore, it is possible to combine all or part of each embodiment as long as it does not contradict the original concept.

[0103] This application claims priority to Japanese Patent Application No. 2021-128845 (filed on August 5, 2021), and all of its contents are incorporated into the specification of this application. [Explanation of symbols]

[0104] 1: Mobile communication systems 10:5GC 100 :UE 110: Wireless Communication Section 130: Control Unit 200 :gNB 210: Wireless Communication Section 220: Network Communications Department 230: Control Unit 301: AMF 302: UPF

Claims

1. A communication control method performed on a user device, Performing a random access procedure using resources associated with slice groups, The process includes transmitting RACH information obtained when the aforementioned random access procedure is executed to a network node. The RACH information includes information indicating the identifier of the slice group associated with the resource, and the identifier of the slice that was RAC'd. Communication control method.

2. User equipment and The system includes a network node that performs wireless communication with the user device, The User device is Perform a random access procedure using resources associated with slice groups. The user device transmits the RACH information acquired when executing the random access procedure to the network node. The RACH information includes information indicating the identifier of the slice group associated with the resource, and the identifier of the slice that was RAC'd. Mobile communication system.

3. A control unit that performs a random access procedure using resources associated with slice groups, The system includes a transmission unit that transmits RACH information acquired when the aforementioned random access procedure is executed to a network node, The RACH information includes information indicating the identifier of the slice group associated with the resource, and the identifier of the slice that was RAC'd. User device.

4. Performing a random access procedure using resources associated with slice groups, The log information obtained when the aforementioned random access procedure was executed is sent to the network node, The user device is made to execute this, The RACH information includes information indicating the identifier of the slice group associated with the resource, and the identifier of the slice that was RAC'd. program.

5. A chipset for controlling user devices, Performing a random access procedure using resources associated with slice groups, The RACH information obtained when the aforementioned random access procedure was executed is sent to the network node, and the following is performed: The RACH information includes information indicating the identifier of the slice group associated with the resource, and the identifier of the slice that was RAC'd. Chipset.

Images