Information processing device, base station device, communication method and communication system

Abstract

An information processing device (260) is provided with a control unit (263). The control unit (263) acquires information from a device (100) for providing an application function to a terminal device (400). On the basis of the information, the control unit (263) uses an application programming interface (API) to notify a base station device (300), that communicates with the terminal device (400), of setting information pertaining to terminal device (400) intermittent reception.

Description

[Technical Field]

[0001] The present disclosure relates to an information processing device, a base station device, a communication method, and a communication system. [Background technology]

[0002] Studies are underway on next-generation mobile communication systems that can be used by various entities according to regional and individual needs. For example, next-generation mobile communication systems include mechanisms that allow various entities, such as local companies and local governments, to flexibly build and use networks on a spot basis within their own buildings or premises, separate from nationwide 5G services provided by mobile phone operators. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-57929 Summary of the Invention [Problem to be solved by the invention]

[0004] When networks are constructed in a spot manner, multiple networks exist simultaneously, and a server that provides application functions to a terminal device may simultaneously communicate with terminal devices connected to different networks. For example, when terminal devices connected to different networks play a game at the same time, they simultaneously communicate with the same game server.

[0005] When multiple terminal devices synchronously connect to a single server, such as when playing a network game, there is a risk that the amount of delay that occurs in communication with the server may differ for each terminal device. In this case, if the amount of delay for each terminal device is constant, the multiple terminal devices can communicate with the server in synchronization by taking the delay into account in advance on the server side. However, if the delay fluctuates, the amount of delay will not be fixed, and it may be difficult for multiple terminal devices to communicate with the server in synchronization.

[0006] Thus, there has been a demand for suppressing delay fluctuations when multiple terminal devices communicate with a server in synchronization.

[0007] Therefore, the present disclosure provides a mechanism that can further suppress delay fluctuations. [Means for solving the problem]

