Information processing device, information processing method, communication system and entity

Abstract

Provided is an information processing device having a push notification server function, the information processing device enabling an exchange of messages and the like by a simple procedure. The information processing device of the present disclosure has a function for performing push notification. The information processing device with the function for performing push notification is disposed in a local area network (LAN) including a base station device to which a terminal device is connected and a core network, and performs push notification with respect to the terminal device on the basis of a connection-less protocol.

Description

[Technical Field]

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

[0002] An application is used that exchanges messages between multiple terminal devices. In such an application, messages are exchanged via a service provider's server. Specifically, a message from a terminal device is forwarded to the service provider's server. The service provider's server then transmits the message to another terminal device. This allows messages to be exchanged between the terminal devices. If one terminal device disconnects from the network, messages addressed to that terminal device are stored in the service provider's server. When the terminal device connects to the network, the stored messages are transmitted from the service provider's server. The message transmission method used is a pull method or a push method.

[0003] In the pull method, a terminal connected to a network inquires with a service provider's server about the presence of a message addressed to it. However, since the message is sent after waiting for an inquiry from the terminal, there is a problem of delay.

[0004] In contrast, the push method is a method in which a server that holds messages sends messages to terminal devices connected to a network. Compared to the pull method, this method can reduce delays in message transmission. In addition to the service provider's server, the push method also uses a push notification server that holds messages addressed to terminal devices that have disconnected from the network. This push notification server is located on the same public network (e.g., the Internet) as the service provider's server. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] US Patent Application Publication No. 2016 / 241605 Summary of the Invention [Problem to be solved by the invention]

[0006] However, in the above-described conventional technology, the terminal device needs to exchange messages with a push notification server located on a public network, which causes a problem of complicated procedures.

[0007] Therefore, the present disclosure proposes an information processing device, an information processing method, a communication system, and an entity that have the functionality of a push notification server that allows messages to be exchanged through simple procedures. [Means for solving the problem]

[0008] According to the present disclosure, an information processing device is provided that is arranged in a local area network (LAN) having a base station device and a core network to which a terminal device is connected, and that has the function of sending push notifications to the terminal device based on a connectionless protocol. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram for explaining an overview of a communication system according to an embodiment of the present disclosure. [Figure 2] FIG. 1 is a diagram illustrating an example of 5G architecture. [Figure 3] FIG. 1 is a diagram illustrating an example of 4G architecture. [Figure 4] FIG. 2 is a block diagram illustrating a configuration example of a base station device according to an embodiment of the present disclosure. [Figure 5] FIG. 1 is a block diagram illustrating a configuration example of a terminal device according to an embodiment of the present disclosure. [Figure 6]FIG. 1 is a block diagram illustrating a configuration example of an information processing device according to an embodiment of the present disclosure. [Figure 7] FIG. 1 is a simplified diagram illustrating a communication system according to an embodiment of the present disclosure. [Figure 8] FIG. 4 is a sequence diagram showing a procedure of a push communication process according to the first embodiment of the present disclosure. [Figure 9] FIG. 10 is a sequence diagram showing a procedure of a push communication process according to a second embodiment of the present disclosure. [Figure 10] FIG. 10 is a diagram illustrating a connection cycle and a connection period to a network according to a third embodiment of the present disclosure. [Figure 11] FIG. 11 is a sequence diagram showing a procedure of a push communication process according to a third embodiment of the present disclosure. [Figure 12] FIG. 13 is a sequence diagram showing a procedure of a push communication process according to a fourth embodiment of the present disclosure. [Figure 13] FIG. 13 is a sequence diagram showing another procedure of the push communication process according to the fourth embodiment of the present disclosure. [Figure 14] FIG. 13 is a sequence diagram showing another procedure of the push communication process according to the fourth embodiment of the present disclosure. [Figure 15] FIG. 13 is a sequence diagram showing a procedure of a push communication process according to a fifth embodiment of the present disclosure. [Figure 16] FIG. 13 is a sequence diagram showing another procedure of the push communication process according to the fifth embodiment of the present disclosure. [Figure 17] FIG. 10 is a simplified diagram illustrating a communication system according to a sixth embodiment of the present disclosure. [Figure 18] FIG. 13 is a diagram showing correspondence between a terminal device and a UPF according to a sixth embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0035] As mentioned above, 5GC / NGC200 provides an interface for transmitting information and controlling functions via an application programming interface (API) called a service-based interface.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0067] The modulation unit 312b modulates the coded bits output from the coding unit 312a using a predetermined modulation method such as BPSK, QPSK, 16QAM, 64QAM, or 256QAM. In this case, the signal points on the constellation do not necessarily have to be equidistant. The constellation may be a non-uniform constellation.

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

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

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

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

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

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

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

[0075] The terminal device 400 may simultaneously connect to multiple base station devices or multiple cells to perform communication. For example, if one base station device can provide multiple cells, the terminal device 400 can perform carrier aggregation by using one cell as a pCell and using another cell as an sCell. Furthermore, if multiple base station devices 300 can each provide one or multiple cells, the terminal device 400 can realize DC (Dual Connectivity) by using one or multiple cells managed by one base station device (MN (e.g., MeNB or MgNB)) as a pCell, or a pCell and sCell(s), and using one or multiple cells managed by the other base station device (SN (e.g., SeNB or SgNB)) as a pCell (PSCell), or a pCell (PSCell) and sCell(s). DC may also be referred to as MC (Multi Connectivity).

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

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

[0078] The communication unit 410 is a signal processing unit for wireless communication with other wireless communication devices (for example, the base station device 300 and other terminal devices 400). Control unit 450 The communication unit 410 may be a wireless transceiver that supports one or more wireless access methods. 410 The communication unit 410 supports both NR and LTE. In addition to NR and LTE, the communication unit 410 may also support W-CDMA and cdma2000. The communication unit 410 may also support communication using NOMA.

[0079] The communication unit 410 includes a reception processing unit 411, a transmission processing unit 412, and an antenna 413. The communication unit 410 may include a plurality of reception processing units 411, a plurality of transmission processing units 412, and a plurality of antennas 413. 413 The base station device 300 includes a communication unit 310, a reception processing unit 311, a transmission processing unit 312, and an antenna 313 is the same as:

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

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

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

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

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

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

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

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

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

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

[0090] <<3. Overview of the proposed system>> An overview of a communication system 1 according to an embodiment of the present disclosure will be described with reference to Fig. 7. Fig. 7 is a simplified diagram illustrating a communication system according to an embodiment of the present disclosure.

