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

Abstract

An information processing apparatus (260) is provided with a control unit (263). The control unit (263) acquires information from an apparatus (100) for providing an application function to a terminal apparatus (400). The control unit (263) notifies, using an application programming interface (API), a base station apparatus (300) that communicates with the terminal apparatus (400) of setting information on intermittent reception of the terminal apparatus (400) based on the information.

Description

Technical Field

[0001] This disclosure relates to information processing equipment, base station equipment, communication methods, and communication systems. Background Technology

[0002] Research is underway on next-generation mobile communication systems that can be used by various entities based on regional and individual needs. These next-generation mobile communication systems include, for example, mechanisms that allow various entities, such as local companies and local governments, to flexibly build and use the network in their own buildings and locations, in addition to nationwide 5G services provided by mobile phone operators.

[0003] Citation List

[0004] Patent documents

[0005] Patent Document 1: JP 2019-57929 A Summary of the Invention

[0006] Technical issues

[0007] When networks are built in a point-to-point manner, multiple networks exist simultaneously, and servers providing application functionality to terminal devices may communicate with terminal devices connected to different networks at the same time. For example, when terminal devices connected to different networks are playing a game simultaneously, they may be communicating with the same game server at the same time.

[0008] In situations where multiple terminal devices connect to a server synchronously, such as in online gaming, there is a risk that the latency generated during communication with the server may differ for each terminal device. In such cases, for example, if the latency for each terminal device is constant, multiple terminal devices can communicate synchronously with the server by pre-considering latency on the server side. However, if latency fluctuates, the latency is not fixed, and multiple terminal devices may find it difficult to communicate synchronously with the server.

[0009] As mentioned above, when multiple terminal devices communicate with the server simultaneously, there is a need to suppress latency fluctuations.

[0010] Therefore, this disclosure provides a mechanism that can further suppress delay fluctuations.

[0011] Solution to the problem

[0012] According to this disclosure, an information processing device is provided. The information processing device includes a control unit. The control unit obtains information from a device that provides application functions to a terminal device. Based on the information, the control unit uses an application programming interface (API) to notify a base station device communicating with the terminal device of setting information regarding the intermittent reception of the terminal device. Attached Figure Description

[0013] Figure 1 This is a diagram illustrating the general outline of a communication system 1 according to an embodiment of the present disclosure.

[0014] Figure 2 This is a diagram illustrating an example of 5G architecture.

[0015] Figure 3 This is a diagram illustrating an example of 4G architecture.

[0016] Figure 4 This is a diagram illustrating an example configuration of a dedicated 5G according to an embodiment of the present disclosure.

[0017] Figure 5 This is a block diagram illustrating an example of the configuration of an information processing device according to an embodiment of the present disclosure.

[0018] Figure 6 This is a block diagram illustrating an example of the configuration of a base station device according to an embodiment of the present disclosure.

[0019] Figure 7 This is a block diagram illustrating an example of the configuration of a terminal device according to an embodiment of the present disclosure.

[0020] Figure 8 This is a diagram used to explain the delay in a communication system according to a first embodiment of the present disclosure.

[0021] Figure 9 This is a diagram used to illustrate the overview of DRX.

[0022] Figure 10 This is a diagram used to explain the fluctuations in latency caused by CDRX.

[0023] Figure 11 This is a diagram used to explain the fluctuations in latency caused by CDRX.

[0024] Figure 12 This is a diagram illustrating an example of CDRX configuration processing performed in a communication system according to a first embodiment of the present disclosure.

[0025] Figure 13 This is a sequence diagram used to explain the flow of CDRX setting processing according to the first embodiment of the present disclosure.

[0026] Figure 14 This is a sequence diagram illustrating an example of a CDRX setting request processing flow according to an embodiment of the present disclosure.

[0027] Figure 15 This is a diagram used to explain the fluctuations in delay according to the second embodiment of this disclosure.

[0028] Figure 16 This is a diagram illustrating the timing of video data reception by a terminal device used to explain the second embodiment of this disclosure.

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

[0030] Figure 18 This is a sequence diagram illustrating an example of the process for handling arrival timing notification according to a second embodiment of the present disclosure.

[0031] Figure 19 This is a sequence diagram illustrating another example of the flow for explaining the arrival timing notification processing according to a second embodiment of the present disclosure.

[0032] Figure 20 This is a diagram used to explain the start timing of CDRX.

[0033] Figure 21 This is an illustration of an example of the CDRX synchronization process according to a third embodiment of the present disclosure.

[0034] Figure 22 This is an illustration of an example of the CDRX synchronization process according to a third embodiment of the present disclosure.

[0035] Figure 23 This is a diagram illustrating an example of the switching process according to a fourth embodiment of the present disclosure. Detailed Implementation

[0036] The embodiments of this disclosure will now be described in detail with reference to the accompanying drawings. Note that in this specification and the drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and repeated descriptions are omitted.

[0037] Furthermore, in this specification and accompanying drawings, similar components of embodiments can be distinguished by appending different letters after the same reference numerals. However, when it is not necessary to specifically distinguish each similar component, only the same reference numerals are assigned.

[0038] The one or more embodiments (including examples and variations) described below can be implemented independently. On the other hand, at least some of the embodiments described below can be suitably combined with at least some of the embodiments described below. These embodiments may include novel features that differ from each other. Therefore, these embodiments can help solve different purposes or problems and can exhibit different effects.

[0039] Note that the explanation will be given in the following order.

[0040] 1. Overview

[0041] 1.1. Schematic diagram of the system

[0042] 1.2. Summary of the proposed technology

[0043] 2. Example of a communication system configuration

[0044] 2.1. Example of network architecture

[0045] 2.2. Dedicated 5G

[0046] 2.3. Information processing equipment

[0047] 2.4. Base Station Equipment

[0048] 2.5. Terminal Equipment

[0049] 3. First Embodiment

[0050] 4. Second Embodiment

[0051] 5. Third Embodiment

[0052] 6. Fourth Embodiment

[0053] 7. Variations

[0054] <<1. Summary>>

[0055] <1.1. System Schematic Structure>

[0056] First, refer to Figure 1 An outline of a communication system 1 according to an embodiment of the present disclosure is provided. Figure 1 This is a diagram illustrating the general outline of a communication system 1 according to an embodiment of the present disclosure.

[0057] exist Figure 1 In the example shown in the diagram, the communication system 1 includes information processing equipment 100, core networks 200A and 200B, base station equipment 300A and 300B, and terminal equipment 400A and 400B.

[0058] Information processing device 100 is a server (device) that provides application functions to terminal device 400. In the following text, information processing device 100 is referred to as application server 100.

[0059] Application server 100 communicates synchronously with multiple terminal devices 400. For example, application server 100 is a game server that provides online games to multiple terminal devices 400. In this case, application server 100 may synchronously distribute augmented reality (AR) / virtual reality (VR) data, which serves as game data, to multiple terminal devices 400.

[0060] Application server 100 may be, for example, a server for Internet of Things (IoT) control. For instance, application server 100 may be a control server that arranges multiple vehicles (an example of terminal device 400) for driving. In this case, for example, application server 100 controls the multiple vehicles synchronously with a timer. For example, application server 100 synchronously distributes IoT control information (e.g., vehicle control information) to multiple terminal devices 400.

[0061] The core network 200 is a local cellular network such as local 5G or local 4G. The core network 200 includes, for example, an information processing device 260 with application function (AF) nodes.

[0062] Information processing device 260 sends transmission data sent by application server 100 to terminal device 400. For example, information processing device 260 may be a push notification server that sends transmission data to terminal device 400 via push notification.

[0063] Base station equipment 300 is a wireless communication device that communicates wirelessly with terminal equipment 400. Base station equipment 300 is a type of communication equipment. Furthermore, base station equipment 300 is a type of information processing equipment.

[0064] Terminal device 400 is a wireless communication device that communicates wirelessly with base station device 300. Terminal device 400 can be, for example, a mobile phone, smart device (smartphone or tablet), personal digital assistant (PDA), or personal computer. Furthermore, terminal device 400 can be an M2M (machine-to-machine) device or an IoT (Internet of Things) device. Additionally, terminal device 400 can be a head-mounted display, VR glasses, etc.

[0065] Terminal device 400 is connected to core network 200 via base station device 300.

[0066] <1.2. Summary of the proposed technology>

[0067] exist Figure 1 In the communication system 1 shown in the diagram, when the application server 100 and the terminal device 400 communicate with each other, a communication delay occurs between the application server 100 and the terminal device 400. At this time, as... Figure 1As illustrated, when multiple terminal devices 400A and 400B are connected to different core networks 200A and 200B, the communication latency may differ between terminal devices 400A and 400B.

[0068] For example, when the communication latency is constant in terminal devices 400A and 400B, application server 100 adjusts data transmission based on the latency, so that terminal devices 400A and 400B can distribute data synchronously.

[0069] However, when the communication latency of terminal devices 400A and 400B fluctuates, it is difficult to adjust the data transmission on the application server 100 side, making it difficult to distribute the synchronized data in terminal devices 400A and 400B.

[0070] For example, fluctuations in communication latency may occur when terminal devices 400A and 400B perform intermittent reception (e.g., connected-mode DRX (Discontinuous Transmission)). If the reception timings of terminal devices 400A and 400B performing intermittent reception are different, terminal devices 400A and 400B cannot receive data synchronously, and there is a risk of fluctuations in communication latency. Note that details of communication latency fluctuations will be explained later.

[0071] In particular, in conventional terminal devices 400A and 400B, when the core network 200 to be connected is different, it is difficult to synchronize the receiving timing of intermittent reception.

[0072] 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 communicating with the terminal device 400 of setting information regarding the intermittent reception of the terminal device 400.

[0073] Note that the information received by the information processing device 260 from the application server 100 may include, for example, information specifying the terminal device 400 to be synchronized and information about the timing of data transmission.

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

[0075] As a result, the information processing device 260 can ensure the timing consistency of the intermittent reception of the terminal device 400, thereby suppressing fluctuations in communication delay.

[0076] <<2. Example of a Communication System Structure>>

[0077] <2.1. Example of Network Architecture>

[0078] Next, we will refer to Figure 2 This section illustrates the architecture of a fifth-generation mobile communication system (5G), using the core network 200 of communication system 1 as an example. Figure 2 This is a diagram illustrating an example of a 5G architecture. The 5G core network 200 is also referred to as 5GC (5G Core) / NGC (Next Generation Core). In the following text, the 5G core network 200 is also referred to as 5GC / NGC 200. The 5GC / NGC 200 is connected to the User Equipment (UE) 401 via (R)AN 301.

[0079] (R)AN 301 has the capability to connect to a radio access network (RAN) and to access networks (AN) other than the RAN. (R)AN 301 includes base station equipment referred to as gNB or ng-eNB.

[0080] The 5GC / NGC 200 primarily handles connection permission and session management when the UE 401 connects to the network. The 5GC / NGC 200 may include user plane function group 220 and control plane function group 240.

[0081] User plane function group 220 includes User Plane Function (UPF) 221 and Data Network (DN) 222. UPF 221 has user plane processing capabilities. UPF 221 includes routing / forwarding capabilities for data processed in the user plane. DN 222 has the capability to provide connections to the operator's own services, such as those provided by a mobile network operator (MNO), to the Internet, or to third-party services. As described above, user plane function group 220 acts as a gateway, serving as the boundary between 5GC / NGC 200 and the Internet.

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