[0008] According to the present disclosure, there is provided an information processing device. The information processing device includes a control unit. The control unit acquires information from a device that provides an application function to a terminal device. Based on the information, the control unit notifies a base station device that communicates with the terminal device of setting information related to discontinuous reception of the terminal device using an application programming interface (API). [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram for explaining an overview of a communication system 1 according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating an example of 5G architecture. [Figure 3] FIG. 1 is a diagram illustrating an example of 4G architecture. [Figure 4] FIG. 1 is a diagram for explaining a configuration example of Private 5G according to an embodiment of the present disclosure. [Figure 5] FIG. 1 is a block diagram illustrating a configuration example of an information processing device according to an embodiment of the present disclosure. [Figure 6] FIG. 2 is a block diagram illustrating a configuration example of a base station device according to an embodiment of the present disclosure. [Figure 7] FIG. 1 is a block diagram illustrating a configuration example of a terminal device according to an embodiment of the present disclosure. [Figure 8] FIG. 2 is a diagram for explaining a delay in the communication system according to the first embodiment of the present disclosure. [Figure 9]FIG. 1 is a diagram illustrating an overview of DRX. [Figure 10] FIG. 10 is a diagram for explaining delay fluctuations caused by CDRX. [Figure 11] FIG. 10 is a diagram for explaining delay fluctuations caused by CDRX. [Figure 12] 10A to 10C are diagrams for explaining an example of a CDRX setting process executed in the communication system according to the first embodiment of the present disclosure. [Figure 13] FIG. 2 is a sequence diagram for explaining the flow of a CDRX setting process according to the first embodiment of the present disclosure. [Figure 14] FIG. 10 is a sequence diagram illustrating an example of the flow of a CDRX setting request process according to an embodiment of the present disclosure. [Figure 15] FIG. 10 is a diagram for explaining delay fluctuation according to the second embodiment of the present disclosure. [Figure 16] FIG. 10 is a diagram for explaining the timing of receiving video data by a terminal device according to a second embodiment of the present disclosure. [Figure 17] FIG. 10 is a diagram illustrating the arrival timing of data notified by a base station device according to a second embodiment of the present disclosure. [Figure 18] FIG. 10 is a sequence diagram for explaining an example of the flow of a notification process of arrival timing according to the second embodiment of the present disclosure. [Figure 19] FIG. 10 is a sequence diagram for explaining another example of the flow of the arrival timing notification process according to the second embodiment of the present disclosure. [Figure 20] FIG. 10 is a diagram for explaining the start timing of CDRX. [Figure 21] FIG. 10 is a diagram for explaining an example of the flow of CDRX synchronization processing according to the third embodiment of the present disclosure. [Figure 22] FIG. 10 is a diagram for explaining an example of the flow of CDRX synchronization processing according to the third embodiment of the present disclosure. [Figure 23] FIG. 13 is a diagram for explaining an example of the flow of a switching process according to the fourth embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this specification and drawings, components having substantially the same functional configurations are designated by the same reference numerals, and redundant description will be omitted.

[0011] In this specification and drawings, similar components of the embodiments may be distinguished by adding different letters to the same reference numerals. However, when there is no need to particularly distinguish between the similar components, only the same reference numerals are used.

[0012] One or more embodiments (including examples and modifications) described below can be implemented independently. However, at least a portion of the embodiments described below may be implemented in appropriate combination with at least a portion of another embodiment. These embodiments may include novel features that are different from one another. Therefore, these embodiments may contribute to solving different purposes or problems and may produce different effects.

[0013] The explanation will be given in the following order. 1. Overview 1.1. System Overview 1.2. Overview of the proposed technology 2. Example of communication system configuration 2.1. Network Architecture Configuration Example 2.2.Private 5G 2.3. Information Processing Device 2.4.Base station equipment 2.5. Terminal Device 3. First embodiment 4. Second Embodiment 5. Third Embodiment 6. Fourth Embodiment 7. Variations

[0014] <<1. Overview>> <1.1. System Overview> First, an overview of a communication system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 1. Fig. 1 is a diagram for explaining an overview of the communication system 1 according to an embodiment of the present disclosure.

[0015] In the example shown in FIG. 1, the communication system 1 includes an information processing device 100, core networks 200A and 200B, base station devices 300A and 300B, and terminal devices 400A and 400B.

[0016] The information processing device 100 is a server (device) that provides application functions to the terminal device 400. Hereinafter, the information processing device 100 will be referred to as the application server 100.

[0017] The application server 100 communicates synchronously with a plurality of terminal devices 400. For example, the application server 100 is a game server that provides a network game to a plurality of terminal devices 400. In this case, the application server 100 synchronously distributes Augmented Reality (AR) / Virtual Reality (VR) data, which is game data, to the plurality of terminal devices 400.

[0018] Furthermore, the application server 100 may be, for example, an IoT (Internet of Things) control server. For example, the application server 100 may be a control server that causes a plurality of automobiles (an example of the terminal devices 400) to line up and run. In this case, the application server 100 controls the plurality of automobiles by, for example, synchronizing timing. The application server 100, for example, delivers IoT control information (for example, automobile control information) to the plurality of terminal devices 400 in a synchronized manner.

[0019] The core network 200 is a local cellular network such as local 5G or local 4G. The core network 200 includes an information processing device 260 having the functionality of an AF (Application Function) node, for example.

[0020] The information processing device 260 transmits the transmission data transmitted by the application server 100 to the terminal device 400. For example, the information processing device 260 may be a Push Notification server that transmits the transmission data to the terminal device 400 by Push notification.

[0021] The base station device 300 is a wireless communication device that wirelessly communicates with the terminal device 400. The base station device 300 is a type of communication device. The base station device 300 is also a type of information processing device.

[0022] The terminal device 400 is a wireless communication device that wirelessly communicates with the base station device 300. The terminal device 400 is, for example, a mobile phone, a smart device (smartphone or tablet), a PDA (Personal Digital Assistant), or a personal computer. The terminal device 400 may also be an M2M (Machine to Machine) device or an IoT (Internet of Things) device. The terminal device 400 may also be a head mounted display, VR goggles, or the like.

[0023] The terminal device 400 connects to the core network 200 via the base station device 300 .

[0024] <1.2. Overview of proposed technology> In the communication system 1 shown in Fig. 1, when an application server 100 communicates with a terminal device 400, a communication delay occurs between the application server 100 and the terminal device 400. At this time, if multiple terminal devices 400A and 400B are connected to different core networks 200A and 200B, respectively, as shown in Fig. 1, the amount of communication delay may differ between the terminal devices 400A and 400B.

[0025] For example, if the amount of communication delay is constant between the terminal devices 400A and 400B, the application server 100 can adjust data transmission taking the amount of delay into account, thereby enabling the terminal devices 400A and 400B to deliver data in synchronization.

[0026] However, if the communication delay amount of the terminal devices 400A and 400B fluctuates, it becomes difficult for the application server 100 to adjust data transmission, making it difficult to distribute synchronized data between the terminal devices 400A and 400B.

[0027] Such fluctuations in the amount of communication delay are likely to occur, for example, when the terminal devices 400A and 400B perform discontinuous reception (for example, Connected DRX (Discontinuous Transmission)). If the reception timings of the terminal devices 400A and 400B performing discontinuous reception differ from each other, the terminal devices 400A and 400B may not be able to receive data in synchronization, which may result in fluctuations in the amount of communication delay. Details of such fluctuations in the amount of communication delay will be described later.

[0028] In particular, with the conventional terminal devices 400A and 400B, if the connected core networks 200 are different, it is difficult to synchronize the reception timing of the intermittent reception.

[0029] Therefore, the information processing device 260 according to an embodiment of the present disclosure receives information from the application server 100. Based on the received information, the information processing device 260 notifies the base station device 300 that communicates with the terminal device 400 of setting information related to discontinuous reception of the terminal device 400.

[0030] The information that the information processing device 260 receives from the application server 100 may include, for example, information for identifying the terminal device 400 to be synchronized and information regarding the timing of transmitting data.

[0031] Furthermore, the information processing device 260 may notify the base station device 300 of the configuration information via, for example, an AMF (Access Management Function) node (not shown). Alternatively, the information processing device 260 may have an AMF function and may notify the base station device 300 of the configuration information directly.

[0032] This allows the information processing device 260 to synchronize the timing of the intermittent reception of the terminal device 400, thereby suppressing fluctuations in the amount of communication delay.

[0033] <<2. Example of communication system configuration>> <2.1. Network architecture configuration example> Next, the architecture of a fifth generation mobile communication system (5G) will be described as an example of the core network 200 of the communication system 1 with reference to Fig. 2. Fig. 2 is a diagram showing an example of the 5G architecture. The 5G core network 200 is also called 5GC (5G Core) / NGC (Next Generation Core). Hereinafter, the 5G core network 200 is also referred to as 5GC / NGC 200. The 5GC / NGC 200 connects to a UE (User Equipment) 401 via an (R)AN 301.

[0034] The (R)AN 301 has a function that enables connection to a Radio Access Network (RAN) and connection to an Access Network (AN) other than the RAN. The (R)AN 301 includes a base station device called a gNB or ng-eNB.

[0035] The 5GC / NGC 200 mainly performs connection permission and session management when the UE 401 connects to a network. The 5GC / NGC 200 can be configured to include a user plane function group 220 and a control plane function group 240.

[0036] The user plane function group 220 includes a UPF (User Plane Function) 221 and a DN (Data Network) 222. The UPF 221 has a function for processing the user plane. The UPF 221 includes a function for routing / forwarding data handled in the user plane. The DN 222 has a function for providing a connection to an operator's own services, such as an MNO (Mobile Network Operator), an Internet connection, or a connection to a third-party service. In this way, the user plane function group 220 serves as a gateway that serves as the boundary between the 5GC / NGC 200 and the Internet.

[0037] The control plane function group 240 includes an AMF (Access Management Function) 241, an SMF (Session Management Function) 242, an AUSF (Authentication Server Function) 243, an NSSF (Network Slice Selection Function) 244, an NEF (Network Exposure Function) 245, an NRF (Network Repository Function) 246, a PCF (Policy Control Function) 247, an UDM (Unified Data Management) 248, and an AF (Application Function) 249.

[0038] The AMF 241 has functions such as UE 401 registration processing, connection management, and mobility management. The SMF 242 has functions such as session management and UE 401 IP allocation and management. The AUSF 243 has an authentication function. The NSSF 244 has a function related to network slice selection. The NEF 245 has a function to provide network function capabilities and events to third parties, the AF 249, and edge computing functions.

[0039] The NRF 246 has the function of discovering network functions and maintaining network function profiles. The PCF 247 has the function of policy control. The UDM 248 has the function of generating 3GPP AKA authentication information and processing user IDs. The AF 249 has the function of interacting with the core network to provide services.

[0040] For example, the control plane function group 240 acquires information from the UDM 248 in which subscriber information of the UE 401 is stored, and determines whether or not the UE 401 may connect to the network. For this determination, the control plane function group 240 uses the contract information of the UE 401 and an encryption key contained in the information acquired from the UDM 248. The control plane function group 240 also generates encryption keys and the like.

[0041] That is, the control plane function group 240 determines whether or not the UE 401 can connect to the network depending on whether or not information about the UE 401 linked to a subscriber number called an IMSI (International Mobile Subscriber Identity) is stored in the UDM 248. The IMSI is stored in a SIM (Subscriber Identity Module) card in the UE 401, for example.

[0042] Here, Namf is a service-based interface provided by the AMF 241, and Nsmf is a service-based interface provided by the SMF 242. Furthermore, Nnef is a service-based interface provided by the NEF 245, and Npcf is a service-based interface provided by the PCF 247. Nudm is a service-based interface provided by the UDM 248, and Naf is a service-based interface provided by the AF 249. Nnrf is a service-based interface provided by the NRF 246, and Nnssf is a service-based interface provided by the NSSF 244. Nausf is a service-based interface provided by the AUSF 243. Each of these NFs (Network Functions) exchanges information with other NFs via their respective service-based interfaces.

[0043] Also, N1 shown in Fig. 1 is a reference point between the UE 401 and the AMF 241, and N2 is a reference point between the RAN / AN 301 and the AMF 241. N4 is a reference point between the SMF 242 and the UPF 221, and information is exchanged between these NFs (Network Functions).

[0044] As mentioned above, the 5GC / NGC200 provides an interface for transmitting information and controlling functions via an API (Application Programming Interface) called a service-based interface.

[0045] An API allows you to specify a resource and perform operations such as GET (retrieving the resource), POST (creating a resource or adding data), PUT (creating a resource or updating a resource), and DELETE (deleting a resource) on that resource. Such functions are commonly used in, for example, web-related technical fields.

[0046] For example, the AMF 241, SMF 242, and UDM 248 shown in Figure 2 exchange information with each other using APIs when establishing a communication session. Conventionally, it has not been assumed that an application (e.g., AF 249) would use such an API. However, if the AF 249 uses such an API, it is possible that the AF 249 can use information on the 5G cellular network, thereby further improving the functionality of the application.

[0047] In a public network, it is difficult for the AF289 to use the APIs used by the AMF241, SMF242, and UDM248. However, in a non-public private 5G network, it is possible to configure a system, for example, by modifying the APIs of the 5GC / NGC200, so that the AF289 can use such APIs.

[0048] An example of the API will now be described. API(1) to API(4) described here are described in 3GPP TS23.502.

[0049] [API(1)] API (1) is an API that SMF242 notifies that a pre-registered UE401 has transitioned from a power-off state to a power-on state and attached to a network, and the IP address acquired at that time.

[0050] When the UE 401 with the registered IMSI acquires an IP address using the API (1), the SMF 242 notifies the NF.

[0051] [API(2)] The UE 401 is in idle mode when not communicating, and transitions to connected mode when communicating. API (2) is an API that the AMF 241 notifies whether the UE 401 is in idle mode or connected mode.

[0052] [API(3)] The API (3) is an API for broadcasting a message (paging message) from the base station to instruct the UE 401 to transition from the idle mode to the connected mode.

[0053] [API(4)] API (4) is an API that the AMF 241 provides with location information of the UE 401. The AMF 241 can use API (4) to notify which Tracking Area the UE 401 is in, which Cell it belongs to, and when it enters a specific area.

[0054] 2 is the terminal device 400 of this embodiment. An example of the RAN / AN 301 is the base station device 300 of this embodiment.

[0055] 1 is an example of a device having the functions of, for example, the AF 249 or the AMF 241. The application server 100 is connected to the core network 200 via the Internet, and is not shown in FIG.

[0056] The architecture of a fourth generation mobile communication system (4G) will be described as an example of the core network 200 of the communication system 1 with reference to Fig. 3. Fig. 3 is a diagram showing an example of the architecture of 4G.

[0057] As shown in FIG. 3, the core network 200 includes an eNB 302, a Mobility Management Entity (MME) 252, a Serving Gateway (S-GW) 253, a Packet Data Network Gateway (P-GW) 254, and a Home Subscriber Server (HSS) 255.

[0058] The eNB 302 functions as a 4G base station. The MME 252 is a control node that handles control plane signals and manages the movement state of the UE 401. The UE 401 transmits an Attach request to the MME 252 in order to attach to the cellular system.

[0059] The S-GW 253 is a control node that handles user plane signals and is a gateway device that switches the transfer path of user data. The P-GW 254 is a control node that handles user plane signals and is a gateway device that serves as a connection point between the core network 200 and the Internet. The HSS 255 is a control node that handles subscriber data and performs service control.

[0060] The MME 252 corresponds to the functions of the AMF 241 and the SMF 242 in a 5G network. The HSS 255 corresponds to the functions of the UDM 248.

[0061] As shown in Figure 3, the eNB 302 is connected to the MME 252 via an S1-MME interface and to the S-GW 253 via an S1-U interface. The S-GW 253 is connected to the MME 252 via an S11 interface, and the MME 252 is connected to the HSS 255 via an S6a interface. The P-GW 254 is connected to the S-GW 253 via an S5 / S8 interface.

[0062] <2.2.Private 5G> A part of a communication system 1 according to an embodiment of the present disclosure may employ Private 5G or Private 4G. Currently, wireless LANs conforming to the 802.11 standard are used in LANs (Local Area Networks). Private 5G or Private 4G is a cellular system in which a base station device 300 of a cellular system (for example, RAN / AN 301 in FIG. 2 or eNB 302 in FIG. 3) is installed and operated in the LAN. In 3GPP, Private 5G or Private 4G is referred to as a Non-Public Network. Note that the following description will be given assuming that a part of the communication system 1 employs Private 5G.

[0063] A case where Private 5G is adopted as a cellular system (a system configured with a base station device 300 and a core network 200) in the communication system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 4. Fig. 4 is a diagram for describing a configuration example of Private 5G according to an embodiment of the present disclosure.

[0064] In Private 5G, a base station device 300, a terminal device 400, and information processing devices 260A and 260B having some of the functions of a core network 200 are arranged in a local area network (LAN). Information processing devices 260C to 260F having the remaining functions of the core network 200 are arranged, for example, in a cloud data center connected to the Internet.

[0065] 4, information processing devices 260A and 260B having the functions of UPFs 221A and 221B are arranged in a local area network (LAN). Information processing devices 260C and 260D having the functions of UPFs 221C and 221D are arranged on a cloud over an internet line. Furthermore, an information processing device 260E functioning as the control plane function group 240 is arranged on a cloud over an internet line. Furthermore, an information processing device 260F (e.g., corresponding to the information processing device 260 in FIG. 1) having the function of the AF 249 may be arranged on a cloud separately from the information processing device 260E functioning as the control plane function group 240.

[0066] The UPFs 221A and 221B arranged in the local area network exist in the local area network when the control plane functions group 240 is launched or when the core network 200 starts operating. On the other hand, the UPFs 221C and 221D arranged in the cloud do not exist in the cloud when the control plane functions group 240 is launched or when the core network 200 starts operating. The UPFs 221C and 221D are functions that are launched, for example, after the control plane functions group 240 is launched or when the core network 200 starts operating.

[0067] 4 is installed in, for example, an office, a house, or a private home, and is connected to the Internet via, for example, a network N.

[0068] Private IP addresses are assigned to the base station device 300 and the core network 200. The base station device 300 and the core network 200 communicate with each other using the private IP addresses. For example, by using a technology such as a Virtual Private Network, the base station device 300 and the core network 200 can communicate with each other using the private IP addresses. In other words, the network connecting the base station device 300 and the core network 200 can be considered as a private network (closed network).

[0069] 4, the base station device 300, the terminal device 400, and part of the UPF 221 (UPFs 221A and 221B) are arranged in a local area network. Also, the control plane functions group 240 and part of the UPF 221 (UPFs 221C and 221D) are arranged on the cloud, but this is not limiting. It is sufficient to arrange the base station device 300 and the terminal device 400 on the local area network, and the functions of the UPFs 221A and 221B may be realized on the cloud. Also, at least part of the functions of the control plane functions group 240 may be realized on the local area network.

[0070] As such, the communication system 1 according to the embodiment of the present disclosure is a system in which a network-side application transmits data to a plurality of terminal devices 400, each using a different Private 5G. In the embodiment of the present disclosure, for example, a use case is assumed in which an application server 100 (see FIG. 1) simultaneously distributes control information for controlling a device, video information for a game, and the like to a plurality of terminal devices 400.

[0071] More specifically, the application server 100, which is deployed outside Private 5G, notifies the terminal device 400 of data via the information processing device 260F, which is deployed within Private 5G. Therefore, it can also be said that the information processing device 260F is a Push Notification server deployed in Private 5G. Note that Push Notification is a technology in which a network is the originating point and a message (an example of data) is transmitted to the terminal device 400.

[0072] <2.3. Information processing device> Next, a configuration example of the information processing device 260 according to an embodiment of the present disclosure will be described with reference to Fig. 5. Fig. 5 is a block diagram showing a configuration example of the information processing device 260 according to an embodiment of the present disclosure.

[0073] The information processing device 260 is a device that realizes the functions of an NF or AF of the core network 200. The information processing device 260 is, for example, a server device. The information processing device 260 may be a device collectively called a cloud server or an edge server.

[0074] As shown in Fig. 5, the information processing device 260 includes a communication unit 261, a storage unit 262, and a control unit 263. Note that the configuration shown in Fig. 5 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the information processing device 260 may be distributed and implemented in multiple physically separated configurations. For example, the information processing device 260 may be configured by multiple server devices.

[0075] The communication unit 261 is a communication interface for communicating with other devices. The communication unit 261 may be a network interface or a device connection interface. For example, the communication unit 261 may be a LAN (Local Area Network) interface such as a NIC (Network Interface Card), or a USB (Universal Serial Bus) interface configured by a USB host controller, a USB port, etc. Furthermore, the communication unit 261 may be a wired interface or a wireless interface. The communication unit 261 functions as a communication means of the information processing device 260. The communication unit 261 communicates with the base station device 300, other NF nodes, and AN nodes under the control of the control unit 263.

[0076] The storage unit 262 is a data readable / writable storage device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, a hard disk, etc. The storage unit 262 functions as a storage means of the information processing device 260.

[0077] The control unit 263 is a controller that controls each unit of the information processing device 260. The control unit 263 is realized by a processor such as a CPU (Central Processing Unit), an MPU (Micro Processing Unit), or a GPU (Graphics Processing Unit). For example, the control unit 263 is realized by the processor executing various programs stored in a storage device inside the information processing device 260 using a RAM (Random Access Memory) or the like as a working area. Note that the control unit 263 may also be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The CPU, MPU, GPU, ASIC, and FPGA can all be considered as controllers.

[0078] <2.4.Base station equipment> Next, a configuration example of the base station device 300 according to an embodiment of the present disclosure will be described with reference to Fig. 6. Fig. 6 is a block diagram showing a configuration example of the base station device 300 according to an embodiment of the present disclosure.

[0079] The base station device 300 is a wireless communication device that wirelessly communicates with the terminal device 400. The base station device 300 is a type of communication device. The base station device 300 is also a type of information processing device.

[0080] The base station device 300 may be configured as a collection of multiple physical or logical devices. For example, in an embodiment of the present disclosure, the base station device 300 may be divided into multiple devices, a baseband unit (BBU) and a radio unit (RU), and interpreted as a collection of these multiple devices. Additionally or alternatively, in an embodiment of the present disclosure, the base station device 300 may be either or both of a BBU and a RU. The BBU and the RU may be connected via a predetermined interface (e.g., eCPRI). Additionally or alternatively, the RU may be referred to as a remote radio unit (RRU) or a radio DoT (RD). Additionally or alternatively, the RU may support the gNB-DU (gNB-DU) described below. Additionally or alternatively, the BBU may support the gNB-CU (gNB-CU) described below. Additionally or alternatively, the RU may be a device integrated with an antenna. The antenna of the base station device 300 (e.g., an antenna integrated with the RU) may employ an advanced antenna system and support MIMO (e.g., FD-MIMO) and beamforming. In an Advanced Antenna System, the antenna of base station apparatus 300 (e.g., an antenna integrally formed with an RU) may have, for example, 64 transmitting antenna ports and 64 receiving antenna ports. Furthermore, the antenna mounted on the RU may 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-handed circularly polarized antenna panel and a left-handed circularly polarized antenna panel. Furthermore, the RU may form and control an independent beam for each antenna panel.

[0081] Furthermore, multiple base station devices 300 may be connected to each other. One or more base station devices 300 may be included in a Radio Access Network (RAN). That is, the base station device 300 may simply be referred to as a RAN, a RAN node, an Access Network (AN), or an AN node. The RAN in LTE is called EUTRAN (Enhanced Universal Terrestrial RAN). The RAN in NR is called NGRAN. The RAN in W-CDMA (UMTS) is called UTRAN. The LTE base station device 300 is called eNodeB (Evolved Node B) or eNB. That is, the EUTRAN includes one or more eNodeBs (eNBs). The NR base station device 300 is called gNodeB or gNB. That is, the NGRAN includes one or more gNBs. Furthermore, the EUTRAN may include a gNB (en-gNB) connected to a core network (EPC) in an LTE communication system (EPS). Similarly, the NGRAN may include an ng-eNB connected to a core network 5GC in a 5G communication system (5GS). Additionally or alternatively, if the base station device 300 is an eNB, gNB, or the like, it may be referred to as a 3GPP access. Additionally or alternatively, if the base station device 300 is a wireless access point (Access Point), it may be referred to as a non-3GPP access. Additionally or alternatively, the base station device 300 may be an optical extension device called an RRH (Remote Radio Head). Additionally or alternatively, if the base station device 300 is a gNB, it may be referred to as a combination of the gNB CU (Central Unit) and gNB DU (Distributed Unit) described above, or as either one of them. The gNB CU (Central Unit) hosts multiple upper layers (e.g., RRC, SDAP, PDCP) in the Access Stratum for communication with UEs. On the other hand, the gNB-DU hosts multiple lower layers (e.g., RLC, MAC, PHY) in the Access Stratum.That is, among the messages and information described below, RRC signaling (e.g., MIB, various SIBs including SIB1, RRC Setup message, RRC Reconfiguration message) may be generated by the gNB CU, while DCI and various physical channels (e.g., PDCCH, PBCH) described below may be generated by the gNB-DU. Alternatively, among the RRC signaling, 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 below. A base station device 300 may be configured to be able to communicate with other base station devices 300. For example, when multiple base station devices 300 are eNBs or a combination of an eNB and an en-gNB, the base station devices 300 may be connected to each other via an X2 interface. Additionally or alternatively, when multiple base station devices 300 are gNBs or a combination of a gn-eNB and a gNB, the devices may be connected to each other via an Xn interface. Additionally or alternatively, when the multiple base station devices 300 are a combination of a gNB CU (Central Unit) and a gNB DU (Distributed Unit), the devices may be connected via the F1 interface described above. Message information (information included in RRC signaling or DCI) described below may be communicated between the multiple base station devices 300 (for example, via the X2, Xn, or F1 interface).

[0082] Furthermore, as described above, the base station device 300 may be configured to manage multiple cells. A cell provided by the base station device 300 is called a serving cell. The serving cell includes a PCell (Primary Cell) and an SCell (Secondary Cell). 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., a terminal device 400), a PCell and zero or one or more SCell(s) provided by a Master Node (MN) are called a Master Cell Group. Furthermore, the serving cell may include a PSCell (Primary Secondary Cell or Primary SCG Cell). In other words, when dual connectivity is provided to a UE, a PSCell and zero or one or more SCell(s) provided by a Secondary Node (SN) are called a Secondary Cell Group (SCG). Unless special configuration (for example, PUCCH on SCell) is performed, the Physical Uplink Control Channel (PUCCH) is transmitted on the PCell and PSCell, but not on the SCell. Furthermore, Radio Link Failure is detected on the PCell and PSCell, but not on the SCell (it does not have to be detected). As such, the PCell and PSCell have special roles among the Serving Cell(s), and are therefore also called Special Cells (SpCells). One cell may be associated with one Downlink Component Carrier and one Uplink Component Carrier. Furthermore, the system bandwidth corresponding to one 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 an Active BWP. Also, radio resources (for example, frequency band, numerology (subcarrier spacing), slot format (Slot configuration)) that the terminal device 400 can use may differ for each cell, each component carrier, or each BWP.