[0091] The communication system 1 in Fig. 7 includes a local area network (LAN). In Fig. 7, a virtual private network 500 is used as an example of this LAN. Here, a private network corresponds to the non-public network described above and is a private network that differs from public networks such as the Internet. For example, it is a network that targets a specific area such as a factory and is not open to the public. A virtual private network is also a network that extends across public networks and the like. The virtual private network 500 includes a wireless network including a terminal device 400A and a base station device 300, a core network 200, and a router 510.

[0092] The core network 200 in FIG. 7 includes an AMF 241, an SMF 242, a UPF 221, and an information processing device 260. The information processing device 260 corresponds to the information processing device 260 with the push notification function described in FIG. 1. Hereinafter, the information processing device 260 will be referred to as a push notification server 260. The push notification server 260 can store messages sent to itself in the storage unit 262 described in FIG. 6. FIG. 7 illustrates an example in which the push notification server 260 is located in the core network 200. The push notification server 260 can also be located outside the core network 200. In either case, the push notification server 260 is located within the virtual private network 500. A router 510 connects the virtual private network 500 and the Internet 100.

[0093] The application server 110 described in FIG. 1 is connected to the Internet 100. A server of a service provider can be applied to this application server 110. Furthermore, an application for exchanging messages between a plurality of terminal devices connected to the network is assumed as the application of the application server 110. In FIG. 6, it is assumed that messages are exchanged between terminal device 400A and terminal device 400B. Such messages are called instant messages.

[0094] The procedure for sending and receiving a message in the communication system 1 of Fig. 7 will be described. Assume that a message is sent from terminal device 400B to terminal device 400A. The user of terminal device 400A sends information such as his or her email address and phone number to register in the application of application server 110. The application of application server 110 manages terminal device 400A by an identifier (ID) linked to this email address, etc.

[0095] First, the terminal device 400A registers with the push notification server 260. In response, the terminal device 400A receives a token from the push notification server 260. This token is used to identify the terminal device 400A when sending a message.

[0096] Next, the user of terminal device 400B generates a message and sends it to the ID of terminal device 400A. This message is stored in the application server 110. Next, an application on the application server 110 sends the stored message from terminal device 400B to the push notification server 260. This message can be sent based on the Transmission Control Protocol (TCP). A TCP connection is set up between the application server 110 and the push notification server 260. This TCP connection allows a message to be transmitted from the application server 110 on the Internet 100 to the push notification server 260 in the virtual private network 500 via the router 510.

[0097] The terminal device 400A Virtual Private Network If the terminal device 400A is connected to the wireless network of the virtual private network 500 and the core network 200, the push notification server 260 immediately sends a message to the terminal device 400A. This message can be sent based on a connectionless protocol, for example, based on the User Datagram Protocol (UDP). This is because private IP addresses are used for devices located inside the virtual private network 500, so there is no need to set up a TCP connection. This allows the terminal device 400A to receive the message from the terminal device 400B. The user of the terminal device 400A can read the message.

[0098] On the other hand, if the terminal device 400A is not connected to the wireless network and the core network 200 of the virtual private network 500, for example, if the terminal device 400A is powered off, the push notification server 260 waits until the terminal device 400A is connected to the wireless network and the core network 200. At this time, the message is held and accumulated in the push notification server 260. When the terminal device 400A is connected to the wireless network and the core network 200, the push notification server 260 performs a push notification and transmits the message to the terminal device 400A.

[0099] As described above, by placing the push notification server 260 inside the virtual private network 500, messages can be exchanged between the push notification server 260 and the terminal device 400A based on UDP, which is a connectionless protocol. This UDP is a protocol that omits processes such as handshakes when sending messages, and allows for easy message transmission.

[0100] In contrast, TCP requires that a connection be established in advance, making message transmission more complicated. Specifically, a TCP connection is established through a procedure known as a three-way handshake, which involves sending and receiving three packets. When using devices that frequently connect and disconnect from the network, such as IoT devices, the number of TCP connections established increases, increasing the processing load and power consumption of the push notification server 260.

[0101] Furthermore, maintaining a TCP connection for a long period of time for continuous push notifications also increases the burden on the push notification server 260 and the terminal device 400A. This is because packets must be sent and received periodically to maintain the TCP connection. When a large number of terminal devices are connected, the burden on the push notification server 260 increases even more. Furthermore, maintaining TCP connections with a large number of terminal devices can cause the problem of depletion of IP address resources. This is because an IP address is assigned to each terminal device. Sending messages based on UDP, a connectionless protocol, can simplify the transmission procedure between the terminal device 400A and the push notification server 260.

[0102] In contrast, if the push notification server 260 is located outside the virtual private network 500, message transmission based on UDP cannot be applied and message transmission based on TCP must be performed. Within the virtual private network 500, private IP addresses are applied to devices such as the terminal device 400A. When this terminal device 400A sends a packet outside the virtual private network 500, the private IP address is converted into a public IP address before transmission. By receiving the packet with this public IP address added, a server or the like located outside the virtual private network 500 can determine the public IP address of the terminal device 400A. In other words, if the push notification server 260 is located outside the virtual private network 500, the public IP address of the terminal device 400A is not obtained, and therefore push notification based on UDP cannot be performed.

[0103] Note that the conversion from a private IP address to a public IP address can be performed by Network Address Translation (NAT), which is usually performed in a gateway.

[0104] On the other hand, when a TCP connection is established between the terminal device 400A and the push notification server 260, push notification can be sent from outside the virtual private network 500. By establishing a TCP connection starting from the terminal device 400A, a packet is sent from the terminal device 400A to the push notification server 260. By receiving this packet, the push notification server 260 can obtain the IP address of the terminal device 400A before sending the push notification.

[0105] There are also systems that do not use the above-mentioned NAT, such as Internet Protocol Version 6 (IPv6). In such systems, it is possible to send packets using UDP from outside the virtual private network 500. However, in such systems, security problems arise because NAT is not performed.

[0106] These problems can be solved by placing the push notification server 260 inside the virtual private network 500 and transmitting messages between the push notification server 260 and the terminal device 400A based on UDP, which is a connectionless protocol.

[0107] 4. First Embodiment A procedure for push notification processing according to the first embodiment of the present disclosure will be described with reference to Fig. 8. Fig. 8 is a sequence diagram showing a procedure for push communication processing according to the first embodiment of the present disclosure. Fig. 8 illustrates a terminal device 400A, a UPF 221, an SMF 242, an AMF 241, a push notification server 260, an application server 110, and a terminal device 400B. For convenience, the application server 110 is abbreviated as "server." The SMF 242 and the AMF 241 are collectively illustrated as a control plane (C-Plane) in 5G. The UPF 221 corresponds to a user plane (U-Plane) in 5G.

[0108] First, the terminal device 400A is connected to the wireless network and the core network 200 (referred to as a network in FIG. 8) (step S101). At this time, an IP address is assigned by the SMF 242.

