Base station equipment

Abstract

To provide a technology that is to contribute to the realization of stable video content distribution.SOLUTION: A base station device obtains periodicity information of XR traffic from a core network. The periodicity information of XR traffic is indicated by information related to the traffic. The periodicity information of XR traffic is used to set DRX (Discontinuous Reception).SELECTED DRAWING: Figure 13

Description

Technical Field

[0001] This disclosure relates to a base station device.

Background Art

[0002] Wireless access methods and wireless networks for cellular mobile communications (hereinafter also referred to as “Long Term Evolution (LTE)”, “LTE-Advanced (LTE-A)”, “LTE-Advanced Pro (LTE-A Pro)”, “New Radio (NR)”, “New Radio Access Technology (NRAT)”, “Evolved Universal Terrestrial Radio Access (EUTRA)”, or “Further EUTRA (FEUTRA)”) are being studied in the 3rd Generation Partnership Project (3GPP (registered trademark)). In the following description, LTE includes LTE-A, LTE-A Pro, and EUTRA, and NR includes NRAT and FEUTRA. In LTE, the base station device (base station, communication device) is an eNodeB (evolved NodeB), in NR, the base station device (base station, communication device) is a gNodeB, and in LTE and NR, the terminal device (mobile station, mobile station device, terminal, communication device) is also referred to as a UE (User Equipment). LTE and NR are cellular communication systems in which a plurality of areas covered by a base station device are arranged in a cell shape. A single base station device may manage a plurality of cells.

[0003] NR (Network Rating) is characterized by its ultra-high speed, low latency, high reliability, and ability to handle a large number of simultaneous connections. One use case for NR that leverages these characteristics is being considered for use in services utilizing Augmented Reality (AR) and Virtual Reality (VR). For example, with AR technology, it becomes possible to overlay virtual content of various forms, such as text, icons, or animations, onto real objects captured in images of real space and present them to the user. Non-Patent Documents 1 and 2 disclose use cases and (potential) requirements for services using Augmented Reality (AR) and Virtual Reality (VR) (e.g., AR / VR games). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP TR 22.842, V17.1.0 (2019-09) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Network Controlled Interactive Services (Release 17) [Non-Patent Document 2] 3GPP TS 22.261 v17.0.1 (2019-10) 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for next generation new services and markets (Release 17) [Overview of the project] [Problems that the invention aims to solve]

[0005] NR (Non-Radio Wave) is expected to be used for transmitting 4K and 8K video due to its characteristics of ultra-high speed, low latency, high reliability, and massive simultaneous connections. Furthermore, as a post-smartphone technology, the proliferation of wearable devices is anticipated. Some use cases for wearable devices require consideration not only of ultra-high speed but also of low latency and high reliability. For example, in cases where VR content is displayed on an HMD (Head-Mounted Display) wirelessly, it is crucial to keep motion-to-photon latency within a certain range to prevent VR sickness. Thus, there is a need to deliver video content that requires real-time performance in a stable manner.

[0006] Therefore, this disclosure proposes a technology that contributes to the realization of stable and displayable video content distribution.

[0007] It should be noted that the above-mentioned problems or objectives are merely one of several problems or objectives that can be solved or achieved by the multiple embodiments disclosed herein. [Means for solving the problem]

[0008] According to this disclosure, a base station device is provided. The base station device acquires periodic information of XR traffic from the core network. The periodic information of the XR traffic is indicated by information relating to the traffic. The periodic information of the XR traffic is used to configure DRX (Discontinuous Reception). [Brief explanation of the drawing]

[0009] [Figure 1] This figure shows an example configuration of a content distribution system according to an embodiment of this disclosure. [Figure 2] This figure shows an example configuration of an information processing device according to an embodiment of this disclosure. [Figure 3] This figure shows an example configuration of a base station device according to the present disclosure. [Figure 4] This figure shows an example configuration of a terminal device according to the embodiments of this disclosure. [Figure 5] This is a diagram showing an example of a 5G architecture. [Figure 6] This is a sequence diagram showing an example of content delivery processing according to an embodiment of this disclosure. [Figure 7] This figure illustrates an example of rendering processing according to the embodiments of this disclosure. [Figure 8] This figure illustrates another example of the rendering process according to the embodiments of this disclosure. [Figure 9] This is a sequence diagram showing an example of the registration process according to the embodiments of this disclosure. [Figure 10] This is a sequence diagram showing an example of the PDU session establishment process according to the embodiment of this disclosure. [Figure 11] This is a sequence diagram showing an example of the RRC_CONNECTED transition process according to the embodiment of this disclosure. [Figure 12] This diagram illustrates an example of video data distribution using a content distribution system. [Figure 13] This figure illustrates the resetting of the SPS by a base station device according to an embodiment of this disclosure. [Figure 14] This is a flowchart showing the flow of the SPS reset process according to the embodiment of this disclosure. [Figure 15] This figure illustrates an example of SPS settings using a base station device according to an embodiment of this disclosure. [Figure 16] This figure illustrates an example of SPS settings using a base station device according to an embodiment of this disclosure. [Figure 17] This figure illustrates an example of setting up an SPS using a base station device according to an embodiment of this disclosure. [Figure 18] This figure illustrates the resetting of the computer grid (CG) by a base station device according to an embodiment of this disclosure. [Figure 19] This figure illustrates the resetting of the computer grid (CG) by a base station device according to an embodiment of this disclosure. [Figure 20] It is a diagram for explaining an example of display processing by a terminal device according to an embodiment of the present disclosure. [Figure 21] It is a diagram for explaining another example of display processing by a terminal device according to an embodiment of the present disclosure. [Figure 22] It is a diagram for explaining an example of video data allocation processing by a base station device according to an embodiment of the present disclosure. [Figure 23] It is a diagram for explaining an example of video data allocation processing by a base station device according to an embodiment of the present disclosure. [Figure 24] It is a diagram for explaining an example of video data allocation processing by a base station device according to an embodiment of the present disclosure. [Figure 25] It is a diagram for explaining an example of video data allocation processing by a base station device according to an embodiment of the present disclosure. [[ID=I7]] [Figure 26] It is an image diagram of a rendering server and an AR / VR client regarding rendering.

Embodiments for Carrying Out the Invention

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the present specification and drawings, for components having substantially the same functional configuration, the same reference numerals are given to omit redundant description.

[0011] Also, in the present specification and drawings, for similar components of the embodiments, different alphabets may be attached after the same reference numeral for distinction. However, when it is not necessary to particularly distinguish each of the similar components, only the same reference numeral is given.

[0012] The one or more embodiments (including examples and modifications) described below can each be implemented independently. On the other hand, at least some of the embodiments described below may be implemented in appropriate combination with at least some of the other embodiments. These embodiments may contain novel features that differ from each other. Therefore, these embodiments may contribute to solving different objectives or problems and may produce different effects.

[0013] The explanation will be given in the following order. 1. Example of a content distribution system configuration 1.1. Example of an overall content distribution system configuration 1.2. Example of an information processing device configuration 1.3. Example of Base Station Equipment Configuration 1.4. Example of terminal device configuration 1.5. Example of Network Architecture Configuration 2. Examples of information processing in content distribution systems 2.1. Example of content delivery processing 2.2. Rendering Process Example 2.3. Communication Processing Examples 3.Technical challenges 4. Technical Features 4.1. Reconfiguring SPS 4.2. Multiple SPS Settings 4.3. CG Reconfiguration 4.4. Changing Time Warp 4.5. Setting Priorities 5. Other Embodiments 6. Application Examples 7. Conclusion

[0014] <<1. Example of a Content Distribution System Configuration>> <1.1. Example of the overall configuration of a content distribution system> Figure 1 shows an example configuration of a content distribution system 100 according to an embodiment of this disclosure. The content distribution system 100 is a system that distributes video content to a terminal device 110 via a wireless access network. Here, the wireless access network may be E-UTRAN (Evolved Universal Terrestrial Radio Access Network) or NG-RAN (Next Generation Radio Access Network).

[0015] The content distribution system 100 comprises a terminal device 110, a base station device 130, and an information processing device 150. In the content distribution system 100, video content is distributed from the information processing device 150 to the terminal device 110 via the base station device 130.

[0016] The terminal device 110 and the base station device 130 are connected via the wireless access network described above. The base station device 130 and the information processing device 150 may be connected via a wireless or wired access network.

[0017] It should be noted that the devices in the diagram can be considered as devices in a logical sense. In other words, some of the devices in the diagram may be implemented as virtual machines (VMs), containers, Docker, etc., and these may be implemented on the same physical hardware.

[0018] Furthermore, LTE base stations are sometimes referred to as eNodeB (Evolved Node B) or eNB. Similarly, NR base stations are sometimes referred to as NGRAN Node (Next Generation RAN node), gNodeB, or gNB. In addition, in both LTE and NR, terminal equipment (also called mobile station, mobile station equipment, or terminal) is sometimes referred to as UE (User Equipment). Terminal equipment is a type of communication device and is also called a mobile station, mobile station equipment, or terminal.

[0019] In this embodiment, the concept of a communication device includes not only portable mobile devices (terminal devices) such as mobile terminals, but also devices installed on structures or mobile objects. Structures or mobile objects themselves may be considered communication devices. Furthermore, the concept of a communication device includes not only terminal devices but also base station devices. A communication device is a type of processing device and information processing device. A communication device can also be referred to as a transmitting device or a receiving device.

[0020] [Information Processing Device] The information processing device 150 is a content management device that manages video content on the terminal device 110. The information processing device 150 may be, for example, a personal computer, a workstation, or a game console. Alternatively, the information processing device 150 may be a device collectively referred to as a cloud server or edge server.

[0021] [Base station equipment] The base station device 130 is a wireless communication device that communicates wirelessly with the terminal device 110. The base station device 130 is a type of communication device. Furthermore, the base station device 130 is a type of information processing device.

[0022] The base station device 130 may consist of a collection of multiple physical or logical devices. For example, in embodiments of this disclosure, the base station device 130 may be distinguished into multiple devices of BBU (Baseband Unit) and RU (Radio Unit), and may be interpreted as a collection of these multiple devices. Furthermore or alternatively, in embodiments of this disclosure, the base station device 130 may consist of either or both of the BBU and RU. The BBU and RU may be connected by a predetermined interface (e.g., eCPRI). Furthermore or alternatively, the RU may be referred to as a Remote Radio Unit (RRU) or Radio DoT (RD). Furthermore or alternatively, the RU may correspond to a gNB-DU described later. Furthermore or alternatively, the BBU may correspond to a gNB-CU described later. Furthermore or alternatively, the RU may be a device formed integrally with an antenna. The antenna of the base station device 130 (e.g., an antenna formed integrally with the RU) may employ an Advanced Antenna System and support MIMO (e.g., FD-MIMO) and beamforming. The Advanced Antenna System may have an antenna (for example, an antenna integrally formed with the RU) on the base station device 130 that includes, for example, 64 transmitting antenna ports and 64 receiving antenna ports. The antenna mounted on the RU may also be an antenna panel composed of one or more antenna elements, and the RU may be equipped with one or more antenna panels. For example, the RU may be equipped with two types of antenna panels, a horizontally polarized antenna panel and a vertically polarized antenna panel, or two types of antenna panels, a right-hand circularly polarized antenna panel and a left-hand circularly polarized antenna panel. The RU may also form and control independent beams for each antenna panel.

[0023] Furthermore, multiple base station devices 130 may be connected to each other. One or more base station devices 130 may be included in a Radio Access Network (RAN). That is, base station devices 130 may simply be referred to as RAN, RAN node, AN (Access Network), or AN node. In LTE, the RAN is called EUTRAN (Enhanced Universal Terrestrial RAN). In NR, the RAN is called NGRAN. In W-CDMA (UMTS), the RAN is called UTRAN. In LTE, base station devices 130 are referred to as eNodeB (Evolved Node B) or eNB. That is, EUTRAN includes one or more eNodeB (eNB). Also, in NR, base station devices 130 are referred to as gNodeB or gNB. That is, NGRAN includes one or more gNBs. Furthermore, EUTRAN may include gNBs (en-gNB) connected to the core network (EPC) in the LTE communication system (EPS). Similarly, NGRAN may include ng-eNB connected to the core network 5GC in a 5G communication system (5GS). Furthermore, or alternatively, if the base station equipment 130 is an eNB, gNB, etc., it may be referred to as 3GPP Access. Furthermore, or alternatively, if the base station equipment 130 is an Access Point, it may be referred to as Non-3GPP Access. Furthermore, or alternatively, the base station equipment 130 may be an optical extension device called an RRH (Remote Radio Head). Furthermore, or alternatively, if the base station equipment 130 is a gNB, the base station equipment 130 may be referred to as a combination of the gNB CU (Central Unit) and gNB DU (Distributed Unit) described above, or either of these. The gNB CU (Central Unit) hosts multiple upper layers (e.g., RRC, SDAP, PDCP) of the Access Stratum for communication with the UE. On the other hand, the gNB-DU hosts multiple lower layers (e.g., RLC, MAC, PHY) of the Access Stratum.In other words, among the messages and information described later, RRC signalling (e.g., MIB, various SIBs including SIB1, RRCSetup message, RRCReconfiguration message) may be generated by the gNB CU, while DCI and various Physical Channels (e.g., PDCCH, PBCH) described later may be generated by the gNB-DU. Alternatively, among the RRC signalling, some configurations, such as IE:cellGroupConfig, may be generated by the gNB-DU, and the remaining configurations may be generated by the gNB-CU. These configurations may be transmitted and received via the F1 interface described later. The base station device 130 may be configured to communicate with other base station devices 130. For example, if multiple base station devices 130 are eNBs or a combination of eNB and en-gNB, the base station devices 130 may be connected via the X2 interface. Furthermore, or alternatively, if multiple base station devices 130 are gNBs or a combination of gn-eNB and gNB, the devices may be connected via the Xn interface. Furthermore, or alternatively, if the multiple base station devices 130 are a combination of gNB CU (Central Unit) and gNB DU (Distributed Unit), the devices may be connected to each other via the F1 interface described above. The messages and information described later (information included in RRC signalling or DCI) may be communicated between the multiple base station devices 130 (for example, via the X2, Xn, and F1 interfaces).