[0083] Base station device 300 shown in Fig. 6 includes a communication unit 310, a storage unit 320, a network communication unit 330, and a control unit 340. Note that the configuration shown in Fig. 6 is a functional configuration, and the hardware configuration may be different. Furthermore, the functions of base station device 300 may be distributed and implemented in multiple physically separated components.

[0084] The communication unit 310 is a signal processing unit for wireless communication with other wireless communication devices (e.g., terminal device 400 and other base station devices 300). The communication unit 310 operates under the control of the control unit 340. When the other wireless communication device is a terminal device 400, the communication unit 310 may be a wireless transceiver that supports one or more wireless access methods. For example, the communication unit 310 supports both NR and LTE. The communication unit 310 may also support W-CDMA and cdma2000 in addition to NR and LTE. The communication unit 310 may also support communication using NOMA. When the other wireless communication device is another base station device 300, the communication unit 310 may be an X2 interface, an Xn interface, or an F1 interface.

[0085] The communication unit 310 includes a reception processing unit 311, a transmission processing unit 312, and an antenna 313. The communication unit 310 may include a plurality of reception processing units 311, a plurality of transmission processing units 312, and a plurality of antennas 313. Note that when the communication unit 310 supports a plurality of radio access methods, each unit of the communication unit 310 may be configured separately for each radio access method. For example, the reception processing unit 311 and the transmission processing unit 312 may be configured separately for LTE and NR.

[0086] The reception processing unit 311 processes an uplink signal received via the antenna 313. The reception processing unit 311 operates as a receiving unit that receives a received signal. The reception processing unit 311 includes a radio receiving unit 311a, a demultiplexing unit 311b, a demodulating unit 311c, and a decoding unit 311d.

[0087] The radio receiving unit 311a performs down-conversion, removal of unnecessary frequency components, control of amplification level, orthogonal demodulation, conversion to a digital signal, removal of guard intervals (cyclic prefixes), extraction of frequency domain signals by fast Fourier transform, etc. on the uplink signal. The demultiplexing unit 311b separates uplink channels such as a PUSCH (Physical Uplink Shared Channel) and a PUCCH (Physical Uplink Control Channel) and an uplink reference signal from the signal output from the radio receiving unit 311a.

[0088] The demodulator 311c 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 311c may be 16QAM (Quadrature Amplitude Modulation), 64QAM, or 256QAM. In this case, the signal points on the constellation do not necessarily need to be equidistant. The constellation may be a non-uniform constellation (NUC).

[0089] The decoding unit 311d performs a decoding process on the coded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to the control unit 340.

[0090] The transmission processing unit 312 performs transmission processing of the downlink control information and downlink data. In this way, the transmission processing unit 312 is an acquisition unit that acquires, for example, bit sequences such as the downlink control information and downlink data from the control unit 340. The transmission processing unit 312 includes an encoding unit 312a, a modulation unit 312b, a multiplexing unit 312c, and a radio transmission unit 312d.

[0091] The encoder 312a encodes the downlink control information and downlink data input from the controller 340 using a coding method such as block coding, convolutional coding, or turbo coding. Note that the encoder 312a may also encode using a polar code or a low density parity check code (LDPC code).

[0092] The modulation unit 312b modulates the coded bits output from the coding unit 312a using a predetermined modulation method 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 non-uniform constellation.

[0093] The multiplexing unit 312c multiplexes the modulation symbols of each channel and the downlink reference signal and allocates the multiplexed symbols to predetermined resource elements. The radio transmitting unit 312d performs various signal processing on the signal from the multiplexing unit 312c. For example, the radio transmitting unit 312d performs processing such as conversion from the time domain to the frequency domain using fast Fourier transform, addition of a guard interval (cyclic prefix), generation of a baseband digital signal, conversion to an analog signal, quadrature modulation, up-conversion, removal of unnecessary frequency components, and power amplification. The signal generated by the transmission processing unit 312 is transmitted from the antenna 313.

[0094] The storage unit 320 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 320 functions as a storage means of the base station device 300.

[0095] The network communication unit 330 is a communication interface for communicating with a node located at a higher level on the network (for example, the information processing device 260). For example, the network communication unit 330 may be a LAN interface such as a NIC. Additionally or alternatively, the network communication unit 330 may be an S1 interface or an NG interface for connecting to a core network node. The network communication unit 330 may be a wired interface or a wireless interface. The network communication unit 330 functions as a network communication means of the base station device 300.

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

[0097] <2.5. Terminal Device> Next, a configuration example of the terminal device 400 according to an embodiment of the present disclosure will be described with reference to Fig. 7. Fig. 7 is a block diagram showing a configuration example of the terminal device 400 according to an embodiment of the present disclosure.

[0098] The terminal device 400 is a wireless communication device that wirelessly communicates with the base station device 300. The terminal device 400 is, for example, a mobile phone, a smart device (smartphone or tablet), a PDA (Personal Digital Assistant), or a personal computer. The terminal device 400 may also be a head mounted display or VR goggles that has a function of transmitting and receiving data wirelessly.

[0099] Furthermore, the terminal device 400 may be capable of sidelink communication with other terminal devices 400. When performing sidelink communication, the terminal device 400 may be able to use an automatic retransmission technique such as HARQ (Hybrid Automatic Repeat reQuest). The terminal device 400 may be capable of NOMA (Non Orthogonal Multiple Access) communication with the base station device 300. Note that the terminal device 400 may also be capable of NOMA communication in communication (sidelink) with other terminal devices 400. Furthermore, the terminal device 400 may be capable of LPWA (Low Power Wide Area) communication with other communication devices (for example, the base station device 300 and other terminal devices 400). Alternatively, the wireless communication used by the terminal device 400 may be wireless communication using millimeter waves. Note that the wireless communication (including sidelink communication) used by the terminal device 400 may be wireless communication using radio waves or wireless communication using infrared or visible light (optical wireless).