[0109] Next, the terminal device 400A registers its own ID with the push notification server 260 (step S102). At this time, the IMSI of the terminal device 400A is also registered with the push notification server 260. Next, the push notification server 260 transmits a token to the terminal device 400A as a response to the ID registration (step S103).

[0110] Next, the push notification server 260 makes a request (subscription) to the SMF 242 to be notified of the IP address of the terminal device 400A that has disconnected from the network and will be connected to the network again (step S104). This request can be made using the IMSI of the terminal device 400A. An API for accepting this request is implemented in the SMF 242. The push notification server 260 can make the request through this API.

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

[0112] Thereafter, when the network connection of the terminal device 400A is stopped (step S106), 、 The IP address assigned in step S101 is lost. Note that the SMF 242 notifies the push notification server 260 of the termination of the network connection of the terminal device 400A (step S107).

[0113] The push notification server 260 establishes a TCP connection with the application server 110 (step S108). Meanwhile, the application on the application server 110 notifies the terminal device 400B, which has subscribed to the same service (message exchange), of the ID of the terminal device 400A (step S109). When a message addressed to the terminal device 400A is generated in the terminal device 400B, the message is transmitted from the terminal device 400B to the application server 110 together with the ID (step S110). The application on the application server 110 identifies the destination terminal device 400A based on the ID attached to the transmitted message. Next, the application on the application server 110 transmits the message and the token of the terminal device 400A to the push notification server 260 (step S111). This transmission is performed via the TCP connection established in step S108. Because the terminal device 400A is not connected to the network, the push notification server 260 holds the transmitted message.

[0114] Next, the terminal device 400A is reconnected to the network and a new IP address is assigned (step S112). Based on the request in step S104, the SMF 242 notifies the push notification server 260 of this new IP address (step S113). This notification can be performed using the API (1) described in FIG. 2.

[0115] Next, the push notification server 260 performs a push notification based on the notified IP address (step S114). Specifically, the push notification server 260 forms an IP header using the notified IP address as the destination network address. Next, the push notification server 260 forms a UDP packet using this IP header and data including a message addressed to the terminal device 400A. Next, the push notification server 260 transmits this UDP packet to the UPF 221. Note that step S114 is an example of performing a push notification as recited in the claims.

[0116] Next, the UPF 221 transmits a message based on the push notification to the terminal device 400A (step S115). Specifically, the UPF 221 forms a virtual communication path between the UPF 221 and the terminal device 400A, and transmits a UDP packet including the message transmitted by the push notification to the terminal device 400A. Note that the virtual communication path can be configured based on, for example, GTP (General Packet Radio System Tunneling Protocol).

[0117] By the procedure described above, a message from terminal device 400B can be transmitted to terminal device 400A. In step S104, terminal device 400A requests that it be notified of its IP address when it reconnects to the network after disconnecting from the network, and thereby the IP address of terminal device 400A when it reconnects can be quickly acquired. This allows push notifications to be sent at high speed. Note that in response to the API subscription in step S104, a notice is sent in step S113, but a request / response type API can also be used.

[0118] The configuration of virtual private network 500 is not limited to this example. For example, the push notification server 260 may be configured to further include a network function (NF), which is a group of individual functions required for a network. In this case, an application deployed on the push notification server 260 may use the API of an entity in the core network 200. Also, for example, the push notification server 260 may be configured to further include an application function (AF) that functions as an application server.

[0119] The application server 110 can also be located inside the virtual private network 500. In this case, messages can be exchanged between the push notification server 260 and the application server 110 based on the UDP protocol.

[0120] In this way, by placing the push notification server 260 in the virtual private network 500, push notification based on a connectionless protocol can be performed between the push notification server 260 and the terminal device 400A. This allows messages to be exchanged using a simple procedure. Furthermore, push notification based on a connectionless protocol enables messages to be sent with low latency. Furthermore, when the push notification server 260 is placed in the core network 200, it is possible to use APIs of entities in the core network 200. This improves the usability of the push notification server 260.

[0121] 5. Second Embodiment In the first embodiment, even when the terminal device 400A is not connected to the network, the application server 110 transmits a message addressed to the terminal device 400A to the push notification server 260. In contrast, the application server 110 may wait until the terminal device 400A is connected to the network before transmitting a message addressed to the terminal device 400A to the push notification server 260. This case will be described as the second embodiment. Note that the second embodiment uses the virtual private network 500, core network 200, base station device 300, terminal device 400, and push notification server 260 with the same configurations as those in the first embodiment, and therefore a description of the overlapping configurations and operations will be omitted.

[0122] The push notification server 260 in the first embodiment receives notification of the connection status of the terminal device 400A to the network from the SMF 242. In contrast, the push notification server 260 in the second embodiment further notifies the application server 110 of the connection status of the terminal device 400A to the network. That is, when the push notification server 260 in the second embodiment determines that the terminal device 400A is not connected to the network, it notifies the application server 110 to that effect. This allows the application server 110 to stop sending messages to the push notification server 260 while the terminal device 400A is not connected to the network.

[0123] The procedure of push notification processing according to the second embodiment of the present disclosure will be described with reference to Fig. 9. Fig. 9 is a sequence diagram showing the procedure of push communication processing according to the second embodiment of the present disclosure. Note that the same processes as those in the sequence diagram of Fig. 8 are designated by the same reference numerals, and descriptions thereof will be omitted.

[0124] In step S107, the push notification server 260 is notified that the network connection of the terminal device 400A has been stopped. Thereafter, the push notification server 260 establishes a TCP connection with the application server 110 (step S108) and notifies the application server 110 of the disconnected state of the terminal device 400A to the network (step S116). Upon receiving this notification, the application of the application server 110 further notifies the terminal device 400B of the disconnected state of the terminal device 400A to the network (step S117).

[0125] Thereafter, when the terminal device 400A is reconnected to the network and a new IP address is assigned (step S112), the IP address is notified to the push notification server 260 (step S113). The push notification server 260 notifies the application server 110 of the connection status of the terminal device 400A to the network (step S118). The application of the application server 110 notifies the terminal device 400B of the connection status of the terminal device 400A to the network (step S119). Based on this notification, the terminal device 400B generates a message addressed to the terminal device 400A and transmits it to the application server 110 (step S110).

[0126] The application on the application server 110 transmits the received message to the push notification server 260 (step S111). Because the terminal device 400A is connected to the network, the push notification server 260 can immediately perform the push notification (step S114).

[0127] As described above, the push notification server 260 obtains information on whether the terminal device 400A is connected to the network via the SMF 242, which is an entity located in the core network 200. If the terminal device 400A is connected to the network, the push notification server 260 obtains the IP address of the terminal device 400A. This IP address corresponds to the information on the terminal device 400A for performing push notification. The push notification server 260 also notifies the application of the application server 110 that the terminal device 400A is connected to the network and has an IP address. In other words, the push notification server 260 transmits information on the terminal device 400A to the application server 110, which is a server that stores a message that triggers a push notification for the terminal device 400A.