[0024] Furthermore, as mentioned above, the base station device 130 may be configured to manage multiple cells. The cells provided by the base station device 130 are called Serving cells. A Serving cell includes PCells (Primary Cells) and SCells (Secondary Cells). When Dual Connectivity (e.g., EUTRA-EUTRA Dual Connectivity, EUTRA-NR Dual Connectivity (ENDC), EUTRA-NR Dual Connectivity with 5GC, NR-EUTRA Dual Connectivity (NEDC), NR-NR Dual Connectivity) is provided to a UE (e.g., terminal device 110), the PCells and zero or more SCell(s) provided by the MN (Master Node) are called a Master Cell Group. Furthermore, a Serving cell may also include a PSCell (Primary Secondary Cell or Primary SCG Cell). That is, when Dual Connectivity is provided to a UE, the PSCells and zero or more SCell(s) provided by the SN (Secondary Node) are called a Secondary Cell Group (SCG). Unless otherwise specified (e.g., PUCCH on SCell), the Physical Uplink Control Channel (PUCCH) is transmitted by PCell and PSCell, but not by SCell. Similarly, Radio Link Failure is detected by PCell and PSCell, but not by SCell (and does not need to be detected). Because PCell and PSCell have special roles within Serving Cell(s), they are also called Special Cells (SpCell). A single cell may be associated with one Downlink Component Carrier and one Uplink Component Carrier. Furthermore, the system bandwidth corresponding to a single cell may be divided into multiple Bandwidth Parts.In this case, one or more Bandwidth Parts (BWPs) may be configured for the UE, and one Bandwidth Part may be used by the UE as the Active BWP. Furthermore, the radio resources (e.g., frequency band, numerology (subcarrier spacing), slot format) available to the terminal device 110 may differ for each cell, component carrier, or BWP.

[0025] [Terminal device] Terminal device 110 is a wireless communication device that communicates wirelessly with base station device 130. Terminal device 110 may be, for example, a mobile phone, a smart device (smartphone or tablet), a PDA (Personal Digital Assistant), or a personal computer. Terminal device 110 may also be a head-mounted display or VR goggles, etc., that have the function of sending and receiving data wirelessly.

[0026] Furthermore, terminal device 110 may be capable of sidelink communication with other terminal devices 110. When performing sidelink communication, terminal device 110 may use automatic retransmission technology such as HARQ (Hybrid Automatic Repeat reQuest). Terminal device 110 may be capable of NOMA (Non Orthogonal Multiple Access) communication with base station device 130. In addition, terminal device 110 may also be capable of NOMA communication in communication (sidelink) with other terminal devices 110. Furthermore, terminal device 110 may be capable of LPWA (Low Power Wide Area) communication with other communication devices (for example, base station device 130 and other terminal devices 110). In addition, the wireless communication used by terminal device 110 may be wireless communication using millimeter waves. Furthermore, the wireless communication used by terminal device 110 (including sidelink communication) may be wireless communication using radio waves, or wireless communication using infrared or visible light (optical wireless).

[0027] The terminal device 110 may simultaneously connect to and communicate with multiple base station devices or multiple cells. For example, if one base station device can provide multiple cells, the terminal device 110 can perform carrier aggregation by using one cell as a pCell and other cells as sCells. Also, if multiple base station devices 130 can each provide one or more cells, the terminal device 110 can achieve DC (Dual Connectivity) by using one or more cells managed by one base station device (MN (e.g., MeNB or MgNB)) as a pCell, or a pCell and sCell(s), and one or more cells managed by the other base station device (SN (e.g., SeNB or SgNB)) as a pCell(PSCell), or a pCell(PSCell) and sCell(s). DC may also be referred to as MC (Multi Connectivity).

[0028] Furthermore, when a communication area is supported via cells of different base station devices 130 (multiple cells with different cell identifiers or the same cell identifier), it is possible to combine these multiple cells using carrier aggregation (CA), dual connectivity (DC), or multi-connectivity (MC) technologies to enable communication between the base station device 130 and the terminal device 110. Alternatively, it is also possible for the terminal device 110 to communicate with these multiple base station devices 130 via cells of different base station devices 130 using coordinated multi-point transmission and reception (CoMP) technology.

[0029] The configuration of each device constituting the content distribution system 100 will be described in detail below. Note that the configurations of each device shown below are merely examples. The configuration of each device may differ from the configurations shown below.

[0030] <1.2. Example of Information Processing Device Configuration> Figure 2 shows an example configuration of an information processing device 150 according to an embodiment of the present disclosure. The information processing device 150 is, for example, a device that manages or generates video content. The information processing device 150 comprises a communication unit 151, a storage unit 152, and a control unit 153. Note that the configuration shown in Figure 2 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the information processing device 150 may be distributed and implemented across multiple physically separated configurations. For example, the information processing device 150 may be composed of multiple server devices.

[0031] The communication unit 151 is a communication interface for communicating with other devices. The communication unit 151 may be a network interface or an equipment connection interface. For example, the communication unit 151 may be a LAN (Local Area Network) interface such as a NIC (Network Interface Card), or a USB interface consisting of a USB (Universal Serial Bus) host controller, USB port, etc. Furthermore, the communication unit 151 may be a wired interface or a wireless interface. The communication unit 151 functions as a communication means for the information processing device 150. The communication unit 151 communicates with the base station device 130 according to the control of the control unit 153.

[0032] The memory unit 152 is a data read / write storage device such as DRAM (Dynamic Random Access Memory), SRAM (Static Random Access Memory), flash memory, or hard disk. The memory unit 152 functions as a storage means for the information processing device 150. The memory unit 152 stores, for example, video content.

[0033] The control unit 153 is a controller that controls each part of the information processing device 150. The control unit 153 is implemented by a processor such as a CPU (Central Processing Unit), MPU (Micro Processing Unit), or GPU (Graphics Processing Unit). For example, the control unit 153 is implemented by the processor executing various programs stored in the internal memory of the information processing device 150 using RAM (Random Access Memory) or the like as a working area. The control unit 153 may also be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array). CPUs, MPUs, GPUs, ASICs, and FPGAs can all be considered controllers.

[0034] The control unit 153 comprises an inertial measurement information acquisition unit 1531, a video data generation unit 1532, and a wireless resource allocation request unit 1533. Each block constituting the control unit 153 (from the inertial measurement information acquisition unit 1531 to the wireless resource allocation request unit 1533) is a functional block that represents the function of the control unit 153. These functional blocks may be software blocks or hardware blocks. For example, each of the above-mentioned functional blocks may be a single software module implemented in software (including a microprogram), or a single circuit block on a semiconductor chip (die). Of course, each functional block may also be a single processor or a single integrated circuit. The configuration method of the functional blocks is arbitrary. The control unit 153 may also be composed of functional units different from the above-mentioned functional blocks.

[0035] The inertial measurement information acquisition unit 1531 acquires inertial measurement information from the terminal device 110 via the base station device 130. The inertial measurement information is information related to inertia, such as acceleration information and angular velocity information of the terminal device 110, or detection results detected by sensors mounted on the terminal device 110 (for example, the direction of the user's gaze). The inertial measurement information is information that indicates the state of the user using the terminal device 110 (for example, the direction of the head and gaze). As a more specific example, the information related to inertia may be the change in the yaw, pitch, and roll components of the user's head movement. These components may be detected by sensors mounted on the terminal device 110 (accelerometers and angular velocity sensors (gyro sensors)).

[0036] The video data generation unit 1532 determines the video region based on the acquired inertial measurement information and generates video data to be distributed to the terminal device 110. Based on the inertial measurement information, the video data generation unit 1532 determines the video region to be distributed, which is the direction the user is looking, and generates video data.

[0037] The wireless resource allocation request unit 1533 requests the base station device 130 to allocate wireless resources to be used for transmitting video data.

[0038] The control unit 153 may also acquire information related to user-inputted operations from the terminal device 110 via the base station device 130, determine the video area based on this operation information, and generate video data to be distributed to the terminal device 110. Here, the user-inputted operations may include, for example, game operations, remote control of a device, or operations for driving.

[0039] <1.3. Example of Base Station Equipment Configuration> Next, the configuration of the base station device 130 will be described. Figure 3 is a diagram showing an example of the configuration of the base station device 130 according to the present disclosure.

[0040] The base station device 130 comprises a communication unit 131, a storage unit 132, a network communication unit 133, and a control unit 134. Note that the configuration shown in Figure 3 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the base station device 130 may be implemented in a distributed manner across multiple physically separated configurations.

[0041] The communication unit 131 is a signal processing unit for wireless communication with other wireless communication devices (e.g., terminal device 110 and other base station devices 130). The communication unit 131 operates according to the control of the control unit 134. If the other wireless communication device is terminal device 110, the communication unit 131 may be a wireless transceiver that supports one or more wireless access schemes. For example, the communication unit 131 supports both NR and LTE. In addition to NR and LTE, the communication unit 131 may also support W-CDMA and cdma2000. Furthermore, the communication unit 131 may support communication using NOMA. If the other wireless communication device is another base station device 130, the communication unit 131 may have an X2 interface, an Xn interface, or an F1 interface.

[0042] The communication unit 131 comprises a receiving processing unit 1311, a transmitting processing unit 1312, and an antenna 1314. The communication unit 131 may have multiple receiving processing units 1311, transmitting processing units 1312, and antennas 1314. If the communication unit 131 supports multiple wireless access methods, each part of the communication unit 131 may be configured separately for each wireless access method. For example, the receiving processing unit 1311 and the transmitting processing unit 1312 may be configured separately for LTE and NR.

[0043] The receiving processing unit 1311 processes the uplink signal received via the antenna 1314. The receiving processing unit 1311 operates as a receiving unit that receives the received signal. The receiving processing unit 1311 comprises a wireless receiving unit 1311a, a multiplexing / decoupling unit 1311b, a demodulation unit 1311c, and a decoding unit 1311d.

[0044] The wireless receiver 1311a performs functions such as down-conversion, removal of unwanted frequency components, amplification level control, quadrature demodulation, conversion to digital signals, removal of guard intervals (cyclic prefixes), and extraction of frequency domain signals using fast Fourier transform on the uplink signal. The multiplexing / decoupling unit 1311b separates the uplink channels and uplink reference signals, such as PUSCH (Physical Uplink Shared Channel) and PUCCH (Physical Uplink Control Channel), from the signal output from the wireless receiver 1311a.

[0045] The demodulator 1311c demodulates the received signal using a modulation scheme such as BPSK (Binary Phase Shift Keying) or QPSK (Quadrature Phase Shift Keying) for the modulation symbols of the uplink channel. The modulation scheme used by the demodulator 1311c may be 16QAM (Quadrature Amplitude Modulation), 64QAM, or 256QAM. In this case, the signal points on the constellation do not necessarily have to be equidistant. The constellation may be a non-uniform constellation (NUC).

[0046] The decoding unit 1311d performs decoding on the encoded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to the control unit 134.

[0047] The transmission processing unit 1312 performs the transmission processing of downlink control information and downlink data. Thus, the transmission processing unit 1312 is an acquisition unit that acquires bit sequences such as downlink control information and downlink data from the control unit 134. The transmission processing unit 1312 comprises an encoding unit 1312a, a modulation unit 1312b, a multiplexing unit 1312c, and a wireless transmission unit 1312d.

[0048] The encoding unit 1312a encodes the downlink control information and downlink data input from the control unit 134 using encoding methods such as block coding, convolutional coding, and turbo coding. The encoding unit 1312a may also perform encoding using polar code or LDPC (Low Density Parity Check Code).

[0049] The modulation unit 1312b modulates the encoded bits output from the encoding unit 1312a using a predetermined modulation scheme such as BPSK, QPSK, 16QAM, 64QAM, or 256QAM. In this case, the signal points on the constellation do not necessarily have to be equidistant. The constellation may be a heterogeneous constellation.

[0050] The multiplexer 1312c multiplexes the modulation symbols and downlink reference signals for each channel and places them in predetermined resource elements. The wireless transmitter 1312d performs various signal processing on the signals from the multiplexer 1312c. For example, the wireless transmitter 1312d performs processing such as time-domain to frequency-domain conversion using the Fast Fourier Transform, addition of guard intervals (cyclic prefixes), generation of baseband digital signals, conversion to analog signals, quadrature modulation, upconversion, removal of extraneous frequency components, and power amplification. The signals generated by the transmission processing unit 1312 are transmitted from the antenna 1314.

[0051] The memory unit 132 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk. The memory unit 132 functions as a storage means for the base station device 130.

[0052] The network communication unit 133 is a communication interface for communicating with a node located higher up on the network (for example, an information processing device 150). For example, the network communication unit 133 may be a LAN interface such as a NIC. Alternatively, the network communication unit 133 may be an S1 interface or an NG interface for connecting to a core network node. The network communication unit 133 may be a wired interface or a wireless interface. The network communication unit 133 functions as a network communication means for the base station device 130.

[0053] The control unit 134 is a controller that controls various parts of the base station device 130. The control unit 134 is implemented by a processor (hardware processor) such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). For example, the control unit 134 is implemented by the processor executing various programs stored in the memory device inside the base station device 130 using RAM (Random Access Memory) or the like as a working area. The control unit 134 may also be implemented by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). CPUs, MPUs, ASICs, and FPGAs can all be considered controllers.

[0054] The control unit 134 includes a wireless resource allocation setting unit 1341. The blocks constituting the control unit 134 (wireless resource allocation setting unit 1341) are functional blocks that indicate the functions of the control unit 134. Functional blocks may be software blocks or hardware blocks. For example, the above-mentioned functional block may be a single software module implemented in software (including a microprogram), or a single circuit block on a semiconductor chip (die). Of course, the functional block may also be a single processor or a single integrated circuit. The configuration method of the functional block is arbitrary. Note that the control unit 134 may be composed of functional units different from the above-mentioned functional blocks.