[0083] AMF 241 provides functions such as registration processing, connection management, and mobility management for UE 401. SMF242 provides functions such as session management and IP allocation and management for UE 401. AUSF 243 provides authentication functions. NSSF 244 provides functions related to network slice selection. NEF 245 provides network function capabilities and events to third parties, AF 249, and edge computing functions.

[0084] NRF 246 provides network discovery functionality and maintains network function profiles. PCF 247 provides policy control functionality. UDM 248 provides 3GPP AKA authentication information generation and user ID processing functionality. AF 249 provides the ability to interact with the core network to provide services.

[0085] For example, control plane function group 240 obtains information from UDM 248, which stores subscriber information of UE 401, and determines whether UE 401 can connect to the network. Control plane function group 240 uses UE 401's contract information and encryption keys included in the information obtained from UDM 248 for this determination. Additionally, control plane function group 240 generates encryption keys, etc.

[0086] That is, control plane function group 240 determines, for example, whether a network can be connected based on whether information associated with the subscriber number of UE 401, called the International Mobile Subscriber Identity (IMSI), is stored in UDM 248. Note that the IMSI is stored, for example, in the subscriber identification module (SIM) card of UE 401.

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

[0088] in addition, Figure 1The diagram shows N1 as the reference point between UE 401 and AMF 241, and N2 as the reference point between RAN / AN301 and AMF 241. N4 is the reference point between SMF 242 and UPF 221, and information is exchanged between these network functions (NFs).

[0089] As mentioned above, in 5GC / NGC 200, an interface is prepared for transmitting information and controlling functions via an application programming interface (API) called a service-based interface.

[0090] An API specifies a resource and enables GET (resource retrieval), POST (resource creation and data addition), PUT (resource creation and update), and DELETE (resource deletion) methods for that resource. This functionality is commonly used in web-related technology fields.

[0091] For example, when establishing a communication session, Figure 2 The diagram shows AMF 241, SMF 242, and UDM 248 exchanging information with each other using an API. It is generally not assumed that applications (e.g., AF 249) use such an API. However, when AF 249 uses such an API, it can utilize information from the 5G cellular network and believes it can further evolve the functionality of its applications.

[0092] Note that in public networks, the AF 289 has difficulty using the APIs used by the AMF 241, SMF 242, and UDM 248. However, in the case of non-public private 5G networks, it is believed that the system can be configured, for example, to include changes to the API of the 5GC / NGC 200, enabling the AF 289 to use such APIs.

[0093] Here, examples of APIs will be described. APIs (1) to (4) described here are described in 3GPP TS 23.502.

[0094] [API(1)]

[0095] API(1) is the API in which SMF 242 notifies the pre-registered UE 401 to change from a power-off state to a power-on state and attach to the network, and the IP address obtained at this time.

[0096] When a UE 401 with a registered IMSI obtains its IP address using API (1), the SMF 242 notifies the NF of the IP address.

[0097] [API(2)]

[0098] UE 401 enters idle mode when not communicating and switches to connected mode when communicating. API (2) is the API in which AMF 241 notifies UE 401 whether it is in idle mode or connected mode.

[0099] [API(3)]

[0100] API (3) is an API used to broadcast messages (paging messages) from the base station to instruct UE 401 to switch from idle mode to connected mode.

[0101] [API(4)]

[0102] API (4) is the API in which AMF 241 provides location information for UE 401. AMF 241 can use API (4) to notify UE 401 which tracking area it is in, which cell it belongs to, and when it enters a specific area.

[0103] Notice, Figure 2 The example of UE 401 is the terminal device 400 of this embodiment. The example of RAN / AN 301 is the base station device 300 according to this embodiment.

[0104] also, Figure 1 The information processing device 260 shown in the diagram is an example of a device, for example, with the functionality of an AF 249 or AMF 241. The application server 100 is connected to the core network 200 via the Internet and is not in... Figure 2 As shown in the image.

[0105] Reference Figure 3 This section illustrates the architecture of a fourth-generation mobile communication system (4G), using the core network 200 of communication system 1 as an example. Figure 3 This is a diagram illustrating an example of 4G architecture.

[0106] like Figure 3 As shown in the diagram, 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.

[0107] The eNB 302 functions as a 4G base station. The MME 252 is the control node that processes control plane signals and manages the mobility state of the UE 401. The UE 401 sends an attachment request to the MME 252 to attach to the cellular system.

[0108] S-GW 253 is a control node that processes user plane signals and serves as a gateway device for switching the transmission path of user data. P-GW 254 is a control node that processes user plane signals and serves as a gateway device that acts as the connection point between the core network 200 and the Internet. HSS 255 is a control node that processes subscriber data and performs service control.

[0109] MME 252 corresponds to the functions of AMF 241 and SMF 242 in 5G networks. Additionally, HSS 255 corresponds to the functions of UDM248.

[0110] like Figure 3 As shown in the diagram, eNB 302 is connected to MME 252 via the S1-MME interface and to S-GW 253 via the S1-U interface. S-GW 253 is connected to MME 252 via the S11 interface, and MME 252 is connected to HSS255 via the S6a interface. P-GW 254 is connected to S-GW 253 via the S5 / S8 interface.

[0111] <2.2. Dedicated 5G>

[0112] A portion of the communication system 1 according to embodiments of this disclosure may employ dedicated 5G or dedicated 4G. Currently, in local area networks (LANs), wireless LANs conforming to the 802.11 standard are used. Dedicated 5G or dedicated 4G refers to base station equipment 300 (e.g., [missing information]) installed in the LAN and employing a cellular system. Figure 2 RAN / AN 301 or Figure 3 The eNB 302) is a cellular system. In 3GPP, dedicated 5G or dedicated 4G is referred to as a non-public network. Note that in the following description, it is assumed that a portion of communication system 1 uses dedicated 5G.

[0113] Reference Figure 4 This describes a case where a dedicated 5G is used as a cellular system (including a base station device 300 and a core network 200) in a communication system 1 according to an embodiment of the present disclosure. Figure 4 This is a diagram illustrating an example configuration of a dedicated 5G according to an embodiment of the present disclosure.

[0114] In dedicated 5G, base station equipment 300, terminal equipment 400, and information processing equipment 260A and 260B with some functions of the core network 200 are deployed in a local area network (LAN). Additionally, information processing equipment 260C to 260F with the remaining functions of the core network 200 are deployed, for example, in a cloud data center with an Internet connection.

[0115] exist Figure 4In the example, information processing devices 260A and 260B, which have the functions of UPF 221A and 221B, are arranged in a local area network (LAN). Information processing devices 260C and 260D, which have the functions of UPF 221C and 221D, are arranged in the cloud of the Internet line. Additionally, information processing device 260E, which functions as control plane function group 240, is arranged in the cloud of the Internet line. Furthermore, information processing device 260F, which has the function of AF 249 (e.g., corresponding to...), is also arranged in the cloud. Figure 1 The information processing device 260 in the cloud can be arranged separately from the information processing device 260E that functions as the control plane functional group 240.

[0116] Note that UPFs 221A and 221B, deployed on the local area network (LAN), are present on the LAN when the control plane function group 240 starts up or when the core network 200 begins operation. On the other hand, UPFs 221C and 221D, deployed in the cloud, are not present in the cloud when the control plane function group 240 starts up or when the core network 200 begins operation. UPFs 221C and 221D are, for example, functions that start after the control plane function group 240 starts up or after the core network 200 begins operation.

[0117] Figure 4 A local area network (LAN) is typically located in an office, factory, or private residence. A LAN is connected to the Internet via a network N, for example.

[0118] Dedicated IP addresses are assigned to base station equipment 300 and core network 200. Base station equipment 300 and core network 200 communicate with each other using these dedicated IP addresses. For example, by using technologies such as Virtual Private Networks (VPNs), base station equipment 300 and core network 200 can communicate with each other using dedicated IP addresses. That is, the network connecting base station equipment 300 and core network 200 can be considered a dedicated network (closed network).

[0119] Note that in Figure 4 In this configuration, base station equipment 300, terminal equipment 400, and a portion of UPF 221 (UPF 221A and 221B) are deployed in a local area network (LAN). Furthermore, although control plane function group 240 and a portion of UPF 221 (UPF 221C and 221D) are deployed in the cloud, their deployment is not limited to this. Base station equipment 300 and terminal equipment 400 can be deployed in a LAN, and the functions of UPF 221A and 221B can be implemented in the cloud. Additionally, at least some functions of control plane function group 240 can be implemented on a LAN.

[0120] As described above, the communication system 1 according to an embodiment of the present disclosure is a system in which an application on the network side sends data to multiple terminal devices 400 using different dedicated 5G networks. In embodiments of the present disclosure, for example, it is assumed that an application server 100 (see...) Figure 1 It simultaneously distributes control information for controlling devices, video information for games, and other usage information to multiple terminal devices 400.

[0121] More specifically, the application server 100, located outside the dedicated 5G network, notifies the terminal device 400 of data via the information processing device 260F, located within the dedicated 5G network. Therefore, the information processing device 260F can also be described as a push notification server located within the dedicated 5G network. Note that push notification is a technology that sends messages (examples of data) to the terminal device 400 originating from the network.

[0122] <2.3. Information Processing Equipment>

[0123] Next, we will refer to Figure 5 This section describes an example of the configuration of an information processing device 260 according to an embodiment of the present disclosure. Figure 5 This is a block diagram illustrating an example configuration of an information processing device 260 according to an embodiment of the present disclosure.

[0124] Information processing device 260 is a device that implements the NF or AF functions of the core network 200. Information processing device 260 is, for example, a server device. Information processing device 260 can be a device collectively referred to as a cloud server or edge server.

[0125] like Figure 5 As shown in the diagram, the information processing device 260 includes a communication unit 261, a storage unit 262, and a control unit 263. Note that... Figure 5 The configuration shown in the diagram is a functional configuration; the hardware configuration may differ from the functional configuration. Furthermore, the functions of the information processing device 260 can be distributed across multiple physically separate configurations. For example, the information processing device 260 may include multiple server devices.

[0126] Communication unit 261 is a communication interface used for communicating with other devices. Communication unit 261 can be a network interface or a device connection interface. For example, communication unit 261 can be a local area network (LAN) interface such as a network interface card (NIC), or a USB interface including a universal serial bus (USB) host controller, USB port, etc. Furthermore, communication unit 261 can be a wired interface or a wireless interface. Communication unit 261 functions as the communication unit of information processing device 260. Communication unit 261 communicates with base station device 300, other NF nodes, or AN nodes under the control of control unit 263.

[0127] Storage unit 262 is a data read / write storage device such as dynamic random access memory (DRAM), static random access memory (SRAM), flash memory, or hard disk. Storage unit 262 serves as the storage unit of information processing device 260.

[0128] Control unit 263 is a controller that controls each unit of information processing device 260. Control unit 263 is implemented, for example, by a processor such as a central processing unit (CPU), microprocessor unit (MPU), or graphics processing unit (GPU). For instance, control unit 263 is implemented by a processor that uses random access memory (RAM) as its working area to execute various programs stored in storage devices within information processing device 260. Note that control unit 263 can be implemented by integrated circuits such as application-specific integrated circuits (ASICs) or field-programmable gate arrays (FPGAs). Any of a CPU, MPU, GPU, ASIC, and FPGA can be considered a controller.

[0129] <2.4. Base Station Equipment>

[0130] Next, we will refer to Figure 6 This section describes an example of the configuration of a base station device 300 according to an embodiment of the present disclosure. Figure 6 This is a block diagram illustrating an example configuration of a base station device 300 according to an embodiment of the present disclosure.