[0128] While the terminal device 400A is not connected to the network, no messages are sent from the application server 110, and therefore the number of messages accumulated in the push notification server 260 decreases. This reduces the capacity of the storage unit 262 of the push notification server 260. Furthermore, the application of the application server 110 waits for the terminal device 400A to connect to the network before sending a message to the push notification server 260, and therefore messages can be reliably sent to the terminal device 400A.

[0129] Note that the procedure of the push notification process according to the second embodiment of the present disclosure is not limited to this example. For example, the application of the application server 110 may omit the notification of the non-connection state of the terminal device 400A to the network (step S117). In this case, the message sent from the terminal device 400B and addressed to the terminal device 400A is held and accumulated in the application server 110.

[0130] In this way, the push notification server 260 according to the second embodiment of the present disclosure acquires information on whether or not the terminal device 400A has an IP address as information on the terminal device 400A. This allows the push notification to be performed by determining whether or not the terminal device 400A is capable of receiving a message, thereby improving convenience.

[0131] 6. Third Embodiment In the second embodiment, the push notification server 260 acquires the connection status of the terminal device 400A to the network and transmits it to the application server 110. Alternatively, the application server 110 may specify the desired timing for the terminal device 400A to connect to the network. This case will be described as the third embodiment. Note that the third embodiment also uses the virtual private network 500, core network 200, base station device 300, terminal device 400, and push notification server 260 with the same configurations as those in the first embodiment, and therefore a description of the overlapping configurations and operations will be omitted.

[0132] The push notification server 260 in the third embodiment sets a network connection cycle and connection period for the terminal device 400A. This setting can be performed, for example, via the AMF 241, which is an entity of the core network 200. Specifically, an API for setting the network connection cycle and connection period is implemented and the setting can be performed using this API. An application on the application server 110 can request a desired network connection cycle and connection period from the push notification server 260. Based on this request, the push notification server 260 can set the network connection cycle and connection period for the terminal device 400A. When multiple applications request a network connection cycle and connection period, the push notification server 260 can select a connection time or the like that satisfies these multiple requests and set it for the terminal device 400A.

[0133] The network connection cycle and connection period will be described with reference to FIG. 10. FIG. 10 is a diagram showing the network connection cycle and connection period according to the third embodiment of the present disclosure. In FIG. 10, connection 601 represents the connection period of the terminal device 400A to the network, and connection stop 602 represents the connection stop period of the terminal device 400A to the network. The connection cycle is the sum of the connection 601 and connection stop 602. During the connection 601 period, an IP address is assigned to the terminal device 400A. That is, during the connection 601 period, the terminal device 400A has already acquired an IP address. In contrast, during the connection stop 602, the IP address assigned to the terminal device 400A is released.

[0134] The push notification server 260 can notify the application server 110 of the set network connection cycle and connection period of the terminal device 400A. The application of the application server 110 can obtain the period during which the terminal device 400A is connected to the network, and can send messages during this period.

[0135] The procedure of push notification processing according to the third embodiment of the present disclosure will be described with reference to Fig. 11. Fig. 11 is a sequence diagram showing the procedure of push communication processing according to the third embodiment of the present disclosure. Note that the same processes as those in the sequence diagram of Fig. 8 are designated by the same reference numerals, and descriptions thereof will be omitted.

[0136] First, the application of the application server 110 requests the push notification server 260 for a desired network connection cycle and connection period for the terminal device 400A (step S120). Based on this request, the push notification server 260 determines the network connection cycle and connection period, and requests an API for setting the network connection cycle and connection period from the AMF 241 (step S121). Thereafter, the AMF 241 sets the network connection cycle and connection period for the terminal device 400A using the API (not shown).

[0137] In step S107, the push notification server 260 is notified that the terminal device 400A has stopped connecting to the network. The push notification server 260 establishes a TCP connection with the application server 110 (step S108) and notifies the application server 110 of the state and duration of the terminal device 400A's disconnection from the network (step S122). The duration of this disconnection state can be calculated from the connection cycle and connection duration. Upon receiving this notification, the application of the application server 110 further notifies the terminal device 400B of the state and duration of the terminal device 400A's disconnection from the network (step S123).

[0138] Thereafter, when the terminal device 400A is connected to the network again and a new IP address is assigned (step S112), the IP address is notified to the push notification server 260 (step S113). The push notification server 260 notifies the application server 110 of the connection status and duration of the terminal device 400A to the network (step S124). The application of the application server 110 notifies the terminal device 400B of the connection status and duration of the terminal device 400A to the network (step S125). The terminal device 400B transmits a message addressed to the terminal device 400A during the notified connection period of the terminal device 400A to the network (step S110).

[0139] The application on the application server 110 transmits the received message to the push notification server 260 (step S111). Because the terminal device 400A is connected to the network, the push notification server 260 can immediately perform the push notification (step S114).

[0140] As described above, the push notification server 260 acquires the connection period and connection duration of the terminal device 400A to the network via the AMF 241, which is an entity disposed in the core network 200. The connection period and connection duration of the terminal device 400A to the network correspond to information on the duration of the connection of the terminal device 400A to the core network 200, and correspond to information on the terminal device 400A for performing push notification.

[0141] Furthermore, the push notification server 260 transmits information about the period during which the terminal device 400A is connected to the core network 200 to the application of the application server 110. The application of the application server 110 can transmit messages to the push notification server 260 while the terminal device 400A is connected to the network, thereby optimizing the timing of message transmission. Furthermore, the terminal device 400A can control power on and off based on the set connection cycle and connection period, thereby reducing power consumption while ensuring message reception.

[0142] Note that the procedure of the push notification process according to the third embodiment of the present disclosure is not limited to this example. For example, the application of the application server 110 may omit the notification of the non-connection state of the terminal device 400A to the network (step S123). In this case, the message sent from the terminal device 400B and addressed to the terminal device 400A is held and accumulated in the application server 110.

[0143] In this way, the push notification server 260 according to the third embodiment of the present disclosure acquires the network connection cycle and connection period as information about the terminal device 400A. This allows the terminal device 400A to send a push notification during a period in which the terminal device 400A can receive messages, thereby further improving convenience.

[0144] 7. Fourth Embodiment In the second embodiment, the push notification server 260 obtains the connection status of the terminal device 400A to the network and transmits it to the application server 110. However, information on the connection of the terminal device 400A to the base station device 300 may also be obtained. This case will be described as the fourth embodiment. Note that the fourth embodiment also uses the virtual private network 500, core network 200, base station device 300, terminal device 400, and push notification server 260 with the same configurations as in the first embodiment, and therefore a description of the overlapping configurations and operations will be omitted.