[0100] The terminal device 400 may simultaneously connect to multiple base station devices or multiple cells to perform communication. For example, if one base station device can provide multiple cells, the terminal device 400 can perform carrier aggregation by using one cell as a pCell and using another cell as an sCell. Furthermore, if multiple base station devices 300 can each provide one or multiple cells, the terminal device 400 can realize DC (Dual Connectivity) by using one or multiple cells managed by one base station device (MN (e.g., MeNB or MgNB)) as a pCell, or a pCell and sCell(s), and using one or multiple 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).

[0101] When a communication area is supported via cells of different base station devices 300 (multiple cells having different cell identifiers or the same cell identifier), the multiple cells can be bundled together using carrier aggregation (CA), dual connectivity (DC), or multi-connectivity (MC) technology to enable communication between the base station device 300 and the terminal device 400. Alternatively, the terminal device 400 can also communicate with the multiple base station devices 300 via the cells of the different base station devices 300 using coordinated multi-point transmission and reception (CoMP) technology.

[0102] The terminal device 400 includes a communication unit 410, a storage unit 420, a network communication unit 430, an input / output unit 4400, and a control unit 450. Note that the configuration shown in Fig. 7 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the terminal device 400 may be distributed and implemented in multiple physically separated configurations.

[0103] The communication unit 410 is a signal processing unit for wireless communication with other wireless communication devices (for example, the base station device 300 and other terminal devices 400). The communication unit 410 operates under the control of the control unit 115. The communication unit 410 may be a wireless transceiver compatible with one or more wireless access methods. For example, the communication unit 410 is compatible with both NR and LTE. The communication unit 410 may be compatible with W-CDMA or cdma2000 in addition to NR and LTE. The communication unit 410 may also be compatible with communication using NOMA.

[0104] The communication unit 410 includes a reception processing unit 411, a transmission processing unit 412, and an antenna 413. The communication unit 410 may include a plurality of reception processing units 411, a plurality of transmission processing units 412, and a plurality of antennas 413. The configurations of the communication unit 410, the reception processing unit 411, the transmission processing unit 412, and the antenna 414 are similar to those of the communication unit 310, the reception processing unit 311, the transmission processing unit 312, and the antenna 314 of the base station device 300.

[0105] The storage unit 420 is a data readable / writable storage device such as a DRAM, an SRAM, a flash memory, a hard disk, etc. The storage unit 420 functions as a storage means of the terminal device 400.

[0106] The network communication unit 430 is a communication interface for communicating with other devices connected via a network. For example, the network communication unit 430 is a LAN interface such as a NIC. The network communication unit 430 may be a wired interface or a wireless interface. The network communication unit 430 functions as a network communication means of the terminal device 400. The network communication unit 430 communicates with other devices under the control of the control unit 450.

[0107] The input / output unit 440 is a user interface for exchanging information with the user. For example, the input / output unit 440 is an operation device such as a keyboard, a mouse, operation keys, or a touch panel that allows the user to perform various operations. Alternatively, the input / output unit 440 is a display device such as a liquid crystal display (LCD) or an organic electroluminescence display (OLED). The input / output unit 440 may be an audio device such as a speaker or a buzzer. Furthermore, the input / output unit 440 may be a lighting device such as an LED (Light Emitting Diode) lamp. The input / output unit 440 functions as input / output means (input means, output means, operation means, or notification means) of the terminal device 400.

[0108] The control unit 450 is a controller that controls each unit of the terminal device 400. The control unit 450 is realized by a processor such as a CPU, an MPU, or a GPU. For example, the control unit 450 is realized by the processor executing various programs stored in a storage device inside the terminal device 400 using RAM or the like as a work area. The control unit 450 may also be realized by an integrated circuit such as an ASIC or an FPGA. The CPU, MPU, GPU, ASIC, and FPGA can all be considered as controllers.

[0109] <<3. First Embodiment>> As described above, when multiple terminal devices 400 belong to different private networks, data transmitted by the application server 100 arrives at each terminal device 400 with a different amount of delay. This point will be described with reference to FIG.

[0110] FIG. 8 is a diagram for explaining delay in the communication system 1 according to the first embodiment of the present disclosure.

[0111] 8 shows a case where an application server 100 installed in Tokyo simultaneously transmits data to a terminal device 400A connected to a private network installed in Hong Kong and a terminal device 400B connected to a private network installed in Osaka. Here, the application server 100 transmits (push) VR game video information as data at predetermined intervals.

[0112] When application server 100 transmits the video information, terminal device 400B first receives the video information (step S11). This is because the distance between Tokyo, where application server 100 is located, and Osaka, where terminal device 400B is located, is shorter than the distance between Tokyo and Hong Kong, where terminal device 400A is located.

[0113] Upon receiving the video information, the terminal device 400B transmits response information corresponding to the video information to the application server 100 (step S12). The response information includes control information such as command operations for a game, for example.

[0114] On the other hand, when the terminal device 400A receives the video information later than the terminal device 400B (step S13), it transmits response information corresponding to the video information to the application server 100 (step S14). In the example of Fig. 8, the response information transmitted by the terminal device 400A arrives at the application server 100 with a delay of D1 from the response information transmitted by the terminal device 400B.

[0115] In this way, the amount of communication delay that exists between the terminal devices 400 that belong to different private networks and the application server 100 differs for each private network.

[0116] 8, it is assumed that the amount of delay between the application server 100 and the terminal device 400A and the amount of delay between the application server 100 and the terminal device 400B are constant. Note that the processing of steps S15 to S18 is the same as the processing of steps S11 to S14, and therefore a description thereof will be omitted.

[0117] In this way, when the amount of delay of the terminal device 400A and the amount of delay of the terminal device 400B are constant, the delay difference D1 between the response information received by the application server 100 is also constant. When the delay difference between the multiple terminal devices 400A is constant, the application server 100 can take the delay difference into consideration to reduce the effect of the delay between the terminal devices 400.

[0118] For example, suppose that the application server 100 determines which of the terminal devices 400A and 400B performed a command operation first. In this case, the application server 100 makes the determination after adding a delay difference D1 to the timing of receiving response information from the terminal device 400B in advance. This allows the application server 100 to correctly determine which of the terminal devices 400A and 400B performed a command operation first, even if the terminal devices 400 have different amounts of delay.

[0119] In this way, when the amount of signal delay between the terminal device 400 and the application server 100 is constant, the effect of the delay can be reduced by the application server 100. This allows the application server 100 to ensure fairness in the services provided to the terminal device 400. For example, even in a game in which the terminal devices 400A and 400B compete to see which one captures the flag first, the terminal devices 400A and 400B connected to different private networks can play the game simultaneously.

[0120] However, if the delay amount of the terminal device 400A and the delay amount of the terminal device 400B fluctuate, it becomes difficult for the application server 100 to correct the delay amount.

[0121] 8, if the amount of delay when the terminal device 400A receives data is greater than steps S13 and S18 (step S22), the timing at which the application server 100 receives a response from the terminal device 400A will be delayed (step S23). As a result, the delay difference between the terminal devices 400A and 400B becomes D2, which is greater than D1.

[0122] Furthermore, if the amount of delay when the terminal device 400A receives data is smaller than that in steps S13 and S18 (step S26), the timing at which the application server 100 receives a response from the terminal device 400A becomes earlier (step S27). As a result, the delay difference between the terminal devices 400A and 400B becomes D3, which is smaller than D1.

[0123] When the delay amount fluctuates in this way, the correction amount (delay difference) is no longer constant, making it difficult for the application server 100 to make corrections. For example, even if the terminal devices 400A and 400B simultaneously perform command operations, the application server 100 may erroneously determine that one of the terminal devices 400A and 400B performed the operation earlier, which may result in failure to ensure fairness in the service.

[0124] Such fluctuations occur due to various factors. One of the factors is, for example, queuing in a switch buffer in the network of the communication system 1, including the private network. A lot of traffic flows through the network, and many packets (data) may be stuck in the switch buffer. Fluctuations in the amount of stuck packets can be one of the factors that cause fluctuations in the amount of delay.

[0125] In this case, for example, by setting priorities for packets using QoS (Quality of Service) control and sending packets with higher priorities to the output of the switch first, packet delays can be reduced and delay fluctuations can be suppressed.

[0126] Another cause of delay fluctuations is DRX (Discontinuous Reception) operation. Here, an overview of DRX will be explained using Fig. 9. Fig. 9 is a diagram for explaining the overview of DRX. DRX is discontinuous reception performed in a RAN (Radio Access Network) to reduce power consumption of a terminal device 400.

[0127] As shown in Fig. 9, a terminal device 400 performing DRX performs a reception operation during a period of on duration, and does not perform a reception operation during other periods. By repeating this in a DRX cycle, the terminal device 400 performs discontinuous reception. The terminal device 400 can reduce power consumption by turning off the power of the receiving unit during periods other than the on duration.

[0128] DRX is disclosed in Rel15 TS36.321 Section 5.7 (LTE) and Rel15 TS38.321 Section 5.7 (NR). DRX operates in the same way in LTE and NR. When DRX is not being performed, the terminal device 400 basically monitors the PDCCH, which is a control signal, in all subframes. When the PDCCH indicates the presence of a PDSCH addressed to the terminal device 400, the terminal device 400 receives the PDSCH indicated in the PDCCH. Receiving the PDCCH when there is no PDSCH addressed to the terminal device 400 increases the power consumption of the terminal device 400. Furthermore, when performing a reception operation, the terminal device 400 periodically reports channel measurement results, etc., via uplink to the base station device 300. Therefore, when a terminal device 400 that does not transmit or receive data performs a reception operation, the processing load and power consumption increase for not only the terminal device 400 but also the base station device 300.

[0129] Therefore, NR and LTE have a mechanism for performing discontinuous reception in an RRC connected state by the terminal device 400. In this discontinuous reception (DRX), a period (on duration) is set in which the terminal device 400 monitors the PDCCH at a fixed period (DRX cycle), and the terminal device 400 does not need to monitor the PDCCH outside of that period.

[0130] This DRX is performed in both RRC Idle and RRC Connected states, but the factor that causes the amount of delay to fluctuate when the terminal device 400 is receiving services from the application server 100 is the DRX (CDRX: Connected DRX) when the terminal device 400 is RRC Connected, as described above.

[0131] CDRX has various parameters, and the terminal device 400 performs various discontinuous receptions according to the combination of parameters. For simplicity of explanation, the terminal device 400 will be described here as performing the most basic discontinuous reception.

[0132] CDRX includes Long DRX and Short DRX. In Long DRX, the terminal device 400 receives the PDCCH for a period of on duration as shown in Fig. 9. In Short DRX, the terminal device 400 receives the PDCCH for a period of Short drx on time (not shown).

[0133] When it is found that there is a PDSCH (user data) addressed to the terminal device 400 from the PDCCH received during the Short drx on duration or Short drx on time, the terminal device 400 receives the PDSCH following the PDCCH.

[0134] The terminal device 400 receives the PDCCH for on duration or short drx on time in a cycle of the DRX cycle or short drx cycle. Therefore, the timing for the terminal device 400 to receive the PDCCH comes in a cycle of the DRX cycle or short drx cycle.

[0135] The decision on whether to use Long DRX or Short DRX, the reception period (on duration or Short drx on time), and the cycle (DRX cycle or short drx cycle) are determined by the base station device 300 and notified to the terminal device 400. This allows the terminal device 400 to perform discontinuous reception for a predetermined period and cycle.

[0136] In the following description, unless otherwise specified, Long DRX will be described, but the same applies to Short DRX.

[0137] Next, delay fluctuations caused by CDRX will be described with reference to Figures 10 and 11. Figures 10 and 11 are diagrams for explaining delay fluctuations caused by CDRX.

[0138] 10(a) shows the transmission timing of data (e.g., AR / VR video) transmitted by the application server 100. Here, it is assumed that the application server 100 transmits data at a cycle of period T1. For example, if the application server 100 updates the game screen 60 frames per second, then T1 = 1 second / 60 = 16.6 ms.