[0055] The wireless resource allocation setting unit 1341, for example, performs wireless resource allocation in response to a request from the information processing device 150. The wireless resource allocation setting unit 1341 may also be a function referred to as a scheduler.

[0056] <1.4. Example of terminal device configuration> Next, the configuration of the terminal device 110 will be described. Figure 4 is a diagram showing an example of the configuration of the terminal device 110 according to the present disclosure.

[0057] The terminal device 110 comprises a communication unit 111, a storage unit 112, an inertial measuring device 114, a control unit 115, and a display unit 116. Note that the configuration shown in Figure 4 is a functional configuration, and the hardware configuration may differ. Furthermore, the functions of the terminal device 110 may be implemented in a distributed manner across multiple physically separated configurations.

[0058] The communication unit 111 is a signal processing unit for wireless communication with other wireless communication devices (e.g., base station device 130 and other terminal devices 110). The communication unit 111 operates according to the control of the control unit 115. The communication unit 111 may be a wireless transceiver that supports one or more wireless access schemes. For example, the communication unit 41 supports both NR and LTE. In addition to NR and LTE, the communication unit 111 may also support W-CDMA and cdma2000. Furthermore, the communication unit 111 may also support communication using NOMA.

[0059] The communication unit 111 includes a receiving processing unit 1111, a transmitting processing unit 1112, a network communication unit 113, and an antenna 1114. The communication unit 111 may have multiple receiving processing units 1111, transmitting processing units 1112, and antennas 1114. The configuration of the communication unit 111, receiving processing unit 1111, transmitting processing unit 1112, and antenna 1114 is the same as that of the communication unit 131, receiving processing unit 1311, transmitting processing unit 1312, and antenna 1314 of the base station device 130.

[0060] The memory unit 112 is a data read / write storage device such as DRAM, SRAM, flash memory, or hard disk. The memory unit 112 functions as a storage means for the terminal device 110.

[0061] The network communication unit 113 is a communication interface for communicating with other devices connected via the network. For example, the network communication unit 113 is a LAN interface such as a NIC. The network communication unit 113 may be a wired interface or a wireless interface. The network communication unit 113 functions as a network communication means for the terminal device 110. The network communication unit 113 communicates with other devices according to the control of the control unit 115. Other devices may be, for example, a controller into which the user inputs information related to the operation.

[0062] The inertial measurement device 114, also known as an IMU (Inertial Measurement Unit), is a device that detects angular velocity and acceleration in three axes. The inertial measurement device 114 may include, for example, an acceleration sensor and a gyroscope. To improve reliability, the inertial measurement device 114 may be equipped with a magnetic field sensor, a barometric pressure sensor, a temperature sensor, etc.

[0063] The acceleration information and angular velocity information detected by the inertial measurement device 114 are transmitted to the information processing device 150 as information related to inertia (an example of inertial measurement information and user information).

[0064] Alternatively, the control unit 115 may calculate the user's state (e.g., head and gaze direction) based on the acceleration and angular velocity information detected by the inertial measurement device 114, and transmit the user's state to the information processing device 150. The user's state is information collectively referred to as, for example, pose information.

[0065] The control unit 115 is a controller that controls various parts of the terminal device 110. The control unit 115 is implemented by a processor such as a CPU, MPU, or GPU. For example, the control unit 115 is implemented by the processor executing various programs stored in the memory device inside the terminal device 110 using RAM or the like as a working area. The control unit 115 may also be implemented by an integrated circuit such as an ASIC or FPGA. CPUs, MPUs, GPUs, ASICs, and FPGAs can all be considered controllers.

[0066] The control unit 115 comprises a video application control unit 1151, a display area identification unit 1152, and a rendering unit 1153. Each block constituting the control unit 115 (video application control unit 1151 to rendering unit 1153) is a functional block that indicates the function of the control unit 115. These functional blocks may be software blocks or hardware blocks. For example, each of the above-mentioned functional blocks may be a single software module implemented in software (including microprograms), or a single circuit block on a semiconductor chip (die). Of course, each functional block may also be a single processor or a single integrated circuit. The configuration of the functional blocks is arbitrary. The control unit 45 may be composed of functional units different from those described above.

[0067] The video application control unit 1151 is a control unit that controls a video application that plays video content, etc. The video application control unit 1151 launches the video application, for example, in response to instructions from the user.

[0068] The display area identification unit 1152 estimates the user's viewpoint using information about inertia and identifies the display area to be displayed on the display unit 116 from the acquired video data.

[0069] The rendering unit 1153 generates images to be displayed in each frame, based on the video data acquired from the information processing device 150, and edits the video to match the display area identified by the display area identification unit 1152.

[0070] The display unit 116 is a display device such as a screen, and displays various information such as images generated by the rendering unit 1153. The display unit 116 is, for example, an opaque, video see-through, or optical see-through display. The display unit 116 plays back the video edited by the rendering unit 1153 by displaying images at a predetermined frame rate.

[0071] <1.5. Example of Network Architecture Configuration> Here, as an example of a communication system applicable to the content distribution system 100 according to the embodiment of this disclosure, the architecture of a fifth-generation mobile communication system (5G) will be described. Figure 5 is a diagram showing an example of a 5G architecture. The 5G architecture includes a UE (User Equipment) 10, a RAN (Radio Access Network) / AN (Access Network) 230, an NGC (Next Generation Core) / 5GC (5G Core) 20, and a DN (Data Network) 240.

[0072] 5GC / NGC20 is also called the 5G core network. 5GC / NGC20 is connected to UE10 via RAN / AN230.

[0073] RAN230 is a base station device that provides a wireless interface, while AN230 is a wired interface device, such as an access point or router. RAN / AN230 includes base station devices called gNBs or ng-eNBs.

[0074] The 5GC / NGC20 consists of a control plane function group 21 and a UPF (User Plane Function) 220.

[0075] The control plane function group 21 includes AUSF (Authentication Server Function) 201, NEF (Network Exposure Function) 202, NRF (Network Repository Function) 203, NSSF (Network Slice Selection Function) 204, PCF (Policy Control Function) 205, SMF (Session Management Function) 206, UDM (Unified Data Management) 207, AF (Application Function) 208, and AMF (Access Management Function) 209.

[0076] UDM207 has the functions of generating 3GPP AKA authentication information and processing user IDs. UDM207 includes a UDR (Unified Data Repository) that holds and manages subscriber information and an FE (Front End) unit that processes subscriber information.

[0077] Furthermore, the AMF209 has functions such as UE10 registration processing, connection management, and mobility management.

[0078] SMF206 has functions such as session management and IP assignment and management for UE10. AUSF201 has authentication functions. NSSF204 has functions related to network slice selection. NEF202 has functions that provide network functionality capabilities and events to third parties, AF208 and edge computing functions.

[0079] NRF203 has the ability to discover network functions and maintain network function profiles. PCF205 has the ability to control policies. AF208 has the ability to interact with the core network and provide services.

[0080] Furthermore, the UPF (User Plane Function) 220 has the function of user plane processing. DN240 is, for example, an entity that provides connections to operator-specific services such as an MNO (Mobile Network Operator), an entity that provides internet connectivity, or an entity that provides connections to third-party services.

[0081] Here, Namf is a service-based interface provided by AMF209, Nsmf is a service-based interface provided by SMF206, Nnef is a service-based interface provided by NEF202, and Npcf is a service-based interface provided by PCF205. Nudm is a service-based interface provided by UDM207, and Naf is a service-based interface provided by AF208. Nnrf is a service-based interface provided by NRF203, and Nnssf is a service-based interface provided by NSSF204. Nausf is a service-based interface provided by AUSF201. Each of these Network Functions (NFs) exchanges information with other NFs via their respective service-based interfaces.

[0082] Furthermore, N1 is a reference point between UE10 and AMF209, and N2 is a reference point between RAN / AN230 and AMF209. N4 is a reference point between SMF206 and UPF220, and information is exchanged between these Network Functions (NFs).

[0083] An example of UE10 is the terminal device 110 in this embodiment. An example of RAN / AN230 is the base station device 130 in this embodiment.

[0084] Furthermore, the information processing device 150 may be an edge server installed within (or near) 5GC / NGC20, or a cloud server (not shown), or a cloud server installed on the internet.

[0085] Alternatively, the information processing device 150 may consist of multiple devices, for example, including 5GC. In this case, the inertial measurement information acquisition unit 1531 is implemented in AF208, and the wireless resource allocation request unit 1533 may be implemented as a function of AMF209 or SMF206. The video data generation unit 1532 corresponds to an edge server installed within 5GC / NGC20, or a cloud server (not shown), or a cloud server (not shown) installed on the internet. The video data generation unit 1532 may also be implemented in AF208.

[0086] <<2. Examples of information processing in content distribution systems>> Next, we will describe an example of information processing performed by the content distribution system 100. <2.1. Example of content delivery processing> Figure 6 is a sequence diagram showing an example of content distribution processing according to an embodiment of this disclosure.

[0087] First, the terminal device 110 launches a video application in response to user instructions (step S101), and requests the information processing device 150 to deliver video content specified by the video application via the base station device 130 (step S102).

[0088] The terminal device 110 measures information related to inertia (step S103) and transmits the measured information related to inertia to the information processing device 150 via the base station device 130 (step S104). The processes in steps S103 and S104 are executed at fixed or variable intervals, or in response to events.

[0089] The information processing device 150 determines the region of the video to be transmitted to the terminal device 110 based on the acquired inertia information (step S105), and generates video data for the determined region (step S106).

[0090] The information processing device 150 transmits the generated video data to the terminal device 110 via the base station device 130 (step S107).

[0091] The terminal device 110 determines the display area of ​​the acquired video data based on the latest measured inertia information (step S108). The terminal device 110 edits the video by generating images to be displayed in each frame from the acquired video data to match the determined display area, and then displays it on the display unit 116 (step S109).

[0092] <2.2. Rendering Process Example> Next, an example of the rendering process performed by the terminal device 110 will be described using Figure 7. Figure 7 is a diagram illustrating an example of the rendering process according to the embodiment of this disclosure. The rendering process described here is performed, for example, in step S109 of Figure 6.

[0093] Figure 7 shows the display timing of the image generated by the terminal device 110 (hereinafter also referred to as the frame image), or in other words, the timing of displaying the frame image.

[0094] The terminal device 110 displays video on the display unit 116 by updating (generating) frame images, which are still images, at a period corresponding to the frame rate.

[0095] For example, if the frame rate is K [fps], K frame images #n (where n is an integer between 1 and (K+1)) are generated per second and displayed on the display unit 116. In this case, the frame image update cycle is 1 / K seconds.

[0096] Next, another example of the rendering process performed by the terminal device 110 will be described using Figure 8. Figure 8 is a diagram illustrating another example of the rendering process according to the embodiment of this disclosure. The rendering process described here is performed, for example, in step S109 of Figure 6.

[0097] When rendering frame images, a technique called Timewarp is sometimes used to draw the frame images. Timewarp is a technique that generates an image of the predicted display area based on acquired video data and the latest inertia information in order to keep the motion-to-photon latency within a certain value. As one application example of this Timewarp, the rendering unit 1153 sets the frame rate displayed on the display unit 116 to m times (m>1) the frame rate of the video data acquired from the information processing device 150.

[0098] Furthermore, the rendering unit 1153 may apply time warp to the rendering of each frame image in order to keep the motion-to-photon latency within a certain value in a delay environment caused by wireless communication between the information processing device 150 and the terminal device 110.

[0099] In VR, it is known that VR sickness occurs due to a "gap" between what the user sees on the screen displayed in front of their eyes through the head-mounted display (HMD) and their own physical sensations. For example, when a user turns around and the scenery on the screen changes, the scenery displayed on the HMD may be slightly delayed from what the user expects to see based on their own perception. This delay is called motion-to-photon latency. Alternatively, when a user perceives depth (space) and moves, the scenery displayed on the HMD may be different from what the user expects to see after moving. When such delays or discrepancies occur, VR sickness is more likely to occur.

[0100] One known method to alleviate VR sickness is to increase the frame rate of the images displayed on the screen. By increasing the frame rate, the difference between the view the user expects and the view actually displayed on the screen is reduced, thereby suppressing the occurrence of VR sickness.

[0101] Furthermore, applying the aforementioned time warp technique can reduce motion-to-photon latency, thereby improving VR sickness.

[0102] In the rendering process explained using Figure 7, the frame rate is K [fps], and the frame image is updated every 1 / K seconds. More specifically, the terminal device 110 generates frame images #1, #2, ... from the video data acquired from the information processing device 150 every 1 / K seconds. At this time, the terminal device 110 generates frame images #1, #2, ... using the video data acquired each time.

[0103] Therefore, if the terminal device 110 tries to increase the frame rate, for example, to suppress the occurrence of VR sickness, it needs to shorten the period during which it acquires video data, which increases the load on wireless communication.

[0104] Therefore, the terminal device 110 uses time warp technology to increase the frame rate of the frame images displayed on the display unit 116 without changing the cycle for acquiring video data from the information processing device 150.

[0105] As shown in Figure 8, the terminal device 110 generates frame image #1 using the acquired video data D1 and displays it on the display unit 116. The terminal device 110 also generates frame image #1-1 using the acquired video data D1 and displays it on the display unit 116. At this time, the terminal device 110 generates frame image #1-1 by applying a time warp process to the video data D1 using the latest inertia information. The terminal device 110 determines the user's viewpoint, or the field of view including the viewpoint, using the latest inertia information, and determines the display area based on the determined viewing direction. This display area is also called a viewport. The terminal device 110 extracts the determined display area from the video data D1 to generate frame image #1-1. In this case, the inertia information can be measured at a shorter period than, for example, the display period of the frame image displayed on the display unit 116.

[0106] In this way, the terminal device 110 can increase the frame rate without shortening the video data acquisition period by generating multiple frame images from a single video data using the latest inertia information measured at different times. For example, in Figure 8, the terminal device 110 generates two frame images #1 and #1-1 from one video data D1. As a result, the terminal device 110 can shorten the period for display on the display unit 116 (hereinafter also referred to as the frame period) to half that of the case where one frame image #1 is generated from one video data D1.