[0145] The terminal device 400A can be in a connected state (connected) in which radio resources are allocated, a link with the base station device 300 is established, and transmission and reception are possible, as well as a standby state (idle) in which radio resources are released. By placing the terminal device 400A in this standby state, power consumption of the terminal device 400A can be reduced. The terminal device 400A transitions from the standby state to the connected state as necessary to perform communication. Push notifications and messages need to be received when the terminal device 400A is in a connected state with the base station device 300. A transition from the standby state to the connected state can be performed by transmitting a message from the base station device 300 to the terminal device 400A. As described above in FIG. 2, this message is called a paging message. The base station device 300 can transmit paging messages to the terminal device 400A at predetermined intervals. The connected state of the terminal device 400A is also called an RRC connected state (Radio Resource Control Connected).

[0146] The push notification server 260 in the fourth embodiment acquires information about the connection of the terminal device 400A to the base station device 300, for example, whether or not the terminal device 400A has transitioned from a standby state to a connected state. This can be done, for example, by using the API of the AMF 241, which is an entity of the core network 200. This API specifies an ID such as an IMSI to identify the terminal device 400A.

[0147] The acquired information about the connection of the terminal device 400A to the base station device 300 can be notified to the application server 110. The application of the application server 110 can transmit a message when the terminal device 400A is in a connected state with the base station device 300.

[0148] The procedure of push notification processing according to the fourth embodiment of the present disclosure will be described with reference to Fig. 12. Fig. 12 is a sequence diagram showing the procedure of push communication processing according to the fourth embodiment of the present disclosure. Note that the same processes as those in the sequence diagram of Fig. 8 are designated by the same reference numerals, and descriptions thereof will be omitted.

[0149] In step S108, the push notification server 260 establishes a TCP connection with the application server 110. Next, the push notification server 260 requests the AMF 241 for an API that notifies the connection status of the terminal device 400A to the base station device 300 (step S126). After that, the AMF 241 notifies the push notification server 260 that the terminal device 400A has transitioned from a standby state to a connected state with the base station device 300 (step S127). The push notification server 260 notifies the application server 110 of this change in the connection status of the terminal device 400A (step S128). Based on this notification, the application of the application server 110 transmits a message to the push notification server 260 (step S111). Because the terminal device 400A is in a connected state with the base station device 300, the push notification server 260 can immediately perform push notification (step S114).

[0150] 12, the push notification server 260 requests the AMF 241 for an API that notifies the connection status of the terminal device 400A to the base station device 300, and the AMF 241 notifies the change in the connection status of the terminal device 400A. In contrast, a request / response type API can also be used. This API can be the API (2) described in FIG. 2.

[0151] A procedure for using a request / response type API will be described with reference to Fig. 13. Fig. 13 is a sequence diagram showing another procedure for push communication processing according to the fourth embodiment of the present disclosure. Note that the same processes as those in the sequence diagram of Fig. 12 are designated by the same reference numerals, and descriptions thereof will be omitted.

[0152] In step S108, the push notification server 260 establishes a TCP connection with the application server 110. Next, the application on the application server 110 notifies the push notification server 260 that there is a message addressed to the terminal device 400A (step S129). The push notification server 260 requests the AMF 241 to transmit an API that reports the connection status of the terminal device 400A to the base station device 300 (step S130). When the terminal device 400A transitions from a standby state to a connected state with the base station device 300, the AMF 241 reports the connection status (step S131). The push notification server 260 notifies the application server 110 of the connection status of the terminal device 400A (step S132). Based on this notification, the application on the application server 110 transmits a message to the push notification server 260 (step S111). Since the terminal device 400A is in a connected state with the base station device 300, the push notification server 260 can immediately send a push notification (step S114).

[0153] When a message exists in the application server 110, the application of the application server 110 can request the push notification server 260 to obtain the connection status of the terminal device 400A to the base station device 300. Furthermore, when there are multiple application servers 110 that transmit messages, etc. to the terminal device 400A, the push notification server 260 can request an API from the AMF 241 in response to requests from these multiple applications. For example, a configuration can be adopted in which the push notification server 260 requests an API from the AMF 241 when multiple requests arrive from applications. When the terminal device 400A is in a connected state with the base station device 300, multiple applications are notified that message exchange is possible.

[0154] In the process of FIG. 13, the application of the application server 110 is an application for exchanging instant messages, but it may also be a game application.

[0155] With reference to Fig. 14, a procedure when applied to a game application will be described. Fig. 14 is a sequence diagram showing another procedure of push communication processing according to the fourth embodiment of the present disclosure. In Fig. 14, the terminal device 400B is omitted. Also, a game application that transmits a video stream is assumed as the application of the application server 110. Note that the same processes as those in the sequence diagram of Fig. 13 are designated by the same reference numerals, and descriptions thereof will be omitted.

[0156] In step S108, the push notification server 260 establishes a TCP connection with the application server 110. Next, when the application of the application server 110 notifies the push notification server 260 that a stream addressed to the terminal device 400A exists (step S133), the push notification server 260 requests the AMF 241 to transmit an API that returns the connection status of the terminal device 400A to the base station device 300 (step S130). When the terminal device 400A transitions from a standby state to a connected state with the base station device 300, the AMF 241 returns the connection status response (step S131).

[0157] The push notification server 260 notifies the application server 110 of the connection status of the terminal device 400A (step S132). Based on this notification, the application of the application server 110 transmits a stream to the push notification server 260 (step S134). The push notification server 260 performs a push notification of the stream based on the UDP protocol (step S135). The UPF 221 transmits the stream to the terminal device 400A (step S136).

[0158] In this way, the push notification server 260 can also send push notifications about data other than messages.

[0159] As described above, the push notification server 260 acquires information about the connection state of the terminal device 400A with the base station device 300 as information about the connection of the terminal device 400A to the base station device 300. By transmitting messages and the like to the terminal device 400A in this connected state, it is possible to transmit messages and the like collectively. Because messages and the like are transmitted after the terminal device 400A has entered a connected state with the base station device 300, it is possible to transmit messages and the like without increasing the number of transitions to the connected state of the terminal device 400A.

[0160] The paging message may include information indicating that an instant message addressed to the terminal device 400A exists, thereby allowing the terminal device 400A in standby mode to know that an instant message exists.