[0139] 10(b) shows the timing of discontinuous reception and the timing of receiving the PDCCH of the terminal device 400. Here, it is assumed that the DRX Cycle of the terminal device 400 is the same as the cycle T1 at which the application server 100 transmits data (DRX Cycle=T1=16.6 ms), for example.

[0140] In this case, the terminal device 400 can receive, during the on duration period, a PDCCH indicating that there is data addressed to the terminal device 400 and a PDSCH including data addressed to the terminal device 400. If the length of the on duration is, for example, 1 ms, the terminal device 400 can enter a mode in which it does not receive data for 15.6 ms.

[0141] On the other hand, a case where the DRX Cycle of the terminal device 400 is different from, for example, the cycle T1 at which the application server 100 transmits data is shown in FIG.

[0142] FIG. 11(a) shows the transmission timing of data (for example, AR / VR video) transmitted by the application server 100, similar to FIG. 10(a).

[0143] FIG. 11(b) shows a case where the DRX Cycle of the terminal device 400 is longer than, for example, the period T1 at which the application server 100 transmits data.

[0144] 11, after the terminal device 400 receives the PDCCH and PDSCH during the first On duration, the application server 100 transmits data until the next On duration. However, the terminal device 400 is not performing a reception operation when transmitting this data. Therefore, during the next On duration, the terminal device 400 receives two PDCCHs and PDSCHs: a PDCCH and PDSCH corresponding to data transmitted in a non-reception mode, and a PDCCH and PDSCH corresponding to data transmitted during the On duration.

[0145] As a result, the reception timing of the PDCCH and PDSCH received by the terminal device 400 is not constant and appears to fluctuate significantly from the perspective of the terminal device 400. As a result, the timing at which the terminal device 400 returns a response to such data via uplink also fluctuates. This causes the amount of delay between the application server 100 and the terminal device 400 to fluctuate rather than be constant.

[0146] In particular, the above-mentioned CDRX is set within one base station device 300. Therefore, conventionally, CDRX provided by multiple base station devices 300 belonging to multiple private networks is set independently for each base station device 300. Furthermore, conventional CDRX setting values are closed within the base station device 300 and are not made public by an API. For example, conventional core network APIs do not include an API for controlling CDRX setting values.

[0147] Therefore, in the communication system 1 according to the first embodiment of the present disclosure, the CDRX cycle is set to match the cycle T1 at which the application server 100 transmits (pushes) data among multiple terminal devices 400 that simultaneously receive services from the application server 100. For example, the CDRX cycle is set to match the cycle at which AR / VR video images of the game are pushed among multiple terminal devices 400 participating in the same game.

[0148] Note that the terminal device 400 may be simultaneously performing multiple communications other than those for the services provided by the application server 100 (hereinafter also simply referred to as provided services, e.g., games). For this reason, the base station device 300 cannot determine the DRX cycle solely to receive data for the provided services. However, it may be possible in implementation for the base station device 300 to set an appropriate DRX cycle according to the timing of data arriving from the application server 100. However, since a certain amount of learning time is required for the base station device 300 to be able to set an appropriate DRX cycle, it may be possible that an appropriate DRX cycle cannot be set in many cases depending on the implementation.

[0149] Therefore, in the first embodiment of the present disclosure, the AF 429 performs a CDRX setting process to notify the base station device 300 of a CDRX setting including an appropriate DRX cycle for providing a service, based on information from the application server 100. This allows the base station device 300 to set an appropriate CDRX for the terminal device 400 that receives the service.

[0150] Furthermore, in the first embodiment of the present disclosure, for example, the AF 249 configures the CDRX using the API of the AMF 241. This allows the CDRX to be configured by the NF or the AF 249 in the private network.

[0151] Such CDRX setting processing will be described with reference to Fig. 12. Fig. 12 is a diagram for explaining an example of CDRX setting processing executed in the communication system 1 according to the first embodiment of the present disclosure.

[0152] 12, the application server 100 requests the AMF 241A via the AF 249A to configure a CDRX using the API of the AMF 241 (step S31). The AMF 241A transmits the received request to the base station device 300A (step S32).

[0153] When the base station device 300A configures the CDRX, the application server 100 transmits and receives data to and from the terminal device 400A via the UPF 221A (step S33).

[0154] Similarly, the application server 100 requests the AMF 241B via the AF 249B to set the CDRX using the API (step S34). The AMF 241B transmits the received request to the base station device 300B (step S35).

[0155] When the base station device 300B configures the CDRX, the application server 100 transmits and receives data synchronized with the terminal device 400A to and from the terminal device 400B via the UPF 221B (step S36).

[0156] In this way, the application server 100 can set CDRX according to the timing of data transmission for the terminal device 400 by notifying the base station device 300 of the CDRX setting via the AF 249 and AMF 241. This allows the application server 100 to transmit data synchronously to the multiple terminal devices 400A and 400B.

[0157] Although the application server 100 requests the setting of the CDRX here, the present invention is not limited to this. The AF 249 may request the setting of the CDRX instead of the application server 100.

[0158] In this case, the AF 249 receives information from the application server 100 and requests CDRX settings based on this information. This information includes, for example, information for identifying the terminal device 400 whose data transmission cycle and CDRX cycle are to be synchronized, information about the data transmission cycle (for example, frame rate), etc. Upon receiving the information, the AF 249 notifies the AMF 241 of the CDRX settings that have been set in advance in accordance with this information using the API of the AMF 241.

[0159] In addition to the CDRX setting, the AF 249 may have a function of pushing data from the application server 100. In other words, the AF 249 may be a Push Notification Server.

[0160] Generally, a Push Notification Server is installed outside the VPN (Virtual Private Network) that constitutes a private network, but when the Push Notification Server configures the CDRX as in this embodiment, it is desirable to place the Push Notification Server inside the VPN. This is because it is desirable for the Push Notification Server to be installed inside the VPN in order to configure the CDRX using the AMF241 API.

[0161] In this way, when the AF 249 performs the CDRX setting, the application server 100 may be located inside or outside the VPN. By the AF 249 performing the CDRX setting, the application server 100 can provide a service to the terminal device 400 without being aware of the CDRX.

[0162] 12 shows a case where the terminal devices 400A and 400B are connected to different private networks, but this is not limiting. The terminal devices 400A and 400B may be connected to the same private network. In this case, the terminal devices 400A and 400B may belong to the same base station device 300, or may belong to different base station devices 300.

[0163] 12 illustrates a case where an API that receives a CDRX setting request is newly provided in the AMF 241, but the present invention is not limited to this. For example, this API may be provided in the base station device 300. In this case, the AF 249 transmits a CDRX setting request to the base station device 300 using the API without going through the AMF 241.

[0164] Here, the CDRX setting process will be described in detail with reference to Fig. 13. Fig. 13 is a sequence diagram for explaining the flow of the CDRX setting process according to the first embodiment of the present disclosure. Fig. 13 illustrates a case where a CDRX setting is configured for one of a plurality of terminal devices 400.

[0165] 13, first, the terminal device 400 is connected to the wireless network and the core network 200 (step S101). At this time, an IP address is assigned by the SMF 242 (see FIG. 2).

[0166] Next, the terminal device 400 registers its own ID in the AF 249 (step S102). At this time, the IMSI of the terminal device 400 is also registered in the AF 249. Next, the AF 249 transmits a token to the terminal device 400 as a response to the ID registration (step S103).

[0167] Next, the terminal device 400 transmits the token and its own ID to the application server 110 (step S104). The application server 110 registers the token and ID of the terminal device 400.

[0168] The AF 249 establishes a TCP connection with the application server 110 (step S105).

[0169] When the TCP connection is established, the application server 100 transmits a CDRX setting request to the AF 249 (step S106). As described above, the AF 249 may notify the AMF 241 of the CDRX setting request instead of the application server 100. In this case, the application server 100 requests the AF 249 to transmit the CDRX setting request by notifying the AF 249 of information required for the CDRX setting request instead of the CDRX setting request.

[0170] The AF 249 notifies the AMF 241 of a CDRX setting request by using the API of the AMF 241 (step S107). Upon receiving the request, the AMF 241 notifies the base station apparatus 300 of the CDRX setting request (step S108).

[0171] Upon receiving the request, the base station device 300 configures CDRX in accordance with the CDRX configuration request and causes the terminal device 400 to start CDRX (step S109).

[0172] The application server 100 transmits transmission data, for example, AR / VR video, to the AF 249 (step S110). The AF 249 pushes the received transmission data (AR / VR content) to the UPF 221 (step S111). The UPF 221 pushes the transmission data (AR / VR content) to the terminal device 400 (step S112).

[0173] Thereafter, the application server 100 similarly pushes transmission data to the terminal device 400 at a predetermined cycle (for example, frame rate).

[0174] Next, an example of a CDRX setting request process by the AF 249 will be described with reference to Fig. 14. Fig. 14 is a sequence diagram showing an example of the flow of a CDRX setting request process according to an embodiment of the present disclosure.

[0175] The AF 249 notifies the AMF 241 of a CDRX setting request including the ID of the terminal device 400 (step S201). The ID of the terminal device 400 may be, for example, the IMSI() or SUPI.

[0176] Upon receiving the CDRX setting request, the AMF 241 responds with an acknowledgement to the AF 249 (step S202).

[0177] In this way, the AF 249 sets the CDRX in response to a request from the application server 100, thereby making it possible to reduce fluctuations in delay of data (packets) transmitted from the application server 100 to the terminal device 400.

[0178] <<4. Second Embodiment>> In the CDRX setting process of the first embodiment described above, even if the period T1 of data transmitted by the application server 100 and the CDRX period set by the base station device 300 are matched, delay fluctuations may occur. A method for suppressing the fluctuations that occur in this case will be described as a second embodiment. First, the delay fluctuations that occur in this case will be described with reference to Fig. 15. Fig. 15 is a diagram for explaining delay fluctuations according to the second embodiment of the present disclosure.

[0179] FIG. 15(a) shows the timing at which the video data transmitted by the application server 100 arrives at the base station device 300.

[0180] The application server 100 transmits, for example, video data in a predetermined cycle T1, but due to the influence of the switch buffer and the like described above, slight delay fluctuations may occur in the video data that arrives at the base station device 300. For example, as shown in Fig. 15(a), it may take a period T2, which is longer than the cycle T1, from when one video data arrives at the base station device 300 until the next video data arrives.

[0181] Although the fluctuation in delay due to the switch buffer etc. is slight, depending on the timing of data reception by the terminal device 400, the fluctuation in delay may become large.

[0182] For example, as shown in Fig. 15(b), there is a case where the video data transmitted by the base station device 300 is received near the end of the On duration period. In this case, due to fluctuations in the arrival timing of the video data, the timing at which the terminal device 400 receives the video data may be shifted to the next On duration period. Note that Fig. 15(b) shows the CDRX timing and the reception timing of the PDCCH and PDSCH by the terminal device 400.

[0183] In this way, the fluctuation in delay may become large depending on the timing when the terminal device 400 performs discontinuous reception and the timing when the base station device 300 transmits video data to the terminal device 400 (in other words, the timing when the video data arrives at the base station device 300). More specifically, when the terminal device 400 receives video data at the end of the reception period (On duration), the fluctuation in arrival timing may cause the fluctuation in delay to become large.

[0184] 16, in the communication system 1 according to the second embodiment of the present disclosure, the terminal device 400 is configured to receive video data during a period excluding the end of the On duration, in other words, before a predetermined period. For example, if the terminal device 400 receives video data around the middle of the On duration, the terminal device 400 can receive the video data during the On duration even if the arrival timing fluctuates.