[0107] The terminal device 110 can reduce motion-to-photon latency and suppress VR sickness by reflecting changes in inertia-related information in the same video data and shortening the frame period. This method of reflecting changes in inertia-related information in the same video data is called time warp, or asynchronous time warp (ATW), as described above. By applying this time warp, or asynchronous time warp, motion-to-photon latency can be reduced and the frame period can be shortened.

[0108] <2.3. Communication Processing Examples> Next, an example of communication processing performed in the content distribution system 100 will be explained using Figures 9 to 11. As described above using Figure 5, the NR network architecture is applied in the content distribution system 100.

[0109] In the NR network architecture, for UE10 to receive services via 5GC / NGC20, it performs a registration with 5GC / NGC20, for example. UE10 selects a PLMN (Public Land Mobile Network) corresponding to 5GC / NGC20 and executes a registration procedure.

[0110] Below, an example of the communication process that UE10 undergoes to receive services via 5GC / NGC20, including the registration process, will be explained using Figures 9 to 11.

[0111] (Registration process) First, the registration process performed by UE10 will be explained using Figure 9. Figure 9 is a sequence diagram showing an example of the registration process according to the embodiment of this disclosure.

[0112] As shown in Figure 9, UE10 in the RM-DEREGISTERED state, that is, unregistered with 5GC / NGC20, sends a Registration Request message to RAN / AN230 to perform Initial Registration (step S301). At this time, UE10 sends the Registration Request message including its UE identity.

[0113] UE identity is the 5G-GUTI mapped from the EPS GUTI, if a valid EPS GUTI is present. Here, EPS (Evolved Packet System) refers to the 4G system equivalent to LTE (Long Term Evolution), and consists of EUTRAN and EPC. EPS GUTI (Globally Unique Temporary Identifier) ​​is a temporary ID used to identify a UE within the EPS, instead of IDs uniquely assigned to each UE, such as IMSI (International Mobile Subscriber Identity) or IMEI (International Mobile Equipment Identity), from a security standpoint.

[0114] Alternatively, the UE identity is the PLMN-specific 5G-GUTI assigned by the PLMN that UE10 is attempting to register, if available.

[0115] Alternatively, the UE identity is a PLMN-specific 5G-GUTI assigned by a PLMM to the PLMN (Public Land Mobile Network) that the UE10 is attempting to register with, if available, and treated as an equivalent PLMN.

[0116] Alternatively, the UE identity is a PLMN-specific 5G-GUTI assigned by any PLMN, if available.

[0117] Otherwise, UE10 will include a SUCI (Subscription Concealed Identifier) ​​in the registration request message. Here, the SUCI is an encrypted ID of the SUPI (Subscription Permanent Identifier), which is an ID uniquely assigned to each UE10.

[0118] UE10 includes a mapping of each S-NSSAI (Single NSSAI) of the Requested NSSAI to the S-NSSAIs of the HPLMN (Home PLMN) in the registration request message. This allows UE10 to verify whether the S-NSSAI(s) of the Requested NSSAI (Network Slice Selection Assistance Information) can be authorized based on the Subscribed S-NSSAIs.

[0119] Additionally, if UE10 is using Default Configured NSSAI, it will include the Default Configured NSSAI Indication in the registration request message.

[0120] Here, S-NSSAI consists of a mandatory SST (Slice / Service Type) that identifies the slice type, and an optional SD (Slice Differentiator) that distinguishes different slices within the same SST. The mandatory SST is 8 bits, and the optional SD is 24 bits.

[0121] Furthermore, all or each of the services for AR, VR, MR (Mixed Reality), SR (Substitutional Reality), and XR (X Reality, or eXtended Reality) applications may be defined as slices identified by this S-NSSAI. In other words, services for AR, VR, MR, SR, and XR applications may be implemented by one or more network slices. That is, one or more S-NSSAIs may be associated with services for AR, VR, MR, SR, and XR applications.

[0122] Here, AR, also known as Augmented Reality, is a technology that overlays virtual worlds, such as 3D images and characters created with CG (Computer Graphics), onto the real world.

[0123] VR, also known as virtual reality, is a technology that allows users to experience a virtual world using CG or 360° cameras to capture panoramic images.

[0124] MR, also known as mixed reality, is a technology that closely blends the real world and the virtual world to create a more realistic representation of the virtual world.

[0125] SR, also known as Substitutional Reality, is a technology that makes a virtual world appear as if it were the real world.

[0126] XR is a general term encompassing AR, VR, MR, and SR, which are technologies that create experiences that alter the real world in some way.

[0127] When RAN / AN230 receives a registration request message from UE10, it performs AMF Selection (step S302). If the registration request message does not contain 5G-S-TMSI (5G S-Temporary Mobile Subscription Identifier) ​​or GUAMI (Globally Unique AMF Identifier), RAN / AN230 selects AMF209 based on (R)AT (Radio Access Technology) and, if available, the Requested NSSAI. Alternatively, if the registration request message does not indicate a valid AMF209, RAN / AN230 selects AMF209 based on (R)AT (Radio Access Technology) and, if available, the Requested NSSAI.

[0128] If RAN / AN230 is an NG-RAN, a registration request including the selected PLMN ID, or a combination of the PLMN ID and NID (Network Identifier) ​​that identifies the SNPN (Standalone NonPublic Network), is forwarded to AMF209 (step S303).

[0129] If UE10 has not provided SUCI to AMF209, AMF209 initiates an Identity Request process and sends an Identity Request message to UE10 requesting SUCI (step S304).

[0130] If UE10 receives an Identity Request message in step S304, it responds with an Identity Response message containing the SUCI (step S305). Here, UE10 may obtain the SUCI using the HPLMN's public key.

[0131] The AMF209 performs AUSF Selection based on SUPI or SUCI (step S306) to initiate authentication of the UE10.

[0132] When AUSF201 receives an authentication request from AMF209, it must perform authentication on UE10.

[0133] AUSF201 selects UDM207 for authentication and retrieves authentication data from UDM207.

[0134] Once UE10 is authenticated, AUSF201 provides security information to AMF209.

[0135] If authentication is successful with AMF209, AMF209 initiates NGAP (NG Application Protocol) processing and provides security context to RAN / AN230.

[0136] RAN / AN230 retains the security context and returns a response to AMF209.

[0137] RAN / AN230 will use this security context to protect messages exchanged with UE10 thereafter.

[0138] AMF209 performs UDM Selection based on SUPI and selects UDM207 (step S307).

[0139] AMF209 is registered with UDM207 using Nudm_UECM_Registration (step S308).

[0140] If AMF209 does not have the subscriber information (Subscription Data) for UE10, it uses Nudm_SDM_Get (step S309) to obtain Subscription Data such as Access and Mobility Subscription data and SMF Selection Subscription data (step S310).

[0141] AMF209 retrieves Access and Mobility Subscription data from UDM207 and then generates a UE context. The Access and Mobility Subscription data includes information indicating whether or not the NSSAI can be included in plain text in the RRC Connection Establishment for 3GPP Access.

[0142] The AMF209 sends a Registration Accept message to the UE10 (step S311). The Registration Accept message includes 5G-GUTI and Registration Area. The N2 message containing the Registration Accept message includes Allowed NSSAI.

[0143] Allowed NSSAIs include only S-NSSAIs that do not require Network Slice-Specific Authentication and Authorization based on subscriber information, or S-NSSAIs that have successfully performed Network Slice-Specific Authentication and Authorization based on the AMF209 UE context.

[0144] Furthermore, while AMF209 may provide a list of equivalent PLMNs to UE10s registered in PLMN, AMF209 must not provide a list of equivalent PLMNs to UE10s registered in SNPN.

[0145] UE10 sends a Registration Complete message to AMF209 to notify it that a new 5G-GUTI has been allocated (step S312).

[0146] Following the registration process described above, UE10 enters a registered state with 5GC / NGC20, i.e., the RM-REGISTERED state.

[0147] (PDU session establishment process) Next, the PDU session establishment process performed by UE10 will be described using Figure 10. Figure 10 is a sequence diagram showing an example of the PDU session establishment process according to the embodiment of this disclosure.

[0148] As shown in Figure 10, UE10, registered with AMF209, sends a PDU Session Establishment Request message to AMF209 (step S401). Here, the PDU Session Establishment Request message includes the S-NSSAI corresponding to the requested service from the Allowed NSSAI, and the UE Requested DNN (Data Network Name). The UE Requested DNN is, for example, a DNN that enables connection to AR, VR, MR, SR, and XR services.

[0149] Upon receiving a PDU session establishment request message, the AMF209 performs SMF Selection (step S402). If the PDU session establishment request message includes an S-NSSAI but not a DNN, the default DNN for that S-NSSAI is selected as the DNN. For example, suppose all or each of the services for AR, VR, MR, SR, and XR applications are defined as slices identified by a specific S-NSSAI. In this case, the default DNN for that specific S-NSSAI will be the DNN that enables connections to the AR, VR, MR, SR, and XR services.

[0150] AMF209 sends an Nsmf_PDUSession_CreateSMContext Request containing the Allowed NSSAI S-NSSAI to the selected SMF206 (step S403). Here, the Nsmf_PDUSession_CreateSMContext Request contains SUPI, S-NSSAI, UE Requested DNN, or DNN.

[0151] If Session Management Subscription data corresponding to SUPI, DNN, and S-NSSAI is not available, SMF206 will use Nudm_SDM_Get to retrieve the Session Management Subscription data from UDM207. SMF206 will also use Nudm_SDM_Subscribe to register for notifications when the Session Management Subscription data is updated.

[0152] Upon receiving an Nsmf_PDUSession_CreateSMContext Request, SMF206 generates an SM context if it can process the PDU session establishment request. SMF206 then provides the SM context ID to AMF209 by responding with an Nsmf_PDUSession_CreateSMContext Response (step S404).

[0153] If a second authentication and authorization process by the DN-AAA server is required during the establishment of the PDU session, the SMF206 initiates the PDU Session establishment authentication / authorization process (step S405).

[0154] If dynamic PCC (Policy and Charging Control) is applied to the PDU session being established, SMF206 performs PCF Selection (step S406). Otherwise, SMF206 may apply a local policy.

[0155] Alternatively, SMF206 may perform the SM Policy Association Establishment procedure to establish an SM Policy Association with PCF205 and obtain default PCC Rules for the PDU session (step S407). This allows the PCC Rules to be obtained before selecting UPF220.

[0156] SMF206 performs UPF Selection to select one or more UPF220s (step S408).

[0157] SMF206 sends an N4 Session Establishment Request message to the selected UPF220 (step S409).

[0158] UPF220 responds to SMF206 by sending back an N4 Session Establishment Response message (step S410).

[0159] If multiple UPF220s are selected for a PDU session, this N4 session establishment process will be initiated for each UPF220.

[0160] SMF206 sends a Namf_Communication_N1N2MessageTransfer message to AMF209 (step S411). Here, the Namf_Communication_N1N2MessageTransfer message includes the PDU Session ID, N2 SM information, CN Tunnel Info, S-NSSAI of Allowed NSSAI, and N1 SM container. Here, N2 SM information includes the PDU Session ID, QFI(s), QoS Profile(s), etc. Also, if multiple UPF220s are used for the PDU session, CN Tunnel Info includes tunneling information related to these multiple UPF220s terminating N3.

[0161] The N1 SM container contains the PDU Session Establishment Accept that AMF209 must supply to UE10. The PDU Session Establishment Accept also contains the S-NSSAI of Allowed NSSAI.

[0162] The Namf_Communication_N1N2MessageTransfer message includes the PDU Session ID so that AMF209 knows which access it will use for UE10.

[0163] AMF209 sends an N2 PDU Session Request message to RAN / AN230 (step S412). Here, AMF209 sends a Non-Access-Stratum (NAS) message containing a PDU Session ID and PDU Session Establishment Accept, addressed to UE10, along with N2 SM information received from SMF206, to RAN / AN230 via the N2 PDU Session Request message.

[0164] RAN / AN230 forwards a NAS message containing the PDU Session ID and N1 SM container to UE10 (step S413). Here, the N1 SM container contains PDU Session Establishment Accept.

[0165] RAN / AN230 responds to AMF209 with an N2 PDU Session Response message (step S414).

[0166] AMF209 forwards the N2 SM information received from RAN / AN230 to SMF206 via an Nsmf_PDUSession_UpdateSMContext Request message containing the SM Context ID and N2 SM information (step S415).

[0167] SMF206 initiates an N4 session modification procedure with UPF220 and sends an N4 session modification request message to UPF220 (step S416). SMF206 provides UPF220 with AN tunneling information in addition to the forwarding rules.

[0168] The UPF220 responds to the SMF206 with an N4 Session Modification Response message (step S417). If multiple UPF220s are used in the PDU session, the above N4 session modification procedure applies to all UPF220s terminating N3.

[0169] Following the above steps, a PDU session is established.

[0170] Furthermore, for each QoS flow, the QoS Profile must include QoS parameters. Examples of QoS parameters include 5QI (5G QoS Identifier) ​​and ARP (Allocation and Retention Priority).

[0171] The QoS flow may be either "GBR (Guaranteed Bit Rate)" or "Non-GBR," depending on the QoS Profile.

[0172] For non-GBR QoS flows, the QoS Profile may include a QoS parameter called RQA (Reflective QoS Attribute).

[0173] For a GBR QoS flow, the QoS parameters GFBR (Guaranteed Flow Bit Rate) and MFBR (Maximum Flow Bit Rate) must be included for both the uplink and downlink.

[0174] 5QI are parameters for access nodes that control the forwarding process of QoS flows. Examples include scheduling weights, admission thresholds, queue management thresholds, and link layer settings.

[0175] ARP includes information on priority level, pre-emption capability, and pre-emption vulnerability.