[0161] As described above, paging messages are transmitted to the terminal device 400A at predetermined intervals. The push notification server 260 can also acquire information about the timing at which paging messages are transmitted. This can be achieved, for example, by implementing an API for acquiring the interval at which paging messages are transmitted in the AMF 241 and having the push notification server 260 use this API. The push notification server 260 can acquire the timing at which paging messages are transmitted based on the acquired interval. This allows the push notification server 260 to determine the timing at which the terminal device 400A can be connected to the base station device 300. The push notification server 260 can also notify the application server 110 of the timing at which the terminal device 400A will be connected. An application on the application server 110 can prepare to transmit a message addressed to the terminal device 400A based on this timing, thereby improving the efficiency of message transmission. The AMF 241 is an example of an entity described in the claims.

[0162] In this way, the push notification server 260 according to the fourth embodiment of the present disclosure acquires information about the connection of the terminal device 400A to the base station device 300. It becomes possible to transmit a push notification and a message based on the acquired information about the connection of the terminal device 400A to the base station device 300, thereby improving convenience.

[0163] 8. Fifth Embodiment In the fourth embodiment, information on the connection state of the terminal device 400A with the base station device 300 is acquired, and a message or the like is transmitted after the terminal device 400A transitions to a connected state with the base station device 300. In contrast, when the terminal device 400A is in a standby state, the terminal device 400A may transition to a connected state and transmit a message. This case will be described as the fifth embodiment. Note that the fifth embodiment also uses the virtual private network 500, core network 200, base station device 300, terminal device 400, and push notification server 260 with the same configurations as those in the first embodiment, and therefore a description of the overlapping configurations and operations will be omitted.

[0164] The push notification server 260 in the fifth embodiment can use the API (3) described in FIG. 2 to cause the terminal device 400A in standby mode to send a paging message.

[0165] The procedure of push notification processing according to the fifth embodiment of the present disclosure will be described with reference to Fig. 15. Fig. 15 is a sequence diagram showing the procedure of push communication processing according to the fifth embodiment of the present disclosure. Note that the same processes as those in the sequence diagram of Fig. 13 are designated by the same reference numerals, and descriptions thereof will be omitted.

[0166] When a standby state response is returned in response to the API request for the AMF 241 in step S130, which responds with the connection state of the terminal device 400A to the base station device 300 (step S142), the push notification server 260 requests an API for transmitting a paging message to the terminal device 400A (step S137). Based on this request, the AMF 241 causes the base station device 300 (not shown) to transmit a paging message to the terminal device 400A (step S138). Based on this paging message, a link is established between the terminal device 400A and the base station device 300 (step S139). As a result, the terminal device 400A transitions to a connected state with the base station device 300.

[0167] Thereafter, when the push notification server 260 issues an API request for responding with the connection status of the terminal device 400A to the base station device 300 (step S140), the AMF 241 responds with the connection status (step S141). The connection status of the terminal device 400A is notified to the application server 110 (step S132), and a message is transmitted (step S111).

[0168] 15, the application server 110 is notified after it is confirmed that the terminal device 400A is in a connected state with the base station device 300. In contrast, if it is possible to estimate the time from the transmission of a paging message to the terminal device 400A to the transition to a connected state, the message can be transmitted without waiting for confirmation of the connection state of the terminal device 400A. Specifically, the application server 110 transmits a message (instant message) to the push notification server 260 after a predetermined time (estimated time) has elapsed since the transmission of the paging message to the terminal device 400A.

[0169] With reference to Fig. 16, a procedure for transmitting a message to the push notification server 260 after a predetermined time has elapsed since the transmission of a paging message will be described. Fig. 16 is a sequence diagram showing another procedure for push communication processing according to the fifth embodiment of the present disclosure. The processing in Fig. 16 is based on the assumption that a message is transmitted to the push notification server 260 10 ms after the transmission of a paging message. Note that the same reference numerals are used for the same processes as in the sequence diagram in Fig. 15, and descriptions thereof will be omitted.

[0170] In step S137, the push notification server 260 requests an API for transmitting a paging message to the terminal device 400A. At that time, the push notification server 260 requests the application of the application server 110 to transmit a message 10 ms later (step S143). 10 ms later, the application of the application server 110 transmits a message to the push notification server 260 (step S111). Because the terminal device 400A is in a connected state with the base station device 300, the push notification server 260 immediately performs a push notification (step S114). Compared to the case of FIG. 15, the message can be transmitted more quickly from the application server 110.

[0171] As described above, when the terminal device 400A is in a standby state, the push notification server 260 transitions the terminal device 400A to a connected state and transmits a message. This reduces the accumulation of messages in the application server 110, etc. This prevents an increase in the data buffer capacity in the application server 110, etc. This is particularly effective when the application on the application server 110 transmits still images or videos.

[0172] In this way, the push notification server 260 according to the fifth embodiment of the present disclosure transitions the terminal device 400A to a connected state and performs a push notification, thereby preventing messages from being stored and reducing delays in message transmission.

[0173] 9. Sixth Embodiment In the first embodiment, one UPF 221 is arranged in the core network 200. However, multiple UPFs 221 can also be arranged in the core network 200. This is to distribute the processing of the UPFs 221 when a large number of terminal devices 400 are arranged. This case will be described as the sixth embodiment.

[0174] A communication system 1 according to a sixth embodiment of the present disclosure will be described with reference to Fig. 17. Fig. 17 is a simplified diagram of the communication system according to the sixth embodiment of the present disclosure. The core network 200 in Fig. 17 illustrates an example in which 32 UPFs 221 (UPF1 to UPF32) are deployed. A base station device 300 and a terminal device 400 are connected to these UPFs 221, respectively. Note that the AMF 241 and the SMF 242 are omitted from Fig. 17.

[0175] The push notification server 260 in the sixth embodiment selects and sends a push notification to one of multiple UPFs 221. This selection can be made by acquiring the correspondence between the terminal device 400 and the UPF 221 and determining which UPF 221 the desired terminal device 400 is connected to.

[0176] With reference to Fig. 18, the correspondence between terminal devices 400 and UPFs 221 according to the sixth embodiment of the present disclosure will be described. Fig. 18 is a diagram showing the correspondence between terminal devices and UPFs according to the sixth embodiment of the present disclosure. In Fig. 18, "UPF1" to "UPF32" correspond to the 32 UPFs 221 shown in Fig. 17. "IP address" indicates the range of global IP addresses assigned to terminal devices 400 connected to these UPFs 221. A different address is set for each terminal device 400 in the "X" of the fourth 8-bit address in the "IP address" column in Fig. 18.

[0177] The third 8-bit address identifies 32 UPFs 221. The push notification server 260 can recognize which UPF 221 the terminal device 400 is connected to by using the third 8-bit address of the IP address. This correspondence between the terminal device and the UPFs allows the push notification server 260 to select one of the multiple UPFs 221 and send a push notification.