[0185] 16 is a diagram for explaining the reception timing of video data by the terminal device 400 according to the second embodiment of the present disclosure. Fig. 16(a) shows the timing at which the video data transmitted by the application server 100 arrives at the base station device 300, and Fig. 16(b) shows the CDRX timing and the reception timing of the PDCCH and PDSCH by the terminal device 400.

[0186] In this way, one possible method for the terminal device 400 to receive video data before a predetermined period of the On duration is for the base station device 300 to adjust the CDRX settings in implementation according to the arriving video data.

[0187] However, not only video data but also other traffic data arrive at the base station device 300. In the method of adjusting the CDRX setting in implementation as described above, the base station device 300 needs to determine whether the arriving data is video data from the application server 100, which is considered difficult to implement.

[0188] Therefore, in the communication system 1 according to the second embodiment of the present disclosure, the base station device 300 notifies the AF 249 of the relationship between the reception period (On duration) in CDRX and the arrival timing of data, for example, in response to a request from the AF 249.

[0189] FIG. 17 is a diagram illustrating the arrival timing of data notified by the base station device 300 according to the second embodiment of the present disclosure.

[0190] Figure 17(a) shows the timing at which data transmitted by the base station device 300 arrives at the terminal device 400. Figure 17(b) shows CDRX of the terminal device 400. Note that Figure 17(b) shows the case where the DRX Cycle of the terminal device 400 is three times the On duration.

[0191] As shown in Fig. 17, the base station device 300 designates the beginning of a DRX cycle as 0% and the beginning of the next DRX cycle as 300%, and notifies the AMF 241 of the arrival timing, i.e., the position at which data will arrive between 0% and 299% at the end of the DRX cycle. In the case of Fig. 17, 0% to 100% indicates that data has arrived within the On duration. Also, 101% to 299% indicates that data has arrived outside the On duration, in other words, does not arrive within the On duration.

[0192] The base station device 300 calculates the percentage of the position at which the data will arrive at the terminal device 400 based on the data arrival timing and the CDRX setting of the terminal device 400, and notifies the AMF 241 of the calculation result.

[0193] In order for the base station device 300 to transmit this notification to the AMF 241, the base station device 300 needs to identify data for determining the arrival timing. The base station device 300 cannot identify data by an IP address or the like, but can identify data by the GTP-tunnel ID.

[0194] Therefore, the AMF 241 requests the base station device 300 to notify the data arrival timing by specifying the ID of the GTP tunnel. More specifically, the AF 249 requests the AMF 241 to notify the data arrival timing by specifying the destination IP address of the data and the source IP address of the data. The destination IP address is, for example, the IP address of the terminal device 400. The source IP address is, for example, the IP address of the AF 249. The AMF 241 identifies the ID of the GTP tunnel corresponding to these IP addresses, and requests the base station device 300 to notify the data arrival timing including the ID of the GTP tunnel.

[0195] The base station device 300 reports to the AMF 241 the arrival timing of the data that has arrived with the ID of the specified GTP tunnel.

[0196] 18 is a sequence diagram for explaining an example of the flow of the arrival timing notification process according to the second embodiment of the present disclosure. Note that the same processes as those in the sequence diagram of FIG. 13 are assigned the same reference numerals, and the description thereof will be omitted.

[0197] In step S105, the AF 249, which has established a TCP connection with the application server 100, transmits test data for measuring the arrival timing of data to the base station device 300 via the UPF 221 (step S301).

[0198] Furthermore, the base station device 300 instructs the terminal device 400 to start CDRX (step S302).

[0199] The AF 249 that has transmitted the test data transmits a data arrival timing request including the IP address of the terminal device 400 as the destination and the IP address of its own device as the sender to the AMF 241 (step S303).

[0200] Upon receiving the data arrival timing request, AMF 241 identifies the GTP tunnel ID from the IP address included in the request, and transmits a data arrival timing request including the identified GTP tunnel ID to base station device 300 (step S304).

[0201] Based on the CDRX configuration and the arrival timing of the test data, the base station device 300 transmits a data arrival timing report including the position (percentage) in the DRX cycle at which the test data arrives to the AMF 241 (step S305). Based on the data arrival timing report, the AMF 241 notifies the AF 249 of the measurement result of the data arrival timing (step S306).

[0202] Based on the measurement result, the AF 249 adjusts the arrival timing of user data (for example, AR / VR video data) received from the application server 100 so that the data arrives at the terminal device 400 at a desired position of the On duration (for example, a section before a predetermined period). The AF 249 transmits the user data to the terminal device 400 via the UPF 221 and the base station device 300 at the adjusted timing (step S307).

[0203] It is desirable that the AF 249 adjusts the transmission timing so that the user data arrives between 10% and 50% of the DRX Cycle, for example (see FIG. 17). By adjusting the transmission timing in this way, the AF 249 can receive the user data in the desired On duration even if fluctuations occur in the arrival timing of the user data, and delay fluctuations can be further suppressed.

[0204] The transmission timing is adjusted once for each packet group (user data) that is periodically transmitted. In other words, the notification process illustrated in Fig. 18 is executed before the application server 100 transmits the user data.

[0205] Therefore, in Fig. 18, the CDRX setting is not changed when transmitting test data and user data, and the same setting is maintained. Alternatively, the transmission timing shown in Fig. 18 is adjusted every time the CDRX setting is changed.

[0206] Although the AF 249 adjusts the transmission timing of user data here, the present invention is not limited to this. The base station apparatus 300 may adjust the CDRX setting so that the user data arrives at the terminal apparatus 400 at a desired timing.

[0207] 19 is a sequence diagram for explaining another example of the flow of the arrival timing notification process according to the second embodiment of the present disclosure. Note that the same processes as those in the sequence diagram of FIG. 18 are assigned the same reference numerals, and their explanations will be omitted.

[0208] In step S304, the base station apparatus 300 receives the data arrival timing request and adjusts the CDRX setting according to the timing at which the test data arrives (step S401).

[0209] When the adjustment is completed, the base station device 300 notifies the AMF 241 of an ACK indicating that the adjustment is completed (step S402). Upon receiving the ACK, the AMF 241 notifies the AF 249 of an ACK indicating that the CDRX setting adjustment is completed (step S403).

[0210] Thereafter, the AF 249 transmits the user data (for example, AR / VR video data) received from the application server 100 to the terminal device 400 via the UPF 221 and the base station device 300 (step S404).

[0211] In this way, the base station apparatus 300 can further suppress delay fluctuations by adjusting the CDRX setting.

[0212] It is assumed that the CDRX setting is adjusted once for a group of packets (user data) that are periodically transmitted. In other words, the notification process illustrated in Fig. 19 is executed before the application server 100 transmits user data.

[0213] 19, the test data and user data are transmitted at the same interval. Alternatively, the CDRX setting is adjusted every time the data transmission interval is changed. Also, the test data is transmitted periodically multiple times.

[0214] Conventionally, the means for the AF 249 to acquire information about the CDRX setting of the base station device 300 has not been clearly defined, and it has been difficult for the AF 249 to know at what timing of the CDRX the data will arrive.

[0215] Therefore, in the second embodiment of the present disclosure, the AF 249 can request the base station device 300 to report the relationship between the CDRX setting and the data arrival timing via the API of the core network 200. This allows the application side to more accurately adjust the delay between multiple terminal devices 400.

[0216] Furthermore, conventionally, it has been difficult for the base station device 300 to determine the timing at which data arrived from the AF 249, since it has been difficult for the base station device 300 to identify the data transmitted from the AF 249 using the IP address.

[0217] Therefore, in the second embodiment of the present disclosure, the AMF 241 is configured to enable the base station device 300 to identify data transmitted by the AF 249 using the ID of the GTP tunnel. This allows the base station device 300 to know the arrival timing of data transmitted from the AF 249 and adjust the CDRX setting according to the arrival timing. Therefore, it is possible to further suppress the fluctuation in delay of the terminal device 400.

[0218] <<5. Third Embodiment>> In the CDRX setting process of the first embodiment, it is possible to align the CDRX settings (period) among multiple terminal devices 400, but no consideration is given to the timing at which the multiple terminal devices 400 start CDRX. As a result, there is a risk that the timing at which the CDRX starts may differ among the multiple terminal devices 400.

[0219] Here, the timing to start CDRX will be described with reference to Fig. 20. Fig. 20 is a diagram for explaining the timing to start CDRX.

[0220] In period T11 shown in Fig. 20, the terminal device 400 monitors the PDCCH in units of subframes. If there is no transmission / reception data addressed to the terminal device 400 for a certain period (a certain number of subframes), the terminal device 400 starts CDRX.

[0221] More specifically, the terminal device 400 monitors the PDCCH of a subframe, starts the drx-InactivityTimer from the timing when the PDSCH addressed to the terminal device no longer exists, and measures the period (number of subframes) during which the PDSCH addressed to the terminal device no longer exists. Alternatively, the terminal device 400 may monitor the PDCCH of a subframe and start measurement after the PDSCH is no longer scheduled. When the measurement period exceeds a predetermined period, the terminal device 400 transitions to discontinuous reception mode and starts CDRX.

[0222] In the example of Fig. 20, if there is no PDSCH addressed to the terminal device 400 in the three subframes monitored in period T11, the terminal device 400 performs CDRX in the next period T12. In Fig. 20, the terminal device 400 alternately repeats reception and stopping of PDCCH every two subframes, receives PDCCH in the On duration section, and checks whether there is a PDSCH addressed to the terminal device 400.

[0223] Here, the terminal device 400 is running multiple applications, and therefore multiple sessions are established between the terminal device 400 and the core network 200, and traffic may occur between the terminal device 400 and devices other than the application server 100.

[0224] Therefore, multiple terminal devices 400 receiving the same service from the same application server 100 do not necessarily start CDRX at the same timing. For example, a terminal device 400 that receives data from a device other than the application server 100 during period T11 in Fig. 20 does not start CDRX from period T12. As such, in conventional communication systems, it has been difficult to align the start timing of CDRX across multiple terminal devices 400.

[0225] If the CDRX start timing differs, for example, one terminal device 400 may be performing CDRX while the other terminal device 400 is not performing CDRX. In this case, the degree of variation in packet reception timing may differ between the terminal device 400 performing CDRX and the terminal device 400 not performing CDRX.

[0226] For example, in a terminal device 400 that continuously receives PDCCH and PDSCH without performing CDRX, there is little variation in packet reception timing, whereas in a terminal device 400 that performs CDRX and discontinuous reception, there is large variation in packet reception timing.

[0227] As described above, by setting the CDRX period, it is possible to align the CDRX periods of multiple terminal devices 400. However, if the timing at which CDRX starts differs among the multiple terminal devices 400, there may be a large difference in the degree of delay fluctuation between the terminal device 400 that starts CDRX first and the terminal device 400 that starts CDRX later.

[0228] 20, a terminal device 400 that starts CDRX at time T10 cannot receive a packet addressed to itself at time T10 until the next on duration. On the other hand, a terminal device 400 that does not start CDRX at time T10 can receive a packet addressed to itself in the subframe following time T10.

[0229] In this way, if the timing at which CDRX starts differs, even if the CDRX cycle is the same, there is a risk that the timing at which multiple terminal devices 400 receive packets will differ, which may increase the impact of delay fluctuations.

[0230] In this way, when the terminal device 400 is running multiple applications, the applications that are affected by delay fluctuations (applications provided by the application server 100) are separated from the other applications. By separating the applications, the CDRX start timings of multiple terminal devices 400 that receive data from a specific application are aligned.

[0231] For example, in 4G and 5G LTE, one terminal device 400 can use multiple Component Carriers (CCs). Also, in 5G, one Component Carrier can use multiple BWPs (Bandwidth Parts). Therefore, the terminal device 400 uses different CCs or BWPs for each application.