[0176] The ARP priority level defines the relative importance of a QoS flow, with 1 being the highest level of importance, and can be set on a scale from 1 to 15.

[0177] ARP's pre-emption capability is an indicator that defines whether a QoS flow can use resources already allocated to other QoS flows with lower priority levels.

[0178] ARP pre-emption vulnerability is an indicator that defines whether or not resources allocated to a QoS flow are relinquished to allow other QoS flows with a higher priority level.

[0179] The ARP pre-emption capability and ARP pre-emption vulnerability must be set to either "enabled" or "disabled".

[0180] (RRC_CONNECTED transition processing) Signaling between the UE10 and the core network (e.g., AMF209) is performed via NAS signaling. A NAS signaling connection is used to enable this NAS signaling.

[0181] The NAS signaling connection consists of an AN signaling connection between UE10 and AN (Access Network), and an N2 connection between AN and AMF209. Here, the AN signaling connection is, for example, an RRC (Radio Resource Control) connection.

[0182] Therefore, using Figure 11, we will explain the RRC_CONNECTED transition process that transitions the RRC state of UE10 from RRC_IDLE to RRC_CONNECTED. Figure 11 is a sequence diagram showing an example of the RRC_CONNECTED transition process according to the embodiment of this disclosure. The RRC_CONNECTED transition process is activated by UE10 (an example of a terminal device 110) when transitioning from RRC_IDLE to RRC_CONNECTED.

[0183] First, assume that UE10 is in the RRC_IDLE and CM-IDLE state (step S500). Here, the RRC_IDLE state means that an RRC connection has not been established with the base station device 130. The CM-IDLE state means that a NAS signaling connection via N1 has not been established with AMF209.

[0184] UE10 sends an RRCSetupRequest message via SRB (Signalling Radio Bearer)0 for a new connection with base station equipment 130 (step S501).

[0185] When UE10 receives an RRC setup message from base station equipment 130 (step S502), it transitions the RRC state from RRC_IDLE to RRC_CONNECTED, while maintaining CM-IDLE (step S503).

[0186] When the base station device 130 receives an RRC setup complete message from the UE 10 (step S504), it completes the RRC setup process, and the UE 10 transitions to CM-CONNECTED (step S505).

[0187] The initial NAS message (INITIAL UE MESSAGE) from UE10, which is included in the RRCSetupComplete message, is sent to AMF209 (step S506).

[0188] Here, the first NAS message is, for example, a Registration Request message (see step S301 in Figure 9) or a PDU Session Establishment Request message (step S401 in Figure 10). Several NAS messages are also exchanged between UE10 and AMF209.

[0189] The AMF209 prepares the UE context data and sends it to the base station equipment 130 via an Initial Context Setup Request message (step S507). Here, the UE context data includes the PDU session context, Security Key, UE Radio Capability, and UE Security Capabilities, etc.

[0190] The base station device 130 sends a SecurityModeCommand message to the UE 10 (step S508), and when the UE 10 sends a SecurityModeComplete message to the base station device 130 via the SRB1 (step S509), the base station device 130 activates AS (Access-Stratum) security.

[0191] To configure SRB2 and DRBs (Data Radio Bearers), the base station equipment 130 sends an RRC Reconfiguration message to UE10 (step S510), and when UE10 sends an RRC Reconfiguration Complete message to the base station equipment 130 via SRB1 (step S511), the RRC reconfiguration process is completed.

[0192] The base station device 130 sends an "INITIAL CONTEXT SETUP RESPONSE" message to the AMF209 (step S512) to notify it that the setup process is complete.

[0193] (SPS-Config and ConfiguredGrantConfig settings) When AMF209 receives a PDU session establishment request message (see step S401 in Figure 10) from terminal device 110 that includes an S-NSSAI corresponding to a specific service (e.g., S-NSSAI1), it selects SMF206 to provide the service corresponding to this S-NSSAI1. Here, the specific service is, for example, a service for AR, VR, MR, SR, or XR applications.

[0194] Furthermore, the SMF206, selected to provide services compatible with S-NSSAI1, will, for example, select the PCF205 and UPF220 necessary to provide services for AR, VR, MR, SR, and XR applications.

[0195] Furthermore, for example, the base station device 130 may, in response to instructions from the AMF209, determine the SPS-Config and ConfiguredGrantConfig to be set for the downlink and uplink to the terminal device 110, respectively.

[0196] The base station device 130 can configure SPS-Config and ConfiguredGrantConfig on the terminal device 110 via RRC. For example, the base station device 130 configures the terminal device 110 by including SPS-Config and ConfiguredGrantConfig in an RRC reconfiguration message (see step S508 in Figure 11) and sending it.

[0197] SPS-Config is used to configure downlink semi-persistent transmission. Multiple SPS (Semi-Persistent Scheduling) can be configured for a single Bandwidth Part (BWP) of a serving cell. Multiple SPS are configured in SPS-ConfigList.

[0198] In addition, the base station device 130 can also configure ConfiguredGrantConfig via a PDCCH specifying a CS-RNTI (Radio Network Temporary Identifier), in addition to the method referred to as Type 1 via RRC described above.

[0199] The SPS-Config information element included in the RRC message contains the fields periodicity, periodicityExt, and SPS-ConfigIndex.

[0200] Here, if the SPS-Config information element does not contain periodicityExt, it refers to periodicity; if it does contain periodicityExt, it ignores periodicity.

[0201] TS38.331 defines the following values ​​for the periodicity of SPS-Config: 10ms, 20ms, 32ms, 40ms, 64ms, 80ms, 128ms, 160ms, 320ms, and 640ms.

[0202] Furthermore, regarding the periodicityExt in SPS-Config, when the SCS (Subcarrier Spacing) is 15kHz, it is defined that any number of slots between 1 and 640 slots can be set as periodicityExt. When the SCS is 30kHz, it is defined that any number of slots between 1 and 1280 slots can be set as periodicityExt. When the SCS is 60kHz, it is defined that any number of slots between 1 and 2560 slots can be set as periodicityExt. When the SCS is 120kHz, it is defined that any number of slots between 1 and 5120 slots can be set as periodicityExt.