[0178] The procedure of the push notification process is the same as that in Fig. 8, and therefore a description thereof will be omitted. Note that the UPF 221 is an example of a UPF entity described in the claims.

[0179] As described above, in the sixth embodiment of the present disclosure, when multiple UPFs 221 are deployed in the core network 200, a correspondence relationship between the terminal device 400 and the UPF 221 is set in advance. The push notification server 260 selects a UPF 221 based on the set correspondence relationship between the terminal device 400 and the UPF 221 and performs a push notification. This enables push notification to be performed in a virtual private network 500 having a core network 200 in which multiple UPFs 221 are deployed.

[0180] The configuration of the sixth embodiment of the present disclosure can be applied to other embodiments. Specifically, the sequences shown in Figures 8, 9, and 11 to 16 can be applied even when multiple UPFs 221 are arranged in the core network 200.

[0181] (effect) The information processing device (push notification server 260) of the present disclosure is arranged in a local area network LAN having a base station device 300 and a core network 200 to which a terminal device 400 is connected, and has the function of sending push notifications to the terminal device 400 based on a connectionless protocol.

[0182] This allows push notifications to be sent based on a connectionless protocol, allowing messages to be exchanged through simple procedures.

[0183] The LAN may also be a virtual private network 500 .

[0184] This allows push notifications in the virtual private network 500 to be performed based on a connectionless protocol.

[0185] Alternatively, the connectionless protocol may be the User Datagram Protocol (UDP).

[0186] This allows push notifications to be based on UDP.

[0187] Furthermore, the information processing device (push notification server 260) may be located in the core network 200.

[0188] This allows the information processing device (push notification server 260) to be used as an entity of the core network 200.

[0189] In addition, the information processing device (push notification server 260) may further have a function as an application function of the core network 200.

[0190] This can simplify the interaction between the application and the push notification server.

[0191] Furthermore, the information processing device (push notification server 260) may further include a function as a network function of the core network 200.

[0192] This allows the information processing device (push notification server 260) to use the API of the entity of the core network 200.

[0193] Furthermore, the information processing device (push notification server 260) may acquire information about the terminal device 400 for performing push notification via an entity (AMF 241) disposed in the core network 200.

[0194] This allows information about the terminal device 400 to be obtained using an entity located in the core network 200.

[0195] Furthermore, the information on the terminal device 400 may be acquired through the application programming interface (API) of the entity.

[0196] This allows the information on the terminal device 400 to be acquired using the API of the entity.

[0197] Alternatively, the acquired information about the terminal device 400 may be sent to a server (application server 110) that holds a message addressed to the terminal device 400 that triggers the push notification.

[0198] This allows the application on the application server 110 to use the information on the terminal device 400 .

[0199] The information about the terminal device 400 may also be an Internet Protocol address (IP address).

[0200] This allows the application on the application server 110 to use the IP address of the terminal device 400 .

[0201] Furthermore, the information on the terminal device 400 may be information on whether or not the terminal device 400 has an IP address.

[0202] This allows the application on the application server 110 to obtain whether the terminal device 400 is connected to the network.

[0203] Furthermore, the information about the terminal device 400 may be information about the period during which the terminal device 400 is connected to the core network 200 .

[0204] This allows the push notification server 260 to send a push notification while the terminal device 400 is connected to the network.

[0205] Furthermore, the information on the terminal device 400 may be information on the connection of the terminal device 400 to the base station device 300 .

[0206] This allows the push notification server 260 to obtain the connection status between the terminal device 400 and the base station device 300.

[0207] Furthermore, the information on the terminal device 400 may be information on the terminal device 400 transitioning from a standby state to a connected state in which transmission and reception with the base station device 300 are possible.

[0208] This allows the push notification server 260 to send a push notification when the terminal device 400 and the base station device 300 are in a connected state.

[0209] Furthermore, the information about the terminal device 400 may be information about the timing at which a message for transitioning the terminal device 400 from a standby state to a connected state is to be sent to the terminal device.

[0210] This allows the push notification server 260 to predict when the terminal device 400 will transition to a connected state.

[0211] Furthermore, control may be further performed to cause the terminal device 400 to transmit a message for transitioning the terminal device 400 from a standby state to a connected state.

[0212] As a result, the push notification server 260 can transition the terminal device 400 to a connected state and perform a push notification.

[0213] In addition, the core network 200 may have multiple user plane function (UPF) entities (UPF221) connected to the terminal device 400 and performing transmission and reception processing, and may further have a function of retaining information about the UPF entities (UPF221) connected to the terminal device 400 when the terminal device performs push notification via one of the multiple UPF entities (UPF221).

[0214] This makes it possible to select the UPF 221 to be connected to the desired terminal device 400 even when multiple UPFs 221 are installed.

[0215] Furthermore, a message may be transferred based on the Transmission Control Protocol between a server (application server 110) that is located outside the LAN and that holds a message addressed to the terminal device 400 that triggers the push notification.

[0216] This allows secure message transfer to and from the application server 110 located outside the LAN.

[0217] Furthermore, a message may be transferred based on a connectionless protocol between a server (application server 110) that is located within the LAN and that holds a message addressed to the terminal device 400 that triggers the push notification.

[0218] This allows for simple message transfer to and from the application server 110 located within the LAN.

[0219] The information processing method of the present disclosure also includes sending a push notification to the terminal device 400 based on a connectionless protocol by an information processing device (push notification server 260) located in a LAN having a base station device 300 to which the terminal device 400 is connected and a core network 200.

[0220] This allows push notifications to be sent based on a connectionless protocol, allowing messages to be exchanged through simple procedures.

[0221] The communication system of the present disclosure also includes a terminal device 400, and an information processing device (push notification server 260) that is located in a LAN having a base station device 300 and a core network 200 to which the terminal device 400 is connected and has the function of sending push notifications to the terminal device 400 based on a connectionless protocol.

[0222] This allows push notifications to be sent based on a connectionless protocol, allowing messages to be exchanged through simple procedures.

[0223] Furthermore, the entity of the present disclosure causes an information processing device (push notification server 260) that is located in a LAN having a base station device 300 and a core network 200 to which a terminal device 400 is connected and has the function of sending push notifications to the terminal device 400 based on a connectionless protocol to send a push notification, to have the information processing device (push notification server 260) use an API that notifies information about when a message that transitions the terminal device 400 and the base station device 300 to a connected state will be sent to the terminal device 400 in order for the information processing device (push notification server 260) to send a push notification.

[0224] This allows the push notification server 260 to predict when the terminal device 400 will be connected to the base station device 300.

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