[0232] As a result, CDRX of a specific CC or BWP can be started based on an instruction from the base station device 300, rather than being started according to the actual traffic generation timing. That is, the base station device 300 determines the CC or BPW to be used for communication with the application server 100, and performs CDRX configuration, including the CDRX start or end timing, in that CC or BPW. Note that CDRX configuration is performed based on an instruction from, for example, the application server 100 or the AF 249. The application server 100 or the AF 249 uses the API to instruct the base station device 300 via the AMF 241.

[0233] For example, when starting to provide a service, the AF 249 or the application server 100 requests the base station device 300 to start CDRX so that CDRX is started at the same timing for multiple terminal devices 400 that are simultaneously receiving the service. This request is made to each of the multiple core networks 200 to which the multiple terminal devices 400 are connected.

[0234] More specifically, a new API is provided in the AMF 241 of the core network 200, and the AF 249 uses this API to request the start of CDRX.

[0235] It is assumed here that the multiple core networks 200 to which the multiple terminal devices 400 are connected are frame synchronized with each other. That is, frame synchronization is not only achieved between the multiple base station devices 300 belonging to the same private network, but also between the base station devices 300 belonging to different private networks.

[0236] Cellular networks are typically made up of 10 ms frames, each of which is assigned a number called a System Frame Number. The maximum System Frame Number is 1024, and the frame following a frame with a System Frame Number of 1 is assigned a System Frame Number of 1.

[0237] When frame synchronization is established, multiple base station devices 300 communicate using frames assigned the same System Frame Number at the same timing. Therefore, if frame synchronization is established between multiple base stations, the AF 249 can specify the subframe from which CDRX should be started, thereby enabling the multiple base station devices 300 to configure CDRX so that CDRX starts at the same timing.

[0238] Generally, frame synchronization is not achieved between base station devices 300 that belong to different private networks. However, by using existing technology, frame synchronization can be achieved between base station devices 300 that belong to different private networks in terms of implementation.

[0239] An example of a process in which the AF 249 instructs the start timing of CDRX (hereinafter also referred to as CDRX synchronization process) will be described with reference to Figures 21 and 22. Figures 21 and 22 are diagrams for explaining an example of the flow of the CDRX synchronization process according to the third embodiment of the present disclosure.

[0240] 21, upon receiving notification of the start of service provision (for example, a game) from the application server 100, the AF 249A requests the AMF 241A to start CDRX using an API (step S41). Furthermore, the AMF 241A calculates the CDRX start timing in a predetermined procedure from the game start timing notified by the application server 100, for example, and requests the start of CDRX. The AF 249A may notify the AMF 241A of the CDRX start request in accordance with the CDRX start timing, or may notify the CDRX start request including the CDRX start timing.

[0241] The AMF 241A that has received the CDRX start request notifies the base station device 300A to start CDRX at the CDRX start timing (step S42). In response to this, the base station device 300A configures the terminal device 400A to start CDRX from the CDRX start timing.

[0242] Thereafter, communication is performed between the application server 100 and the terminal device 400A via the AF 249A, the UPF 221A, and the base station device 300A using CDRX (step S43).

[0243] Similarly, upon receiving notification of the start of service provision (for example, a game) from the application server 100, the AF249B requests the AMF241B to start CDRX using an API (step S44). The AMF241B also calculates the CDRX start timing in a predetermined procedure from the game start timing notified by the application server 100, and requests the start of CDRX. The AF249B may notify the AMF241B of the CDRX start request in accordance with the CDRX start timing, or may notify the CDRX start request including the CDRX start timing.

[0244] The AMF 241B that has received the CDRX start request notifies the base station device 300B to start CDRX at the CDRX start timing (step S45). In response to this, the base station device 300B configures the terminal device 400B to start CDRX from the CDRX start timing.

[0245] Thereafter, communication is performed between the application server 100 and the terminal device 400B via the AF 249B, the UPF 221B, and the base station device 300B using CDRX (step S46).

[0246] Frame synchronization is established between the private network to which the base station device 300A belongs and the private network to which the base station device 300B belongs. Therefore, the AFs 249A and 249B can instruct the base station device 300 via the AMF 241 to start CDRX at the same CDRX start timing.

[0247] The AF 249 may include the above-described setting related to the CDRX cycle in the CDRX start request. That is, the AF 249 may request the base station apparatus 300 via the AMF 241 to set both the CDRX start timing and the CDRX cycle.

[0248] Next, a case where the AF 249 sets the timing to end CDRX will be described with reference to FIG.

[0249] As shown in FIG. 22, the AF 249A, which has received a notification from the application server 100 that the provision of a service (for example, a game) has ended, requests the AMF 241A to end the CDRX using the API (step S47).

[0250] The AMF 241B that has received the CDRX termination request notifies the base station device 300B to terminate CDRX at the CDRX termination timing (step S48). In response to this, the base station device 300A sets the terminal device 400B to terminate CDRX at the CDRX termination timing.

[0251] Similarly, upon receiving a notification from the application server 100 that the service provision (for example, a game) has ended, the AF 249B requests the AMF 241B to end the CDRX using the API (step S49).

[0252] The AMF 241B that has received the CDRX termination request notifies the base station device 300B to terminate CDRX at the CDRX termination timing (step S45). In response to this, the base station device 300B sets the terminal device 400B to terminate CDRX at the CDRX termination timing.

[0253] This allows the terminal devices 400A and 400B to end CDRX at the same CDRX end timing.

[0254] In this way, when the AF 249 determines the timing to start CDRX, the AF 249 also indicates the timing to end CDRX, which allows the base station device 300 to return to normal communication when the service provided by the application server 100 is finished.

[0255] As described above, the AF 249 can control the start and end timings of CDRX using the API, which allows the application server 100 to deliver data (e.g., AR / VR video data) to multiple terminal devices 400 belonging to different private networks with reduced delay fluctuations.

[0256] Also, in the uplink, it is possible to further reduce fluctuations in delay of data arriving at the application server 100 from a plurality of terminal devices 400 belonging to different private networks.

[0257] This allows a plurality of terminal devices 400 belonging to different private networks to operate in cooperation with each other.

[0258] <<6. Fourth Embodiment>> In the above first to third embodiments, the method in which the AF 249 sets CDRX has been described mainly using the case of Long DRX as an example, but CDRX includes two types: Long DRX and Short DRX. Compared to Long DRX, Short DRX has a shorter cycle (CDRX cycle) for intermittently monitoring the PDCCH. When starting CDRX, the terminal device 400 first performs Short DRX, and transitions from Short DRX to Long DRX if there are no transmitted or received packets addressed to the terminal device 400 for a predetermined period.

[0259] As described above, to align CDRX among multiple terminal devices 400, it is necessary to align not only the CDRX start timing but also the timing of Short DRX and Long DRX, in other words, the timing of switching from Short DRX to Long DRX.

[0260] Therefore, in the fourth embodiment of the present disclosure, after CDRX is started at the CDRX start timing instructed by the AF 249, the AF 249 switches between Short DRX and Long DRX using an API.

[0261] An example of processing in which the AF 249 instructs switching of the CDRX (hereinafter also referred to as switching processing) will be described with reference to Fig. 23. Fig. 23 is a diagram for describing an example of the flow of switching processing according to the fourth embodiment of the present disclosure.

[0262] 23, based on a notification from the application server 100, the AF 249A requests the AMF 241A to switch from Short DRX to Long DRX at the switching timing using an API (step S51). The notification from the application server 100 includes, for example, a notification to suspend data transmission for a certain period of time or a notification to lower the frame rate.

[0263] The AMF 241A that has received the switching request notifies the base station device 300A to switch CDRX from Short DRX to Long DRX at the switching timing (step S52). In response to this, the base station device 300A configures the terminal device 400A to switch from Short DRX to Long DRX at the switching timing.

[0264] Similarly, based on an instruction from the application server 100, the AF 249B requests the AMF 241B to switch from Short DRX to Long DRX at the switching timing using an API (step S53). The notification from the application server 100 includes, for example, a notification to suspend data transmission for a certain period of time or a notification to lower the frame rate.

[0265] The AMF 241B that has received the switching request notifies the base station device 300B to switch CDRX from Short DRX to Long DRX at the switching timing (step S53). In response to this, the base station device 300B configures the terminal device 400B to switch from Short DRX to Long DRX at the switching timing.

[0266] As described above, the AF 249 can control the timing of switching between Short DRX and Long DRX using the API, which allows the application server 100 to deliver data (e.g., AR / VR video data) to multiple terminal devices 400 belonging to different private networks with reduced delay fluctuations.

[0267] Also, in the uplink, it is possible to further reduce fluctuations in delay of data arriving at the application server 100 from a plurality of terminal devices 400 belonging to different private networks.

[0268] This allows a plurality of terminal devices 400 belonging to different private networks to operate in cooperation with each other.

[0269] Note that, although the AF 249 controls switching between Short DRX and Long DRX in accordance with a notification from the application server 100, the present invention is not limited to this. For example, the AF 249 may monitor data addressed to the terminal device 400, and perform switching control if there is no data addressed to the terminal device 400 for a certain period of time.

[0270] <<7. Modifications>> The processing according to each of the above-described embodiments may be implemented in various different forms (modifications) of each of the above-described embodiments.

[0271] In the above embodiment, the AF 249 controls CDRX (for example, setting the CDRX cycle, etc.), but this is not limiting. For example, an entity located outside the private network may control CDRX. This entity may be the application server 100, or may be an entity different from the application server 100.

[0272] Because the AF 249 is located inside the private network, it can directly access the API of the AMF 241 that belongs to the same private network. However, when an entity located outside the private network issues an instruction related to CDRX to the AMF 241, it cannot directly connect to the API of the AMF 241. Therefore, in this case, the entity located outside the private network may connect to the API of the AMF 241 via, for example, a gateway of the API of the NEF 245.

[0273] Furthermore, the terminal device 400, the base station device 300, or the control device that controls the information processing device 260 of this embodiment may be realized by a dedicated computer system or a general-purpose computer system.

[0274] For example, a program for executing the above-described operations is stored in a computer-readable recording medium such as an optical disk, a semiconductor memory, a magnetic tape, or a flexible disk and distributed. Then, for example, the program is installed in a computer and the above-described processing is executed to configure a control device. In this case, the control device may be a device (for example, a personal computer) external to the terminal device 400, the base station device 300, or the information processing device 260. Furthermore, the control device may be a device (for example, the control unit 450, the control unit 340, or the control unit 263) internal to the terminal device 400, the base station device 300, or the information processing device 260.

[0275] The communication program may also be stored in a disk device provided in a server device on a network such as the Internet, and may be downloaded to a computer. The above-mentioned functions may also be realized by cooperation between an OS (Operating System) and application software. In this case, the parts other than the OS may be stored on a medium and distributed, or may be stored in a server device and downloaded to a computer.

[0276] Furthermore, among 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 using a known method. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0277] Furthermore, the components of each device shown in the figure are conceptual functional components and do not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads, usage conditions, etc.

[0278] The above-described embodiments can be combined as appropriate within the scope of the processing content without causing inconsistency. The order of the steps shown in the sequence diagrams or flowcharts of the present embodiment can be changed as appropriate.

[0279] Furthermore, for example, this embodiment can also be implemented as any configuration that constitutes an apparatus or system, such as a processor as a system LSI (Large Scale Integration), a module using multiple processors, a unit using multiple modules, a set in which other functions are added to a unit, etc. (i.e., a configuration of a part of an apparatus).

[0280] In this embodiment, a system refers to a collection of multiple components (devices, modules (components), etc.), regardless of whether all the components are in the same housing. For example, multiple devices housed in separate housings and connected via a network, etc., and a single device in which multiple modules are housed in a single housing are both systems.

[0281] Furthermore, for example, this embodiment can be configured as a cloud computing system in which one function is shared and processed jointly by a plurality of devices via a network.