[0203] When an SPS is set, the MAC entity must determine that the Nth downlink will be assigned to a slot (Slot#_N) in the SFN (System Frame Number) that satisfies the following equation (1):

[0204] (numberOfSlotsPerFrame×SFN+Slot#_N)= [(numberOfSlotsPerFrame×SFNinit+slotinit) [+N × periodicity × numberOfSlotsPerFrame / 10] modulo(1024×numberOfSlotsPerFrame)...(1)

[0205] Here, numberOfSlotsPerFrame is the number of slots in the wireless frame (for example, 10 if the SCS is 15kHz), and SFNinit and slotinit are the SFN and slot# for which the first PDSCH (Physical Downlink Shared Channel) transmission was made after the SPS was set, respectively.

[0206] Furthermore, to allocate multiple slots consecutively as SPS resources on the time axis, an additional parameter called numberOfSlotsPerSPS may be introduced. The MAC entity determines that the Nth downlink allocation occurs for the number of consecutive slots in the SFN that satisfy equation (1) above (Slot#_N), starting with numberOfSlotsPerSPS.

[0207] The ConfiguredGrantConfig information element includes the fields periodicity, periodicityExt, and ConfiguredGrantConfigIndex.

[0208] Here, if the ConfiguredGrantConfig information element does not contain periodicityExt, it refers to periodicity; if it does contain periodicityExt, it ignores periodicity.

[0209] TS38.331 defines the periodicity of ConfiguredGrantConfig as 2, 7, n*14 symbols when the SCS is 15kHz. Here, n is one of the values ​​1, 2, 4, 5, 8, 10, 16, 20, 32, 40, 64, 80, 128, 160, 320, or 640.

[0210] Furthermore, regarding the periodicityExt in ConfiguredGrantConfig, for example, if the SCS is 15kHz, it is defined so that any number of symbols between 1 and 640 symbols can be set as periodicityExt, and a period of periodicityExt*14 symbols can be set.

[0211] When a CG (Configured Grant) is set, the MAC entity must determine that the Nth uplink will be assigned to the symbol (Symbol#_N) in the Slot# of the SFN (System Frame Number) that satisfies the following equation (2).

[0212] [(SFN × numberOfSlotsPerFrame × numberOfSymbolsPerSlot) +(Slot#×numberOfSymbolsPerSlot)+Symbol#_N]= (timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity) modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)...(2)

[0213] Here, numberOfSlotsPerFrame is the number of slots in a wireless frame (for example, 10 if SCS is 15kHz), and numberOfSymbolsPerSlot is the number of symbols in a slot (14 for Normal CP). Also, timeDomainOffset and S are parameters obtained from SLIV (Start and length indicator value). timeDomainOffset is the time-axis offset value of the resource when SFN=0, and S is the symbol (Symbol#) to which PUSCH (Physical Uplink Shared Channel) was first assigned.

[0214] Furthermore, to allocate multiple symbols consecutively as CG resources on the time axis, an additional parameter called numberOfSymbolsPerCg may be introduced. The MAC entity determines that the Nth uplink allocation occurs for the number of consecutive symbols numberOfSymbolsPerCg, starting with the symbol (Symbol#_N) in the Slot# within the SFN that satisfies equation (2) above.

[0215] <<3.Technical issues>> Next, we will explain the technical challenges of the content distribution system 100 according to the embodiment of this disclosure, with particular focus on the case where video data is transmitted using semi-persistent transmission.

[0216] Figure 12 illustrates an example of video data distribution by a content distribution system. In Figure 12, video data is communicated between the base station device 130 and the terminal device 110 via SPS. The terminal device 110 displays the video by doubling the frame rate using the time warp described above.

[0217] For example, terminal device 110, which is an HMD, sends a PDU session establishment request message including S-NSSAI1 (see step S401 in Figure 10) to AMF209 in order to use the XR service. Upon receiving the PDU session establishment request message, AMF209 instructs base station device 130 to set SPS-Config and ConfiguredGrantConfig for the downlink and uplink to terminal device 110, respectively.

[0218] The terminal device 110 receives video data with a frame rate of, for example, 45 fps via the base station device 130 using downlink SPS (Semi-Persistent Scheduling). Hereinafter, the frame rate of the video data transmitted by the information processing device 150 will also be referred to as the first frame rate.

[0219] Furthermore, the terminal device 110 transmits the inertia-related information measured by the inertial measurement device 114 via the base station device 130 using the uplink CG (Configured Grant).

[0220] The terminal device 110 uses time warp to display the received video data at a first frame rate (45fps) as a video at, for example, a frame rate of 90fps. Hereinafter, the frame rate of the video displayed by the terminal device 110 on the display unit 116 will also be referred to as the second frame rate.

[0221] The video at the second frame rate (90fps) is displayed on the terminal device 110's screen at a cycle of 11.11ms. Ideally, the video data at the first frame rate (45fps) should be received at a cycle of 22.22ms. However, since the SPS cycle is set in slot units (1ms when SCS is 15kHz), the closest cycle is set to, for example, 22ms.

[0222] Here, we will explain how to set the SPS period. Information related to the format, including the frame rate of the video handled by the service corresponding to S-NSSAI1, is stored, for example, in the UDR (Unified Data Repository).

[0223] When SMF206 requests the establishment of a PDU session to provide a service compatible with S-NSSAI1, it obtains information about the format, including the frame rate of the video handled by the S-NSSAI1-compatible service, from the UDR and provides it to AMF209 via a NAS message.

[0224] The AMF209 determines the SPS period from the information related to the format of the acquired video and instructs the base station device 130 to set the SPS to the determined period.

[0225] Alternatively, based on information related to the format, including the frame rate of the video handled by the service corresponding to S-NSSAI1 obtained from the UDR, the SMF206 may determine the SPS period and provide the SPS period to the base station equipment 130 via the AMF209. For example, the SPS period may be included in the QoS Profile or QoS parameters included in the N2 SM information that the SMF206 provides to the base station equipment 130 via the AMF209.

[0226] Furthermore, the QoS Profile, or QoS parameter, may include information to explicitly indicate the SPS setting. For example, setting it to “sps-enabled”.

[0227] Furthermore, the SMF206 may include the SPS period and information to explicitly instruct the base station equipment 130 to configure SPS, such as "sps-enabled," in the Alternative QoS Profile provided to the base station equipment 130.

[0228] Alternatively, information regarding the format, including the frame rate of videos handled by services compatible with S-NSSAI1, may be included in the PCC Rules provided from PCF205 to SMF206.

[0229] Alternatively, the SMF206 may define a QFI (QoS Flow Identifier) ​​and 5QI (5G QoS Identifier) ​​corresponding to the video format handled by the service compatible with S-NSSAI1, or to the SPS cycle, and notify the base station equipment 130 of this QFI and 5QI.

[0230] At the NAS level, the QoS flow is characterized by a QoS Profile provided from 5GC to base station equipment 130 and QoS rule(s) provided from 5GC to terminal equipment 110. The QoS Profile is used by base station equipment 130 to determine how to process the wireless interface.

[0231] A QoS Profile includes QoS parameters, such as 5QI and ARP.

[0232] QoS rule(s) are used to specify the correspondence between data in the uplink user plane and the QoS flow. For example, CG settings are included in a QoS rule.

[0233] Here, the CG settings include the CG cycle, as well as information to explicitly instruct the CG settings, such as "cg-enabled".

[0234] At the AS level, the DRB determines how packets are processed on the radio interface. The mapping of QoS flows by the base station equipment 130 to the DRB is performed based on the QFI and the associated QoS Profile.

[0235] As described above, the terminal device 110 receives video data at a cycle of 22ms and displays the video (frame image) on the display unit 116 at a cycle of 11.11ms.

[0236] In the example shown in Figure 12, the terminal device 110 receives video data D1 from point A within a predetermined reception period. At the next display timing (point B1), the terminal device 110 displays a first video generated from the received video data D1. Furthermore, at point B2, the terminal device 110 displays a second video generated from the video data D1 as a time warp to the first video displayed at point B1 (hereinafter also referred to as time warp display).

[0237] The terminal device 110 receives video data at a cycle of 22ms and displays the video at a display cycle of 11.11ms. More specifically, the terminal device 110 displays the first video at a cycle of 22.22ms and displays the second video in a time-warp display at a cycle of 22.22ms.

[0238] Thus, the period during which the terminal device 110 receives video data (SPS period) and the period during which the terminal device 110 displays the first video (first frame rate) are different. Therefore, as shown at point A in Figure 12, even if the timing of receiving video data and the timing of displaying the video at the first frame rate (45fps) are synchronized at a given point, a gradual discrepancy will occur between the reception timing and the display timing. Although this discrepancy is small, as it gradually accumulates, the amount of delay until display becomes too large to ignore from the perspective of motion-to-photon latency, or conversely, the display may not be able to keep up.

[0239] • Overview of the proposed technology Therefore, this disclosure proposes a technology that enables stable display of video in a terminal device 110 that periodically receives video data and periodically displays video. As a proposed technology, the base station device 130 changes the settings related to the reception timing when the difference between the periodic reception timing of video data and the video display timing in the terminal device 110 satisfies predetermined conditions.

[0240] <<4. Technical Features>> <4.1. Reconfiguring SPS> Figure 13 is a diagram illustrating the reconfiguration of the SPS by the base station device 130 according to the embodiment of this disclosure.

[0241] As described above, the terminal device 110 receives video data at a cycle of 22 ms, and the terminal device 110 displays the first video at a cycle of 22.22 ms.

[0242] Thus, if the period during which the terminal device 110 receives video data (the SPS period) and the period during which the terminal device 110 displays the first video are different, a discrepancy (difference) will occur between the reception timing and the display timing.

[0243] When the absolute value of the difference between the reception timing at which terminal device 110 receives video data and the display timing of the first video exceeds a predetermined threshold, base station device 130 resets the SPS. Base station device 130 resets the current SPS setting and sets the SPS again. Base station device 130 resets the SPS-Config so that the reception timing at which terminal device 110 receives video data and the display timing of the first video are synchronized.

[0244] When the terminal device 110 detects that the absolute value of the difference between the reception timing for receiving video data and the display timing of the first video exceeds a predetermined threshold, it receives the video data at the modified reception timing based on the reset SPS-Config.

[0245] Figure 14 is a flowchart illustrating the flow of the SPS reset process according to the embodiment of this disclosure. Figure 14 shows the case where the terminal device 110 performs the SPS reset process.

[0246] The terminal device 110 sets the SPS based on a notification from the base station device 130 (for example, an RRC message including SPS-Config) (step 601). The terminal device 110 receives video data from the base station device 130 at the set SPS cycle (step S602).

[0247] The terminal device 110 measures the cumulative time difference between the SPS period (e.g., 22ms) and the video data frame rate (e.g., a first frame rate, 22.22ms) (step S603). More specifically, each time video data is received, the terminal device 110 accumulates the difference between the SPS period and the first frame rate (0.22ms) and calculates the difference between this difference and the display timing at the time the video data was received.

[0248] The terminal device 110 may also calculate the difference between the reception timing and the display timing by calculating the difference between the time the video data was received and the time the video data was displayed.

[0249] The terminal device 110 determines whether the measured cumulative time is equal to or greater than a predetermined threshold (step S604). If the cumulative time is less than the threshold (step S604; No), the process returns to step S602, and the terminal device 110 receives video data at the SPS cycle.

[0250] On the other hand, if the cumulative time is greater than or equal to the threshold (step S604; Yes), the terminal device 110 initiates a process to request the base station device 130 to reset the SPS (step S605), and returns to step S601.

[0251] In step S605, the terminal device 110 may report the request for SPS reconfiguration (SPS-Config reconfiguration) including the cumulative time to be corrected, or the number of slots corresponding to this cumulative time to be corrected, as an offset value.

[0252] When the base station device 130 receives a request from the terminal device 110 to reset the SPS-Config, it resets the SPS based on the reported information regarding the cumulative time to be corrected. This request to reset the SPS-Config is made via an RRC message.

[0253] The terminal device 110 performs the above SPS reset process while receiving video data.

[0254] Here, it is assumed that the terminal device 110 requests SPS resetting, but this is not limited to this (i.e., the request for SPS resetting by the terminal device 110 is not a mandatory component). For example, the base station device 130 may calculate the difference between the display timing at the time of receiving the video data and the reception timing, and determine whether or not to reset the SPS. In this case, the base station device 130 obtains information regarding the frame rate of the video data from, for example, the information processing device 150. Alternatively, the base station device 130 may obtain information regarding the frame rate of the video data from the UDR or the NF of 5GC / NGC20. Alternatively, the base station device 130 may obtain information from higher layers that are not originally terminated (i.e., information regarding the frame rate of the video data) by reading it using DPI (Deep Packet Inspection), etc.

[0255] Alternatively, the NF of 5GC / NGC20 may be configured to reset the SPS based on the difference between the display timing at the time of reception of the video data and the actual timing of display. Here, we will describe the case in which the SMF206 instructs the base station device 130 on the timing to reset the SPS.

[0256] In this case, the terminal device 110 includes, in addition to S-NSSAI1, the absolute value of the cumulative time difference between the period of SPS and the period of the video frame rate that the terminal device 110 can tolerate in the PDU session establishment request message (see step S401 in Figure 10) that it sends to receive the service corresponding to S-NSSAI1.

[0257] SMF206 obtains the cumulative time that S-NSSAI1 and terminal device 110 can tolerate from AMF209 via Nsmf_PDUSession_CreateSMContext Request (see step S401 in Figure 10).

[0258] Note that here, it is assumed that the terminal device 110 notifies the allowable cumulative time, but it is not limited to this. For example, the SMF 206 may use a pre-determined value based on Motion-to-photon latency or the like as the allowable cumulative time.

[0259] The SMF 206 acquires information related to the format including the frame rate of the video handled by the service corresponding to the S-NSSAI 1 from the UDR.

[0260] The SMF 206 determines the period of the SPS based on the frame rate of the video and determines the period for setting the SPS based on the allowable cumulative time. Here, the period for setting the SPS is the period from when the SPS is set until re-setting of the SPS becomes necessary.

[0261] The AMF 209 acquires the period of the SPS and the period for setting the SPS from the SMF 206 via the N2 SM information of Namf_Communication_N1N2MessageTransfer (refer to step S411 in FIG. 10).

[0262] The AMF 209 notifies the base station device 130, via the N2 PDU session request message (refer to step S412 in FIG. 10), of the period of the SPS and the period for setting the SPS acquired from the SMF 206, and the number of slots corresponding to the cumulative time to be corrected as an offset value.

[0263] The base station device 130 sets the period of the SPS in the downlink with the terminal device 110 based on the period of the SPS and the period for setting the SPS acquired from the AMF 209, and starts a timer set for the period for setting the SPS.

[0264] When the expiration date of this timer expires, the base station device 130 re-sets the SPS with the slot for starting the SPS offset by the number of slots corresponding to the offset value, and resets the timer.

[0265] From this point onward, this SPS reconfiguration process will be repeated until terminal device 110 terminates the service that supports S-NSSAI1.

[0266] <4.2. Multiple SPS Settings> The example described above explains the case where the base station device 130 configures one SPS, but the base station device 130 may configure multiple SPSs. This allows the base station device 130 to increase the resources allocated to the SPS.

[0267] Figures 15 and 16 are diagrams illustrating an example of SPS settings by the base station device 130 according to the embodiment of this disclosure.

[0268] As shown in Figure 15, the base station device 130 may set multiple SPS in multiple consecutive slots within the SPS period (e.g., 22 ms). Alternatively, as shown in Figure 16, the base station device 130 may set multiple SPS in multiple distributed slots.

[0269] The base station device 130, for example, assigns video data to multiple slots where SPS is set and transmits it.

[0270] Alternatively, the base station device 130 may perform SPS reconfiguration by switching between each of the multiple SPS.

[0271] In Figures 15 and 16, the base station device 130 sets SPS in multiple slots from the beginning of the SPS cycle, but it is not limited to this. The base station device 130 may set SPS in multiple slots from the end of the SPS cycle, or it may set SPS in multiple slots located in the middle of the SPS cycle. Also, in Figures 15 and 16, the number of resource allocations for which the base station device 130 sets SPS is set to three, but it is not limited to this, and it may be two or four or more.

[0272] Furthermore, the base station device 130 sets intermittent reception, DRX (Discontinuous Reception), on the terminal device 110 in order to periodically monitor the PDCCH. One of the processes performed by the terminal device 110 in idle mode is to monitor the PDCCH that notifies the base station device 130 of paging. Therefore, in idle mode, DRX is set to periodically monitor the PDCCH in order to reduce power consumption during standby.

[0273] Furthermore, reducing power consumption is also important in the connected mode terminal device 110. Therefore, the base station device 130 can configure C-DRX (Connected mode DRX) using RRC Connection Setup or RRC Connection Reconfiguration. The value of longDRX-Cycle is set according to the monitoring period of the PDCCH, and the values ​​of drxStartOffset and onDurationTimer are set based on the slot position to which the PDCCH is assigned. In addition, drx-InactivityTimer is set as the period for receiving scheduling information via the PDCCH and receiving the data indicated by that scheduling information. Furthermore, in addition to this Long DRX, the base station device 130 can configure Short DRX.

[0274] Short DRX is configured by drxShortCycleTimer and shortDRX-Cycle. In connected mode, terminal device 110 monitors the PDCCH according to the Long DRX setting. If demodulation of the PDCCH containing scheduling information is successful over the period that onDurationTimer is active, drx-InactivityTimer is started, and data indicated by the scheduling information can be received over the period that drx-InactivityTimer is active. When the drx-InactivityTimer expires, terminal device 110 starts drxShortCycleTimer and monitors the PDCCH at a shorter frequency (shortDRX-Cycle) than longDRX-Cycle for the period that drxShortCycleTimer is active. This monitoring of the PDCCH at shortDRX-Cycle can ensure, for example, QoS for packets transmitted over short periods. When the drxShortCycleTimer expires, terminal device 110 resumes periodic monitoring of the PDCCH according to the Long DRX setting.

[0275] The base station device 130 sets the C-DRX on the terminal device 110 based on the PDCCH monitoring period and the SPS period. For example, when PDCCH is announced within a slot where SPS is set, one Long DRX is set. The value of longDRX-Cycle is set according to the SPS period, and the values ​​of drxStartOffset and onDurationTimer are set based on the slot location where SPS is set. Here, if SPS is set in multiple consecutive slots (Figure 15), the value of onDurationTimer is set according to the number of consecutive slots. Alternatively, the values ​​of drxStartOffset and onDurationTimer of the Long DRX are set according to the position of the first slot where SPS is set, and the value of drx-InactivityTimer is set according to the position of the second and subsequent slots. If SPS is set in multiple distributed slots (Figure 16), the value of onDurationTimer is set so that all of the distributed slots are included. Alternatively, if SPS is set in multiple distributed slots, the values ​​of Long DRX's drxStartOffset and onDurationTimer are set according to the position of the first slot where SPS is set, and Short DRX's drxShortCycleTimer and shortDRX-Cycle are set according to the positions of the second and subsequent slots. The value of drxShortCycleTimer is set based on the period of the distributed slots within the SPS period, and shortDRX-Cycle is set based on the period that includes the multiple distributed slots.

[0276] Furthermore, when PDCCH is notified in a slot adjacent to a slot where SPS is set, a longDRX-Cycle value is set according to the SPS period, and the values ​​of drxStartOffset and onDurationTimer are set based on the positions of that adjacent slot and the slot where SPS is set. In other words, PDCCH monitoring and data sent using the slot where SPS is set are received over the period of onDurationTimer.

[0277] Note that this single Long DRX setting is reset when the SPS is reset. If the SPS reset is achieved by switching between each of the multiple SPS, the Long DRX will be reset each time the SPS is switched. The values ​​of drxStartOffset and onDurationTimer or drx-InactivityTimer will be reset based on the slot position of the switched SPS. In order to update each parameter of the DRX during this DRX reset, you may also notify each parameter via DCI.

[0278] Alternatively, the monitoring period for PDCCH and the period for SPS can be flexibly set, meaning two independent Long DRXs can be configured to set different periods. A first Long DRX is configured for PDCCH monitoring, and a second Long DRX is configured for receiving data via SPS. The value of the first longDRX-Cycle is set to match the PDCCH monitoring period, and the values ​​of the first drxStartOffset and the first onDurationTimer are set to match the slot that notifies PDCCH. The value of the second longDRX-Cycle is set to match the SPS period, and the values ​​of the second drxStartOffset and the second onDurationTimer are set based on the slot position where SPS is configured. Note that the method described above for configuring a single Long DRX can be used to configure the second Long DRX. Here, if the duration of the first onDurationTimer and the duration of the second onDurationTimer overlap, part or all of them, the terminal device 110 determines the onDurationTimer duration to be the period that is the logical OR of the duration of the first onDurationTimer and the duration of the second onDurationTimer. Furthermore, if the timing of the end of the first onDurationTimer and the timing of the start of the second onDurationTimer, or the timing of the end of the second onDurationTimer and the timing of the start of the first onDurationTimer are below a certain threshold, it may become difficult to control the on / off state of the receiving system of the terminal device 110. In such cases, the terminal device 110 can avoid this problem of controlling the on / off state of the receiving system by designating a continuous period including the durations of the first and second onDurationTimers as the duration of the third onDurationTimer. Furthermore, the threshold for this determination (e.g., 5 slots) may be notified to the terminal device 110 as one of the parameters of the Long DRX (e.g., DurationThreshold) when configuring the second Long DRX. Note that the above-mentioned concept of slots in the configuration of SPS or DRX may include mini-slots.

[0279] FIG. 17 is a diagram for explaining an example of setting SPS by the base station device 130 according to an embodiment of the present disclosure.

[0280] In FIG. 17, the base station device 130 sets a plurality of SPSs having the same period within the period of SPS (for example, 22 ms).

[0281] The base station device 130 sets resource allocations 701 to 704 corresponding to four SPSs having an interval of arbitrary slots in the downlink with the terminal device 110. In FIG. 17, there are six slots vacant between resource allocations 701 and 702, between resource allocations 702 and 703, and between resource allocations 703 and 704. Also, there are four slots vacant between resource allocation 704 and resource allocation 701 of the next period.

[0282] The base station device 130 can individually activate each of the set plurality of resource allocations using DCI (Downlink Control Information). Here, for example, the base station device 130 first activates only the SPS corresponding to the resource allocation 701.

[0283] Suppose that the cumulative time of the difference between the period of SPS and the period of the first frame rate of the video becomes the time difference between resource allocation 701 and resource allocation 702, that is, six slots or more in the example of FIG. 17. In this case, the base station device 130 deactivates the SPS corresponding to the resource allocation 701 using DCI and activates the SPS corresponding to the resource allocation 702.

[0284] Next, let's assume that the cumulative time difference between the SPS period and the first frame rate period of the video exceeds 6 slots, which is the time difference between resource allocation 702 and resource allocation 703. In this case, the base station device 130 uses DCI to deactivate the SPS corresponding to resource allocation 702 and activate the SPS corresponding to resource allocation 703.

[0285] Next, let's assume that the cumulative time difference between the SPS period and the period of the first frame rate of the video exceeds 6 slots, which is the time difference between resource allocation 703 and resource allocation 704. In this case, base station device 130 deactivates the SPS corresponding to resource allocation 703 using DCI, and base station device 130 activates the SPS corresponding to resource allocation 704.

[0286] Similarly, suppose the cumulative time difference between the SPS period and the first frame rate period of the video exceeds 4 slots, which is the time difference between resource allocation 704 and resource allocation 701 for the next period. In this case, the base station device 130 uses DCI to deactivate the SPS corresponding to resource allocation 704 and activate the SPS corresponding to resource allocation 701.

[0287] From this point forward, the activation / deactivation process for each of the configured SPS will continue until terminal device 110 terminates the service corresponding to S-NSSAI1.

[0288] As described above, when the base station device 130 switches the SPS used for transmitting video data, it may notify the terminal device 110 of the SPS offset before and after the switch, for example using DCI.

[0289] Here, information regarding the SPS period, the number of SPS to be set within the SPS period, the arrangement of resource allocations corresponding to each SPS within the SPS period, and the period from activation to deactivation of each SPS is notified from the SMF206 to the base station device 130 during the PDU session establishment process.

[0290] <4.3. CG Reset> In applications such as AR, VR, MR, SR, and XR, where users view free-viewpoint or real-time video on an HMD, it is important to keep motion-to-photon latency within a certain range, as described above. Therefore, in order to reflect head movements, viewpoints, or changes in the field of view including viewpoints in each frame of the video, a periodic uplink occurs in which the terminal device 110 transmits the latest inertial information it has detected. When the terminal device 110 sends a PDU session establishment request to the AMF209 to receive the service corresponding to S-NSSAI1, the 5GC sets CG (Configured Grant) in addition to the SPS described above. Here, the method for setting CG is the same as the method for setting SPS described so far.

[0291] Furthermore, in the PDU session establishment process for the service corresponding to S-NSSAI1, the selected SMF206 may use AF208 to provide the service corresponding to S-NSSAI1.

[0292] For example, if the application used by terminal device 110 requires periodic downlink reception, AF208 determines the SPS setting. Furthermore, if the application involves video reception, AF208 identifies the video format and determines the necessary SPS setting according to the identified video format.

[0293] Furthermore, AF208 may determine the CG settings if the application used by terminal device 110 requires periodic uplink transmission. For example, in order to reflect inertia-related information detected by terminal device 110 in the video received by the application, the CG settings are determined taking into account the video frame rate. In other words, AF208 provides other NFs or base station equipment 130 with information to assist in setting the settings necessary for receiving video data and the settings necessary for transmitting information used to generate video data (e.g., inertia-related information) based on the video format handled by the application.

[0294] The SPS and CG settings determined by AF208 are provided to the base station equipment 130 via SMF206 and AMF209.

[0295] In the example described above, we explained the case where the base station device 130 reconfigures the SPS, but the base station device 130 may also reconfigure the ConfiguredGrantConfig (CGConfig). This point will be explained using Figures 18 and 19.

[0296] Figures 18 and 19 are diagrams illustrating the resetting of the CG by the base station device 130 according to the embodiment of this disclosure.

[0297] As shown in Figure 18, the information processing device 150 periodically receives inertial measurement information via the base station device 130 during the inertial measurement information reception period. The period at this time is determined by the uplink communication period during which the base station device 130 receives inertial measurement information from the terminal device 110, and matches, for example, the CG period set in ConfiguredGrantConfig.

[0298] The information processing device 150 generates video data by performing video data generation processing based on the received inertial measurement information and transmits it to the terminal device 110 via the base station device 130. This video data is transmitted using SPS data transmission at an SPS cycle.

[0299] If the SPS period and the CG period are the same, the information processing device 150 can generate video data based on the most recently received inertial measurement information.

[0300] In this case, if the cumulative time difference between the SPS period and the first frame rate exceeds a threshold, the base station device 130 resets the SPS. This causes a delay in data transmission using SPS.

[0301] In the example shown in Figure 18, the SPS is reconfigured to speed up the transmission timing of data transmission using SPS. As a result, even if the information processing device 150 generates video data based on the most recently received inertial measurement information, it will not be able to send the video data in time with the reconfigured transmission timing. Alternatively, the information processing device 150 may have to generate video data using inertial measurement information received previously in order to send the video data.

[0302] Therefore, as shown in Figure 19, the base station device 130 according to this embodiment resets the Configured Grant (CG) when resetting the SPS. In this case, it is desirable for the base station device 130 to reset the CG before resetting the SPS. This allows the information processing device 150 to generate video data based on the most recently received inertial measurement information, even after resetting the SPS.

[0303] <4.4. Time Warp Changes> In the example described above, the base station device 130 reduced the discrepancy between the communication timing and the display timing occurring in the terminal device 110 by resetting the SPS or CG, but the method of reducing the discrepancy is not limited to this. For example, the terminal device 110 may reduce such a discrepancy by adjusting the number of time warp images displayed using time warp.

[0304] Figure 20 is a diagram illustrating an example of display processing by a terminal device 110 according to an embodiment of this disclosure.

[0305] As shown in Figure 20, the terminal device 110 generates and displays a frame image (hereinafter also referred to as the first image) using the latest inertia information from the video data received during the reception period of the SPS cycle. The terminal device 110 also displays the frame image (time warp image) generated in the same manner using time warp. The terminal device 110 displays the first image or the time warp image as a frame image at a second frame rate.

[0306] In this case, the accumulation of slight discrepancies between the SPS period and the first frame rate (45fps) period results in a situation where the video data is not received in time to display the first image. In Figure 20, at point B, the video data is not received in time to display the first image.

[0307] Assume that the cumulative time difference between the SPS period and the first frame rate period exceeds a certain threshold, resulting in a situation where the display timing of the first image cannot be kept up. As shown in the lower diagram of Figure 20, the terminal device 110 displays a time-warped image, which is created by applying time warp to the video data received at a previous reception timing, at the timing when the first image would normally be displayed. This allows the terminal device 110 to delay the display timing of the first image by half a cycle, and to display the first image generated using the most recently received video data.

[0308] The above example described a case where the video data is received too late and does not coincide with the display timing of the first image. Now, let's discuss a case where the video data is received too early.

[0309] Figure 21 is a diagram illustrating another example of display processing by the terminal device 110 according to the embodiment of this disclosure.

[0310] The accumulation of slight discrepancies between the SPS period and the first frame rate (45fps) period can lead to a situation where the delay between receiving the video data and displaying the first image generated based on that video data becomes large. In Figure 21, at point D, the delay between receiving the video data and displaying the first image becomes so large that, for example, motion-to-photon latency cannot be ignored.

[0311] Thus, suppose that the cumulative time difference between the SPS period and the first frame rate period exceeds a certain threshold, and the delay from receiving the video data to displaying the first image becomes so large that the motion-to-photon latency cannot be ignored.

[0312] As shown in the lower diagram of Figure 21, the terminal device 110 displays a first image generated from the most recently received video data at the timing (point C) where it displays a time-warped image obtained by applying time warp to the video data received at the previous reception timing. This allows the terminal device 110 to display the first image half a cycle earlier, thereby reducing the effects of motion-to-photon latency.

[0313] <4.5. Setting Priorities> The examples described above illustrate cases where one video data is assigned to one SPS, but this is not limited to this. For example, the base station device 130 may assign video data divided into multiple regions to multiple SPS according to the priority of each region. Here, each divided video data is, for example, called a segment.

[0314] Figures 22 to 25 illustrate an example of video data allocation processing by a base station device 130 according to an embodiment of this disclosure.

[0315] The information processing device 150 sets the user's viewpoint, or the field of view including the viewpoint, based on the latest inertia-related information obtained from the terminal device 110. Furthermore, the information processing device 150 determines an area so that the set viewpoint or field of view point is at the center, and generates video data for the determined area.

[0316] At this point, as shown in Figure 22, the information processing device 150 divides the generated video data into multiple regions. The information processing device 150 then changes the resolution of the divided regions according to the distance between the set user viewpoint and the divided regions.

[0317] For example, as shown in Figure 22, the information processing device 150 generates video data assuming the user's viewpoint is located in the center of the video data, and divides the generated video data into nine 3x3 regions.

[0318] In this case, as shown in Figure 23, the information processing device 150 sets the resolution of the central region 801, which is closest to the viewpoint, to the highest resolution (high resolution). The information processing device 150 also sets the resolution of regions 806-809, which are furthest from the viewpoint and located at the corners of the video data, to the lowest resolution (low resolution). The information processing device 150 sets the resolution of the remaining regions 802-805 to a resolution between high resolution and low resolution (medium resolution). Regions 802-805 are regions that are adjacent to region 801, which is closest to the viewpoint, by an edge, and regions 806-809 are regions that are adjacent to regions 802-805 by an edge.

[0319] Note that while this explanation describes dividing video data into nine parts, the number of divisions for image data is not limited to nine. The number of divisions may be between two and eight, or ten or more. Also, while this explanation describes dividing a region into three resolutions (low, medium, and high), the number of resolutions is not limited to three. The number of resolutions may be two, or four or more. Furthermore, while this explanation describes the case where each divided region is the same size, the example is not limited to cases where each region is the same size. For example, the data may be divided into regions of different sizes.

[0320] Here, multiple video data formats with different resolutions may be predefined as applicable to each region. In other words, the information processing device 150 selects a video format with a different resolution depending on the distance from the viewpoint and generates video data.

[0321] The information processing device 150 may select different resolution video formats based on the distance from the viewpoint, as well as the communication quality between the terminal device 110 and the base station device 130. For example, AF208 includes a wireless communication quality acquisition unit (not shown) to acquire the communication quality between the terminal device 110 and the base station device 130 from the base station device 130. The wireless communication quality acquisition unit provides the information processing device 150 with the communication quality between the terminal device 110 and the base station device 130 acquired from the base station device 130.

[0322] As shown in Figure 24, AF208 assigns priorities to each region of the video according to its resolution. High priority is assigned to the high-resolution region 801, medium priority to the medium-resolution regions 802-805, and low priority to the low-resolution regions 806-809. Here, the priorities are, for example, QFI (QoS Flow identifier) ​​and 5QI (5G QoS Identifier).

[0323] Here, a QoS flow is the finest granularity concept for differentiating QoS within a PDU session, and in 5GS, a QoS flow is identified by a QFI. In N3 between the UPF220 and the RAN / AN230 corresponding to the base station equipment 130, each data flow is sent with an encapsulated QFI attached to the header. Note that the QFI may be equivalent to 5QI.

[0324] The AMF209 determines the SPS settings, including the SPS period, based on the frame rate of the video in each priority region. Here, the AMF209 may set the frame rate of the video in each priority region to be the same, or it may lower the frame rate of the video in the lower priority region.

[0325] Furthermore, the SPS setting for each priority is determined by taking into consideration that videos from higher priority areas are received by the terminal device 110 before videos from lower priority areas.

[0326] The SPS settings for each priority determined by AMF209 are provided to the base station equipment 130 via SMF206 and AMF209.

[0327] The base station device 130 performs resource allocation for SPS based on the SPS settings for each priority obtained from the AMF209.

[0328] In the example shown in Figure 25, the base station device 130 sets up periodic resource allocation 810 for high priority SPS, periodic resource allocation 811 for medium priority SPS, and periodic resource allocation 812 for low priority SPS.

[0329] The base station device 130 identifies the priority based on the QFI attached to the data flow received from the UPF220 and transmits the data for each region of the video data using resource allocation according to priority. For example, the base station device 130 transmits the high-priority region 801 to the terminal device 110 using resource allocation 810. Similarly, the base station device 130 transmits the medium-priority regions 802-805 to the terminal device 110 using resource allocation 811, and the low-priority regions 806-809 to the terminal device 110 using resource allocation 812.

[0330] Furthermore, information including the mapping and format of each region necessary for the rendering unit 1153 of the terminal device 110 to restore the divided video into a single video is transmitted using periodic resource allocation 810 for sending high-priority data. Here, the information including the mapping and format of each region necessary for restoring the divided video into a single video may be, for example, an MPD (Media Presentation Description) or a file for a similar purpose.

[0331] The rendering unit 1153 can apply a decoding method suitable for the format of each divided region, based on the information including the mapping and the format of each region, to reconstruct it as video data for a single region.

[0332] The rendering unit 1153 sets the timing of the video frames to be displayed (for example, see point B1 in Figure 12) based on the timing set by the SPS (for example, see point A in Figure 12) when the data is first received via the periodic resource allocation 810. This video frame timing is subject to, for example, the time required for decoding, the time required for rendering, and an offset period that takes into account margins. This offset period is controlled by the video application control unit 1151.

[0333] Here, we have shown an example where the resolution of the divided regions is changed according to the distance between the user's viewpoint and the divided region. However, it is also possible to change only the priority without changing the resolution of each divided region. The information processing device 150 sets the priority of region 801, which is the closest to the viewpoint and located in the center of the divided region, to the highest priority (high priority). The information processing device 150 also sets the priority of regions 806 to 809, which are the furthest from the viewpoint and located at the corners of the video data, to the lowest priority (low priority). The information processing device 150 sets the priority of the remaining regions 802 to 805 to a priority between high priority and low priority (medium priority). Here, the priorities are, for example, QFI and 5QI.

[0334] Furthermore, when transmitting data for each region, the transmission order may be determined based on pixels. For example, even if the terminal device 110 cannot receive information for all pixels within a predetermined period, the information processing device 150 prioritizes transmitting information for pixels in specific locations of the frame image so that a low-resolution image can be displayed. Subsequently, it controls the transmission of information for the remaining pixels. The base station device 130 transmits data for each region to the terminal device 110 according to this pixel-based priority. The rendering unit 1153 synthesizes the received low-resolution frame images to generate a high-resolution frame image.

[0335] <<5. Other Embodiments>> The above-described embodiment is merely an example, and various modifications and applications are possible.

[0336] In the embodiments described above, an example was shown in which a video with a frame rate of 45fps is displayed as a 90fps video using time warp, but the frame rate is not limited to this example. The technology of this disclosure can be applied to the display of videos with various frame rates.

[0337] In the above-described embodiment, the information processing device 150 generates video data based on inertia-related information and transmits it to the terminal device 110. That is, the information processing device 150 generates video data corresponding to the user's viewpoint from 360-degree video information and transmits it to the terminal device 110, but is not limited to this. For example, the information processing device 150 may transmit the 360-degree video data as is to the terminal device 110. In this case, the information processing device 150 may reduce the amount of data transmitted by, for example, transmitting 360-degree video data with a lower resolution. Alternatively, the information processing device 150 may transmit both video data corresponding to the user's viewpoint and 360-degree video data with reduced resolution to the terminal device 110.

[0338] Furthermore, in the above-described embodiment, it was assumed that the NF of the base station device 130 or 5GC / NGC20 acquires the frame rate, but this is not limited to this. That is, the frame rate information acquired by the NF of the base station device 130 or 5GC / NGC20 may be not only the frame rate value itself (e.g., 45fps or 90fps), but also an index corresponding to the frame rate (e.g., QFI or 5QI).

[0339] Furthermore, while an example was shown where information for restoring a divided video into a single video includes mapping and the format of each region, this information for restoring a divided video into a single video may also include information about the frame rate. The NF of the base station equipment 130 and 5GC / NGC20 may obtain the frame rate through this information for restoring a divided video into a single video.

[0340] Furthermore, although the above-described embodiment described a case in which the terminal device 110 receives video data on the downlink and transmits inertia-related information on the uplink, the invention is not limited to this. For example, the data received by the terminal device 110 may be any data that is received in real time and periodically, and may not be video data. Similarly, the data transmitted by the terminal device 110 may be any data that is transmitted in real time and periodically, and may not be inertia-related information. Thus, the technology of this disclosure can be applied to the communication of various types of data that are transmitted in real time and periodically.

[0341] <<6. Application Examples>> Furthermore, in some embodiments, the SPS or CG settings described above may take into account the requirements of services using Augmented Reality (AR), Virtual Reality (VR), Mixed Reality (MR), or Substitutional Reality (SR) (e.g., cloud gaming).

[0342] Several services are being considered as use cases for 5G NR (New Radio). Among these, AR / VR services are expected to be a killer content for 5G NR. 3GPP TR 22.842 v17.1.0 and TS 22.261 v17.0.1 specify requirements for rendering game images for cloud games using AR / VR. More specifically, these technical specifications and reports describe the following regarding motion-to-photon delay and motion-to-sound delay as acceptable delays at a level where AR / VR users do not experience any unnaturalness in the movement of the image during game image rendering.

[0343] • Motion-to-photon delay: While maintaining the required data rate (1Gbps), the motion-to-photon delay is in the range of 7-15ms. • Motion-to-sound delay: Less than 20ms.

[0344] Motion-to-photon delay is defined as the delay between the user's physical head movement and the updated image in the AR / VR headset (e.g., Head Mount Display). Motion-to-sound delay is defined as the delay between the user's physical head movement and the updated sound waves from the head-mounted speaker reaching the user's ears. The AR / VR headset and head-mounted speaker here may be the terminal device 110 in this disclosure.

[0345] To meet these latency requirements, the aforementioned technical specifications and reports stipulate that the 5G system must satisfy the following two rendering requirements:

[0346] • Max Allowed End-to-end latency: 5ms (i.e., the total allowable latency of the uplink and downlink between the interface between the terminal (e.g., terminal device 110) and the data network (e.g., the network where the Application Function (AF) is located) is 5ms). • Service bit rate: user-experienced data rate: 0.1Gbps (100Mbps) (i.e., throughput sufficient to support AR / VR content).

[0347] Rendering here includes Cloud rendering, Edge rendering, and Split rendering. Cloud rendering renders AR / VR data on the cloud of the network (on a certain entity based on the core network (including UPF) and data network (including application servers and AF) deployments, without considering the user's location). Edge rendering renders AR / VR data on the edge of the network (on a certain entity based on the core network (including UPF) and data network (including application servers and AF) deployments closer to the user's location (for example, an Edge Computing Server (an application server in the data network in a network deployment for Edge Computing))). Split rendering means that part of the rendering is done on the cloud and the other part is done on the edge.

[0348] Figure 26 is an illustrative diagram of a rendering server and an AR / VR client related to rendering. Figure 26 is described in the aforementioned technical report. Here, the AR / VR client may correspond to the terminal device 110 in this disclosure. The Cloud Render Server may correspond to the information processing device 150 in this disclosure. The Cloud Render Server may also be an application server for edge computing (e.g., an Edge Computing Server) within a Local Area Data Network (LADN) whose interface is a Local UPF connected to the base station device 130 in this disclosure. The Cloud Render Server may also be named Edge Render Server or Split Render Server.

[0349] In this application example, for example, in the case of data communications (e.g., sessions (PDU sessions), bearers (Radio Bearer), packet flows (QoS flows)) that require motion-to-photon delay (7-15ms) or motion-to-sound delay (less than 20ms), the above-described SPS or CG may be reconfigured.

[0350] In other aspects, the SPS or CG described above may be reconfigured in the case of data communications (e.g., sessions (PDU sessions), bearers (Radio Bearers), packet flows (QoS flows)) that require a rendering requirement of Max Allowed End-to-end latency (5ms).

[0351] <<7. Conclusion>> While preferred embodiments of the present disclosure have been described in detail above with reference to the attached drawings, the technical scope of the present disclosure is not limited to such examples. It is clear to any person with ordinary skill in the art of the present disclosure that various modifications or alterations may be conceived within the scope of the technical ideas described in the claims, and these will naturally also fall within the technical scope of the present disclosure.

[0352] Of the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically by known methods. In addition, the processing procedures, specific names, and information including various data and parameters shown in the above documents and drawings can be changed at will unless otherwise specified. For example, the various information shown in each figure is not limited to the information shown.

[0353] Furthermore, the components of each illustrated device are functionally conceptual and do not necessarily need to be physically configured as shown. In other words, the specific forms of distribution and integration of each device are not limited to those shown, and all or part of them can be functionally or physically distributed and integrated in any unit according to various loads and usage conditions.

[0354] Furthermore, the embodiments described above can be combined as appropriate, as long as the processing content is not contradictory.

[0355] Furthermore, the effects described herein are merely descriptive or illustrative and not limiting. In other words, the technology relating to this disclosure may produce other effects that will be apparent to those skilled in the art from the description herein, in addition to or instead of the effects described herein.

[0356] Furthermore, the following configurations also fall within the technical scope of this disclosure. (1) A wireless communication unit that transmits video data to a terminal device at predetermined intervals, A control unit that changes the settings related to the reception timing when the difference between the periodic reception timing at which the terminal device receives the video data and the display timing at which the video data is displayed on the terminal device at a predetermined frame rate satisfies a predetermined condition, A base station device equipped with the following features. (2) The base station device described in (1) wherein the setting for the reception timing is a Semi-Persistent Scheduling (SPS) setting. (3) The base station device according to (1) or (2), wherein the control unit changes the setting relating to the reception timing by resetting the reception timing so that the reception timing and the display timing are aligned. (4) The base station device according to any one of (1) to (3), wherein the control unit changes the setting relating to the reception timing by notifying the terminal device of an offset indicating the changed reception timing. (5) The base station device according to any one of (1) to (4), wherein the control unit changes the settings relating to the reception timing by notifying the terminal device of the settings to be deactivated and the settings to be newly activated from among the settings relating to the reception timing. (6) The predetermined condition is that the difference is greater than or equal to a threshold, or the cumulative difference is greater than or equal to a threshold, according to any one of (1) to (5). (7) The base station device according to any one of (1) to (6), wherein the control unit changes the setting of the reception timing in response to a request from the terminal device. (8) The base station device according to any one of (1) to (7), wherein the control unit changes the setting of the reception timing in response to instructions from a network function belonging to the connected network. (9) The base station device according to any one of (1) to (8), wherein the control unit obtains information regarding the frame rate from the content server that acquires the video data. (10) The terminal device generates images from the video data based on information about the user's viewpoint, and when displaying the video data at a second frame rate greater than the frame rate, the base station device according to any one of (1) to (9), wherein the terminal device adjusts the number of images to be generated according to the difference. (11) The control unit transmits each of the multiple regions into which the video data has been divided, according to the reception timing setting corresponding to the priority of the region. The priority of the aforementioned region is set based on information regarding the user's perspective. A base station device as described in any one of (1) to (10). (12) The priority of the said region is set according to the resolution of the said region, which is set based on information about the user's viewpoint. (11) The base station equipment described above. (13) A wireless communication unit that receives video data from a base station device at predetermined intervals, A control unit that displays the aforementioned video data at a predetermined frame rate, Equipped with, The wireless communication unit receives the video data based on the changed reception timing setting when the difference between the periodic reception timing for receiving the video data and the display timing for displaying the video data at a predetermined frame rate satisfies a predetermined condition. Terminal device. (14) The process involves transmitting video data to the terminal device at predetermined intervals, The setting for the reception timing is changed when the difference between the periodic reception timing at which the terminal device receives the video data and the display timing at which the video data is displayed on the terminal device at a predetermined frame rate satisfies a predetermined condition. A communication method that includes this. (15) Receiving video data from the base station equipment at predetermined intervals, Displaying the aforementioned video data at a predetermined frame rate, When receiving the aforementioned video data, if the difference between the periodic reception timing for receiving the video data and the display timing for displaying the video data at a predetermined frame rate satisfies a predetermined condition, the video data is received based on the modified reception timing setting. A communication method that includes this. (16) A wireless communication unit that receives user information from a terminal device in a first cycle and transmits video data generated based on the user information in a second cycle, A control unit that changes the setting of the transmission timing for the periodic transmission of information about the user by the terminal device when the difference between the periodic reception timing at which the terminal device receives the video data and the display timing at which the video data is displayed on the terminal device at a predetermined frame rate satisfies a predetermined condition, A base station device equipped with the following features. (17) The base station device according to (1), wherein the control unit further sets the intermittent reception period and the ON period based on the setting for the reception timing. (18) The base station device according to (17), wherein the control unit sets one intermittent reception as the setting for intermittent reception and assigns the downlink control channel to the ON period in the setting for one intermittent reception. (19) The control unit sets a second intermittent reception setting, which is different from the first intermittent reception setting for monitoring the downlink control channel, as the intermittent reception setting. The base station device according to (17), wherein the second intermittent reception period and the ON period are set based on the settings relating to the reception timing. (20) The base station device according to (19), wherein the control unit sets a threshold value relating to the interval between the first ON period of the first intermittent reception and the second ON period of the second intermittent reception as the setting for the second intermittent reception. (twenty one) The terminal device according to (13), wherein the wireless communication unit sets the intermittent reception period and the ON period based on the reception timing setting. (twenty two) The wireless communication unit sets a second intermittent reception setting, which is different from the first intermittent reception setting for monitoring the downlink control channel, as the intermittent reception setting. Herein, the second intermittent reception period and the ON period are set based on the reception timing setting, as described in (21), for the terminal device. (twenty three) The terminal device according to (22), wherein the wireless communication unit sets a third on period that includes the first on period and the second on period when part or all of the first on period of the first intermittent reception and the second on period of the second intermittent reception overlap. (twenty four) The terminal device according to (22), wherein the wireless communication unit sets a threshold value relating to the interval between the first ON period of the first intermittent reception and the second ON period of the second intermittent reception as the setting for the second intermittent reception, and sets a third ON period including the first ON period and the second ON period if the interval between the first ON period of the first intermittent reception and the second ON period of the second intermittent reception is less than or equal to the threshold value. [Explanation of symbols]

[0357] 100 Content Distribution Systems 110 Terminal device 130 Base station equipment 131 Communications Department 134 Control Unit 150 Information Processing Devices

Claims

1. Periodic information of XR traffic is obtained from the core network. The periodic information of the traffic of the XR is shown by the information relating to the traffic. The periodic information of the traffic of the aforementioned XR is used to configure DRX (Discontinuous Reception). Base station equipment.

2. The base station apparatus according to claim 1, wherein the information relating to the traffic of the XR relates to a Policy and Charging Control (PCC) Rule.

3. The base station device according to claim 1, which, in connection with the PDU (Protocol Data Unit) session establishment process for an XR service, acquires the periodic information of the XR traffic from the core network.

4. The base station device according to claim 1, wherein multiple transmission opportunities are set within one cycle of the Configured Grant (CG) setting.

5. The base station device according to claim 4, wherein a plurality of transmission opportunities are set within one cycle of the setting of the CG related to the period information of the traffic of the XR.

Images