[0131] Base station equipment 300 is a wireless communication device that communicates wirelessly with terminal equipment 400. Base station equipment 300 is a type of communication equipment. Additionally, base station equipment 300 is a type of information processing equipment.

[0132] Base station equipment 300 may be comprised of a collection of multiple physical or logical devices. For example, in embodiments of this disclosure, base station equipment 300 may be distinguished as multiple devices of baseband unit (BBU) and radio unit (RU), and may be interpreted as an collection of these multiple devices. Alternatively or alternatively, in embodiments of this disclosure, base station equipment 300 may be either or both of BBU and RU. BBU and RU may be connected via a predetermined interface (e.g., eCPRI). Alternatively or alternatively, RU may be referred to as remote radio unit (RRU) or radio DoT (RD). Alternatively or alternatively, RU may correspond to gNB-DU as described later. Alternatively or alternatively, BBU may correspond to gNB-CU as described later. Alternatively or alternatively, RU may be a device integrally formed with an antenna. The antenna included in base station equipment 300 (e.g., an antenna integrally formed with an RU) may employ an advanced antenna system and support MIMO (e.g., FD-MIMO) or beamforming. In an advanced antenna system, the antenna included in the base station device 300 (e.g., an antenna integrally formed with the RU) may include, for example, 64 transmit antenna ports and 64 receive antenna ports. Additionally, the antenna mounted on the RU may be an antenna panel comprising 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 antenna panels: a horizontally polarized antenna panel and a vertically polarized antenna panel, or two antenna panels: a clockwise circularly polarized antenna panel and a counterclockwise circularly polarized antenna panel. Furthermore, the RU can form and control an independent beam for each antenna panel.

[0133] Furthermore, multiple base station devices 300 can be interconnected. One or more base station devices 300 may be included in a radio access network (RAN). That is, base station device 300 may simply be referred to as RAN, RAN node, access network (AN), or AN node. The RAN in LTE is called Enhanced Universal Terrestrial RAN (EUTRAN). The RAN in NR is called NGRAN. The RAN in W-CDMA (UMTS) is called UTRAN. The base station device 300 in LTE is called an evolved Node B (eNodeB) or eNB. That is, EUTRAN includes one or more eNodeBs (eNBs). Furthermore, the base station device 300 in NR is called a gNodeB or gNB. That is, NGRAN includes one or more gNBs. In addition, EUTRAN may include gNBs (en-gNBs) connected to the core network (EPC) in the LTE communication system (EPS). Similarly, NGRAN may include ng-eNBs connected to the core network 5GC in the 5G communication system (5GS). Alternatively or alternatively, when the base station device 300 is an eNB, gNB, etc., the base station device 300 may be referred to as a 3GPP access. Alternatively, when the base station device 300 is a radio access point, it may be referred to as a non-3GPP access point. Alternatively, the base station device 300 may be an optical extension device referred to as a Remote Radio Header (RRH). Alternatively, when the base station device 300 is a gNB, it may be referred to as a combination of or any of the aforementioned gNBCU (Central Unit) and gNB DU (Distributed Unit). The gNB CU (Central Unit) manages multiple upper-layer access layer functions (e.g., RRC, SDAP, PDCP) for communication with the UE. On the other hand, the gNB-DU manages multiple lower-layer access layer functions (e.g., RLC, MAC, PHY). That is, in the messages and information described below, RRC signaling (e.g., various SIB, RRC Setup, and RRC Reconfiguration messages including MIB and SIB1) may be generated by the gNB CU, while the DCI and various physical channels (e.g., PDCCH, PBCH) described below may be generated by the gNB-DU. Alternatively, in RRC signaling, some configurations, such as IE: cellGroupConfig, can be generated by the gNB-DU, and the remaining configurations can be generated by the gNB-CU. These configurations can be sent and received via the F1 interface, which will be described later. Base station device 300 can be configured to communicate with other base station devices 300. For example, in the case where multiple base station devices 300 are eNBs or a combination of eNBs and en-gNBs, the base station devices 300 can be connected via the X2 interface.Alternatively, if multiple base station devices 300 are combinations of gNBs or gn-eNBs and gNBs, the devices can be connected via the Xn interface. Alternatively, if multiple base station devices 300 are combinations of gNB central units (CUs) and gNB distributed units (DUs), the devices can be connected via the F1 interface described above. Messages / information (including information in RRC signaling or DCI) described later can be communicated between multiple base station devices 300 (e.g., via the X2, Xn, and F1 interfaces).

[0134] Furthermore, as described above, base station equipment 300 can be configured to manage multiple cells. The cells provided by base station equipment 300 are called serving cells. Serving cells include primary cells (PCells) and secondary cells (SCells). When providing dual connectivity to a UE (e.g., terminal equipment 400) (e.g., EUTRA-EUTRA dual connectivity, EUTRA-NR dual connectivity (ENDC), EUTRA-NR dual connectivity with 5GC, NR-EUTRA dual connectivity (NEDC), and NR-NR dual connectivity), the PCell provided by the MN (primary node) and 0 or more SCells are called a primary cell group. Additionally, serving cells may include PSCells (primary / secondary cells or primary SCG cells). In other words, when providing dual connectivity to a UE, the PSCell provided by the SN (secondary node) and 0 or more SCells are called a secondary cell group (SCG). Unless specifically configured (e.g., PUCCH on SCells), the Physical Uplink Control Channel (PUCCH) is transmitted in PCells and PSCells, but not in SCells. Additionally, radio link faults are detected in PCell and PSCell, but not (or can be omitted) in SCell. As mentioned above, because PCell and PSCell have special roles in the serving cell, they are also called special cells (SpCell). A downlink component carrier and an uplink component carrier can be associated with a cell. Furthermore, the system bandwidth corresponding to a cell can be divided into multiple bandwidth portions. In this case, one or more bandwidth portions (BWPs) can be configured for the UE, and for the UE, one bandwidth portion can be used as the active BWP. Moreover, the radio resources (e.g., frequency bands, parameter sets (subcarrier spacing), and slot configurations) available to the terminal device 400 can differ for each cell, each component carrier, or each BWP.

[0135] Figure 6 The base station equipment 300 shown in the diagram includes a communication unit 310, a storage unit 320, a network communication unit 330, and a control unit 340. Note that... Figure 6 The configuration shown in the diagram is the functional configuration, while the hardware configuration may differ from the functional configuration. Furthermore, the functions of the base station equipment 300 can be distributed across multiple physically separate configurations.

[0136] 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). Communication unit 310 operates under the control of control unit 340. When the other wireless communication device is terminal device 400, communication unit 310 can be a wireless transceiver supporting one or more wireless access methods. For example, communication unit 310 supports both NR and LTE. In addition to NR or LTE, communication unit 310 can also support W-CDMA or CDMA 2000. Furthermore, communication unit 310 can support communication using NOMA. When the other wireless communication device is other base station devices 300, communication unit 310 can be an X2 interface, an Xn interface, or an F1 interface.

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

[0138] The receiving processing unit 311 processes the uplink signal received via the antenna 313. The receiving processing unit 311 operates as a receiving unit for receiving received signals. The receiving processing unit 311 includes a wireless receiving unit 311a, a demultiplexing unit 311b, a demodulation unit 311c, and a decoding unit 311d.

[0139] The wireless receiving unit 311a performs down-conversion, removal of unnecessary frequency components, amplification level control, quadrature demodulation, conversion to digital signal, removal of guard interval (cyclic prefix), and extraction of frequency domain signal through fast Fourier transform on the uplink signal. The demultiplexing unit 311b demultiplexes the signal output from the wireless receiving unit 311a into uplink channels such as the Physical Uplink Shared Channel (PUSCH) or Physical Uplink Control Channel (PUCCH) and uplink reference signals.

[0140] The demodulation unit 311c demodulates the received signal for the uplink channel modulation symbols using a modulation method such as Binary Phase Shift Keying (BPSK) or Quadrature Phase Shift Keying (QPSK). The modulation method used by the demodulation unit 311c can be 16-Quadrature Amplitude Modulation (QAM), 64QAM, or 256QAM. In this case, the signal points on the constellation do not necessarily have to be equidistant. The constellation can be a Non-Uniform Constellation (NUC).

[0141] Decoding unit 311d decodes the encoded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to control unit 340.

[0142] The transmission processing unit 312 processes the transmission of downlink control information and downlink data. As described above, the transmission processing unit 312 is an acquisition unit that obtains bit sequences such as 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 wireless transmission unit 312d.

[0143] The encoding unit 312a uses encoding methods such as block coding, convolutional coding, and turbo coding to encode the downlink control information and downlink data input from the control unit 340. Note that the encoding unit 312a can perform encoding using polar codes and encoding using low-density parity-check codes (LDPC codes).

[0144] Modulation unit 312b modulates the encoded bits output from encoding 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 can be a non-uniform constellation.

[0145] Multiplexing unit 312c multiplexes the modulation symbols and downlink reference signals of each channel and arranges the multiplexed symbols in predetermined resource elements. Wireless transmission unit 312d performs various signal processing operations on the signals from multiplexing unit 312c. For example, wireless transmission unit 312d performs operations such as time-domain to frequency-domain conversion via Fast Fourier Transform, addition of guard intervals (cyclic prefixes), generation of baseband digital signals, conversion to analog signals, quadrature modulation, up-conversion, removal of extra frequency components, and power amplification. The signals generated by transmission processing unit 312 are transmitted from antenna 313.

[0146] Storage unit 320 is a storage device capable of reading and writing data, such as DRAM, SRAM, flash memory, or hard disk. Storage unit 320 serves as the storage unit of base station equipment 300.

[0147] The network communication unit 330 is a communication interface for communicating with nodes at a higher layer on the network (e.g., information processing device 260). For example, the network communication unit 330 may be a LAN interface such as a NIC. Alternatively, the network communication unit 330 may be an S1 interface or an NG interface for connecting to core network nodes. The network communication unit 330 may be a wired interface or a wireless interface. The network communication unit 330 functions as the network communication unit of the base station device 300.

[0148] Control unit 340 is a controller that controls each unit of base station equipment 300. Control unit 340 is implemented, for example, by a processor (hardware processor) such as a central processing unit (CPU) or a microprocessor unit (MPU). For instance, control unit 340 is implemented by a processor that uses random access memory (RAM) as its working area and executes various programs stored in storage devices within base station equipment 300. Note that control unit 340 can also be implemented by an integrated circuit such as an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA). Any of a CPU, MPU, ASIC, and FPGA can be considered a controller.

[0149] <2.5. Terminal Equipment>

[0150] Next, we will refer to Figure 7 This section describes an example of the configuration of a terminal device 400 according to an embodiment of the present disclosure. Figure 7 This is a block diagram illustrating an example configuration of a terminal device 400 according to an embodiment of the present disclosure.

[0151] Terminal device 400 is a wireless communication device that communicates wirelessly with base station device 300. Terminal device 400 may be, for example, a mobile phone, a smart device (smartphone or tablet), a personal digital assistant (PDA), or a personal computer. Terminal device 400 may also be a head-mounted display, VR glasses, etc., with wireless data transmission and reception capabilities.