[0226] The present technology can also be configured as follows. (1) An information processing device that is arranged in a local area network (LAN) having a base station device and a core network to which a terminal device is connected, and that has a function of sending a push notification to the terminal device based on a connectionless protocol. (2) The information processing device according to (1), wherein the LAN is a virtual private network. (3) The information processing device according to (1) or (2), wherein the connectionless protocol is User Datagram Protocol (UDP). (4) The information processing device according to any one of (1) to (3) above, which is arranged in the core network. (5) The information processing device according to (4) above, further comprising a function as an application function of the core network. (6) The information processing device according to (4) above, further comprising a function as a network function of the core network. (7) The information processing device according to any one of (1) to (6), wherein the information of the terminal device for performing the push notification is obtained via an entity disposed in the core network. (8) The information processing device according to (7) above, which acquires information about the terminal device through an application programming interface (API) of the entity. (9) The information processing device according to (7), wherein the information processing device transmits the acquired information about the terminal device to a server that stores a message addressed to the terminal device that triggers the push notification. (10) The information processing device according to (7), wherein the information about the terminal device is an Internet Protocol address (IP address). (11) The information processing device according to (7), wherein the information about the terminal device is information about whether the terminal device has an IP address. (12) The information processing device according to (7), wherein the information about the terminal device is information about a period during which the terminal device is connected to the core network. (13) The information processing device according to (7), wherein the information about the terminal device is information about a connection of the terminal device to the base station device. (14) The information processing device according to (13), wherein the information about the terminal device is information about the terminal device transitioning from a standby state to a connected state in which transmission and reception with the base station device is possible. (15) The information processing device according to (14), wherein the information about the terminal device is information about a time when a message for transitioning the terminal device from the standby state to the connected state is to be transmitted to the terminal device. (16) The information processing device according to (14), further performing control to cause the terminal device to transmit a message for transitioning the terminal device from the standby state to the connected state. (17) The core network 、 An information processing device according to any one of (1) to (16), comprising a plurality of User Plane Function (UPF) entities connected to a terminal device for performing transmission and reception processing, and further comprising a function for retaining information of the UPF entities connected to the terminal device when the terminal device performs the push notification via any one of the plurality of UPF entities. (18) An information processing device according to any one of (1) to (17), which transfers the message based on a transmission control protocol between a server located outside the LAN and holding a message addressed to the terminal device that triggers the push notification. (19) The information processing device according to any one of (1) to (17), which is arranged within the LAN and transfers the message based on the connectionless protocol between the server that holds the message addressed to the terminal device that triggers the push notification. (20) An information processing method including: performing a push notification to a terminal device based on a connectionless protocol by an information processing device located in a LAN having a base station device to which the terminal device is connected and a core network. (twenty one) A terminal device; an information processing device that is disposed in a LAN having a base station device and a core network to which the terminal device is connected, and that has a function of sending a push notification to the terminal device based on a connectionless protocol; A communication system comprising: (twenty two) An entity that causes an information processing device, which is located on a LAN having a base station device to which a terminal device is connected and a core network, and has the function of sending push notifications to the terminal device based on a connectionless protocol, to use an API that notifies the information processing device of the time when a message that transitions the terminal device and the base station device to a connected state will be sent to the terminal device in order to send the push notification. [Explanation of symbols]

[0227] 1. Communication Systems 110 Application server (information processing device) 200, 200A, 200B Core Network 221 UPF 241 AMF 242 SMF 260, 260A, 260B Push notification server (information processing device) 300, 300A, 300B base station equipment 400, 400A, 400B terminal equipment 500 Virtual Private Network (LAN)

Claims

1. The device is disposed in a local area network (LAN) having a base station device and a core network to which a terminal device is connected, and has a function of performing a push notification to the terminal device based on a connectionless protocol; acquiring information about the terminal device for performing the push notification via an entity located in the core network; The push notification is performed based on information of the terminal device. The push notification includes data addressed to the terminal device, including the message, which is transferred based on a transmission control protocol between the server that is located outside the LAN and that holds the message addressed to the terminal device that triggers the push notification. Information processing device.

2. 2. The information processing apparatus according to claim 1, wherein the LAN is a virtual private network.

3. 2. The information processing apparatus according to claim 1, wherein the connectionless protocol is User Datagram Protocol (UDP).

4. The information processing device according to claim 1 , which is arranged in the core network.

5. The information processing device according to claim 4 , further comprising a function as an application function of the core network.

6. The information processing device according to claim 4 , further comprising a function as a network function of the core network.

7. 2. The information processing apparatus according to claim 1, wherein the information on the terminal device is acquired through an application programming interface (API) of the entity.

8. The information processing apparatus according to claim 1 , wherein the acquired information on the terminal device is transmitted to the server.

9. 2. The information processing apparatus according to claim 1, wherein the information about the terminal device is an Internet Protocol address (IP address).

10. 2. The information processing apparatus according to claim 1, wherein the information about the terminal device is information about whether or not the terminal device has an IP address.

11. The information processing device according to claim 1 , wherein the information about the terminal device is information about a period during which the terminal device is connected to the core network.

12. The information processing apparatus according to claim 1 , wherein the information about the terminal device is information about a connection of the terminal device to the base station device.

13. The information processing apparatus according to claim 12 , wherein the information about the terminal device is information about the terminal device transitioning from a standby state to a connected state in which transmission and reception with the base station device is possible.

14. The information processing apparatus according to claim 13 , wherein the information about the terminal device is information about a time when a message for transitioning the terminal device from the standby state to the connected state is to be transmitted to the terminal device.

15. The information processing apparatus according to claim 13 , further comprising control for causing the terminal apparatus to transmit a message for transitioning the terminal apparatus from the standby state to the connected state.

16. 2. The information processing device according to claim 1, wherein the core network comprises a plurality of User Plane Function (UPF) entities connected to a terminal device to perform transmission and reception processing, and further comprises a function of retaining information of the UPF entities connected to the terminal device when the terminal device performs the push notification via any one of the plurality of UPF entities.

17. In an information processing device disposed in a LAN having a base station device and a core network to which a terminal device is connected, acquiring, via an entity located in the core network, information about the terminal device for performing a push notification to the terminal device; The push notification includes data addressed to the terminal device, including the message transferred based on a transmission control protocol between the server that is located outside the LAN and that holds a message addressed to the terminal device that triggers the push notification, and the push notification is performed based on information about the terminal device. An information processing method including:

18. A terminal device; The device is provided in a local area network (LAN) having a base station device and a core network to which the terminal device is connected, and has a function of performing a push notification to the terminal device based on a connectionless protocol; acquiring information about the terminal device for performing the push notification via an entity located in the core network; The push notification is performed based on information of the terminal device. The push notification includes data addressed to the terminal device, including the message, which is transferred based on a transmission control protocol between the server that is located outside the LAN and that holds the message addressed to the terminal device that triggers the push notification. Information processing device A communication system comprising:

Images