[0282] (effect) The information processing device 260 (AF 249, AMF 241) of the present disclosure includes a control unit 263. The control unit 263 acquires information from an apparatus (application server 100) that provides application functions to the terminal device 400. Based on the acquired information, the control unit 263 notifies the base station device 300, which communicates with the terminal device 400, of setting information related to discontinuous reception of the terminal device 400, using an API.

[0283] This makes it possible to further suppress fluctuations in delay.

[0284] Furthermore, the control unit 263 may notify the base station device 300 of the setting information via a device (AMF 241) that belongs to the core network 200 to which the base station device 300 is connected and has the functionality of an NF.

[0285] This allows AF249 to suppress delay fluctuations.

[0286] The information processing device 260 may also have a function related to access control.

[0287] This allows the AMF 241 to suppress delay fluctuations.

[0288] The setting information may also include cycle information regarding the reception cycle of the intermittent reception.

[0289] This allows the information processing device 260 to set the reception cycle for intermittent reception.

[0290] The setting information may also include start timing information regarding the timing to start intermittent reception.

[0291] This allows the information processing device 260 to set the start timing of intermittent reception.

[0292] The setting information may also include end timing information regarding the timing to end the intermittent reception.

[0293] This allows the information processing device 260 to set the end timing of the intermittent reception.

[0294] The setting information may also include switching timing related to the timing for switching the reception cycle (Short DRX / Long DRX) of the discontinuous reception.

[0295] This allows the information processing device 260 to set the timing for switching the reception cycle of the intermittent reception.

[0296] Furthermore, the control unit 263 may receive, from the base station device 300, reception timing information regarding the reception timing at which the terminal device 400 receives data transmitted by an apparatus (application server 100) during the reception period of discontinuous reception.

[0297] This allows the data transmission timing to be adjusted so that the terminal device 400 receives the data at a desired reception timing.

[0298] Furthermore, the control unit 263 may transmit test data to the base station device 300 for measuring the reception timing.

[0299] This allows the reception timing to be measured based on the test data.

[0300] Furthermore, the control unit 263 may adjust the transmission timing based on the reception timing information so that the terminal device 400 receives the data before a predetermined period in the reception period, and then transmit the data.

[0301] This allows the terminal device 400 to receive data at a desired timing.

[0302] In addition, the control unit 263 may request the base station device 300 to adjust the reception period so that the reception timing at the terminal device 400 of data transmitted by the device (application server 100) is earlier than a predetermined period in the reception period of intermittent reception, and may transmit test data for adjusting the reception period.

[0303] This allows the base station device 300 to adjust the reception period of discontinuous reception using the test data.

[0304] In addition, the information acquired from the device (application server 100) may include information regarding multiple terminal devices 400 that are each connected to different core networks, and the control unit 263 may notify the base station device 300 that communicates with the terminal device 400 of the multiple terminal devices 400 that is connected to the core network 200 to which the device itself belongs of the configuration information of the terminal device 400.

[0305] This allows a plurality of terminal devices 400 belonging to different core networks 200 to operate in cooperation with each other.

[0306] The information processing device (application server 100) of the present disclosure also includes a control unit. The control unit notifies the entities (AF 249, AMF 241) belonging to the core network 200 to which the terminal device 400 is connected of information related to the terminal device 400 that provides the application function. The information is used by the entities (AF 249, AMF 241) to configure discontinuous reception for the terminal device 400.

[0307] This makes it possible to suppress fluctuations in delay.

[0308] The base station device 300 of the present disclosure also includes a control unit 340. The control unit 340 receives setting information related to discontinuous reception of the terminal device, which is setting information transmitted from entities (AF 249, AMF 241) belonging to the core network 200 based on information from an apparatus (application server 100) that provides application functions to the terminal device 400. The control unit 340 configures the terminal device 400 for discontinuous reception based on the setting information.

[0309] This makes it possible to suppress fluctuations in delay.

[0310] In addition, the communication method of the present disclosure acquires information from an apparatus (application server 100) that provides application functions to the terminal device 400, and based on the information, notifies the base station device 300 that communicates with the terminal device 400 of setting information related to intermittent reception by using an API.

[0311] This makes it possible to suppress fluctuations in delay.

[0312] Furthermore, the communication system 1 of the present disclosure is a communication system including a base station device 300 that communicates with a terminal device 400, an information processing device 260 (AF249, AMF241), and a device that provides application functions (application server 100), and the information processing device 260 includes a control unit that acquires information from the device that provides the application functions and, based on the information, notifies the base station device 300 of setting information regarding intermittent reception of the terminal device 400 using an API.

[0313] This makes it possible to suppress fluctuations in delay.

[0314] Although the embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present disclosure. Furthermore, components of different embodiments and modifications may be combined as appropriate.

[0315] Furthermore, the effects described in this specification are merely examples and are not limiting, and other effects may also be present.

[0316] The present technology can also be configured as follows. (1) Obtaining information from a device that provides application functionality to a terminal device; a control unit that notifies a base station device that communicates with the terminal device of setting information related to discontinuous reception of the terminal device using an application programming interface (API) based on the information; An information processing device comprising: (2) The information processing device described in (1), wherein the control unit belongs to a core network to which the base station device is connected and notifies the base station device of the setting information via a device having a function described in a network function (NF). (3) The information processing device according to (1), wherein the information processing device has a function related to access control. (4) The information processing device according to any one of (1) to (3), wherein the setting information includes cycle information relating to a reception cycle of the intermittent reception. (5) The information processing device according to any one of (1) to (4), wherein the setting information includes start timing information regarding a timing to start the intermittent reception. (6) The information processing device according to any one of (1) to (5), wherein the setting information includes end timing information regarding timing to end the intermittent reception. (7) The information processing device according to any one of (1) to (6), wherein the setting information includes switching timing information regarding timing for switching a reception cycle of the intermittent reception. (8) The information processing device according to any one of (1) to (7), wherein the control unit receives, from the base station device, reception timing information regarding reception timing of data transmitted by the device during a reception period of the discontinuous reception. (9) The information processing device according to (8), wherein the control unit transmits test data for measuring the reception timing to the base station device. (10) The information processing device according to (8) or (9), wherein the control unit adjusts the transmission timing based on the reception timing information so that the terminal device receives the data before a predetermined period in the reception period, and transmits the data. (11) The control unit requesting the base station device to adjust the reception period of the discontinuous reception so that the reception timing of the data transmitted by the device at the terminal device is earlier than a predetermined period in the reception period of the discontinuous reception; transmitting test data for adjusting the reception period; The information processing device according to any one of (1) to (7). (12) the information includes information about a plurality of terminal devices each connected to a different core network; the control unit notifies the base station device that communicates with the terminal device of the setting information of the terminal device that is connected to the core network to which the terminal device belongs, among the plurality of terminal devices; The information processing device according to any one of (1) to (11). (13) a control unit that notifies an entity belonging to a core network to which the terminal device is connected of information about the terminal device that provides the application function; Equipped with The information is used by the entity to configure discontinuous reception of the terminal device. Information processing device. (14) receiving setting information for discontinuous reception of the terminal device, the setting information being transmitted from an entity belonging to the core network based on information from a device that provides an application function to the terminal device; a control unit that sets the terminal device to the discontinuous reception based on the setting information; A base station device comprising: (15) Obtaining information from a device that provides application functionality to a terminal device; Based on the information, the setting information regarding the discontinuous reception of the terminal device is notified to a base station device that communicates with the terminal device using an application programming interface (API). Communication method. (16) A communication system including a base station device that communicates with a terminal device, an information processing device, and a device that provides an application function, The information processing device includes: obtaining information from a device that provides the application function; a control unit that notifies the base station device of setting information related to discontinuous reception of the terminal device based on the information, using an application programming interface (API); A communication system comprising: [Explanation of symbols]

[0317] 1. Communication Systems 100 Application server (information processing device) 200, 200A, 200B Core Network 241 AMF 249AF 300, 300A, 300B base station equipment 400, 400A, 400B terminal equipment

Claims

1. A method for providing a plurality of terminal devices connected to different private networks and / or core networks, comprising: acquiring first information from a device that provides an application function; a control unit that notifies a base station device that communicates with the terminal devices of second information related to the discontinuous reception of the plurality of terminal devices based on the first information, using an application programming interface (API); Equipped with the second information includes setting information for adjusting a cycle of the discontinuous reception in the plurality of terminal devices in accordance with a data transmission interval; the first information includes at least one of information for identifying the terminal device and information regarding a timing for transmitting the data; Information processing device.

2. The information processing device according to claim 1 , wherein the control unit notifies the base station device of the second information via a device that belongs to a core network to which the base station device is connected and has a network function (NF).

3. The information processing device according to claim 1 , wherein the information processing device has a function relating to access control.

4. The information processing device according to claim 1 , wherein the setting information includes cycle information relating to a reception cycle of the intermittent reception.

5. The information processing device according to claim 1 , wherein the setting information includes start timing information regarding a timing for starting the intermittent reception.

6. The information processing device according to claim 1 , wherein the setting information includes end timing information regarding a timing for ending the discontinuous reception.

7. The information processing device according to claim 1 , wherein the setting information includes switching timing information regarding timing for switching the reception cycle of the intermittent reception.

8. The information processing device according to claim 1 , wherein the control unit receives, from the base station device, reception timing information regarding reception timing at which the terminal device receives data transmitted by the device during the reception period of the discontinuous reception.

9. The information processing device according to claim 8 , wherein the control unit transmits test data for measuring the reception timing to the base station device.

10. The information processing device according to claim 8 , wherein the control unit adjusts a transmission timing based on the reception timing information so that the terminal device receives the data before a predetermined period in the reception period, and transmits the data.

11. The control unit requesting the base station device to adjust the reception period of the discontinuous reception so that the reception timing of the data transmitted by the device at the terminal device is earlier than a predetermined period in the reception period of the discontinuous reception; transmitting test data for adjusting the reception period; The information processing device according to claim 1 .

12. The control unit notifies the base station device that communicates with the terminal device of the second information of the terminal device that is connected to the private network or the core network to which the terminal device belongs, among the plurality of terminal devices. The information processing device according to claim 1 .

13. Second information is transmitted from an entity belonging to a core network to a plurality of terminal devices connected to different private networks and / or a core network based on first information from a device providing an application function, the second information relating to intermittent reception of the plurality of terminal devices being received; a control unit that sets the terminal device to the discontinuous reception based on the second information; Equipped with the second information includes setting information for adjusting a cycle of the discontinuous reception in the plurality of terminal devices in accordance with a data transmission interval; the first information includes at least one of information for identifying the terminal device and information regarding a timing for transmitting the data; Base station equipment.

14. An information processing device, acquiring first information from a device that provides application functions to a plurality of terminal devices that are connected to different private networks and / or core networks; notifying a base station device communicating with the terminal devices of second information related to discontinuous reception of the plurality of terminal devices based on the first information, using an application programming interface (API); the second information includes setting information for adjusting a cycle of the discontinuous reception in the plurality of terminal devices in accordance with a data transmission interval; the first information includes at least one of information for identifying the terminal device and information regarding a timing for transmitting the data; Communication method.

15. A communication system comprising: a base station device that communicates with a terminal device; an information processing device; and a device that provides application functions to a plurality of terminal devices that are connected to different private networks and / or core networks, The information processing device includes: acquiring first information from a device that provides the application function; a control unit that notifies the base station device of second information related to discontinuous reception of the plurality of terminal devices based on the first information, using an application programming interface (API); Equipped with the second information includes setting information for adjusting a cycle of the discontinuous reception in the plurality of terminal devices in accordance with a data transmission interval; the first information includes at least one of information for identifying the terminal device and information regarding a timing for transmitting the data; Communication system.

Images