[0152] Furthermore, terminal device 400 can perform sidelink communication with other terminal devices 400. When performing sidelink communication, terminal device 400 can use automatic retransmission techniques such as Hybrid Automatic Repeat Request (HARQ). Terminal device 400 can perform non-orthogonal multiple access (NOMA) communication with base station device 300. Note that terminal device 400 can also perform NOMA communication in communication with other terminal devices 400 (sidelink). In addition, terminal device 400 can perform low-power wide-area (LPWA) communication with other communication devices (e.g., base station device 300 and other terminal devices 400). Furthermore, the wireless communication used by terminal device 400 can be millimeter-wave wireless communication. Note that the wireless communication used by terminal device 400 (sidelink communication) can be wireless communication using radio waves or wireless communication using infrared or visible light (optical wireless).

[0153] Terminal device 400 can simultaneously connect to multiple base station devices or multiple cells for communication. For example, when one base station device can provide multiple cells, terminal device 400 can perform carrier aggregation by using one cell as a pCell and another cell as an sCell. Furthermore, when multiple base station devices 300 can each provide one or more cells, terminal device 400 can achieve dual connectivity (DC) by using one or more cells managed by one base station device (MN (e.g., MeNB or MgNB)) as pCells or pCell and sCells, and using one or more cells managed by other base station devices (SN (e.g., SeNB or SgNB)) as pCells (PSCells) or pCell (PSCells) and sCells. DC can be referred to as multiple connectivity (MC).

[0154] Note that in situations where communication areas are supported by cells (multiple cells with different or the same cell identifier) ​​from different base station devices 300, these multiple cells can be bundled together using carrier aggregation (CA), dual connectivity (DC), or multiple connectivity (MC) technologies, enabling communication between the base station device 300 and the terminal device 400. Alternatively, the terminal device 400 and multiple base station devices 300 can communicate with each other via cells from different base station devices 300 using Cooperative Multipoint Transmission and Reception (CoMP) technology.

[0155] 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... Figure 7The configuration shown in the diagram is the functional configuration, while the hardware configuration may differ from the functional configuration. Furthermore, the functions of the terminal device 400 can be distributed across multiple physically separate configurations.

[0156] Communication unit 410 is a signal processing unit for wireless communication with other wireless communication devices (e.g., base station device 300 and other terminal devices 400). Communication unit 410 operates under the control of control 115. Communication unit 410 can be a wireless transceiver corresponding to one or more wireless access methods. For example, communication unit 410 supports both NR and LTE. In addition to NR or LTE, communication unit 410 can also support W-CDMA or CDMA 2000. Furthermore, communication unit 410 can support communication using NOMA.

[0157] The communication unit 410 includes a receiving processing unit 411, a transmitting processing unit 412, and an antenna 413. The communication unit 410 may include multiple receiving processing units 411, multiple transmitting processing units 412, and multiple antennas 413. The configuration of the communication unit 410, receiving processing unit 411, transmitting processing unit 412, and antenna 414 is similar to that of the communication unit 310, receiving processing unit 311, transmitting processing unit 312, and antenna 314 of the base station device 300.

[0158] Storage unit 420 is a storage device capable of reading and writing data, such as DRAM, SRAM, flash memory, or hard disk. Storage unit 420 serves as the storage unit of terminal device 400.

[0159] The network communication unit 430 is a communication interface used to communicate 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 can be a wired interface or a wireless interface. The network communication unit 430 functions as the network communication unit of the terminal device 400. The network communication unit 430 communicates with other devices under the control of the control unit 450.

[0160] Input / output unit 440 is a user interface for exchanging information with a user. For example, input / output unit 440 may be an operating device for various user operations, such as a keyboard, mouse, operation keys, and touch panel. Alternatively, input / output unit 440 may be a display device such as a liquid crystal display (LCD) or an organic electroluminescent (EL) display. Input / output unit 440 may be an acoustic device such as a speaker or buzzer. Input / output unit 440 may be a lighting device such as a light-emitting diode (LED) lamp. Input / output unit 440 functions as an input / output unit (input device, output device, operating device, or notification device) of terminal device 400.

[0161] Control unit 450 is a controller for each unit of terminal device 400. Control unit 450 is implemented, for example, by a processor such as a CPU, MPU, or GPU. For instance, control unit 450 is implemented by a processor that uses RAM or similar memory as its working area to execute various programs stored in a storage device within terminal device 400. Note that control unit 450 can also be implemented by an integrated circuit such as an ASIC or FPGA. Any of a CPU, MPU, GPU, ASIC, and FPGA can be considered a controller.

[0162] <<3. First Embodiment>>

[0163] As described above, when multiple terminal devices 400 belong to different dedicated networks, the data sent by the application server 100 arrives at each terminal device 400 with varying latency. (Refer to...) Figure 8 This illustrates the point.

[0164] Figure 8 This is a diagram illustrating the delay in a communication system 1 according to a first embodiment of the present disclosure.

[0165] Figure 8 The diagram illustrates a scenario where an application server 100 installed in Tokyo simultaneously sends data to terminal device 400A connected to a dedicated network installed in Hong Kong, China, and terminal device 400B connected to a dedicated network installed in Osaka, China. Here, it is assumed that the application server 100 sends (pushes) VR game video information (VR game videos) as data at predetermined time intervals.

[0166] When sending video information, application server 100 first receives the video information in terminal device 400B (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.

[0167] When video information is received, the terminal device 400B sends the response information corresponding to the video information to the application server 100 (step S12). The response information may include control information such as game commands.

[0168] On the other hand, when terminal device 400B receives video information that evening (step S13), terminal device 400A sends response information corresponding to the video information to application server 100 (step S14). Figure 8 In the example, the response information sent by terminal device 400A arrives at application server 100 after a delay of D1 compared to the response information sent by terminal device 400B.

[0169] As mentioned above, the amount of communication delay between the terminal device 400 and the application server 100, which belong to different dedicated networks, is different for each dedicated network.

[0170] Here, as in Figure 8 As illustrated in steps S15 to S18, it is assumed that the latency between application server 100 and terminal device 400A, and the latency between application server 100 and terminal device 400B, are constant. Note that the processing in steps S15 to S18 is the same as that in steps S11 to S14, therefore its description is omitted.

[0171] As described above, when the latency of terminal device 400A and terminal device 400B is constant, the latency difference of the response information received by application server 100 is also constant, D1. With the latency difference between multiple terminal devices 400A being constant, application server 100 can reduce the impact of latency with terminal devices 400 by taking the latency difference into account.

[0172] For example, suppose application server 100 determines which of terminal devices 400A and 400B initiated a command operation first. In this case, application server 100 makes this determination by pre-adding a delay difference D1 to the timing of receiving the response information from terminal device 400B. As a result, even if the delay amounts of terminal devices 400A and 400B are different, application server 100 can correctly determine which of terminal devices 400A and 400B initiated a command operation first.

[0173] As described above, when the signal delay between terminal device 400 and application server 100 is constant, application server 100 can reduce the impact of delay. As a result, application server 100 can ensure the fairness of the services provided to terminal device 400. For example, even in a game where one of terminal devices 400A and 400B is trying to capture the flag first, terminal devices 400A and 400B connected to different dedicated networks can play the game simultaneously.

[0174] However, if the latency of terminal device 400A and terminal device 400B fluctuates, application server 100 will have difficulty correcting the latency.

[0175] For example, as in Figure 8 As shown in the diagram, when the delay when terminal device 400A receives data is greater than in steps S13 and S18 (step S22), the timing of application server 100 receiving the response from terminal device 400A is delayed (step S23). As a result, the delay difference between terminal devices 400A and 400B becomes D2, which is greater than D1.

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

[0177] Thus, when latency fluctuates, the correction amount (latency difference) becomes inconsistent, making it difficult for application server 100 to perform corrections. For example, even if terminal devices 400A and 400B perform command operations simultaneously, application server 100 may incorrectly determine that one of terminal devices 400A and 400B operated earlier, potentially compromising the fairness of the service.

[0178] This fluctuation occurs due to various factors. One such factor is, for example, the waiting in the switch buffers of a communication system 1 that includes a dedicated network. A large amount of traffic flows through the network, and a large number of packets (data) may become stuck in the switch buffers. Variations in the amount of stuck packets can be one of the factors causing fluctuations in latency.

[0179] In this context, for example, prioritizing packets through Quality of Service (QoS) control and sending packets with higher priority to the switch's output can reduce packet latency and suppress latency fluctuations.

[0180] Another factor contributing to latency fluctuations is discontinuous reception (DRX) operation. Here, we will refer to... Figure 9 This section provides an overview of DRX. Figure 9 This is a diagram illustrating the general structure of DRX. DRX is intermittent reception performed in a radio access network (RAN) to suppress power consumption of terminal equipment 400.

[0181] like Figure 9 As illustrated in the diagram, the terminal device 400 performing DRX performs a receiving operation during the on-duration period and does not perform a receiving operation during other periods. The terminal device 400 performs intermittent reception by repeating this operation during the DRX cycle. The terminal device 400 can suppress power consumption by cutting off the power to the receiving unit during periods other than the on-duration period.

[0182] DRX is disclosed in Rel 15 TS 36.321 Section 5.7 (LTE) and Rel 15 TS 38.321 Section 5.7 (NR). DRX operates in a similar manner in LTE and NR. Without DRX, terminal device 400 monitors the PDCCH as a control signal in virtually all subframes. If the PDCCH indicates the presence of a PDSCH addressing terminal device 400 itself, terminal device 400 receives the PDSCH indicated in the PDCCH. Receiving the PDCCH when there is no PDSCH addressing itself leads to an increase in power consumption for terminal device 400. Furthermore, during receive operations, terminal device 400 periodically reports channel measurement results, etc., to base station device 300 in the uplink. Therefore, when terminal device 400 performs receive operations without transmitting or receiving data, the processing load and power consumption increase for base station device 300, in addition to terminal device 400.

[0183] Therefore, in NR and LTE, there is a mechanism for terminal device 400 to perform intermittent reception while in RRC connection state. In intermittent reception (DRX), the time interval (connection duration) for terminal device 400 to monitor PDCCH is set in a constant period (DRX period), and terminal device 400 does not need to monitor PDCCH in other periods.

[0184] Although DRX occurs in both RRC idle and RRC connected states, the DRX (CDRX: connected state DRX) during the RRC connected state is related to fluctuations in latency when the terminal device 400 receives services from the application server 100.

[0185] CDRX has various parameters, and the terminal device 400 performs various intermittent receptions based on combinations of these parameters. Here, for simplicity, it is assumed that the terminal device 400 performs the most basic intermittent reception.

[0186] CDRX includes long DRX and short DRX. In long DRX, the terminal device 400 receives the PDCCH during the connection duration, such as... Figure 9 As shown in the diagram. In a short DRX, the terminal device 400 receives the PDCCH during the short DRX on-time period (not shown).

[0187] If a PDSCH (user data) addressing the terminal device 400 itself is found in the PDCCH received during the connection duration or short drx connection time, the terminal device 400 receives the PDSCH after the PDCCH.

[0188] Terminal device 400 receives PDCCH during the connection duration or short DRX connection time, using either the DRX period or a short DRX period as the cycle. Therefore, terminal device 400 receives PDCCH using either the DRX period or a short DRX period as the cycle.

[0189] The determination of long DRX and short DRX, the reception period (call duration or short DRX call duration), and the period (DRX period or short DRX period) are made by the base station equipment 300 and notified to the terminal equipment 400. As a result, the terminal equipment 400 is able to perform intermittent reception at predetermined time periods and periods.

[0190] Unless otherwise stated, the following descriptions will refer to the long DRX, but the same applies to the short DRX.

[0191] Next, we will refer to Figure 10 and Figure 11 This explains the latency fluctuations caused by CDRX. Figure 10 and Figure 11 This is a diagram used to explain the fluctuations in latency caused by CDRX.

[0192] Figure 10 (a) A diagram illustrating the timing of data transmission (e.g., AR / VR video) by application server 100. Here, it is assumed that application server 100 transmits data in periods T1. Note that, for example, if application server 100 updates the game screen at 60 frames per second, T1 = 1 second / 60 = 16.6 ms.

[0193] Figure 10 (b) A diagram illustrating the intermittent reception timing and PDCCH reception timing of terminal device 400. Here, it is assumed that the DRX period of terminal device 400 is the same as the data transmission period T1 of application server 100 (DRX period = T1 = 16.6ms).

[0194] In this scenario, during the connection duration, terminal device 400 can receive a PDCCH indicating the presence of data addressing its own device, and a PDSCH including data addressing its own device. If the connection duration is, for example, 1 ms, terminal device 400 can enter a 15.6 ms no-reception mode.

[0195] on the other hand, Figure 11 The diagram illustrates a scenario where the DRX cycle of terminal device 400 differs from the data transmission cycle T1 of application server 100.

[0196] Figure 11 (a) similar to Figure 10(a) A diagram illustrating the timing of data transmission (e.g., AR / VR video) sent by application server 100.

[0197] Figure 11 (b) A diagram illustrating the case where the DRX cycle of terminal device 400 is longer than the data transmission cycle T1 of application server 100.

[0198] exist Figure 11 In the example, after the terminal device 400 receives the PDCCH and PDSCH during the first connection duration, the application server 100 sends data until the next connection duration. However, during the data transmission, the terminal device 400 does not perform a receiving operation. Therefore, during the next connection duration, the terminal device 400 receives two PDCCHs and PDSCHs: one corresponding to the data transmitted in non-receive mode, and the other corresponding to the data transmitted during the connection duration.

[0199] As a result, the reception timing of the PDCCH and PDSCH received by the terminal device 400 is not a constant period and appears to fluctuate significantly from the perspective of the terminal device 400. Consequently, the timing of the response returned by the terminal device 400 to such data in the uplink also fluctuates. This causes the latency between the application server 100 and the terminal device 400 to be inconsistent and fluctuate.

[0200] Specifically, the aforementioned CDRX is a setting within a single base station device 300. Therefore, traditionally, CDRX provided by multiple base station devices 300 belonging to each of multiple dedicated networks is set independently for each base station device 300. Furthermore, the settings of the conventional CDRX are closed within the base station device 300 and are not exposed through an API. For example, there is no API in the API of a conventional core network for controlling the settings of the CDRX.

[0201] Therefore, in the communication system 1 according to the first embodiment of this disclosure, among multiple terminal devices 400 that simultaneously receive service provision from the application server 100, the CDRX cycle is made consistent with the data transmission (push) cycle T1 of the application server 100. For example, among multiple terminal devices 400 participating in the same game, the cycle of pushing AR / VR video images of the game is made consistent with the CDRX cycle.

[0202] Note that in addition to the services provided by application server 100 (hereinafter also referred to as the provided services, such as games), terminal device 400 can also perform multiple communications simultaneously. For example, in addition to games, multiple communications can be performed simultaneously. Therefore, base station device 300 cannot determine the DRX period solely for receiving data from the provided services, but it can be considered that in the implementation, an appropriate DRX period value can be set based on the timing of the data arriving at base station device 300 from application server 100. However, a certain amount of learning time is required for base station device 300 to set an appropriate DRX period. Therefore, it can be considered that in many cases, the appropriate DRX period cannot be set depending on the implementation.

[0203] Therefore, in the first embodiment of this disclosure, AF 429 performs CDRX setting processing based on information from application server 100, which notifies base station device 300 of CDRX settings including appropriate DRX periods for service provisioning. As a result, base station device 300 can set appropriate CDRX for terminal device 400 receiving service provisioning.

[0204] Furthermore, in the first embodiment of this disclosure, for example, AF 249 uses the API of AMF 241 to configure CDRX. As a result, CDRX can be configured by NF or AF 249 in a private network.

[0205] Reference Figure 12 Explanation of CDRX settings and processing. Figure 12 This is a diagram illustrating an example of CDRX setting processing performed in a communication system 1 according to a first embodiment of the present disclosure.

[0206] like Figure 12 As shown in the diagram, application server 100 uses the API of AMF 241 to request AMF 241A to set CDRX via AF 249A (step S31). AMF 241A sends the received request to base station device 300A (step S32).

[0207] When the base station device 300A sets up CDRX, the application server 100 sends and receives data with the terminal device 400A via the UPF 221A (step S33).

[0208] Similarly, application server 100 uses the API to request AMF 241B to set CDRX via AF 249B (step S34). AMF 241B sends the received request to base station device 300B (step S35).

[0209] When the base station device 300B sets CDRX, the application server 100 sends and receives data synchronized with the terminal device 400B and the terminal device 400A via the UPF 221B (step S36).

[0210] As described above, the application server 100 notifies the base station device 300 of the CDRX setting via AF 249 and AMF 241, thereby enabling the terminal device 400 to set the CDRX corresponding to the data transmission timing. As a result, the application server 100 can simultaneously send data to multiple terminal devices 400A and 400B.

[0211] Note that here, application server 100 requests CDRX settings, but the present invention is not limited thereto. AF 249 can replace application server 100 in requesting CDRX settings.

[0212] In this scenario, AF 249 receives information from application server 100 and requests CDRX settings based on that information. This information may include, for example, information specifying the terminal device 400 that synchronizes the data transmission cycle with the CDRX cycle, and information about the data transmission cycle (e.g., frame rate). Upon receiving the information, AF 249 uses the API of AMF 241 to notify the CDRX settings pre-configured based on that information.

[0213] In addition to CDRX settings, AF 249 can also push data from application server 100. In other words, AF 249 can be a push notification server.

[0214] Typically, push notification servers are located outside the Virtual Private Network (VPN) that forms the private network. However, when the push notification server performs CDRX configuration as in this embodiment, it is preferable to deploy it within the VPN. This is because, in order to perform CDRX configuration using the AMF 241 API, the push notification server is preferably deployed within the VPN.

[0215] Thus, when AF 249 is configured for CDRX, application server 100 can be deployed inside or outside the VPN. Because AF 249 is configured for CDRX, application server 100 can provide services to terminal device 400 without knowing the CDRX.

[0216] also, Figure 12The illustration shows terminal devices 400A and 400B connected to different private networks, but the invention is not limited thereto. Terminal devices 400A and 400B can also be connected to the same private network. In this case, terminal devices 400A and 400B may belong to the same base station device 300, or they may belong to different base station devices 300.

[0217] also, Figure 12 The illustration shows a scenario where an API for accepting CDRX configuration requests is newly configured in AMF 241, but the invention is not limited thereto. For example, this API could be configured in base station device 300. In this case, AF 249 uses the API instead of AMF 241 to send CDRX configuration requests to base station device 300.

[0218] Here, we will refer to Figure 13 Detailed explanation of CDRX settings and processing. Figure 13 This is a sequence diagram used to explain the flow of CDRX setting processing according to the first embodiment of the present disclosure. Figure 13 The diagram illustrates the setting of CDRX for one of the multiple terminal devices 400.

[0219] exist Figure 13 First, terminal device 400 connects to the wireless network and core network 200 (step S101). At this time, from SMF 242 (see...) Figure 2 Assign IP addresses.

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

[0221] Next, terminal device 400 sends a token and its own ID to application server 110 (step S104). Application server 110 registers the token and ID of terminal device 400.

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

[0223] When a TCP connection is established, application server 100 sends a CDRX configuration request to AF 249 (step S106). As described above, AF 249 can notify AMF 241 of the CDRX configuration request instead of application server 100. In this case, application server 100 requests AF 249 to send a CDRX configuration request by notifying AF 249 of the information required for the CDRX configuration request instead of the CDRX configuration request itself.

[0224] AF 249 uses the API of AMF 241 to notify AMF 241 of the CDRX configuration request (step S107). Upon receiving the request, AMF 241 notifies the base station device 300 of the CDRX configuration request (step S108).

[0225] Upon receiving the request, the base station device 300 sets up CDRX according to the CDRX setting request and enables the terminal device 400 to start CDRX (step S109).

[0226] Application server 100 sends data, such as AR / VR video, to AF 249 (step S110). AF 249 pushes the received data (AR / VR content) to UPF 221 (step S111). UPF 221 pushes the data (AR / VR content) to terminal device 400 (step S112).

[0227] Subsequently, the application server 100 similarly pushes the data to the terminal device 400 at predetermined intervals (e.g., frame rate).

[0228] Next, we will refer to Figure 14 This section describes an example of CDRX configuration request processing for AF 249. Figure 14 This is a sequence diagram illustrating an example of a CDRX setting request processing flow according to an embodiment of the present disclosure.

[0229] AF 249 notifies AMF 241 of a request to configure CDRX including the ID of terminal device 400 (step S201). Examples of the ID of terminal device 400 include IMSI() and SUPI.

[0230] When a CDRX setting request is received, AMF 241 responds to AF 249 with an acknowledgment (step S202).

[0231] As described above, AF 249 sets CDRX in response to a request from application server 100, thereby reducing the latency fluctuation of data (packets) sent from application server 100 to terminal device 400.

[0232] <<4. Second Embodiment>>

[0233] In the CDRX setting process of the first embodiment, even if the period T1 of the data sent by the application server 100 matches the CDRX time period set by the base station device 300, delay fluctuations may still occur. As a second embodiment, a method for suppressing fluctuations occurring under these circumstances will be described. First, reference will be made to... Figure 15 This explains the delay fluctuations that occur under these circumstances. Figure 15 This is a diagram illustrating the fluctuation of delay according to a second embodiment of the present disclosure.

[0234] Figure 15 (a) A diagram illustrating the timing of video data sent from application server 100 arriving at base station device 300.

[0235] Application server 100 sends, for example, video data at a predetermined period T1; however, due to the effects of the aforementioned switch buffers, slight delay fluctuations occur in the video data arriving at base station device 300. For example, ... Figure 15 As shown in the diagram in (a), there is a situation where the time interval T2, which is longer than the period T1, is required from the arrival of video data at the base station device 300 until the arrival of the next video data.

[0236] Although the latency fluctuations caused by the switch buffer, etc., are small, the latency fluctuations may become larger depending on the data reception timing of the terminal device 400.

[0237] For example, such as Figure 15 As illustrated in diagram (b), there is a situation where video data transmitted by base station device 300 is received near the end of the call duration. In this case, due to fluctuations in the arrival timing of the video data, the timing of the video data received by terminal device 400 may deviate to the next call duration. Note that... Figure 15 (b) A diagram illustrating the CDRX timing of terminal device 400 and the receive timing of PDCCH and PDSCH.

[0238] As described above, the latency fluctuations may increase depending on the timing of the intermittent reception by the terminal device 400 and the timing of the transmission of video data from the base station device 300 to the terminal device 400 (in other words, the timing of the arrival of the video data at the base station device 300). More specifically, when the terminal device 400 receives video data in the final period of the reception period (the duration of the connection), the latency fluctuations may increase due to fluctuations in the arrival timing.

[0239] Therefore, as Figure 16 As illustrated in the diagram, in the communication system 1 according to the second embodiment of this disclosure, the terminal device 400 receives video data during a period other than the end of the connection duration, in other words, before a predetermined period. For example, if the terminal device 400 receives video data near the center of the connection duration, then even if there are fluctuations in the arrival time, the terminal device 400 can still receive video data during the connection duration.

[0240] Notice, Figure 16 This is a diagram illustrating the timing of receiving video data in a terminal device 400 according to a second embodiment of the present disclosure. Figure 16 (a) A diagram illustrating the timing of video data sent by application server 100 arriving at base station device 300, and Figure 16 (b) A diagram illustrating the CDRX timing of terminal device 400 and the receive timing of PDCCH and PDSCH.

[0241] As described above, as a method for terminal device 400 to receive video data before a predetermined period of connection duration, a method is considered to adjust the CDRX setting based on the video data received by base station device 300.

[0242] However, not only video data arrives at base station device 300, but also data from other traffic. In the method described above for adjusting CDRX settings, it is necessary to determine whether the data arriving at base station device 300 is video data from application server 100, making this method difficult to implement.

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

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

[0245] Figure 17 (a) A diagram illustrating the timing of data sent by base station equipment 300 arriving at terminal equipment 400. Figure 17 (b) A diagram illustrating the CDRX of terminal device 400. Note that... Figure 17 (b) A diagram illustrating the case where the DRX cycle of terminal device 400 is 3 times the connection duration.

[0246] like Figure 17 As shown in the diagram, base station equipment 300 sets the beginning of the DRX cycle to 0%, sets the beginning of the next DRX cycle to 300%, and notifies AMF 241 of the arrival timing of the data at which position it arrives between 0% and 299% of the end of the DRX cycle. Figure 17 In this case, the range of indication data from 0% to 100% arrived within the call duration period. Furthermore, the range of indication data from 101% to 299% arrived outside the call duration period; in other words, it did not arrive within the call duration.

[0247] Based on the data arrival timing and the CDRX settings of the terminal device 400, the base station device 300 calculates at what percentage the data arrives at the terminal device 400 and notifies the AMF 241 of the calculation result.

[0248] In order for base station device 300 to send this notification to AMF 241, base station device 300 needs to specify data for determining the arrival timing. Base station device 300 cannot specify data using IP addresses, but can use the GTP-tunnel ID to specify data.

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

[0250] The base station equipment 300 will report the arrival time of the data arriving with the specified GTP-tunnel ID to the AMF 241.

[0251] Figure 18 This is a sequence diagram illustrating an example of the flow for handling arrival timing notification according to a second embodiment of the present disclosure. Note that the same reference numerals are applied to... Figure 13 The same treatment applies to sequence diagrams, and their descriptions will be omitted.

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

[0253] In addition, the base station device 300 instructs the terminal device 400 to start CDRX (step S302).

[0254] After sending the test data, AF 249 sends a data arrival timing request, which includes the IP address of the terminal device 400 as the destination and the IP address of its own device as the source, to AMF 241 (step S303).

[0255] When a data arrival timing request is received, AMF 241 specifies the GTP-tunnel ID based on the IP address included in the request, and sends the data arrival timing request including the specified GTP-tunnel ID to base station device 300 (step S304).

[0256] Based on the CDRX settings and the arrival timing of the test data, the base station device 300 sends a data arrival timing report to the AMF 241, including the position (percentage) of the test data arrival in the DRX cycle (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).

[0257] Based on the measurement results, AF 249 adjusts the arrival timing of user data (e.g., AR / VR video data) received from application server 100 to arrive at the terminal device 400 at a desired location within the call duration (e.g., a period before a predetermined time period). AF 249 then transmits the user data to the terminal device 400 via UPF 221 and base station device 300 at the adjusted timing (step S307).

[0258] Note that the AF 249 can preferably adjust the transmit timing so that user data arrives, for example, between 10% and 50% of the DRX cycle (see [link]). Figure 17 By adjusting the transmission timing in this way via AF 249, even if fluctuations occur in the arrival timing of user data, the terminal device 400 can receive user data within the expected connection duration and can further suppress latency fluctuations.

[0259] For a set of periodically sent packets (user data), adjust the sending timing once. In other words, execute the command before sending user data from application server 100. Figure 18 The notification processing is illustrated in the diagram.

[0260] Therefore, in Figure 18 In this configuration, the CDRX setting remains unchanged between the transmission of test data and the transmission of user data, and is kept the same. Alternatively, the CDRX setting can be adjusted each time it is changed. Figure 18 The transmission timing is shown in the diagram.

[0261] Here, although AF 249 adjusts the timing of user data transmission, the present invention is not limited thereto. Base station equipment 300 can adjust CDRX settings so that user data arrives at terminal equipment 400 at the desired timing.

[0262] Figure 19This is a sequence diagram illustrating another example of the flow for handling arrival timing notification according to a second embodiment of the present disclosure. Note that the same reference numerals are applied to... Figure 18 The same treatment applies to sequence diagrams, and their descriptions will be omitted.

[0263] In step S304, the base station device 300 that receives the data arrival timing request adjusts the CDRX setting according to the timing of the test data arrival (step S401).

[0264] The base station equipment 300, having completed the adjustment, notifies AMF 241 of the completion ACK (step S402). Upon receiving the ACK, AMF 241 notifies AF 249 of the completion ACK indicating that the adjustment set by CDRX has been completed (step S403).

[0265] Then, AF 249 sends the user data (e.g., AR / VR video data) received from application server 100 to terminal device 400 via UPF 221 and base station device 300 (step S404).

[0266] As described above, even when the base station device 300 adjusts the CDRX setting, latency fluctuations can be further suppressed.

[0267] Note that for a set of periodically sent packets (user data), the CDRX setting is adjusted once. In other words, this is performed before sending user data from application server 100. Figure 19 The notification processing is illustrated in the diagram.

[0268] Therefore, in Figure 19 In this scenario, we assume that test data and user data are sent simultaneously while maintaining the same transmission cycle. Alternatively, we can adjust the CDRX setting each time the data transmission cycle changes. Additionally, we assume that test data is sent periodically multiple times.

[0269] Traditionally, AF 249 does not explicitly define a means for obtaining information about the CDRX settings of base station equipment 300, and AF 249 has difficulty knowing the timing of CDRX data arrival.

[0270] Therefore, in the second embodiment of this disclosure, AF 249 can request base station device 300 to report the relationship between CDRX settings and data arrival timing via the API of core network 200. As a result, the application side can more accurately adjust the latency between multiple terminal devices 400.

[0271] In addition, traditionally, because base station equipment 300 has difficulty using IP addresses to determine the data sent from AF 249, it is difficult for base station equipment 300 to know at what time the data arrives from AF 249.

[0272] Therefore, in the second embodiment of this disclosure, AMF 241 enables base station device 300 to specify the data to be transmitted by AF 249 using GTP-tunnel ID. As a result, base station device 300 can know the arrival timing of the data transmitted from AF 249 and adjust the CDRX setting according to the arrival timing. Therefore, fluctuations in the latency of terminal device 400 can be further suppressed.

[0273] <<5. Third Embodiment>>

[0274] In the CDRX setting process of the first embodiment, the CDRX setting (cycle) can be made consistent among multiple terminal devices 400, but the timing of starting CDRX on multiple terminal devices 400 is not taken into account. Therefore, the timing of starting CDRX on multiple terminal devices 400 may be offset.

[0275] Here, we will refer to Figure 20 This indicates the timing for starting CDRX. Figure 20 This is a diagram used to illustrate the start timing of CDRX.

[0276] exist Figure 20 During time period T11, as shown in the diagram, terminal device 400 monitors the PDCCH in subframe units. If no transmit / receive data is addressed within a specific time period (a specific number of subframes), terminal device 400 initiates CDRX.

[0277] More specifically, terminal device 400 monitors the PDCCH of a subframe, starts a drx inactive timer when there is no PDSCH addressed to itself, and measures the period (subframe number) during which there is no PDSCH addressed to itself. Alternatively, terminal device 400 can monitor the PDCCH of a subframe and begin measurement after the PDSCH is no longer scheduled. When the measurement period exceeds a predetermined period, terminal device 400 switches to intermittent receive mode and starts CDRX.

[0278] exist Figure 20 In the example, if there is no PDSCH addressed to terminal device 400 in the three subframes monitored in time period T11, terminal device 400 performs CDRX in the next time period T12. Figure 20 During this process, the terminal device 400 alternately repeats the reception and reception stop of PDCCH every two subframes, receives PDCCH during the on-time duration, and checks whether there is a PDSCH addressed to the terminal device 400 itself.

[0279] Here, terminal device 400 executes multiple applications. Therefore, multiple sessions are established between terminal device 400 and core network 200, and traffic may occur between terminal device 400 and devices other than application server 100.

[0280] Therefore, multiple terminal devices 400 receiving the same service from the same application server 100 do not necessarily start CDRX at the same time. For example, in Figure 20 During time period T11, terminal devices 400 that receive data from devices other than application server 100 do not start CDRX from time period T12. As mentioned above, in a conventional communication system, it is difficult to make the CDRX start timing consistent with multiple terminal devices 400.

[0281] When the CDRX start timings differ, for example, there might be a situation where one terminal device 400 performs CDRX while other terminal devices 400 do not. In this case, the packet reception timing may vary between the terminal device 400 performing CDRX and the terminal device 400 not performing CDRX.

[0282] For example, in terminal device 400 that continuously receives PDCCH and PDSCH without performing CDRX, the variation in packet reception timing is small. On the other hand, terminal device 400 that performs CDRX and performs intermittent reception exhibits a larger variation in packet reception timing.

[0283] As described above, by setting the CDRX cycle, the CDRX cycles of multiple terminal devices 400 can be made consistent. However, when the timing of starting CDRX differs among the multiple terminal devices 400, the degree of latency fluctuation may vary significantly between the terminal device 400 that starts CDRX first and the terminal device 400 that starts CDRX subsequently.

[0284] For example, in Figure 20 Even if a packet addressed to terminal device 400 exists at time T10, terminal device 400 that started CDRX at time T10 cannot receive the packet until the next connection duration. On the other hand, terminal device 400 that has not started CDRX at time T10 can receive packets addressed to terminal device 400 in the next subframe after time T10.

[0285] As mentioned above, when the timing of the CDRX start is different, even if the CDRX period is the same, the timing of multiple terminal devices 400 receiving packets may be different from each other, and the impact of latency fluctuations may become greater.

[0286] As described above, when multiple applications are running on terminal device 400, applications affected by latency fluctuations (applications provided by application server 100) are separated from other applications. By separating applications, the CDRX timing of multiple terminal devices 400 receiving data from specific applications is made consistent.

[0287] For example, in 4G or 5G LTE, a terminal device 400 can use multiple component carriers (CCs). Additionally, in 5G, multiple bandwidth portions (BWPs) can be used on a single component carrier. Therefore, the terminal device 400 uses different CCs or BWPs for each application.

[0288] As a result, CDRX for a specific CC or BWP can be started based on instructions from base station device 300, rather than starting CDRX for a specific CC or BWP based on actual traffic generation timing. That is, base station device 300 determines the CC or BPW to be used for communication with application server 100, and performs CDRX settings, including start or end timing, within that CC or BPW. Note that CDRX settings are performed, for example, based on instructions from application server 100 or AF 249. Application server 100 or AF 249 uses an API to instruct base station device 300 via AMF 241.

[0289] For example, at the start of service provisioning, AF 249 or application server 100 requests base station equipment 300 to start CDRX, so that multiple terminal devices 400 simultaneously receiving services start CDRX at the same time. This request is made to each of the multiple core networks 200 to which the multiple terminal devices 400 are connected.

[0290] More specifically, a new API is set up in AMF 241 of core network 200, and AF 249 uses this API to request CDRX to initiate.

[0291] Note that here, it is assumed that the multiple core networks 200 to which the multiple terminal devices 400 are connected are in frame synchronization with each other. That is, it is assumed that not only are multiple base station devices 300 belonging to the same dedicated network in frame synchronization, but base station devices 300 belonging to different dedicated networks are also in frame synchronization.

[0292] In cellular networks, a frame typically consists of 10 ms frames. This frame is assigned a number called the system frame number. The maximum system frame number is 1024, and the next frame after a frame with system frame number 1024 is assigned a system frame number of 1.

[0293] When frame synchronization is achieved, multiple base station devices 300 communicate using frames assigned the same system frame number at the same timing. Therefore, if frame synchronization is achieved between multiple base stations, AF 249 specifies from which subframe CDRX begins, so that multiple base station devices 300 can set CDRX to start CDRX at the same timing.

[0294] Normally, frame synchronization is not performed between base station devices 300 belonging to different dedicated networks. However, by using existing technology, frame synchronization can be performed between base station devices 300 belonging to different dedicated networks.

[0295] Reference Figure 21 and Figure 22 This section illustrates the processing of the start timing of the AF 249 instruction CDRX (hereinafter also referred to as CDRX synchronization processing). Figure 21 and Figure 22 This is an illustration of an example of the CDRX synchronization process according to a third embodiment of the present disclosure.

[0296] like Figure 21 As illustrated in the diagram, AF 249A, upon receiving a notification from application server 100 that a service provision (e.g., a game) has started, requests AMF 241A to start CDRX using an API (step S41). Alternatively, for example, AMF 241A calculates the CDRX start timing according to a predetermined process based on the game start timing notified by application server 100, and requests the start of CDRX. AF 249A can notify AMF 241A of the CDRX start request based on the CDRX start timing, or it can notify AMF 241A of the CDRX start request including the CDRX start timing.

[0297] Upon receiving the CDRX start request, AMF 241A notifies base station device 300A to start CDRX at the CDRX start timer (step S42). When CDRX is received, base station device 300A configures terminal device 400A to start CDRX at the CDRX start timer.

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

[0299] Similarly, upon receiving a notification from application server 100 that a service provision (e.g., a game) has started, AF 249B uses an API to request AMF 241B to start CDRX (step S44). Alternatively, for example, AMF 241B calculates the start time of CDRX according to a predetermined process based on the game start time notified by application server 100, and requests the start of CDRX. AF 249B can notify AMF 241B of the CDRX start request based on the CDRX start time, or it can notify AMF 241B of the CDRX start request including the CDRX start time.

[0300] Upon receiving the CDRX start request, AMF 241B notifies base station device 300B to start CDRX at the CDRX start timer (step S45). In response, base station device 300B configures terminal device 400B to start CDRX at the CDRX start timer.

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

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

[0303] Note that AF 249 can include the settings for the CDRX period mentioned above in the CDRX start request. That is, AF 249 can set both the CDRX start timing and the CDRX period by requesting base station equipment 300 via AMF 241.

[0304] Next, we will refer to Figure 22 This explains the timing settings for AF 249 to end CDRX.

[0305] like Figure 22 As shown in the diagram, AF 249A, which receives a notification from application server 100 that a service provision (e.g., a game) has ended, uses an API request AMF 241A to end CDRX (step S47).

[0306] Upon receiving the CDRX termination request, AMF 241B notifies base station device 300B to terminate CDRX at the CDRX termination timer (step S48). In response, base station device 300A configures terminal device 400B to terminate CDRX at the CDRX termination timer.

[0307] Similarly, AF 249B, which receives a notification from application server 100 that a service provision (e.g., a game) has ended, uses an API request AMF 241B to end CDRX (step S49).

[0308] Upon receiving the CDRX termination request, AMF 241B notifies base station device 300B to terminate CDRX at the CDRX termination timer (step S45). In response, base station device 300B configures terminal device 400B to terminate CDRX at the CDRX termination timer.

[0309] As a result, terminal devices 400A and 400B are able to terminate CDRX at the same CDRX end timer.

[0310] As described above, when AF 249 determines to start CDRX timing, it also instructs AF 249 to end CDRX timing. As a result, when the service provision of application server 100 is terminated, base station equipment 300 can return to normal communication.

[0311] As described above, AF 249 can use the API to control the start and end timings of CDRX. As a result, application server 100 can deliver data (e.g., AR / VR video data) to multiple terminal devices 400 belonging to different private networks while suppressing latency fluctuations.

[0312] In addition, even in the uplink, the latency fluctuations of data from multiple terminal devices 400 belonging to different private networks to the application server 100 can be further suppressed.

[0313] As a result, multiple terminal devices belonging to different dedicated networks can operate collaboratively.

[0314] <<6. Fourth Embodiment>>

[0315] In the first to third embodiments, the method of setting CDRX by AF 249 is described as an example, mainly in the case of long DRX, but CDRX includes both long DRX and short DRX. Compared with long DRX, short DRX has a shorter period of intermittent monitoring of PDCCH (CDRX period). When CDRX is started, terminal device 400 first performs short DRX, and if no transmit / receive packets of terminal device 400 itself are addressed within a predetermined period of time, it switches from short DRX to long DRX.

[0316] As mentioned above, in order to make CDRX consistent across multiple terminal devices 400, it is necessary not only to make the CDRX timing consistent at the start, but also to make the timing of the short DRX and long DRX consistent, in other words, to make the timing of switching from short DRX to long DRX consistent.

[0317] Therefore, in the fourth embodiment of this disclosure, after CDRX is started by CDRX start timing by instruction AF 249, AF 249 uses API to switch between short DRX and long DRX.

[0318] Reference Figure 23 An example illustrating the switching process of the AF 249 instruction CDRX (hereinafter also referred to as the switching process). Figure 23 This is a diagram illustrating an example of the switching process according to a fourth embodiment of the present disclosure.

[0319] like Figure 23 As illustrated in the diagram, based on a notification from application server 100, AF 249A requests AMF 241A to switch from short DRX to long DRX during the switching time using an API (step S51). Notifications from application server 100 may include, for example, notifications to interrupt data transmission for a certain period or notifications to reduce the frame rate.

[0320] When a handover request is received, AMF 241A notifies base station device 300A to switch CDRX from short DRX to long DRX during the handover timing (step S52). Upon receiving this information, base station device 300A configures terminal device 400A to switch from short DRX to long DRX during the handover timing.

[0321] Similarly, based on instructions from application server 100, AF 249B uses the API to request AMF 241B to switch from short DRX to long DRX during the switching time (step S53). Notifications from application server 100 may include, for example, notifications to interrupt data transmission for a certain period of time or notifications to reduce the frame rate.

[0322] When a handover request is received, AMF 241B notifies base station device 300B to switch CDRX from short DRX to long DRX during the handover timing (step S53). Upon receiving this instruction, base station device 300B configures terminal device 400B to switch from short DRX to long DRX during the handover timing.

[0323] As described above, AF 249 can use an API to control the timing of switching between short and long DRX. As a result, application server 100 is able to deliver data (e.g., AR / VR video data) to multiple terminal devices 400 belonging to different private networks while suppressing latency fluctuations.

[0324] In addition, even in the uplink, the latency fluctuations of data from multiple terminal devices 400 belonging to different private networks to the application server 100 can be further suppressed.

[0325] As a result, multiple terminal devices belonging to different dedicated networks can operate collaboratively.

[0326] Here, AF 249 performs handover control between short DRX and long DRX based on notifications from application server 100, but the invention is not limited thereto. For example, AF 249 can monitor data addressed to terminal device 400 and perform handover control if no data is addressed to terminal device 400 for a period of time.

[0327] <<7. Variations>>

[0328] The processing according to each of the above embodiments can also be carried out in various different forms (variations) in each of the above embodiments.

[0329] In the above embodiment, AF 249 performs CDRX-related control (e.g., CDRX cycle setting), but the invention is not limited thereto. For example, an entity located outside the private network can perform CDRX-related control. This entity can be application server 100, or it can be an entity different from application server 100.

[0330] Because AF 249 is deployed within a private network, it can directly access the API of AMF 241, which belongs to the same private network. However, for entities deployed outside the private network that use the CDRX command AMF 241, the entity cannot directly connect to the AMF 241 API. Therefore, in this case, the entity deployed outside the private network can connect to the AMF 241 API, for example, via a gateway connected to the API of NEF 245.

[0331] Furthermore, the control device for controlling the terminal device 400, base station device 300, or information processing device 260 in this embodiment can be implemented using a dedicated computer system or a general-purpose computer system.

[0332] For example, a program for performing the above operations is stored on and distributed on a computer-readable recording medium such as an optical disc, semiconductor memory, magnetic tape, or floppy disk. Then, for example, the program is installed in a computer, and the above processing is performed to constitute a control device. In this case, the control device may be a device external to the terminal device 400, base station device 300, or information processing device 260 (e.g., a personal computer). Alternatively, the control device may be an internal device of the terminal device 400, base station device 300, or information processing device 260 (e.g., control unit 450, control unit 340, or control unit 263).

[0333] Additionally, the communication program can be stored on a disk device included in a server on a network such as the Internet, allowing it to be downloaded to the computer. Furthermore, the above functionality can be achieved through the collaboration of an operating system (OS) and application software. In this case, components other than the OS can be stored on media and distributed, or components other than the OS can be stored on a server device and downloaded to the computer.

[0334] In the various processes described in the above embodiments, all or part of the processes described as automatically can be performed manually, or all or part of the processes described as manually can be performed automatically using known methods. Furthermore, unless otherwise stated, the processes, specific names, and information including various data and parameters illustrated in the specification and drawings can be arbitrarily changed. For example, the various types of information illustrated in each figure are not limited to the information illustrated in the figures.

[0335] Furthermore, each component of each device shown in the diagram is a functional concept and may not necessarily be physically configured as depicted in the diagram. That is, the specific form of distribution and integration of each device is not limited to the form shown in the diagram. Depending on various loads, usage conditions, etc., all or part of it can be functionally or physically distributed and integrated in any unit.

[0336] Furthermore, the above embodiments can be appropriately combined in areas where the processing content does not contradict each other. Additionally, the order of each step illustrated in the sequence diagram or flowchart of this embodiment can be appropriately changed.

[0337] Furthermore, this embodiment can be implemented as any configuration that constitutes a device or system, such as a processor as a system large-scale integration (LSI), a module using multiple processors, a unit using multiple modules, a collection obtained by further adding other functions to the unit, etc. (i.e., a configuration of a part of a device).

[0338] Note that in this embodiment, a system means a collection of multiple components (devices, modules (parts), etc.), and it is not important whether all components are housed in the same housing. For example, multiple devices housed in separate housings and connected via a network, or a single device in which multiple modules are housed in one housing, are both systems.

[0339] Furthermore, for example, this embodiment may employ a cloud computing configuration in which one function is shared and processed collaboratively by multiple devices via a network.

[0340] (Effect)

[0341] The information processing apparatus 260 (AF 249 and AMF 241) of this disclosure includes a control unit 263. The control unit 263 acquires information from a device (application server 100) that provides application functions to the terminal device 400. Based on the acquired information, the control unit 263 uses an API to notify the base station device 300 communicating with the terminal device 400 of configuration information regarding the intermittent reception of the terminal device 400.

[0342] As a result, fluctuations in latency can be further suppressed.

[0343] Additionally, the control unit 263 can notify the base station device 300 of configuration information via a device (AMF 241) that belongs to the core network 200 to which the base station device 300 is connected and has NF functionality.

[0344] As a result, AF 249 can suppress delay fluctuations.

[0345] In addition, the information processing device 260 may have functions related to access control.

[0346] As a result, delay fluctuations can be suppressed using AMF 241.

[0347] In addition, the configuration information may include periodic information related to the reception period of intermittent reception.

[0348] As a result, the information processing device 260 can set the reception period for intermittent reception.

[0349] In addition, the configuration information may include start timing information related to the timing of the start of intermittent reception.

[0350] As a result, the information processing device 260 can set the start time for intermittent reception.

[0351] In addition, the configuration information may include end timing information related to the timing of ending intermittent reception.

[0352] As a result, the information processing device 260 can set the end time of intermittent reception.

[0353] Additionally, the configuration information may include the switching timing related to the timing of the reception period (short DRX / long DRX) of the switching intermittent reception.

[0354] As a result, the information processing device 260 can set a timing for switching the reception period of intermittent reception.

[0355] In addition, the control unit 263 can receive reception timing information from the base station device 300 during the intermittent reception period, which is related to the reception timing of the terminal device 400 receiving data sent by the device (application server 100).

[0356] As a result, the data transmission timing can be adjusted so that the terminal device 400 receives data at the desired reception timing.

[0357] In addition, the control unit 263 can send test data to the base station equipment 300 for measuring the reception timing.

[0358] Therefore, the receiving timing can be measured based on the test data.

[0359] In addition, the control unit 263 can adjust the transmission timing based on the reception timing information, so that the terminal device 400 receives data before the predetermined time period during the reception period and transmits the data.

[0360] As a result, terminal device 400 can receive data at the expected time.

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

[0362] As a result, the base station equipment 300 can use the test data to adjust the reception period of intermittent reception.

[0363] In addition, the information obtained from the device (application server 100) may include information about multiple terminal devices 400 connected to different core networks, and the control unit 263 may notify the base station device 300 communicating with the terminal device 400 of the configuration information of the terminal device 400 connected to the core network 200 to which its own device belongs.

[0364] As a result, multiple terminal devices 400 belonging to different core networks 200 can operate collaboratively.

[0365] Furthermore, the information processing apparatus (application server 100) according to this disclosure includes a control unit. The control unit notifies entities (AF 249 and AMF 241) belonging to the core network 200 to which the terminal device 400 is connected of information relating to the terminal device 400 that provides application functions. The entities (AF 249 and AMF 241) use this information to configure the intermittent reception of the terminal device 400.

[0366] As a result, fluctuations in latency can be suppressed.

[0367] Furthermore, the base station device 300 of this disclosure includes a control unit 340. The control unit 340 receives configuration information, which is sent from entities (AF 249 and AMF 241) belonging to the core network 200 based on information from a device (application server 100) providing application functions to the terminal device 400, and is related to the intermittent reception of the terminal device. Based on the configuration information, the control unit 340 configures the intermittent reception of the terminal device 400.

[0368] As a result, fluctuations in latency can be suppressed.

[0369] Furthermore, the communication method disclosed herein obtains information from a device (application server 100) that provides application functions to the terminal device 400, and based on that information, notifies the base station device 300 communicating with the terminal device 400 of the setting information regarding the intermittent reception of the terminal device 400 by using an API.

[0370] As a result, fluctuations in latency can be suppressed.

[0371] Furthermore, the communication system 1 disclosed herein includes the following: a base station device 300 communicating with the terminal device 400; an information processing device 260 (AF 249 and AMF 241); and a device providing application functions (application server 100), wherein the information processing device 260 includes a control unit that obtains information from the device providing application functions and, based on that information, uses an API to notify the base station device 300 of setting information regarding the intermittent reception of the terminal device 400.

[0372] As a result, fluctuations in latency can be suppressed.

[0373] Although embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the above embodiments, and various modifications can be made without departing from the spirit of the present disclosure. Furthermore, components of different embodiments and variations can be appropriately combined.

[0374] Furthermore, the effects described in this specification are merely examples and are not limited, and other effects may be provided.

[0375] Note that this technology can also have the following configuration.

[0376] (1) An information processing device, comprising:

[0377] Control unit, the control unit being configured to:

[0378] Information is obtained from devices that provide application functions to terminal devices; and

[0379] Based on the information, the application programming interface (API) is used to notify the base station equipment communicating with the terminal device of the configuration information regarding the intermittent reception of the terminal device.

[0380] (2) The information processing device according to (1), wherein

[0381] The control unit notifies the base station device of the setting information via a device belonging to the core network to which the base station device is connected and having network functionality (NF).

[0382] (3) The information processing device according to (1), wherein

[0383] The information processing equipment has functions related to access control.

[0384] (4) The information processing device according to any one of (1) to (3), wherein

[0385] The setting information includes periodic information regarding the reception period of the intermittent reception.

[0386] (5) The information processing device according to any one of (1) to (4), wherein

[0387] The configuration information includes start timing information regarding the timing of initiating the intermittent reception.

[0388] (6) The information processing device according to any one of (1) to (5), wherein

[0389] The setting information includes end timing information regarding the timing of the end of the intermittent reception.

[0390] (7) The information processing device according to any one of (1) to (6), wherein

[0391] The setting information includes switching timing information regarding the timing of switching the reception period of the intermittent reception.

[0392] (8) The information processing device according to any one of (1) to (7), wherein

[0393] During the intermittent reception period, the control unit receives reception timing information from the base station device related to the reception timing of the data sent by the terminal device.

[0394] (9) The information processing device according to (8), wherein

[0395] The control unit sends test data to the base station equipment for measuring the reception timing.

[0396] (10) The information processing device according to (8) or (9), wherein

[0397] The control unit adjusts the transmission timing based on the reception timing information, so that the terminal device receives the data and transmits the data before a predetermined time period during the reception period.

[0398] (11) The information processing device according to any one of (1) to (7), wherein

[0399] The control unit is configured to:

[0400] The base station device is requested to adjust the reception period so that the data transmitted by the device is received by the terminal device earlier than a predetermined period during the intermittent reception period.

[0401] Send test data for adjusting the received period.

[0402] (12) The information processing device according to any one of (1) to (11), wherein

[0403] The information includes information about multiple terminal devices connected to different core networks, and

[0404] The control unit notifies the base station device communicating with the terminal device of the configuration information of the terminal device connected to the core network to which the terminal device belongs.

[0405] (13) An information processing device, comprising:

[0406] A control unit, configured to notify an entity belonging to the core network to which the terminal device is connected of information relating to a terminal device providing application functionality, wherein...

[0407] The entity uses the information to set the intermittent reception of the terminal device.

[0408] (14) A base station device, comprising:

[0409] Control unit, the control unit being configured to:

[0410] Receive configuration information sent by an entity belonging to the core network based on information from a device providing application functions to the terminal device, the configuration information being related to the intermittent reception of the terminal device; and

[0411] Based on the aforementioned settings, the intermittent reception is configured for the terminal device.

[0412] (15) A communication method, comprising:

[0413] Information is obtained from devices that provide application functions to terminal devices; and

[0414] Based on the information, the application programming interface (API) is used to notify the base station equipment communicating with the terminal device of the configuration information regarding the intermittent reception of the terminal device.

[0415] (16) A communication system, comprising:

[0416] Base station equipment that communicates with terminal devices;

[0417] Information processing equipment; and

[0418] Devices that provide application functionality, among which

[0419] The information processing device includes:

[0420] Control unit, the control unit being configured to:

[0421] Information is obtained from the device providing the application functionality; and

[0422] Based on the information, the application programming interface (API) is used to notify the base station equipment of the intermittent reception settings of the terminal equipment.

[0423] List of reference numerals

[0424] 1. Communication System

[0425] 100 Application Server (Information Processing Equipment)

[0426] 200, 200A, 200B core networks

[0427] 241 AMF

[0428] 249 AF

[0429] 300, 300A, 300B base station equipment

[0430] 400, 400A, 400B terminal equipment

Claims

1. An information processing device, comprising: Control unit, the control unit being configured to: Information is obtained from a device that provides application functionality to multiple terminal devices, the information including information about the multiple terminal devices used for synchronously receiving data from the device; and Based on the information, an application programming interface (API) is used to notify the base station device communicating with the corresponding terminal device among the plurality of terminal devices of the setting information of the intermittent reception of the corresponding terminal device. The setting information is used to set the reception period of the intermittent reception of the corresponding terminal device so that the reception period of the intermittent reception of the corresponding terminal device is consistent with the period of data transmission of the device.

2. The information processing device according to claim 1, wherein... The control unit notifies the base station device of the setting information via a device belonging to the core network to which the base station device is connected and having network functionality (NF).

3. The information processing device according to claim 1, wherein... The information processing equipment has functions related to access control.

4. The information processing device according to claim 1, wherein... The setting information includes periodic information regarding the reception period of the intermittent reception.

5. The information processing device according to claim 1, wherein... The configuration information includes start timing information regarding the timing of initiating the intermittent reception.

6. The information processing device according to claim 1, wherein... The setting information includes end timing information regarding the timing of the end of the intermittent reception.

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

8. The information processing device according to claim 1, wherein... During the intermittent reception period, the control unit receives reception timing information from the base station device related to the reception timing of the data sent by the terminal device.

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

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

11. The information processing device according to claim 1, wherein The control unit is configured to: The base station equipment is requested to adjust the reception period of the intermittent reception so that the data transmitted by the equipment is received by the terminal equipment earlier than a predetermined period during the intermittent reception period. Send test data for adjusting the received period.

12. The information processing device according to claim 1, wherein The multiple terminal devices are connected to different core networks.

13. A base station device, comprising: Control unit, the control unit being configured to: Based on information from a device that provides application functions to multiple terminal devices, configuration information sent by an entity belonging to the core network is received. The information includes information about the multiple terminal devices for synchronously receiving data from the device, and the configuration information is used to set the reception period of the intermittent reception of a terminal device communicating with the base station device so that the reception period of the intermittent reception of the terminal device is consistent with the period of data transmission of the device. and Based on the aforementioned settings, the intermittent reception is configured for the terminal device.

14. A communication method, comprising: Information is obtained from a device that provides application functionality to multiple terminal devices, the information including information about the multiple terminal devices used for synchronously receiving data from the device; and Based on the information, an application programming interface (API) is used to notify the base station device communicating with the corresponding terminal device among the plurality of terminal devices of the setting information of the intermittent reception of the corresponding terminal device. The setting information is used to set the reception period of the intermittent reception of the corresponding terminal device so that the reception period of the intermittent reception of the corresponding terminal device is consistent with the period of data transmission of the device.

15. A communication system, comprising: Base station equipment that communicates with terminal devices; Information processing equipment; as well as A device that provides application functions to multiple terminal devices, among which The information processing device includes: Control unit, the control unit being configured to: Information is obtained from the device providing the application functionality, including information about the plurality of terminal devices used to synchronously receive data from the device; and Based on the information, the application programming interface (API) is used to notify the base station device of the intermittent reception settings of the terminal device. The settings are used to set the reception period of the intermittent reception of the terminal device communicating with the base station device, so that the reception period of the intermittent reception of the terminal device is consistent with the period of data transmission of the device.

Images