Information processing device, information processing method, terminal device and system
By using the SBI interface to acquire and combine terminal device information, the problem of difficulty in obtaining terminal device information on the service side in the 5G network is solved, and more appropriate terminal device selection and communication is achieved, and communication efficiency is improved.
Patent Information
- Application Number
- CN202380035156.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-28
- Filing Date
- 2023-04-19
- Publication Date
- 2024-12-03
AI Technical Summary
In a 5G network, it is difficult for the service side to fully acquire information on the network side, which makes it difficult to properly communicate with mobile terminal devices, especially in the case of Internet of Things terminals.
Through the control unit of the information processing device, the information of the terminal device is obtained from the core network using a service-based interface (SBI), and combined with the measurement information directly obtained by the terminal device, the terminal device is indicated and the relevant information is notified to the client device, so that it is more appropriate communication.
The client device can obtain more detailed terminal device information and select suitable terminal devices for communication, such as selecting based on power status and position information to improve communication efficiency and effect.
Smart Images

Figure CN119072942A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to information processing devices, information processing methods, terminal devices and systems. Background Art
[0002] In recent years, new technologies have been introduced in cellular wireless communications to cope with the diversification of communication services. For example, a technology is known in which a mobile network discloses the state of communication with a terminal to an application function (AF) of a third party, so that the AF establishes a protocol data unit (PDU) session according to network capabilities.
[0003] In addition, a technology is known in which a terminal device (user equipment (UE)) determines whether to send PDU session-related signaling based on area restriction-related information.
[0004] Reference List
[0005] Patent Literature
[0006] PTL 1: JP 2021-513269 T
[0007] PTL 2: JP 2021-532675 T Summary of the invention
[0008] Technical issues
[0009] In the above-described technology, the AF obtains data from each network function (NF) of the mobile network. However, it is difficult to say that the AF can fully obtain data about the mobile terminal.
[0010] For example, in the case where the mobile terminal is an Internet of Things (IoT) terminal, the client (an example of AF) communicating with the mobile terminal can communicate with the mobile terminal more appropriately by using data about the mobile terminal. As described above, it is hoped that the client can communicate with the mobile terminal more appropriately by acquiring data about the mobile terminal.
[0011] Therefore, the present disclosure provides a mechanism that enables more appropriate communication with a mobile terminal.
[0012] It should be noted that the aforementioned problem or purpose is only one of the multiple problems or purposes that can be solved or achieved by the multiple embodiments disclosed in this specification.
[0013] Solutions to the Problem
[0014] The information processing device of the present disclosure includes a control unit. The control unit obtains first information about a terminal device from a core network through a service-based interface (SBI). The control unit obtains second information, wherein the second information includes at least one of measurement information measured based on the first information or terminal-related information obtained from the terminal device directly or through the SBI. The control unit specifies the terminal device from the second information or by associating the first information with the second information. The control unit notifies the client device of at least one of the first information or the second information associated with the specified terminal device. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] Figure 1 is a diagram for describing an overview of an information processing system according to an embodiment of the present disclosure.
[0016] Figure 2 is a diagram showing a configuration example of an information processing device according to an embodiment of the present disclosure.
[0017] Figure 3 is a diagram showing a configuration example of a base station according to an embodiment of the present disclosure.
[0018] Figure 4 is a diagram showing a configuration example of a terminal device according to an embodiment of the present disclosure.
[0019] Figure 5 is a diagram showing an example of a 5G architecture.
[0020] Figure 6 is a diagram for describing a configuration example of a private 5G network according to an embodiment of the present disclosure.
[0021] Figure 7 is a diagram for describing an application programming interface (API) according to an embodiment of the present disclosure.
[0022] Figure 8 is a diagram illustrating an example of an information processing system according to an embodiment of the present disclosure.
[0023] Fig. 9 is a sequence diagram showing an example of setting the idle transition time by a base station.
[0024] Fig.10 is a sequence diagram showing an example of the flow of the first information processing according to the first embodiment of the present disclosure.
[0025] Fig.11 is a flowchart illustrating an example of the flow of confirmation processing according to the first embodiment of the present disclosure.
[0026] Fig.12is a diagram for describing an example of scheduling a user equipment (UE) state through a reachability management network function (RAMNF) according to the first embodiment of the present disclosure.
[0027] Fig.13 is a diagram illustrating an example of an information processing system according to the second embodiment of the present disclosure.
[0028] Fig.14 : is a sequence diagram showing an example of the flow of a registration schedule information providing process according to the second embodiment of the present disclosure.
[0029] Fig.15 is a diagram showing an example of a registration schedule according to the second embodiment of the present disclosure.
[0030] Fig.16 is a diagram showing an example of scheduling regarding registration according to the second embodiment of the present disclosure.
[0031] Fig.17 is a sequence diagram showing an example of the flow of a power information providing process according to the second embodiment of the present disclosure.
[0032] Fig.18 is a diagram showing an example of connection scheduling according to the second embodiment of the present disclosure.
[0033] Fig.19 is a table showing power information according to the second embodiment of the present disclosure.
[0034] Fig. 20 is a table showing an example of terminal location information according to the second embodiment of the present disclosure.
[0035] Fig.21 is a sequence diagram showing an example of the flow of current terminal location information providing processing according to the second embodiment of the present disclosure.
[0036] Fig. 22 : is a sequence diagram showing an example of the flow of past terminal location information providing processing according to the second embodiment of the present disclosure.
[0037] Fig.23 : is a sequence diagram showing an example of the flow of future terminal location information providing processing according to the second embodiment of the present disclosure.
[0038] Fig.24 is a diagram for describing an example of information integration through RAMNF according to the second embodiment of the present disclosure.
[0039] Fig.25: is a sequence diagram showing an example of the flow of provision processing according to registration conditions according to the third embodiment of the present disclosure.
[0040] Fig.26 is a table showing an example of group information according to the third embodiment of the present disclosure.
[0041] Fig. 27 : is a sequence diagram showing another example of the flow of the providing process according to the registration condition according to the third embodiment of the present disclosure.
[0042] Fig.28 : is a sequence diagram showing an example of the flow of providing processing according to position conditions according to the third embodiment of the present disclosure.
[0043] Fig.29 : is a sequence diagram showing an example of the flow of supply processing according to power conditions according to the third embodiment of the present disclosure.
[0044] Fig.30 is a diagram illustrating an example of an information processing system according to a first application example of the present disclosure.
[0045] Fig.31 is a diagram illustrating an example of an information processing system according to a second application example of the present disclosure. DETAILED DESCRIPTION
[0046] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that in the present specification and the accompanying drawings, components having substantially the same functional configuration are provided with the same reference numerals, and thus repeated descriptions of these components are omitted.
[0047] In addition, in the present specification and drawings, similar components of the embodiments may be distinguished by adding different letters or numbers after the same reference numerals, but in the case where it is not necessary to particularly distinguish each similar component, only the same reference numeral is assigned.
[0048] Each of the one or more embodiments (including examples, modified examples and application examples) described below can be implemented independently. On the other hand, at least some of the multiple embodiments described below can be implemented in combination with at least some other embodiments in appropriate circumstances. These multiple embodiments can include novel features that are different from each other. Therefore, these multiple embodiments can contribute to achieving or solving different purposes or problems, and can produce different effects.
[0049] <<1. Introduction>>
[0050] <1.1、Question>
[0051] In recent years, technologies related to services using 5G networks have attracted attention. 5G networks and services using 5G networks basically operate independently. Therefore, it is difficult to say that the service side fully uses the information on the network side.
[0052] The service side can obtain some information from the network side by using the 5G application programming interface (API), but it cannot be said that sufficient information has been obtained. In addition, it cannot be said that the service side has fully notified the network side of the request for the information it wants to obtain.
[0053] For example, by acquiring information about the terminal device implementing communication through the network, the service side can more appropriately implement communication with the terminal device. For example, by acquiring the power status and more detailed location information of the terminal device, the service side can select a terminal device corresponding to the service to implement communication, such as a terminal device whose remaining power is equal to or more than a predetermined value or a terminal device located in a specific area.
[0054] Thus, a mechanism is needed to more appropriately implement communication with the terminal device on the service side.
[0055] <1.2. Overview of Proposed Technology>
[0056] Figure 1 1 is a diagram for describing an overview of an information processing system 1 according to an embodiment of the present disclosure. Figure 1 The information processing system 1 shown in illustrative examples includes information processing devices 10A to 10C, a base station 20 , and a terminal device 40 .
[0057] The information processing device 10A is, for example, a server device that implements the function of a core network CN (an example of a network). Here, one information processing device 10A implements the function of the core network CN, but a plurality of information processing devices 10A may implement the function of the core network CN in cooperation with each other.
[0058] The information processing device 10B is, for example, a server device that implements the function of a reachability management network function (RAMNF) 100. The RAMNF 100 is a platform for notifying the service-side client 200 of information about the core network CN. It should be noted that Figure 1 A case is shown where the RAMNF 100 is an NF (AF) different from the core network CN, but the RAMNF 100 may be implemented as an NF in the core network CN.
[0059] The information processing device 10C is, for example, a server device (client device) that implements the function of the server-side client 200. The client 200 provides a predetermined service to a user by, for example, implementing communication with the terminal device 40 or controlling the terminal device 40.
[0060] The base station 20 is a wireless communication device that performs wireless communication with the terminal device 40. The base station 20 is a type of communication device. The base station 20 is a type of information processing device.
[0061] The terminal device 40 is a wireless communication device that implements wireless communication with the base station 20. The terminal device 40 is, for example, a mobile phone, a smart device (smart phone or tablet PC), a personal digital assistant (PDA), or a personal computer. For example, the terminal device 40 can be a machine-to-machine (M2M) device or an Internet of Things (IoT) device. In addition, the terminal device 40 can be a head-mounted display, VR glasses, etc. The terminal device 40 can be a mobile subject such as a vehicle (car) or a drone.
[0062] For example, when the terminal device 40 is a mobile phone, the client 200 provides a predetermined service for the user using the terminal device 40. In addition, when the terminal device 40 is an M2M device, an IoT device, etc., the client 200 obtains data from the terminal device 40 or controls the terminal device 40, thereby providing the user with a predetermined service.
[0063] like Figure 1 As shown in FIG. 1 , the RAMNF 100 obtains first information about the terminal device 40 from the core network CN through a service-based interface (SBI) (step S1). The first information includes, for example, registration information about the registration of the terminal device 40 (e.g., registered / unregistered, connected / idle, etc.).
[0064] The RAMNF 100 obtains the terminal related information from the terminal device 40 directly or through the SBI (step S2). The RAMNF 100 obtains the measurement information measured based on the first information (step S3). It should be noted that the RAMNF 100 can obtain at least one of the terminal related information or the measurement information. Hereinafter, the measurement information and / or the terminal related information are also collectively referred to as the second information.
[0065] The measurement information includes information about a transition interval of registration of the terminal device 40 calculated based on the registration information. The terminal related information includes, for example, information included in an application layer of the terminal device 40. More specifically, the terminal related information includes, for example, at least one of scheduling information about registration scheduling, power information about power consumption of the terminal device 40, and location information about the location of the terminal device 40.
[0066] The RAMNF 100 specifies the terminal device 40 from the second information or by associating the first information and the second information with each other (step S4). The RAMNF 100 specifies the terminal device 40, for example, by using the second information and / or information included in the first information for specifying the terminal device 40 (e.g., UE ID, such as International Mobile Subscriber Identity (IMSI) or Subscription Permanent Identifier (SUPI)). The RAMNF 100 notifies the client 200 of at least one of the first information or the second information associated with the specified terminal device 40 (step S5).
[0067] As a result, the client 200 can obtain more detailed information of the terminal device 40 and can more appropriately communicate with the terminal device 40. For example, the client 200 can select a terminal device 40 located in a predetermined area to communicate, or can select a terminal device 40 with sufficient remaining power to communicate.
[0068] <<2. Configuration of communication system>>
[0069] <2.1. Configuration Example of Information Processing Equipment>
[0070] The information processing device 10 is connected to the network N (see Figure 1 ). For example, the information processing device 10 is an information processing device that implements at least a part of the functions of the core network CN. For example, the information processing device 10 is an information processing device that implements at least a part of the functions of the RAMNF 100. For example, the information processing device 10 is an information processing device that implements at least a part of the functions of the client 200.
[0071] Figure 2 1 is a diagram showing a configuration example of an information processing device 10 according to an embodiment of the present disclosure. The information processing device 10 includes a communication unit 11, a storage unit 12, and a control unit 13. It should be noted that Figure 2 The configuration shown in is a functional configuration, and the hardware configuration may be different from this. In addition, the functions of the information processing device 10 may be statically or dynamically distributed and implemented in multiple physically separated components. For example, the information processing device 10 may be implemented by multiple server devices.
[0072] The communication unit 11 is a communication interface for communicating with another device. The communication unit 11 may be a network interface, or may be an equipment connection interface. For example, the communication unit 11 may be a local area network (LAN) interface such as a network interface card (NIC), or may be a universal serial bus (USB) interface including a USB host controller, a USB port, etc. In addition, the communication unit 11 may be a wired interface or a wireless interface. The communication unit 11 acts as a communication device of the information processing device 10. The communication unit 11 communicates with another information processing device 10, a base station 20, etc. under the control of the control unit 13.
[0073] The storage unit 12 is a storage device from which data can be read and in which data can be written, such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, or a hard disk. The storage unit 12 serves as storage means of the information processing device 10.
[0074] The control unit 13 is a controller that controls each unit of the information processing device 10. The control unit 13 is implemented by a processor such as a central processing unit (CPU), a microprocessing unit (MPU), or a graphics processing unit (GPU). For example, the control unit 13 is implemented by causing the processor to execute various programs stored in a storage device inside the information processing device 10 using a random access memory (RAM) or the like as a work area. It should be noted that the control unit 13 can be implemented by an integrated circuit such as an application-specific integrated circuit (ASIC) or a field programmable gate array (FPGA). CPU, MPU, GPU, ASIC, and FPGA can all be regarded as controllers.
[0075] <2.2. Base station configuration example>
[0076] The base station 20 is a communication device that operates a cell and provides wireless communication services to one or more terminal devices 40 located within the coverage area of the cell. The cell can be operated according to any wireless communication scheme such as LTE or New Radio (NR). The base station 20 is connected to the core network CN. The core network CN is connected to the packet data network through a gateway device.
[0077] It should be noted that the base station 20 may include a collection of multiple physical or logical devices. For example, in an embodiment according to the present disclosure, the base station 20 is classified into multiple devices including a baseband unit (BBU) and a radio unit (RU), and may be interpreted as a collection of these multiple devices. In addition or alternatively, in an embodiment according to the present disclosure, the base station 20 may be either or both of the BBU and the RU. The BBU and the RU may be connected via a predetermined interface (e.g., eCPRI). In addition or alternatively, the RU may be referred to as a remote radio unit (RRU) or a radio DoT (RD). In addition or alternatively, the RU may correspond to a gNB distributed unit (gNB-DU) described later. In addition or alternatively, the BBU may correspond to a gNB-CU described later. Alternatively, the RU may be connected to a gNB-DU described later. In addition, the BBU may correspond to a combination of a gNB-CU and a gNB-DU described later. In addition or alternatively, the RU may be a device formed integrally with an antenna. The antenna of the base station 20 (e.g., an antenna formed integrally with the RU) may adopt an advanced antenna system and support MIMO (e.g., FD-MIMO) or beamforming. In an advanced antenna system, the antenna of the base station 20 (eg, an antenna integrated with the RU) may include, for example, 64 transmit antenna ports and 64 receive antenna ports.
[0078] In addition, a plurality of base stations 20 may be connected to each other. One or more base stations 20 may be included in a radio access network (RAN). That is, the base station 20 may be simply referred to as a RAN, a RAN node, an access network (AN), or an AN node. The RAN in LTE is referred to as an enhanced universal terrestrial RAN (EUTRAN). The RAN in NR is referred to as an NGRAN. The RAN in W-CDMA (UMTS) is referred to as an UTRAN. The base station 20 in LTE is referred to as an evolved Node B (eNodeB) or an eNB. That is, the EUTRAN includes one or more eNodeBs (eNBs). In addition, the base station 20 of NR is referred to as a gNodeB or a gNB. That is, the NGRAN includes one or more gNBs. In addition, the EUTRAN may include a gNB (ng-eNB) connected to a core network (EPC) in a communication system (EPS) of LTE. Similarly, the NGRAN may include a gNB connected to a core network (5GC) in a 5G communication system (5GS). In addition or alternatively, in the case where the base station 20 is an eNB, a gNB, etc., the base station may be referred to as a 3GPP access. Additionally or alternatively, in the case where the base station 20 is a wireless access point (e.g., an access point of WiFi (registered trademark)), the base station 20 may be referred to as a non-3GPP access. Additionally or alternatively, the base station 20 may be an optical feeding device referred to as a remote radio head (RRH). Additionally or alternatively, in the case where the base station 20 is a gNB, the base station 20 may be referred to as a combination of or any one of the gNB central unit (CU) and gNB distributed unit (DU) described above. The gNB central unit (CU) hosts multiple upper layers of the access layer (e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and PDCP) for communication with the UE. On the other hand, the gNB-DU hosts multiple lower layers of the access layer (e.g., RLC, MAC, and PHY). That is, among the messages and information to be described later, RRC signaling (e.g., various system information blocks (SIBs) including the master information block (MIB) and SIB1, RRCSetup messages, and RRCReconfiguration messages) may be generated by the gNB CU, and the downlink control indicator (DCI) and various physical channels (e.g., PDCCH and PBCH) to be described later may be generated by the gNB-DU. Alternatively, for example, in the RRC signaling, some configurations (configuration information) such as IE:cellGroupConfig may be generated by the gNB-DU, and the rest of the configurations may be generated by the gNB-CU. These configurations (configuration information) may be sent and received via the F1 interface to be described later. The base station 20 may be configured to be able to communicate with another base station 20.For example, in the case where the multiple base stations 20 are a combination of eNBs or eNBs and gn-eNBs, the base stations 20 may be connected via an X2 interface. Additionally or alternatively, in the case where the multiple base stations 20 are a combination of eNBs or gn-eNBs and gNBs, the devices may be connected via an Xn interface. Additionally or alternatively, in the case where the multiple base stations 20 are a combination of gNB CUs and gNB DUs, the devices may be connected via the F1 interface described above. Messages / information (RRC signaling, DCI information, or physical channels) to be described later may be transmitted between multiple base stations 20 (e.g., via an X2, Xn, or F1 interface).
[0079] In addition, as described above, the base station 20 can be configured to manage multiple cells. The cell provided by the base station 20 is called a service cell. The service cell includes a primary cell (PCell) and a secondary cell (SCell). In the case of providing dual connectivity (e.g., EUTRA-EUTRA dual connectivity, EUTRA-NR dual connectivity (ENDC), EUTRA-NR dual connectivity with 5GC, NR-EUTRA dual connectivity (NEDC) or NR-NR dual connectivity) for a UE (e.g., a terminal device 40), the PCell provided by the leading node (MN) and zero or one or more SCells are referred to as a leading cell group. In addition, the service cell may include a primary secondary cell or a primary SCG cell (PSCell). That is, in the case of providing dual connectivity for a UE, the PSCell provided by a secondary node (SN) and zero or one or more SCells are referred to as a secondary cell group (SCG). Unless specially configured (e.g., a physical uplink control channel (PUCCH) on an SCell), the PUCCH is sent by the PCell and the PSCell, but not by the SCell. Radio link failure is detected in PCell and PSCell, but not in SCell (does not need to be detected). As described above, since PCell and PSCell have special roles in (multiple) serving cells, they are also called special cells (SpCell). One downlink component carrier and one uplink component carrier can be associated with one cell. In addition, the system bandwidth corresponding to one cell can be divided into multiple bandwidth parts. In this case, one or more bandwidth parts (BWP) can be set in the UE, and one bandwidth part can be used as an active BWP in the UE. In addition, the radio resources (such as frequency band, parameter set (subcarrier spacing) and time slot configuration) that can be used by the terminal device 40 can be different for each cell, each component carrier or each BWP.
[0080] Figure 3is a diagram showing a configuration example of the base station 20 according to an embodiment of the present disclosure. The base station 20 is a communication device (wireless system) that performs wireless communication with the terminal device 40. The base station 20 is a type of information processing device.
[0081] The base station 20 includes a signal processing unit 21, a storage unit 22, a network communication unit 23 and a control unit 24. It should be noted that Figure 3 The configuration shown in is a functional configuration, and the hardware configuration may be different from this. In addition, the functions of the base station 20 may be distributed to and implemented in a plurality of physically separated devices.
[0082] The signal processing unit 21 is a wireless communication interface for implementing wireless communication with other communication devices (e.g., terminal device 40 and another base station 20). The signal processing unit 21 is a wireless transceiver that operates under the control of the control unit 24. The signal processing unit 21 can support multiple radio access schemes. For example, the signal processing unit 21 can support both NR and LTE. The signal processing unit 21 can support other cellular communication schemes such as W-CDMA or cdma2000. In addition, the signal processing unit 21 can also support wireless LAN communication schemes in addition to the cellular communication scheme. Of course, the signal processing unit 21 can only support one radio access scheme.
[0083] The signal processing unit 21 includes a receiving processing unit 211, a transmitting processing unit 212, and an antenna 213. The signal processing unit 21 may include a plurality of receiving processing units 211, a plurality of transmitting processing units 212, and a plurality of antennas 213. It should be noted that, in the case where the signal processing unit 21 supports multiple radio access schemes, each unit of the signal processing unit 21 may be configured separately for each radio access scheme. For example, in the case where the base station 20 supports NR and LTE, the receiving processing unit 211 and the transmitting processing unit 212 may be configured separately for NR and LTE, respectively.
[0084] The reception processing unit 211 processes an uplink signal received through the antenna 213. The reception processing unit 211 includes a wireless reception unit 211a, a demultiplexing unit 211b, a demodulation unit 211c, and a decoding unit 211d.
[0085] The wireless receiving unit 211a performs down-conversion, removal of unnecessary frequency components, control of amplification level, orthogonal demodulation, conversion to digital signals, removal of guard intervals, extraction of frequency domain signals by fast Fourier transform, etc. on the uplink signal. For example, it is assumed that the radio access scheme of the base station 20 is a cellular communication scheme such as LTE. At this time, the demultiplexing unit 211b separates the uplink channel (such as the physical uplink shared channel (PUSCH) or the physical uplink control channel (PUCCH)) and the uplink reference signal from the signal output from the wireless receiving unit 211a. The demodulation unit 211c performs demodulation of the received signal by using a modulation scheme such as binary phase shift keying (BPSK) or quadrature phase shift keying (QPSK) for the modulation symbol of the uplink channel. The modulation scheme used by the demodulation unit 211c can be multi-level QAM, such as 16-quadrature amplitude modulation (QAM), 64-QAM or 256-QAM. The decoding unit 211d performs decoding processing on the coded bits of the demodulated uplink channel. The decoded uplink data and uplink control information are output to the control unit 24 .
[0086] The transmission processing unit 212 performs transmission processing of downlink control information and downlink data. The transmission processing unit 212 includes a coding unit 212a, a modulation unit 212b, a multiplexing unit 212c, and a wireless transmission unit 212d.
[0087] The coding unit 212a encodes the downlink control information and downlink data input from the control unit 24 by using a coding method such as block coding, convolution coding or turbo coding. The modulation unit 212b modulates the coded bits output from the coding unit 212a by a predetermined modulation scheme such as BPSK, QPSK, 16-QAM, 64-QAM or 256-QAM. The multiplexing unit 212c multiplexes the modulation symbols and downlink reference signals of each channel and maps them to a predetermined resource unit. The wireless transmission unit 212d performs various signal processing on the signal from the multiplexing unit 212c. For example, the wireless transmission unit 212d performs processing such as conversion to the time domain by fast Fourier transform, adding a guard interval, generating a baseband digital signal, converting to an analog signal, orthogonal modulation, up-conversion, removing redundant frequency components or power amplification. The signal generated by the transmission processing unit 212 is transmitted from the antenna 213.
[0088] The storage unit 22 is a storage device such as a DRAM, an SRAM, a flash memory, or a hard disk from which data can be read and in which data can be written. The storage unit 22 serves as a storage device of the base station 20.
[0089] The network communication unit 23 is a communication interface for communicating with other devices (e.g., another base station 20). For example, the network communication unit 23 is a local area network (LAN) interface such as a network interface card (NIC). The network communication unit 23 may be a universal serial bus (USB) interface including a USB host controller, a USB port, etc. In addition, the network communication unit 23 may be a wired interface or a wireless interface. The network communication unit 23 acts as a network communication device of the base station 20. The network communication unit 23 communicates with another device under the control of the control unit 24.
[0090] The control unit 24 is a controller that controls each unit of the base station 20. The control unit 24 is implemented by a processor such as a central processing unit (CPU) or a microprocessing unit (MPU), for example. For example, the control unit 24 is implemented by causing the processor to execute various programs stored in a storage device inside the base station 20 using a random access memory (RAM) or the like as a work area. It should be noted that the control unit 24 can be implemented by an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA). CPU, MPU, ASIC and FPGA can all be regarded as controllers.
[0091] <2.3. Configuration example of terminal equipment>
[0092] The terminal device 40 is a communication device that performs wireless communication with the base station 20 under the control of the base station 20 .
[0093] The terminal device 40 is a wireless communication device that implements wireless communication with other devices. The terminal device 40 is, for example, a sensor or camera device with a communication function, a mobile phone, a smart device (smart phone or tablet PC), a personal digital assistant (PDA), or a personal computer. The terminal device 40 can be a head-mounted display, VR glasses, etc. with the function of wirelessly sending and receiving data. The terminal device 40 can be a mobile subject such as a car or a drone.
[0094] For example, the terminal device 40 implements wireless communication with another terminal device 40 under the control of the base station 20 or autonomously. In this case, the terminal device 40 sends a sidelink signal to another terminal device 40 in the PC5 link, and receives a sidelink signal from another terminal device 40. The transmission and reception of the sidelink signal of the terminal device 40 will be collectively referred to as sidelink communication. When implementing the sidelink communication, the terminal device 40 may be able to use an automatic retransmission technology such as a hybrid automatic repeat request (HARQ).
[0095] The terminal device 40 may be capable of non-orthogonal multiple access (NOMA) communication with the base station 20. The terminal device 40 may also be capable of implementing NOMA communication for communication (sidelink) with another terminal device 40. In addition, the terminal device 40 may be capable of implementing low power wide area (LPWA) communication with another communication device (e.g., the base station 20 and another terminal device 40). In addition, the wireless communication used by the terminal device 40 may be wireless communication using millimeter waves or terahertz waves. It should be noted that the wireless communication (including sidelink communication) used by the terminal device 40 may be wireless communication using radio waves or may be (optical) wireless communication using infrared or visible light.
[0096] Figure 4 is a diagram showing a configuration example of a terminal device 40 according to an embodiment of the present disclosure. The terminal device 40 is a communication device (wireless system) that performs wireless communication with the base station 20. The terminal device 40 is a type of information processing device.
[0097] The terminal device 40 includes a signal processing unit 41, a storage unit 42, an input / output unit 44, and a control unit 45. It should be noted that Figure 4 The configuration shown in FIG. 4 is a functional configuration, and the hardware configuration may be different from this. In addition, the functions of the terminal device 40 may be distributed and implemented in a plurality of physically separated components.
[0098] The signal processing unit 41 is a wireless communication interface for implementing wireless communication with other communication devices (e.g., the base station 20 and another terminal device 40). The signal processing unit 41 is a wireless transceiver that operates under the control of the control unit 45. The signal processing unit 41 supports one or more radio access schemes. For example, the signal processing unit 41 supports both NR and LTE. The signal processing unit 41 may support another radio access scheme such as W-CDMA or cdma2000.
[0099] The signal processing unit 41 includes a reception processing unit 411, a transmission processing unit 412, and an antenna 413. The signal processing unit 41 may include a plurality of reception processing units 411, a plurality of transmission processing units 412, and a plurality of antennas 413. It should be noted that in the case where the signal processing unit 41 supports a plurality of radio access schemes, each unit of the signal processing unit 41 may be configured separately for each radio access scheme. For example, the reception processing unit 411 and the transmission processing unit 412 may be configured separately for LTE and NR, respectively. The configurations of the reception processing unit 411 and the transmission processing unit 412 are similar to those of the reception processing unit 211 and the transmission processing unit 212 of the base station 20.
[0100] The storage unit 42 is a storage device from which data can be read and in which data can be written, such as a DRAM, an SRAM, a flash memory, or a hard disk. The storage unit 42 serves as a storage device of the terminal device 40.
[0101] The input / output unit 44 is a user interface for exchanging information with a user. For example, the input / output unit 44 is an operating device for the user to perform various operations, such as a keyboard, a mouse, an operating key, and a touchpad. Alternatively, the input / output unit 44 is a display device such as a liquid crystal display or an organic electroluminescent (EL) display. The input / output unit 44 can be an audio device such as a speaker or a buzzer. In addition, the input / output unit 44 can be a lighting device such as a light emitting diode (LED) lamp. The input / output unit 44 acts as an input / output device (input device, output device, operating device, or notification device) of the terminal device 40.
[0102] The control unit 45 is a controller that controls each unit of the terminal device 40. The control unit 45 is implemented by a processor such as a CPU or an MPU, for example. For example, the control unit 45 is implemented by causing the processor to execute various programs stored in a storage device inside the terminal device 40 using a RAM or the like as a work area. It should be noted that the control unit 45 can be implemented by an integrated circuit such as an ASIC or an FPGA. CPU, MPU, ASIC, and FPGA can all be regarded as controllers.
[0103] <<3. Network Architecture>>
[0104] The configuration of the information processing system 1 is described above. Next, the network architecture of the information processing system 1 applicable to the present embodiment will be described. As an example of the core network CN of the information processing system 1, the architecture of the fifth generation mobile communication system (5G) will be described below. The 5G architecture described in this article is described in 3GPP TS23.501, for example.
[0105] Figure 5 is a diagram showing an example of a 5G architecture. The core network CN of 5G is also referred to as 5G core / next generation core (5GC / NGC). In the following text, the core network CN of 5G is also referred to as 5GC / NGC. The core network CN is connected to a user equipment (UE) 40 via (R)AN 20. UE 40 is, for example, a terminal device 40.
[0106] (R)AN 20 has a function of achieving connection to a radio access network (RAN) and connection to an access network (AN) other than the RAN. (R)AN 20 includes a base station 20 referred to as a gNB or ng-eNB.
[0107] The core network CN mainly implements connection permission and session management when the UE 40 is connected to the network. The core network CN may include a user plane function group 420 and a control plane function group 440.
[0108] The user plane function group 420 includes a user plane function (UPF) 421 and a data network (DN) 422. The UPF 421 has a user plane processing function. The UPF 421 has a function of routing / forwarding data handled in the user plane. The DN 422 is, for example, an entity that provides access to services specific to operators such as mobile network operators (MNOs), and has a function of providing Internet connection or providing access to services for third parties. As described above, the user plane function group 420 plays the role of a gateway that serves as a boundary between the core network CN and the Internet.
[0109] The control plane function group 440 includes an access management function (AMF) 441, a session management function (SMF) 442, an authentication server function (AUSF) 443, a network slice selection function (NSSF) 444, a network exposure function (NEF) 445, a network repository function (NRF) 446, a policy control function (PCF) 447, a unified data management (UDM) 448 and an application function (AF) 449.
[0110] AMF 441 has functions such as registration processing, connection management, and mobility management for UE 40. SMF 442 has functions such as session management and IP assignment and management for UE 40. AUSF 443 has an authentication function. NSSF 444 has functions related to the selection of network slices. NEF 445 has a function of providing network function capabilities and events to a third party AF 449 and an edge computing function.
[0111] The NRF 446 has a function of discovering network functions and maintaining profiles of network functions. The PCF 447 has a policy control function. The UDM 448 has a function of generating 3GPP AKA authentication information and processing user IDs. The AF 449 has a function of interacting with the core network CN to provide services.
[0112] For example, the control plane function group 440 acquires information from the UDM 448 in which the subscriber information of the UE 40 is stored, and determines whether the UE 40 can connect to the network. For such determination, the control plane function group 440 uses the contract information of the UE 40 and the key for encryption included in the information acquired from the UDM 448. In addition, the control plane function group 440 generates the key for encryption and the like.
[0113] That is, the control plane function group 440 determines whether it is possible to connect to the network, for example, based on whether information of the UE 40 associated with a subscriber number called an International Mobile Subscriber Identity (IMSI) is stored in the UDM 448. It should be noted that the IMSI is stored in a Subscriber Identity Module (SIM) card in the UE 40, for example.
[0114] Here, Namf is a service-based interface provided by AMF 441, and Nsmf is a service-based interface provided by SMF 442. In addition, Nnef is a service-based interface provided by NEF 445, and Npcf is a service-based interface provided by PCF 447. Nudm is a service-based interface provided by UDM 448, and Naf is a service-based interface provided by AF 449. Nnrf is a service-based interface provided by NRF 446, and Nnssf is a service-based interface provided by NSSF 444. Nausf is a service-based interface provided by AUSF 443. Each network function (NF) exchanges information with another NF through its respective service-based interface.
[0115] also, Figure 5 N1 shown in FIG. 4 is a reference point between UE 40 and AMF 441, and N2 is a reference point between (R)AN 20 and AMF 441. N4 is a reference point between SMF 442 and UPF 421, and information is exchanged between network functions (NFs).
[0116] As described above, an interface for transmitting information and controlling functions through an application programming interface (API) called a service-based interface (SBI) is prepared in the core network CN.
[0117] The API specifies resources and implements GET (resource acquisition), POST (resource creation and data addition), PUT (resource creation and resource update), DELETE (resource deletion), etc. Such functions are generally used in, for example, web-related technical fields.
[0118] For example, in the case of establishing a communication session, Figure 5 The AMF 441, SMF 442, and UDM 448 shown in FIG. send and receive information to each other by using an API. It is not assumed that an application (e.g., AF 449) uses such an API so far. However, when AF 449 uses such an API, AF 449 can use information of the 5G cellular network, and it is believed that the functions of the application can be further evolved.
[0119] It should be noted that in a public network, it is difficult for AF 449 to use the API used by AMF 441, SMF 442 and UDM 448. However, in the case of a non-public private 5G network, it is believed that the system may, for example, include a modification of the API of the core network CN so that AF 449 can use such an API.
[0120] (Private 5G)
[0121] An example of a non-public private 5G network will be described here. Figure 6 is a diagram for describing a configuration example of a private 5G network according to an embodiment of the present disclosure.
[0122] Currently, a local area network (LAN) is arranged in many offices and homes. The LAN includes, for example, an Ethernet cable, a router, etc. The LAN is connected to the Internet by using the services of an Internet Service Provider (ISP). The LAN and the cloud are connected, for example, through a virtual private network (VPN). In a VPN, packets are basically routed by private IP addresses. In the case of sending packets outside the VPN, the packets are sent outside the VPN through a gateway router (not shown).
[0123] The private 5G is operated by placing the cellular base station 20 in the LAN. That is, in the private 5G, a plurality of base stations 20_1 to 20_M (M is a natural number), a plurality of UEs 40_1 to 40_N (N is a natural number), and some functions of the CN of the core network are arranged in the LAN. In addition, the remaining functions of the core network CN are arranged in a data center in the cloud of the Internet line, for example.
[0124] exist Figure 6 In the example of , UPF 421_1 to 421_p (p is a natural number and p≤P) are arranged in the LAN. UPF 421_p+1 to 421_P (P is a natural number) are arranged in the cloud of the Internet line. It should be noted that here UPF 421 is arranged in the LAN and / or the cloud, on the contrary, the user plane function group 420 can be arranged in the LAN and / or the cloud.
[0125] In addition, a control plane function group 440 (hereinafter also referred to as CPF 440) is arranged in the cloud of the Internet line.
[0126] As described above, in private 5G, the base station 20 and the UE 40 are arranged in an office, factory, or private residence in which a LAN is arranged. At the same time, the core network CN that controls the base station 20 may be arranged in the LAN, or may be arranged in a data center in the cloud in the Internet. It should be noted that Figure 6It is an example, and at least some functions of CPF 440 may be arranged in the LAN. In addition, all UPF 421 may be arranged in the LAN, or may be arranged in the cloud.
[0127] Private IP addresses are assigned to the base station 20 and the core network CN. The base station 20 and the core network CN are arranged in an environment where the base station 20 and the core network CN can communicate with each other. For example, by using a technology such as VPN, the base station 20 and the core network CN can communicate with each other using private IP addresses.
[0128] That is, the network connecting the base station 20 and the core network CN can be treated as a private network.
[0129] It should be noted that when the CPF 440 is activated or when the operation of the core network CN starts, the UPFs 421_1 to 421_p arranged in the LAN exist in the LAN. On the other hand, when the CPF 440 is activated or when the operation of the core network CN starts, the UPFs 421_p+1 to 421_P arranged in the cloud do not exist in the cloud. The UPFs 421_p+1 to 421_P are, for example, functions that are activated after the CPF 440 is activated or after the operation of the core network CN starts.
[0130] In summary, private 5G can be a non-public network. In practice, UE 40, base station 20, core network CN and applications with client functions are highly likely to be arranged inside VPN. UE 40 and base station 20 are arranged in LAN. Core network CN and applications can be arranged in LAN or in the cloud of the Internet.
[0131] (API)
[0132] An example of the API will be described here. Figure 7 is a diagram for describing an API according to an embodiment of the present disclosure. API (1) to API (4) described here are described in 3GPP TS23.502.
[0133] As described above, UE 40, base station 20 and core network CN are arranged in virtual LAN (VPN 500). Base station 20 and core network CN communicate with a network outside VPN (eg, Internet) through gateway router 510.
[0134] API(1)
[0135] API (1) is an API used by the SMF 442 to notify the fact that the pre-registered UE 40 transitions from the power-off state to the power-on state and attaches to the network, and the IP address acquired at this time.
[0136] The SMF 442 notifies the NF when the UE 40 of the registered IMSI obtains the IP address by using API (1).
[0137] API(2)
[0138] The UE 40 enters the idle mode when no communication is performed, and transitions to the connected mode when communication is performed. API (2) is an API used by the AMF 441 to notify whether the UE 40 is in the idle mode or the connected mode.
[0139] API(3)
[0140] API (3) is an API for broadcasting a message (paging message) for instructing UE 40 to transition from idle mode to connected mode from base station 20. API (3) can be used, for example, when a packet addressed to UE 40 in idle mode arrives at UPF 421.
[0141] API(4)
[0142] API (4) is an API used by AMF 441 to provide location information of UE 40. AMF 441 can use API (4) to notify which tracking area UE 40 is in, which cell UE 40 belongs to, and when UE 40 enters a specific area, notify the fact that UE 40 enters the specific area.
[0143] It should be noted that the location information obtained by using the API (4) is, for example, information having lower accuracy than the location information obtained by the global positioning system (GPS). For example, the location information obtained by the GPS is information in units of longitude and latitude, while the location information obtained by using the API (4) is information in units of cells of the base station 20, for example.
[0144] For example, the location information obtained by GPS is location information of the application layer of the UE 40 equipped with GPS. On the other hand, the location information obtained by API (4) is location information provided from the 3GPP RAN 1 through the AMF 441. The API (API (4)) for acquiring the location information of the 3GPP RAN 1 is provided in the AMF 441.
[0145] It should be noted that Figure 5 An example of the UE 40 is the terminal device 40 of the present embodiment. An example of the (R)AN 20 is the base station 20 of the present embodiment. Figure 2 The information processing device 10 shown in FIG. 1 is, for example, an example of a device having each function of the core network CN.
[0146] <<4. Technical Features>>
[0147] <4.1、RAMNF>
[0148] <4.1.1 Overview of RAMNF>
[0149] Here, in conventional 5G, the network function (NF) of the core network CN uses an API based on the interface of the 5G service. In this embodiment, since a platform called RAMNF 100 is provided, services and applications (that is, the client 200 and the terminal device 40) can more easily obtain information of the core network CN. As a result, the services provided by the client 200 can be further evolved.
[0150] Figure 8 1 is a diagram showing an example of an information processing system 1 according to an embodiment of the present disclosure. Figure 8 As shown in FIG, the client 200 for the service sends and receives user data through the RAMNF 100 or directly with the UPF 421. In addition, the client 200 communicates with the CPF 440 through the RAMNF 100. The RAMNF 100 communicates with the AMF 441 and the SMF 442 through the SBI API.
[0151] For example, before communicating with the terminal device 40, the service-side client 200 queries the RAMNF 100 for the status of the target terminal device 40 (that is, the terminal device 40 with which communication is to be implemented).
[0152] In the case where the query result indicates that the terminal device 40 is deregistered (a state in which an IP address is not assigned), the client 200 does not perform communication with the terminal device 40. As a result, the client 200 can avoid transmitting unnecessary packets.
[0153] Furthermore, even in the case where the terminal device 40 is registered (a state where an IP address is assigned), when the terminal device 40 is in an idle state, the client 200 can be prevented from performing communication with the terminal device 40 .
[0154] When a packet is sent to the terminal device 40 in the idle state, a paging is automatically sent to the terminal device 40, and the terminal device 40 is activated (transitioned to the connected state). For example, in the case where the terminal device 40 is a low power consumption type device, the client 200 can avoid sending packets to the terminal device 40 in the idle state, and instead send packets to the terminal device 40 in the connected state. As a result, the client 200 can prevent the terminal device 40 from being activated unnecessarily, and can further reduce the power consumption of the terminal device 40.
[0155] In addition, when the terminal device 40 is not a low power consumption type device, the client 200 can send a packet to the terminal device 40 in an idle state. At this time, for example, it is assumed that the client 200 sends a paging message to the terminal device 40 in advance using the API of the AMF 441 through the RAMNF 100 before sending the packet.
[0156] For example, in a general cellular system, the client 200 sends a packet to the terminal device 40 in the idle state without causing the terminal device 40 to transition to the connected state. In this case, a paging message for causing the terminal device 40 to transition to the connected state is sent after the packet arrives at the UPF 421. Therefore, in a general cellular system, a large delay occurs when sending a packet to the terminal device 40 in the idle state.
[0157] On the other hand, as described above, when the RAMNF 100 is used, the client 200 according to the present embodiment can cause the state of the terminal device 40 to transition to the connected state before actually sending a packet to the terminal device 40. As a result, the client 200 can further reduce the packet delay time.
[0158] <4.1.2、RAMNF issues>
[0159] It is believed that the demand for obtaining more detailed information of the network (eg, core network CN) by the client 200 providing the service is increasing. This is because the service quality is expected to be higher than before (eg, low latency and low power consumption) through the cooperation between the network and the service.
[0160] As described above, in order for the RAMNF 100 to send more detailed information of the network to the client 200, the RAMNF 100 needs to collect more detailed information of the network.
[0161] Here, the network includes, for example, at least one of the following states.
[0162] - Status of base station 20
[0163] - Status of the core network CN
[0164] - Status of the terminal device 40
[0165] - Traffic status
[0166] - The capability status of at least one of the base station 20, the core network CN or the terminal device 40 requires a mechanism for collecting more detailed information about these statuses.
[0167] Next, the RAMNF 100 may be required to more efficiently deliver information about the network to the client 200. For example, the RAMNF 100 sends information about a plurality of terminal devices 40 as a group to the client 200, so that the client 200 can more appropriately grasp the information of the network in some cases.
[0168] Finally, there may be a situation where the client 200 wishes to control the state of the network in more detail. This is because it may be more beneficial to the service if the network operates as the client 200 expects.
[0169] As described above, it is desirable that the RAMNF 100 also has the following functions.
[0170] (1) Function to collect more detailed information about the network
[0171] (2) Function of providing network information to the client 200 in an easily understandable manner
[0172] (3) Function for implementing control in more detail by the client 200
[0173] More detailed problems and solutions for implementing these functions will be described later. It should be noted that since (1) and (2) can be operated in an integrated manner, the problems and solutions of (1) and (2) can be described simultaneously.
[0174] <4.2. First Embodiment>
[0175] <4.2.1. First question>
[0176] It is desirable that the client 200 can know the time after which the terminal device 40 transitions from the connected mode (state) to the idle mode (state) if no communication is performed. That is, it cannot be said that the client 200 can correctly grasp the information of the network. In other words, it is desirable to enable the RAMNF 100 to collect more detailed registration information about the registration of the terminal device 40.
[0177] As an API of 5G SBI, for example, an API of paging (a function of calling a terminal device 40 in an idle mode) using AMF 441, the RAMNF 100 can instruct the terminal device 40 in an idle mode to transition to a connected mode.
[0178] Here, idle mode means RRC idle state, and means a state where the wireless part between the terminal device 40 and the base station 20 is disconnected. Also, connected mode means RRC connected state, and means a state where the wireless part between the terminal device 40 and the base station 20 is connected.
[0179] The RAMNF 100 can cause the terminal device 40 to transition to the connected mode by activating the API of the AMF 441 in response to a request from the client 200. As a result, the RAMNF 100 can cause the counterpart terminal device 40 with which the client 200 wishes to communicate to transition to the connected mode in advance at the timing when the client 200 starts communication.
[0180] It is desirable to enable the RAMNF 100 to know the time when the terminal device 40 transitions to the idle mode after transitioning to the connected mode once. That is, it is desirable that the RAMNF 100 can know the idle transition time information indicating the time until the terminal device 40 transitions from the connected mode to the idle mode.
[0181] For example, in the case where the RAMNF 100 cannot know the idle transition time information, the RAMNF 100 needs to obtain registration information about the registration of the terminal device 40 by using the API of the AMF 441 before the client 200 sends a packet. Here, the registration information includes information indicating the state of the terminal device 40 (e.g., whether the terminal device 40 is in a connected mode or an idle mode).
[0182] In the case where the terminal device 40 is in the idle mode, the RAMNF 100 needs to implement paging control by using the API of the AMF 441 so that the terminal device 40 transitions to the connected mode.
[0183] The idle transition time is different for each terminal device 40. For example, some terminal devices 40 transition to the idle mode in about one second, and some terminal devices 40 transition to the idle mode in about six seconds. In a state where the idle transition time is uncertain, it cannot be said that the RAMNF 100 sends appropriate information of the network to the client 200.
[0184] The idle transition time (idle return time) is configured by the base station 20 according to the capability of the terminal device 40 . Fig. 9 : is a sequence diagram showing a configuration example of the idle transition time of the base station 20. Fig. 9 The sequence shown in is described, for example, in Section 5.19 of 3GPP TS38.321 or Section 5.3.9 of TS38.331.
[0185] like Fig. 9As shown in , the base station 20 configures the duration (data inactivity timer) for the terminal device 40 to transition to the idle mode according to the capability of the terminal device 40. Therefore, it is considered that the idle transition time is a value configured according to both the terminal device 40 and the base station 20. However, it is difficult for the RAMNF 100 to obtain information about the configuration implemented by the base station 20 (e.g., information about the data inactivity timer) from all the base stations 20, and therefore it is not easy to obtain the idle transition time information.
[0186] <4.2.2. Example of solution to the first problem>
[0187] Fig.10 is a sequence diagram showing an example of the flow of the first information processing according to the first embodiment of the present disclosure. Fig.10 The first information processing shown in is implemented by the information processing system 1 .
[0188] like Fig.10 As shown in , the CPF 440 (eg AMF 441) on the network side configures a data inactivity timer value for the UE 40 (terminal device 40) (step S101).
[0189] The AMF 441 configures the value (data inactivity timer value) in consideration of the specification of the UE 40 and the specification of the base station 20. The data inactivity timer value is, for example, a value such as one second or six seconds.
[0190] If there is no transmission / reception of uplink (UL) and / or downlink (DL) data between UE 40 and base station 20 for a period of time of this value, UE 40 transitions from connected mode to idle mode.
[0191] It should be noted that although the AMF 441 configures the data inactivity timer value here, the configuration can also be implemented by the base station 20.
[0192] Next, the RAMNF 100 implements UE status registration for notifying the RAMNF 100 of the status of the UE 40 (UE status) from the AMF 441 (step S102).
[0193] The RAMNF 100 registers the UE 40 so that the AMF 441 is notified when the state of the UE 40 changes, such as when the UE 40 transitions from a connected mode to an idle mode, or when the UE transitions from an idle mode to a connected mode. For example, the ID of the UE 40 (e.g., a subscription permanent identifier (SUPI)) can be used for this registration.
[0194] If the UE 40 is in the idle mode, the RAMNF 100 requests the AMF 441 for a paging request (step S103). The RAMNF 100 requests the AMF 441 to send a paging to the UE 40 by using the API of the SBI of the AMF 441.
[0195] A paging procedure is implemented between the AMF 441 of the CPF 440 and the UE 40 (step S104). Accordingly, the UE 40 becomes connected (step S105).
[0196] The AMF 441 of the CPF 440 notifies the RAMNF 100 of the state (UE state) of the UE 40 (step S106). Here, the AMF 441 makes a notification that the state of the UE 40 is the connected state. Since the RAMNF 100 performs the UE state registration with respect to the AMF 441 in step S102, the AMF 441 notifies the RAMNF 100 of the state change of the UE 40 (here, the transition from the idle mode to the connected mode).
[0197] Upon receiving the notification, the RAMNF 100 starts the timer (step S107). That is, the RAMNF 100 starts time measurement by the timer.
[0198] like Fig.10 As shown in , when the data inactivity timer expires without UL / DL data transmission (step S108), the UE 40 transitions from the connected mode to the idle mode.
[0199] Since both UE 40 and AMF 441 have data inactivity timers, AMF 441 knows that UE 40 has transitioned to idle mode. In this case, AMF 441 notifies RAMNF 100 of the state of UE 40 (step S109).
[0200] Here, the AMF 441 notifies that the state of the UE 40 is the idle state. Since the RAMNF 100 performs UE state registration with respect to the AMF 441 in step S102, the AMF 441 notifies the RAMNF 100 of the state change of the UE 40 (here, transition from the idle mode to the connected mode).
[0201] The RAMNF 100 receiving the notification stops the timer started in step S107 and calculates the estimated data inactivity timer based on the measurement time of the timer (step S110). For example, the RAMNF 100 estimates the measurement time of the timer as the idle transition time until the UE 40 transitions to the idle state.
[0202] In this way, the RAMNF 100 acquires the first information (here, registration information about the registration (eg, UE status) of the UE 40). The RAMNF 100 calculates information about the transition interval of the registration (an example of measurement time, here, idle transition time information) based on the acquired first information.
[0203] It should be noted that here, AMF 441 makes a notification of the UE status based on the UE status registration of RAMNF 100, but the method by which RAMNF 100 obtains the UE status is not limited to this.
[0204] For example, the RAMNF 100 may periodically (e.g., every 0.5 seconds) send a request to the AMF 441 for knowing the state of the UE 40. In this case, the RAMNF 100 calculates the idle transition time based on the state change of the UE 40 included in the response from the AMF 441.
[0205] The RAMNF 100 notifies the client 200 of the data inactivity timer (step S111). For example, the RAMNF 100 notifies the client 200 of the idle transition time calculated in step S110 as the data inactivity timer.
[0206] The client 200 may know the appropriate access duration to prevent the UE 40 from entering the idle mode (step S112). That is, in the case of continuously sending data to the UE 40, if the client 200 sends data at intervals shorter than the idle transition time, data may be sent to the UE 40 in the connected mode before the UE 40 transitions to the idle mode.
[0207] When the UE 40 enters idle mode, the client 200 needs to send data, for example, after sending a paging to make the UE 40 transition from idle mode to connected mode. Therefore, when the UE 40 enters idle mode, a delay of several hundred ms may occur before the client 200 sends data.
[0208] As described above, by knowing the idle transition time, the client 200 can send data before the UE 40 enters the idle mode, and thus the delay occurring in data transmission can be further reduced.
[0209] It should be noted that in Fig.10In the embodiment, the RAMNF 100 measures the data inactivity timer by performing the operation once (the operation from the start to the end of the timer measurement), but the number of times of the operation performed may be two or more. That is, the RAMNF 100 may calculate the idle transition time (e.g., an average value) by repeatedly performing the operation from step S103 to step S110 (e.g., 10 times).
[0210] For example, when various applications are operated in the UE 40 and transmission and reception are required in the application, the UE 40 side returns to the wireless part of the network (transitions to the connected mode). Therefore, by calculating the idle transition time based on the time measured by repeatedly performing the operation for a plurality of times, the RAMNF 100 can calculate a more accurate idle transition time.
[0211] A supplementary description about special cases will be provided here. It is conceivable that there is a base station 20 among the various base stations 20 that cannot wake up the UE 40 through the paging API. For example, the capabilities of a small base station 20 and a small core network CN used for a private network may be simplified. In this case, even if the RAMNF 100 activates the paging API of the AMF 441, it is still conceivable that the UE 40 will not transition from the idle mode to the connected mode. Therefore, the RAMNF 100 implements a confirmation process of confirming whether the state of the UE 40 has transitioned through paging.
[0212] Fig.11 is a flowchart illustrating an example of the flow of confirmation processing according to the first embodiment of the present disclosure. Fig.11 The confirmation process shown in is performed, for example, by the RAMNF 100 before the measurement of the idle transition time.
[0213] like Fig.11 As shown in FIG. 2 , the RAMNF 100 sends a paging request to the AMF 441 (step S201). For example, when the UE 40 is in idle mode, the RAMNF 100 sends a paging request to the AMF 441.
[0214] Then, the RAMNF 100 determines whether the state of the UE 40 has transitioned from the idle mode to the connected mode (step S202). The RAMNF 100 determines the state of the UE 40 based on the notification from the AMF 441.
[0215] In the case where the state of the UE 40 has transitioned from the idle mode to the connected mode (“Yes” in step S202), the RAMNF 100 determines that the paging API of the AMF 441 can be controlled by the RAMNF 100 (step S203), and ends the process.
[0216] On the other hand, in a case where the state of the UE 40 has not transitioned from the idle mode to the connected mode (No in step S202), the RAMNF 100 determines that the paging API of the AMF 441 cannot be controlled by the RAMNF 100 (step S204), and ends the processing.
[0217] The RAMNF 100 may disclose the result of the confirmation process to the client 200 , that is, whether the paging API of the AMF 441 can be controlled by the RAMNF 100 .
[0218] Here, Fig.12 1 is a diagram for describing an example of scheduling of the state of the UE 40 by the RAMNF 100 according to the first embodiment of the present disclosure. As described above, the RAMNF 100 calculates the idle transition time. Fig.12 In the example, the RAMNF 100 calculates (obtains) the time T as the idle transition time (data inactivity time value).
[0219] The RAMNF 100 sends certain data to the UE 40 to prevent the UE 40 from entering the idle mode before the data inactivity timer expires. As a result, the RAMNF 100 can control the state of the UE 40. Fig.12 In the example of FIG. 4 , the RAMNF 100 schedules the state of the UE 40 so that the UE 40 repeatedly switches between the idle mode and the connected mode at predetermined intervals. The RAMNF 100 notifies the client 200 of the scheduling of the state of the UE 40.
[0220] As described above, the RAMNF 100 communicates with the UE 40 before the timing at which the UE 40 transitions to the idle state based on the idle transition time (an example of measurement information). As a result, the RAMNF 100 controls the duration of the UE 40 being in the idle mode and the duration of the UE being in the connected mode in a planned manner. In addition, the RAMNF 100 notifies the client 200 of the schedule (plan) of the registration (idle / connected) of the UE 40.
[0221] By using the schedule notified from the RAMNF 100, the client 200 can access the UE 40 while the UE 40 is in the connected mode. As a result, the client 200 can access the UE 40 with lower delay.
[0222] As described above, the RAMNF 100 can prevent the UE 40 from transitioning to the idle mode by sending a signal from the network side before the UE 40 transitions to the idle mode, and can control the registration state of the UE 40. It should be noted that the signal sent from the network side at this time can be any signal or a signal with a small amount of data. In this way, since the network side sends a small signal, the increase in network traffic can be suppressed.
[0223] It should be noted that the RAMNF 100 may be defined as a new network function (NF) of the core network CN, and the functions of the RAMNF 100 may be implemented as new functions in the existing AMF 441, SMF 442, and location management function (LMF).
[0224] As described previously, the RAMNF 100 may acquire the idle transition time of the UE 40 as information of the network, and may provide the idle transition time to the client 200.
[0225] As a result, the client 200 can know how long to continue to send signals to the UE 40, so that the UE 40 can continue to communicate without switching to the idle mode. The client 200 can continue to send signals so that the UE 40 does not switch to the idle mode, thereby achieving low-latency communication.
[0226] The RAMNF 100 notifies the client 200 of the schedule of the idle / connected state of the UE 40. At this time, by acquiring the idle transition time, the RAMNF 100 can reduce the number of times the paging control necessary to maintain the schedule is performed and the number of times the UE 40 is awakened by transmitting data. That is, the RAMNF 100 can maintain the schedule of the idle / connected state of the UE 40 with minimal paging control and data transmission based on the idle transition time.
[0227] As a result, the RAMNF 100 can save communication resources and computer resources of the UE 40 and the core network CN. Specifically, the RAMNF 100 can suppress the power consumption of the UE 40. As described above, the RAMNF 100 can efficiently manage the scheduling of registration (idle / connected) of the UE 40.
[0228] <4.3. Second Embodiment>
[0229] <4.3.1. Second question>
[0230] It is desirable that the RAMNF 100 can correctly provide the client 200 with information grasped by the application layer of the UE 40 among the information about the state of the network of the UE 40. In addition, it is desirable that the RAMNF 100 can provide the information to the client 200 in cooperation with other network information (e.g., the first information obtained through the SBI).
[0231] As described above, the RAMNF 100 can obtain information about the network of the UE 40 to some extent through the API of the SBI of the AMF 441 or SMF 442 of the core network CN.
[0232] The information (first information) about the network of UE 40 acquired in this manner includes, for example, information indicating whether UE 40 is in idle mode or connected mode, information indicating whether UE 40 is registered or deregistered, and the like.
[0233] It is desirable that the RAMNF 100 can acquire information about behavior that cannot be known except by the application layer of the UE 40 (hereinafter also described as terminal-related information).
[0234] The terminal related information includes, for example, at least one of scheduling information about the scheduling of registration (registered / cancelled registration), power information about the power consumption of UE 40, or location information about the location of UE 40. It should be noted that the location information here is not the location information of UE 40 estimated from the reference signal of 5G, but high-precision location information using wireless information of GPS, wireless LAN or Bluetooth (registered trademark).
[0235] In addition, it is desirable that the RAMNF 100 can provide the acquired location-related information to the client 200. At this time, it is also desirable that the RAMNF 100 can combine the first information (network information) acquired through the AMF 441 or SMF 442 with the terminal-related information known by the application layer, and provide the items of information to the client 200 as one item of information.
[0236] Since the RAMNF 100 combines the first information with the terminal-related information and provides the first information and the terminal-related information as one piece of information to the client 200, the service can be combined with the network, and a valuable new service can be provided. Therefore, it is necessary to provide such information obtained by combining the first information with the terminal-related information.
[0237] <4.3.2. Example of solution to the second problem>
[0238] Fig.13 is a diagram showing an example of the information processing system 1 according to the second embodiment of the present disclosure. Fig.13 The information processing system 1 shown in Figure 8 The information processing system 1 shown in FIG. 1 is the same as the information processing system 1 shown in FIG. 1 , except that terminal related information is transmitted and received between the RAMNF 100 and the UE 40.
[0239] exist Fig.13 In the information processing system 1 shown in FIG. 1 , information (terminal-related information) stored in the application layer of UE 40 is notified to RAMNF 100, and similar information is also stored in RAMNF 100.
[0240] The terminal related information includes, for example, at least one of schedule information on a registration schedule, power information on power consumption of the UE 40, or location information on the location of the UE 40. Details of an example of the terminal related information will be described hereinafter.
[0241] (Register (be registered / cancel registration) scheduling information)
[0242] The detachment of UE 40 means that UE 40 is completely separated from the network, at which time the IP address assigned to UE 40 by SMF 442 of the core network CN becomes invalid. On the other hand, SMF 442 assigns an IP address to UE 40 when UE 40 is attached to the network.
[0243] Then, when the UE 40 transitions from the idle mode to the connected mode, the wireless part is connected, and the UE 40 can carry out communication. That is, the UE needs to be in a registered state in order for the UE 40 to be connected.
[0244] When UE 40 is registered and in an idle state, UE 40 is assigned an IP address, but UE 40 cannot perform communication. When UE 40 is deregistered, since UE 40 is not assigned an IP address, UE 40 is in a state where communication cannot be performed at all.
[0245] Here, in the case where UE 40 is a low power consumption device, such as the case where UE 40 is an IoT device, in order to save battery, it can be conceived that UE 40 is in the registered state only when necessary. That is, it can be conceived that UE 40 implements a plan (scheduling) in which the registered state and the unregistered state are repeated at a constant cycle on the application layer. In this case, UE 40 repeats attachment and detachment, that is, the registered state and the unregistered state according to the schedule.
[0246] The RAMNF 100 can provide the client 200 with scheduling information by grasping the period as scheduling information.
[0247] Heretofore, it has not been assumed that application layer information such as schedule information is transmitted and received between an application installed in the client server (client 200 ) and an application installed in UE 40 .
[0248] As described above, RAMNF 100 is a platform between the network and the service. In this embodiment, application layer information is provided to the client 200 through RAMNF 100. RAMNF 100 can provide application layer information to the client 200 together with other information of the network.
[0249] (Power Information)
[0250] As the terminal related information (terminal application information) of the UE 40, the RAMNF 100 may provide the client 200 with power information about the battery of the UE 40 in addition to the scheduling information. This is because the power information of the UE 40 affects the scheduling information of the connected / idle state of the UE 40 and the information of the registered / deregistered state (e.g., scheduling information).
[0251] Hereinafter, the connected / idle scheduling information is also referred to as the connection scheduling information. The registered / cancelled scheduling information is also described as the registration scheduling information. Without distinguishing the connection scheduling information and the registration scheduling information from each other, the connection scheduling information and the registration scheduling information are simply described as scheduling information (scheduling information about registration scheduling).
[0252] As described above, the scheduling of registration of the UE 40 affects the power consumption of the UE 40. The RAMNF 100 can not only receive power information from the UE 40, but also request registration scheduling based on the power information. As described above, when the RAMNF 100 issues a registration scheduling request, the RAMNF 100 (or the client 200) can access the UE 40 with more detailed consideration of the power consumption of the UE 40. In this way, the power information can be used to control scheduling and access the UE 40.
[0253] (Location Information)
[0254] Examples of other information included in the terminal related information include location information about the location of the UE 40. The UE 40 may provide the location information to the client 200 or the like through the RAMNF 100.
[0255] In 5G, AMF 441 can acquire information about the location of UE 40. AMF 441 can provide the acquired information to other NFs, etc. by using API. However, the location information of UE 40 handled by AMF 441 is location information acquired using the positioning technology of 3GPP (registered trademark). The location information is, for example, information estimated based on information such as the estimated arrival time of radio waves from the base station 20 and the estimated arrival direction of radio waves.
[0256] As described above, the location information that can be provided by AMF 441 is location information obtained through 3GPP technology.
[0257] On the other hand, the location information acquired by the RAMNF 100 from the UE 40 is location information measured by GPS of the application layer of the UE 40, or location information acquired using radio waves of Bluetooth (registered trademark) or Wi-Fi (registered trademark). That is, the location information is information measured using equipment installed on the UE 40. The location information is information not collected by the AMF 441. The location information not grasped by the AMF 441 may be more accurate than the location information collected by the AMF 441.
[0258] Hereinafter, the location information provided by AMF 441 may be referred to as cellular location information, and the location information obtained by RAMNF 100 from UE 40 may be referred to as terminal location information, in order to distinguish these location information.
[0259] As described above, the RAMNF 100 acquires various terminal-related information with high accuracy from the UE 40. The terminal-related information may be related to the first information collected by the RAMNF 100 through the conventional SBI, such as the terminal location information included in the terminal-related information and the information on the registered / cancelled registration status obtained from the AMF 441.
[0260] When the UE 40 arrives at a specific location, the state may be changed from the unregistered state to the registered state. For example, it is assumed that an automatic transfer robot moving in a factory carries a component to a predetermined location and arrives at the predetermined location. For example, once the automatic transfer robot arrives at the predetermined location, the automatic transfer robot is attached to the network and registered so that communication can be implemented.
[0261] Since the client 200 knows in advance the information that the automatic transfer robot is registered when it arrives at a predetermined position, it is possible, for example, to set the system on the premise that communication becomes possible when the automatic transfer robot is located at a specific position.
[0262] It should be noted that the terminal related information is not limited to the registration scheduling information, power information and location information described above. The terminal related information may include the following information, for example.
[0263] -Whether there is data in the surveillance camera
[0264] - Whether the fault was detected at the factory
[0265] -Whether the factory's transport robot enters a specific area
[0266] -Whether the drone has entered a specific area
[0267] - The movement speed of the drone or whether the speed reaches a certain value or whether the speed becomes a certain value or less
[0268] - Whether the drone detects another drone
[0269] - Whether the automatic teleport robot should stop to avoid collision
[0270] - Earthquakes and fires detected
[0271] -Whether a specific session of the application has started
[0272] - The expected duration of the application
[0273] Such terminal-related information about various applications may also be collected by the RAMNF 100. The RAMNF 100 may collect the terminal-related information and notify the client 200 of the terminal-related information in combination with the first information included in the RAMNF 100.
[0274] As described above, the RAMNF 100 according to the present embodiment acquires information (terminal related information) which is not grasped by the general core network CN from the UE 40, and provides the information to the client 200 together with the first information acquired through the SBI.
[0275] An example of information provision processing performed by the RAMNF 100 for each item of terminal-related information will be described hereinafter.
[0276] (Registration schedule information provision process)
[0277] Fig.14 is a sequence diagram showing an example of the flow of the registration schedule information providing process according to the second embodiment of the present disclosure. It should be noted that the UE 40 that implements a part of the providing process may be an application of the UE 40 .
[0278] like Fig.14As shown in FIG. 3 , the RAMNF 100 notifies the UE 40 of the configuration of the report of the registration schedule (registration schedule information) (step S301).
[0279] The UE 40 determines a schedule regarding registration of the UE 40 (step S302), and notifies the RAMNF 100 of the schedule regarding registration (step S303).
[0280] Here, Fig.15 is a diagram showing an example of a registration schedule according to the second embodiment of the present disclosure. Fig.15 As shown in FIG. 1 , UE 40 notifies RAMNF 100 of registration schedule information including a deregistration duration (seconds) and a registered duration (seconds).
[0281] It should be noted that Fig.15 A registration schedule in which a specific deregistration duration (seconds) and a specific registered duration (seconds) are repeated alternately is shown, but the registration schedule is not limited thereto. For example, a registration schedule with different deregistration durations (seconds) and / or registered durations (seconds) may be notified to the RAMNF 100 each time.
[0282] Description Back Fig.14 The RAMNF 100 notifies the client 200 of the schedule (step S304). The schedule may be, for example, the registration schedule acquired by the RAMNF 100 from the UE 40 in step S303.
[0283] In addition, the RAMNF 100 notifies the client 200 of a schedule including state information of the UE 40, such as a connected / idle state (step S305). The schedule may be schedule information about registration including a registered / deregistered state and a connected / idle state of the UE 40.
[0284] Here, Fig.16 2 is a diagram showing an example of a schedule regarding registration according to the second embodiment of the present disclosure. Fig.16 As shown in , the RAMNF 100 notifies the RAMNF 100 of the scheduling information including the deregistration duration (seconds) and the registered duration (seconds). At this time, the RAMNF 100 makes a notification of the scheduling information including the information about the connected duration (seconds) and the idle duration (seconds) in the registered state.
[0285] In this way, the RAMNF 100 integrates the registration schedule information and the connection schedule information, and notifies the client 200 of the integrated information as one item of schedule information.
[0286] As described above, when the UE 40 accesses the RAMNF 100, the registration schedule information of the UE 40 is transmitted (shared) between the application of the UE 40 and the application of the RAMNF 100.
[0287] As a member of the NF of the core network CN, the RAMNF 100 provides information to the client 200 by combining terminal related information about the application of the UE 40 with the first information about the state of the network.
[0288] In the case where the registration schedule is changed, the UE 40 accesses the RAMNF 100 and notifies the RAMNF 100 of the change.
[0289] Here, the registration scheduling information of the UE 40 is terminal related information known (managed) by the application of the UE 40. The connection scheduling information of the UE 40 is information that can be controlled by the RAMNF 100, that is, information that can be created by the RAMNF 100. By acquiring the registration scheduling information of the UE 40, the RAMNF 100 can provide the client 200 with the registration scheduling information and the connection scheduling information.
[0290] That is, the client 200 can grasp at what time the UE 40 is registered, and at what time the UE is connected during the registered duration. Therefore, the client 200 can access the UE 40 when the UE 40 is in the connected state.
[0291] In the case that the client 200 inadvertently accesses the UE 40, the UE 40 may be deregistered and no IP address is assigned to the UE 40. Alternatively, if the client 200 accesses the UE 40 when the UE 40 is in an idle state, a paging message is sent to the UE 40 and the power consumption of the UE 40 may increase.
[0292] By accessing the UE 40 by the client 200 at the connected time of the UE 40 determined in advance based on the scheduling information, the power consumption of the UE 40 can be suppressed.
[0293] It should be noted that, as the registration schedule information providing process, the RAMNF 100 may notify the client 200 only the duration (connection schedule information) that the UE 40 is in RRC connected. For example, the RAMNF 100 may notify the client 200 of the connection schedule information and the registration schedule information. Furthermore, in this case, the connection schedule information and the registration schedule information are notified in association with each other, so that the client 200 can use the registration schedule information and the connection schedule information provided from the UE 40 as integrated schedule information.
[0294] As described above, also in the case where the RAMNF 100 makes notification of each of the connection scheduling information and the registration scheduling information, it can be said that the connection scheduling information and the registration scheduling information are notified in association with each other, so that these information can be integrated (combined) and notified.
[0295] As described above, the RAMNF 100 combines the connection schedule information with the registration schedule information and provides the combined information to the client 200 as the integrated schedule information of the UE 40. As a result, the client 200 can know in advance when to access the UE 40 to communicate with the UE 40.
[0296] In the case where the UE 40 is an IoT device, it is conceivable that the number of UEs 40 accessed by the client 200 will increase. In addition, it is conceivable that a certain number of clients 200 for services access one UE 40. As described above, even in the case where many communications may occur between the client 200 and the UE 40, the client 200 can access the UE 40 in the connected state, thereby making it possible to reduce useless communications with the UE 40. As a result, low power consumption of the network and / or the UE 40 is achieved.
[0297] It should be noted that in the second embodiment of the present disclosure, the communication between the UE 40 and the RAMNF 100 can be directly implemented between the UE 40 and the RAMNF 100 through the base station 20. Alternatively, the RAMNF 100 can communicate with the UE 40 via SBI through another NF (such as AMF 441) of the core network. As described above, there is no specific limitation on the communication path between the RAMNF 100 and the UE 40. This is also applicable to other embodiments.
[0298] (Power information provision processing)
[0299] Fig.17 2 is a sequence diagram showing an example of the flow of the power information providing process according to the second embodiment of the present disclosure. It should be noted that the UE 40 that implements a part of the providing process may be an application of the UE 40 .
[0300] like Fig.17 As shown in FIG. 4 , the RAMNF 100 notifies the UE 40 of the configuration of the report of the UE power related information (power information) (step S401). The UE 40 notifies the RAMNF 100 of the UE power related information of the UE 40 (step S402).
[0301] The RAMNF 100 determines the connected / idle ratio of the UE 40 according to the UE power related information (step S403). The RAMNF 100 notifies the client 200 of the UE state including the prohibited access duration i based on the determined connected / idle ratio (step S404), for example.
[0302] Here, Fig.18 is a diagram showing an example of connection scheduling according to the second embodiment of the present disclosure. Fig.18 As shown in FIG. 1 , UE 40 notifies RAMNF 100 of connection scheduling information (scheduling UE status) including connected duration (seconds) and idle duration (seconds).
[0303] In this way, RAMNF 100 makes, for example, Fig.18 The notification of the connection scheduling information shown in is used as the UE state. In this case, during the idle duration, the client 200 is prohibited from accessing the UE 40. That is, the idle duration corresponds to the prohibited access duration i.
[0304] As described above, in the power information providing process, by accessing the RAMNF 100 from the UE 40 , the power information of the UE 40 is transmitted (shared) between the application of the UE 40 and the application of the RAMNF 100 .
[0305] Here, Fig.19 is a table showing power information according to the second embodiment of the present disclosure. Fig.19 As shown in , the power information may include the capacity of the battery, the remaining battery power, the expected charging value, etc.
[0306] The critical state of the battery is information indicating the capacity of the battery. For example, when the battery capacity is low, the critical state of the battery is "high", and when the battery capacity is high, the critical state of the battery is "medium". In addition, when the UE 40 is connected to a power source, the critical state of the battery is "low" regardless of the battery capacity.
[0307] The remaining battery capacity is information indicating the remaining battery capacity. The expected charging value is information indicating the time when charging is expected to be performed next time, and can be represented by the time when charging is performed, such as after X hours, for example. The expected charging value can be determined by the UE 40, for example, based on the previous charging time, charging cycle, etc.
[0308] Here, it is assumed that the critical state of the battery and the remaining battery power are expressed in three stages of "high", "medium" and "low", but the expression of the critical state of the battery and the remaining battery power is not limited to this. For example, the critical state of the battery and the remaining battery power can be expressed in two stages of "high" and "low", or can be expressed in four or more stages. In addition, the critical state of the battery and the remaining battery power can be expressed by a numerical value or a ratio (such as a percentage).
[0309] For example, as a member of the NF of the core network CN, the RAMNF 100 that has acquired such power information provides the terminal-related information (eg, power information) of the UE 40 together with the first information (eg, registration information) about the state of the network to the client 200.
[0310] When the power information changes, such as when the remaining battery power changes significantly, the UE 40 accesses the RAMNF 100 and makes a notification of the latest power information.
[0311] As described above, the RAMNF 100 acquires information such as power information managed by the application layer of the UE 40. As a result, the RAMNF 100 can decide the connected / idle ratio according to the power information. In addition, the RAMNF 100 can decide the forbidden access duration of the UE 40 based on the decided ratio, and provide the connection scheduling information including the forbidden access duration to the client 200.
[0312] The client 200 can access the UE 40 while avoiding the access prohibition duration (e.g., idle duration), and can implement low power consumption of the UE 40. For example, the client determines the UE 40 to be accessed based on the terminal related information (e.g., power information) of the UE 40 and the first information (e.g., registration information) about the state of the network. As a result, the client 200 can, for example, access the UE 40 while avoiding the UE 40 with a low remaining battery power.
[0313] (Terminal location information provision processing)
[0314] The RAMNF 100 collects the terminal location information of the UE 40. At this time, the RAMNF 100 may collect at least one of the current terminal location information, the past terminal location information, or the future terminal location information.
[0315] Fig. 20 : is a table showing an example of terminal location information according to the second embodiment of the present disclosure. Fig. 20 As shown in , the RAMNF 100, for example, collects current terminal location information, past terminal location information, and future terminal location information.
[0316] The current terminal location information is information about the current terminal location. The RAMNF 100 collects the current terminal location information and notifies the client 200 of the terminal location information.
[0317] The past terminal location information is information indicating the location that the UE 40 has passed within a specific time in the past. The RAMNF 100 collects the past terminal location information and notifies the client 200 of the terminal location information. At this time, the RAMNF 100 can make a notification of the past terminal location information as group information. The group information will be described in detail in the third embodiment.
[0318] For example, suppose that the client 200 wants to obtain information of a specific location. At this time, when no UE 40 is at the location at the current time, the client 200 can obtain the information of the location by accessing the UE 40 that was at the location in the past. In this way, when the client 200 wants to access the UE 40 that passed the specific location in the past, the past terminal location information is used.
[0319] The future terminal location information is information indicating a possible location to which the UE 40 may go. The RAMNF 100 collects the future terminal location information and notifies the client 200 of the terminal location information.
[0320] The future terminal location information is useful information when the client 200 searches for and accesses the UE 40 that may go to the location (eg, a specific location).
[0321] As described above, the RAMNF 100 according to the present embodiment collects the past terminal location information, the current terminal location information, and the future terminal location information, respectively, and notifies each item of the terminal location information to the client 200. An example of a process of providing each item of the past terminal location information, the current terminal location information, and the future terminal location information will be described hereinafter.
[0322] (Current terminal location information provision processing)
[0323] Fig.21 4 is a sequence diagram showing the flow of the current terminal location information providing process according to the second embodiment of the present disclosure. It should be noted that the UE 40 that implements a part of the providing process may be an application of the UE 40.
[0324] UE 40 updates terminal location information (location information) indicated by, for example, location ID (step S501). UE 40 updates the terminal location information by notifying RAMNF 100 of the current terminal location information.
[0325] The RAMNF 100 stores the ID of the UE 40 (eg, SUPI or International Mobile Subscriber Identity (IMSI)) and the location of the UE 40 (step S502). The RAMNF 100 stores the ID of the UE 40 and the terminal location information acquired in step S501 in association with each other.
[0326] Next, upon receiving the request including the location ID from the client 200 (step S503), the RAMNF 100 responds to the client 200 with the ID (e.g., SUPI) of the UE 40 and the UE state of the UE 40 (step S504). That is, the RAMNF 100 responds to the client 200 by associating the ID of the UE 40 located in the area corresponding to the location ID with the state of the UE 40. The UE state includes, for example, information indicating whether the UE 40 is registered or deregistered and whether the UE 40 is in a connected state or an idle state, and UE state scheduling information.
[0327] The client 200 determines its own action, such as accessing the UE 40, based on the aforementioned information (information in which the ID and the state of the UE 40 are associated with each other) (step S505).
[0328] In this way, the current terminal location information is useful for the client 200 that wishes to access the UE 40 at a specific location. The RAMNF 100, for example, notifies the client 200 of the registered UE 40 located within a specific area specified by the client 200.
[0329] In this way, the RAMNF 100 can provide information to the client 200 by combining the current terminal location information with the first information about the network. The client 200 can know whether the UE 40 in a specific area is accessible. That is, the client 200 can obtain information about the accessible UE 40 in a specific area.
[0330] The specific area is, for example, a mesh area of 10 square meters. In this way, it is assumed that the resolution of the area is predetermined.
[0331] When UE 40 moves to a certain location, UE 40 notifies (updates) RAMNF 100 that UE 40 has transitioned to the registered state and the connected state and has moved to the location. After the notification, UE 40 can transition to the idle state.
[0332] In this way, UE 40 registers the current terminal location information in RAMNF 100.
[0333] The registration of the terminal location information here is different from the conventional tracking update in that the terminal location information is updated based on the terminal location information of the application layer of the UE 40. The area targeted by the conventional tracking update is an area to which a plurality of base stations 20 are bound, and is a very large area compared to the area targeted by the terminal location information. In addition, the conventional tracking update is implemented using 5G radio technology.
[0334] On the other hand, registration of the terminal location information according to the present embodiment is updated based on the terminal location information of the application layer of the UE 40 as described above. As described above, the terminal location information is information targeting a narrow area such as 10 square meters.
[0335] Furthermore, in the present embodiment, the RAMNF 100 acquires the terminal location information directly or through the SBI from the UE 40. In this respect, the tracking update is different from the tracking update of acquiring the location information from the core network CN.
[0336] As described above, the client 200 issues a query about the UE 40 in a specific location (area) to the RAMNF 100. At this time, the client 200 can specify the specific location by using a location ID.
[0337] The RAMNF 100 may respond to the client 200 by associating the ID (IMSI, SUPI, etc.) of the UE 40 in the area corresponding to the location ID with the UE status (e.g., whether the UE 40 is registered). At this time, the RAMNF 100 may send a response including the connection scheduling information and the registration scheduling information described in the first embodiment to the client 200.
[0338] Furthermore, in the case where a plurality of UEs 40 exist in the area corresponding to the location ID, the RAMNF 100 may respond to the client 200 with the plurality of UEs 40 as group information. The group information will be described in detail in the third embodiment.
[0339] (Past terminal location information provision process)
[0340] Fig. 22 is a sequence diagram showing an example of the flow of the past terminal location information providing process according to the second embodiment of the present disclosure. It should be noted that the UE 40 that implements a part of the providing process may be an application of the UE 40 .
[0341] The UE 40 updates the past terminal location information (location information) indicated by, for example, a location ID, etc., for a certain period (step S601). The UE 40 updates the past terminal location information by notifying the RAMNF 100 of the past terminal location information together with the period.
[0342] The RAMNF 100 stores the ID of the UE 40 (eg, SUPI or International Mobile Subscriber Identity (IMSI)) and the past location information of the UE 40 (step S602). The RAMNF 100 stores the ID of the UE 40 and the past terminal location acquired in step S501 in association with each other.
[0343] Next, the RAMNF 100 receives a request including a location ID from the client 200 (step S603). The RAMNF 100 responds to the client 200 with the ID of the UE 40 (e.g., SUPI) and the UE status of the UE 40, or responds to the client 200 with the ID of the UE 40 (e.g., SUPI) if the UE 40 is registered (step S604).
[0344] That is, the RAMNF 100 responds to the client 200 by associating the ID of the UE 40 that has stayed in the area corresponding to the location ID in the past with the state (UE state) of the UE 40. Alternatively, the RAMNF 100 responds to the client 200 with the ID of the UE 40 that has stayed in the area corresponding to the location ID for a predetermined period of time in the past among the registered UEs 40. The UE state includes, for example, information indicating whether the UE 40 is registered or deregistered and whether the UE 40 is in a connected state or an idle state, and UE state scheduling information.
[0345] The client 200 determines its own action, such as accessing the UE 40, based on the foregoing information (information in which the ID and the state of the UE 40 are associated with each other) (step S605).
[0346] In this way, the past terminal location information is useful for the client 200 who wishes to visit the UE 40 that is too located in a specific location. The number of the specific locations may be plural, and the specific location may also be a track.
[0347] For example, assume that while staying (or moving) at a specific location, UE 40 accumulates area information depending on the location, such as temperature and humidity of the location (area). In the past, terminal location information was useful, for example, for client 200 that wanted to acquire the area information.
[0348] In this way, the RAMNF 100 can provide information to the client 200 by combining the past terminal location information with the first information about the network. The client 200 can know whether the UE 40 that was in a specific area in the past is accessible (registered and / or connected). That is, the client 200 can obtain information about the accessible (registered and / or connected) UE 40 that was in the specific area.
[0349] For example, UE 40 notifies RAMNF 100 of information about the location where UE 40 stayed (passed) as past terminal location information at a constant cycle (eg, every day or every few hours). RAMNF 100 accumulates the past terminal location information together with the ID of UE 40.
[0350] The client 200 queries the RAMNF 100 for the location of the UE 40 passing through a specific location.
[0351] For example, the RAMNF 100 sends a response by associating information identifying the UE 40 passing through a specific location (ID of the UE 40) and the state of the UE 40 (UE state) with each other.
[0352] Or, for example, the RAMNF 100 may respond to the client 200 with information from the currently registered UE 40 among the various UEs 40 passing through the specific location. As a result, the client 200 can access the UE 40 passing through the specific location and acquire the area information.
[0353] Alternatively, when a UE 40 passing through a specific location is registered, the client 200 may register with the RAMNF 100, thereby notifying the client 200 of information about the UE 40.
[0354] In this case, when it is detected that the UE 40 passing through a specific location is registered, the RAMNF 100 notifies the client 200 of information about the UE 40. Alternatively, the RAMNF 100 may make a notification to the client 200 when the UE 40 passing through a specific location is registered and connected.
[0355] The area of the past terminal location information may be the same as or different from the area of the current terminal location information. It is sufficient that the target area of the past terminal location information is a narrower area (with higher accuracy) than the area of the location information obtainable from the network side.
[0356] (Future terminal location information provision processing)
[0357] Fig.23is a sequence diagram showing an example of the flow of the future terminal location information providing process according to the second embodiment of the present disclosure. It should be noted that the UE 40 that implements a part of the providing process may be an application of the UE 40 .
[0358] like Fig.23 As shown in , in the case where the UE 40 moves to a specific location, the client 200 requests the RAMNF 100 to make a notification of the fact (step S701).
[0359] In the case where the UE 40 moves to a specific location, the RAMNF 100 requests the UE 40 to make a notification of the fact (step S702).
[0360] When the UE 40 moves to the location specified by the request, the UE 40 is registered and RRC connected, and sends the location ID and UE ID (eg, SUPI) to the RAMNF 100 (step S703).
[0361] The RAMNF 100 stores the ID of the UE 40 (eg, SUPI or International Mobile Subscriber Identity (IMSI)) and the location information of the UE 40 (step S704).
[0362] The RAMNF 100 notifies the client 200 of the ID (eg, SUPI) of the UE 40 and the UE state of the UE 40 (step S705). The UE state includes, for example, information indicating whether the UE 40 is registered or deregistered and whether the UE 40 is in a connected state or an idle state, and UE state scheduling information.
[0363] The client 200 determines its own action, such as accessing the UE 40, based on the foregoing information (information in which the ID and the state of the UE 40 are associated with each other) (step S706).
[0364] Furthermore, in the case where the UE moves out of the location specified in the request, the UE 40 may change its own state from the registered state to the deregistered state (step S707).
[0365] As described above, the future terminal location information is information indicating that the UE 40 may move to a specific location in the future. The client 200 issues a request to the UE 40 through the RAMNF 100 so that the UE 40 is registered when it arrives at the location.
[0366] In addition, the client 200 registers with the RAMNF 100 so as to be notified when the UE 40 moves to a specific location.
[0367] In the case where the UE 40 moves to a designated location, the UE is registered. In addition, the UE 40 is connected and notifies the RAMNF 100 of its arrival at the location. It should be noted that the UE 40 may transition to an idle state after a certain period of time has passed from the notification.
[0368] Upon receiving the notification from the UE 40, the RAMNF 100 notifies the client 200 that the UE 40 has arrived at the designated location. The UE 40 is registered when it arrives at the designated location. Therefore, the client 200 can obtain information such as area information by accessing the UE 40 that has arrived at the designated location. For example, the client 200 can implement operations such as causing the UE 40 to send the temperature of the designated location.
[0369] When UE 40 moves out of the designated location, the UE changes from the registered state to the deregistered state. RAMNF 100 detects that UE 40 changes to the deregistered state, so that it can know that UE 40 has moved out of the designated location. RAMNF 100 can notify client 200 that UE 40 has left the designated location.
[0370] As described above, the RAMNF 100 according to the present embodiment collects past terminal location information, current terminal location information and future terminal location information. The cellular location information provided by the AMF 441 is current location information with low precision and does not include past or future information. In this respect, the terminal location information according to the present embodiment is different from the cellular location information.
[0371] In addition, the RAMNF 100 combines the first information about the network (e.g., registration information) with the terminal location information, and provides the combined information to the client 200. As a result, the client 200 can know the past and / or current location of the UE 40, and further can know whether the UE 40 is accessible. In addition, the client 200 can access the UE 40 that arrives at a specific location in the future. As a result, the client 200 can access the UE 40 at an appropriate time.
[0372] As described above, the RAMNF 100 may integrate the terminal-related information in the application layer of the UE 40 and the information of the UE status acquired through the SBI API (an example of the first information), and provide the integrated information to the client 200.
[0373] Fig.24 2 is a diagram for describing an example of information integration of the RAMNF 100 according to the second embodiment of the present disclosure.
[0374] The RAMNF 100 obtains the terminal related information directly from the UE 40 or through the SBI. In addition, the RAMNF 100 obtains the UE status information from the CPF 440 of the core network CN through the SBI API. The RAMNF 100 notifies the client 200 of the information obtained by integrating the terminal related information and the UE status information.
[0375] By acquiring the terminal related information and the UE status information, the RAMNF 100 can, for example, change the scheduling plan of the UE status, etc. based on the power information of the UE 40. In addition, by acquiring the terminal related information and the UE status information, the RAMNF 100 can optimize the time for accessing the UE 40 based on the terminal location information and the UE status information of the UE 40.
[0376] As described above, the RAMNF 100 integrates (combines) information of different layers such as information of the application layer of the UE 40 and information about the network of the core network CN, and provides the integrated information to the client 200. As a result, the service and the network are combined, and the client 200 can provide valuable new services.
[0377] <4.4. Third embodiment>
[0378] <4.4.1、Third question>
[0379] As described above, the RAMNF 100 provides the client 200 with information of the network, such as the UE status as network information of the UE 40. The UE status includes information indicating whether the UE 40 is registered or deregistered and information indicating whether the UE is in a connected state or an idle state.
[0380] Here, in each of the embodiments described above, the client 200 queries the RAMNF 100 for each UE 40 and obtains the UE status of each UE 40 .
[0381] For example, in the case where the number of UEs 40 targeted by the client 200 is large, the communication between the client 200 and the RAMNF 100 increases. Specifically, in the case where the client 200 provides an IoT service, it is assumed that the number of UEs 40 implementing communication increases.
[0382] In addition, for example, it is difficult for the client 200 to make an inquiry to the RAMNF 100 without clearly determining the number of UEs 40 that are the targets of the client 200. This is because in each of the embodiments described above, an ID (e.g., IMSI or SUPI) for specifying the UE 40 is used when the client 200 makes an inquiry to the RAMNF 100. It should be noted that the ID for specifying the UE 40 may be any information capable of specifying the UE 40, and is not limited to the IMSI or SUPI.
[0383] <4.4.2. Example of solution to the third problem>
[0384] Therefore, in the present embodiment, the RAMNF 100 notifies the client 200 of group information (group-based network information) including at least one item of information on the UE 40 satisfying the condition specified by the client 200.
[0385] The condition specified by the client 200 includes at least one of a registration condition specifying a registration state of the UE 40 , a power condition specifying a power consumption state of the UE 40 , and a location condition specifying a location of the UE 40 .
[0386] (Processing according to registration conditions)
[0387] Fig.25 1 is a sequence diagram showing an example of the flow of providing processing according to a registration condition according to the third embodiment of the present disclosure. Here, the RAMNF 100 acquires group information of the UE 40 in the registered state in response to an instruction from the client 200. That is, here, it is assumed that the registration condition specified by the client 200 is the registered state.
[0388] like Fig.25 As shown in FIG. 8 , UE 40 implements an attach (registered) / detach procedure with CPF 440 (step S801). Although an attach (registered) / detach (cancel registration) procedure of one UE 40 is shown here, CPF 440 may implement an attach (registered) / detach procedure with multiple UEs 40.
[0389] The RAMNF 100 inquires the CPF 440 about the UE status such as the registered / deregistered status for some UEs 40 (step S802), and obtains a response from the CPF 440 (step S803).
[0390] The client 200 inquires the RAMNF 100 about the group of the UE 40 in the registered state (step S804).
[0391] As a response to the client 200, the RAMNF 100 transmits group information of the UE 40 in the registered state (step S805).
[0392] Here, Fig.26 is a table showing an example of group information according to the third embodiment of the present disclosure. Fig.26 The group information shown in is the group information of the UE 40 in the registered state.
[0393] like Fig.26 As shown in , the group information includes an ID and a UE ID. The UE ID is, for example, SUPI. Alternatively, as long as the UE ID is information indicating the UE 40 such as IMSI, the UE ID has no particular limitation.
[0394] The RAMNF 100 notifies the client 200 of information on at least one UE 40 in a registered state as group information.
[0395] In this way, the RAMNF 100 receives a request for the ID of the registered UE 40 from the client 200.
[0396] The RAMNF 100 notifies the client 200 of the UE ID of the registered UE 40 as group information. The RAMNF 100 detects a group of UEs 40 corresponding to the registration condition (here, UEs 40 in a registered state) specified by the client 200 from all the information that has been grasped, and creates group information.
[0397] It should be noted that at least one RAMNF 100 may be arranged in a private network. The RAMNF 100 uses all UEs 40 belonging to a private network as a general parameter, searches for UEs 40 corresponding to the conditions therefrom, and provides information to the client 200.
[0398] It should be noted that the registration condition is not limited to whether the UE 40 is registered or deregistered. For example, the client 200 may request the RAMNF 100 for group information by specifying an idle state or a connected state as a registration condition.
[0399] Fig. 27 1 is a sequence diagram showing another example of the flow of the provision process according to the registration condition according to the third embodiment of the present disclosure. Here, the RAMNF 100 acquires the group information of the UE 40 in the registered state and the connected state in response to the instruction from the client 200. That is, here, it is assumed that the registration condition specified by the client 200 is the registered state and the connected state.
[0400] like Fig. 27 As shown in FIG. 4 , UE 40 implements an attach (registered) / detach procedure with CPF 440 (step S901). Although an attach (registered) / detach (cancel registration) procedure of one UE 40 is shown here, CPF 440 may implement an attach (registered) / detach procedure with multiple UEs 40.
[0401] UE 40 implements idle / connected procedures with CPF 440 (step S902). The idle / connected procedures are processes that allow UE 40 to implement UL / DL communication or transition to a sleep state. Although the idle / connected procedures of one UE 40 are shown here, CPF 440 can implement idle / connected procedures with multiple UEs 40.
[0402] The RAMNF 100 queries the CPF 440 for UE states such as registered / deregistered states and idle / connected states for some UEs 40 (step S903), and obtains a response from the CPF 440 (step S904).
[0403] The client 200 inquires the RAMNF 100 about the group of the UE 40 that is in the registered state and in the connected state (step S905).
[0404] As a response to the client 200, the RAMNF 100 transmits group information of the UEs 40 in the registered state and the connected state (step S906).
[0405] In this way, the RAMNF 100 receives a request for the ID of the UE 40 in the registered state and the connected state from the client 200.
[0406] The RAMNF 100 notifies the client 200 of the UE IDs of the UEs 40 in the registered state and the connected state as group information. The RAMNF 100 detects the group of UEs 40 corresponding to the registration condition (here, the UEs 40 in the registered state and the connected state) specified by the client 200 from all the information that has been grasped, and creates the group information.
[0407] It should be noted that at least one RAMNF 100 may be arranged in a private network. The RAMNF 100 uses all UEs 40 belonging to a private network as a general parameter, searches for UEs 40 corresponding to the conditions therefrom, and provides information to the client 200.
[0408] It should be noted that the registration condition is not limited to the UE 40 in the connected state. For example, the client 200 may request the RAMNF 100 for group information by specifying the UE 40 in the idle state.
[0409] (Provided according to location conditions)
[0410] Fig.28 1 is a sequence diagram showing an example of the flow of the provision process according to the location condition according to the third embodiment of the present disclosure. Here, the RAMNF 100 acquires the group information of the UE 40 in the registered state and the connected state within the specified area in response to the instruction from the client 200. That is, here, it is assumed that the registration condition specified by the client 200 is the registered state and the connected state, and the location condition is the current cellular location information.
[0411] like Fig.28 As shown in FIG. 1 , UE 40 implements an attach (registered) / detach procedure with CPF 440 (step S1001). Although an attach (registered) / detach (cancel registration) procedure of one UE 40 is shown here, CPF 440 may implement an attach (registered) / detach procedure with multiple UEs 40.
[0412] UE 40 implements idle / connected procedures with CPF 440 (step S1002). The idle / connected procedures are processes that cause UE 40 to implement UL / DL communication or transition to a sleep state. Although the idle / connected procedures of one UE 40 are shown here, CPF 440 can implement idle / connected procedures with multiple UEs 40.
[0413] UE 40 updates information about the location of UE 40 (eg, cellular location information) to CPF 440 (step S1003). Although the update of location information of one UE 40 is described here, CPF 440 may update location information with multiple UEs 40.
[0414] The RAMNF 100 inquires the CPF 440 about UE states such as registered / deregistered states and idle / connected states for some UEs 40 and location information of the UEs 40 (step S1004). The RAMNF 100 obtains a response from the CPF 440 (step S1005).
[0415] The client 200 inquires the RAMNF 100 about a group of UEs 40 that are in a registered state and a connected state and are located at a specific location (step S1006).
[0416] As a response to the client 200, the RAMNF 100 transmits group information of the UE 40 that is in the registered state and the connected state and is located at a specific location (step S1007).
[0417] In this way, the RAMNF 100 receives a request for the ID of the UE 40 that is within a specific area and in a registered state and a connected state from the client 200.
[0418] The RAMNF 100 notifies the client 200 of the UE IDs of the UEs 40 that are in a specific area and in a registered state and a connected state as group information. The RAMNF 100 detects a group of UEs 40 that correspond to the registration condition specified by the client 200 (here, the UEs 40 that are in a specific area and in a registered state and a connected state) from all the information that has been grasped, and creates the group information.
[0419] It should be noted that at least one RAMNF 100 may be arranged in a private network. The RAMNF 100 uses all UEs 40 belonging to a private network as a general parameter, searches for UEs 40 corresponding to the conditions therefrom, and provides information to the client 200.
[0420] It should be noted that the location condition is not limited to the condition specifying the cellular location information collected by the CPF 440. For example, the client 200 may request the RAMNF 100 for group information by specifying the terminal location information collected by the RAMNF 100 as the location condition.
[0421] In addition, the client 200 can request group information from the RAMNF 100 by specifying not only current location information but also, for example, past or future terminal location information as location conditions.
[0422] For example, the client 200 may register with the RAMNF 100 to be notified when the UE 40 enters a specific location. In addition, in the present embodiment, the client 200 may register with the RAMNF 100 to be notified of information about the UE 40 (e.g., UE ID) that enters the specific location when the UE 40 enters the specific location without specifying the UE 40.
[0423] (Provided according to power conditions)
[0424] Fig.291 is a sequence diagram showing an example of a flow of a provision process according to a power condition according to a third embodiment of the present disclosure. Here, the RAMNF 100 acquires group information of UEs 40 having a remaining battery level equal to or higher than a certain level and being in a registered state and a connected state in response to an instruction from the client 200. That is, here, it is assumed that the registration condition specified by the client 200 is the registered state and the connected state. It is assumed that the location condition is the current cellular location information. It is assumed that the power condition is that the remaining battery level is equal to or higher than a certain level.
[0425] like Fig.29 As shown in FIG. 1 , UE 40 implements an attach (registered) / detach procedure with CPF 440 (step S1101). Although an attach (registered) / detach (cancel registration) procedure of one UE 40 is shown here, CPF 440 may implement an attach (registered) / detach procedure with multiple UEs 40.
[0426] UE 40 implements idle / connected procedures with CPF 440 (step S1102). The idle / connected procedures are processes that cause UE 40 to implement UL / DL communication or transition to a sleep state. Although the idle / connected procedures of one UE 40 are shown here, CPF 440 can implement idle / connected procedures with multiple UEs 40.
[0427] UE 40 updates information about the location of UE 40 (eg, cellular location information) to CPF 440 (step S1103). Although the update of location information of one UE 40 is described here, CPF 440 may update location information with a plurality of UEs 40.
[0428] UE 40 notifies CPF 440 of information of UE 40 (eg, power information) regarding power of UE 40 (step S1104). Although notification of power information of one UE 40 is shown here, CPF 440 may receive notification of power information from a plurality of UEs 40.
[0429] The RAMNF 100 inquires the CPF 440 about UE states such as registered / deregistered states and idle / connected states for some UEs 40, location information of the UEs 40, and power information (step S1105). The RAMNF 100 obtains a response from the CPF 440 (step S1106).
[0430] The client 200 queries the RAMNF 100 for a group of UEs 40 that are in a registered state and a connected state, are located at a specific location, and have predetermined power information (step S1107). For example, the client 200 queries the RAMNF 100 for a group of UEs 40 that are in a registered state and a connected state, are located at a specific location, and have a remaining battery level equal to or higher than a specific value.
[0431] As a response to the client 200, the RAMNF 100 transmits group information of the UE 40 that is in the registered state and the connected state, is located at a specific location, and has predetermined power information (step S1108). For example, as a response to the RAMNF 100, the client 200 transmits group information of the UE 40 that is in the registered state and the connected state, is located at a specific location, and has a remaining battery level equal to or higher than a specific value.
[0432] In this way, the RAMNF 100 receives from the client 200 a request for the ID of the UE 40 that is in a specific power state (eg, the remaining battery power is equal to or higher than a specific level), is in a specific area, and is in a registered state and a connected state.
[0433] The RAMNF 100 notifies the client 200 of the UE ID of the UE 40 in a specific power state, in a specific area, and in a registered state and a connected state as group information. The RAMNF 100 detects a group of UEs 40 corresponding to the registration condition specified by the client 200 (here, UEs 40 in a specific area, in a registered state and a connected state, and in a specific power state) from all the information that has been grasped, and creates group information.
[0434] It should be noted that at least one RAMNF 100 may be arranged in a private network. The RAMNF 100 uses all UEs 40 belonging to a private network as a general parameter, searches for UEs 40 corresponding to the conditions therefrom, and provides information to the client 200.
[0435] As described above, the RAMNF 100 according to the present embodiment provides the client 200 with at least one UE 40 satisfying the condition specified by the client 200 as group information. As a result, the client 200 can receive one or more candidates for the UE 40 satisfying the condition. The client 200 can access all UEs 40 included in the group information, or can select and access a certain UE 40 therefrom.
[0436] The client 200 can acquire information (e.g., registration information) about the status of the UE 40 as one of the network information (first information) as a group. As a result, compared with the case where the UE 40 is designated to acquire information, the signaling between the client 200 and the RAMNF 100 is reduced according to the number of UEs 40 included in the group information.
[0437] As a result, the operation of the client 200 is simplified, and the client 200 can avoid the congested state of the network.
[0438] <<5. Application Examples>>
[0439] Next, a case where the information processing system 1 according to the embodiment is applied will be described. It should be noted that an application example of the information processing system 1 according to the third embodiment will be described below, but the first and second embodiments can be similarly applied to each case.
[0440] <5.1. First application example>
[0441] Fig.30 is a diagram showing an example of an information processing system 1 according to a first application example of the present disclosure. Fig.30 The information processing system 1 is applied to a factory. Here, the UE 40 is a camera arranged in the factory.
[0442] Fig.30 A case where three cameras 40A1 to 40A3 are arranged is shown, but the number of cameras is not limited to three and may be two or less or four or more.
[0443] For example, the client 200 providing management services for a factory queries the RAMNF 100 to obtain group information of cameras that are arranged in a specific area in the factory (location condition) and are in a registered state (registration condition).
[0444] In the RAMNF 100, for example, it is assumed that 40A1 and 40A2 are UEs 40 that satisfy the condition specified by the client 200. The RAMNF 100 responds to the client 200 with group information including IDs (eg, UE IDs) that specify the cameras 40A1 and 40A2.
[0445] The client 200 that has received the group information accesses the camera 40A2 and, for example, requests the camera 40A2 to upload information captured by the camera 40A2 (or a currently captured image).
[0446] As described above, the client 200 can acquire group information about the UE 40 that satisfies the condition from the RAMNF 100 by specifying the condition.
[0447] <5.2. Second application example>
[0448] Fig.31 is a diagram showing an example of an information processing system 1 according to a second application example of the present disclosure. Fig.31 The information processing system 1 is applied to a drone system. Here, the UE 40 is a drone.
[0449] Fig.31 The situation where four drones 40B1 to 40B4 are flying is shown, but the number of drones is not limited to four, and may be three or less or five or more. For example, the number of drones may be several hundred.
[0450] For example, the client 200 that provides management services for drones makes a query to the RAMNF 100 in order to learn the group information of drones that pass through a specific area and perform image capture. At this time, in order to immediately access the drone, the client 200 specifies the drone that is currently in the registered state and makes a query about the group information. That is, the client 200 makes a query to the RAMNF 100 by using the past terminal location information (passing through the specific area in the past) as the location information and using the current registered state as the registration condition.
[0451] In the RAMNF 100, for example, it is assumed that the drones 40B2 and 40B4 are UEs 40 that satisfy the conditions specified by the client 200. The RAMNF 100 responds to the client 200 with group information including IDs (eg, UE IDs) that specify the drones 40B2 and 40B4.
[0452] The client 200 that has received the group information accesses the drone 40B2 and, for example, requests the drone 40B2 to upload information captured by the drone 40B2 within a specific area.
[0453] As described above, the client 200 can acquire group information about the UE 40 satisfying the condition from the RAMNF 100 by specifying the condition. At this time, the client 200 can specify the past terminal location information and acquire the group information.
[0454] <5.3. Third application example>
[0455] The case where the information processing system 1 is applied to a temperature measurement system will be described. Here, the UE 40 is a temperature sensor arranged in a certain area. A large number of temperature sensors can be arranged in the area. In addition, there can be a plurality of areas where temperature sensors are arranged. The battery of such a temperature sensor is often difficult to replace, so it is desired to suppress power consumption as much as possible.
[0456] Therefore, the client 200 managing the temperature sensor queries the RAMNF 100 to learn the group information of the temperature sensor in the RRC connected state. At this time, the client 200 can specify the area and query.
[0457] The RAMNF 100 responds to the client 200 with group information including IDs (eg, UE IDs) indicating temperature sensors that satisfy the condition (are in the RRC connected state).
[0458] The client 200 receiving the group information selects a predetermined number (eg, five) of temperature sensors from among the temperature sensors included in the group information so that the positions of the temperature sensors are dispersed. The client 200 accesses the selected temperature sensors and acquires temperature information.
[0459] As a result, the client 200 can access the temperature sensor in the RRC connected state, and does not need to activate the temperature sensor in the RRC idle state. In addition, the client 200 can access the temperature sensor at the desired location among the temperature sensors in the RRC connected state, and can obtain the desired temperature information.
[0460] <<6. Other embodiments>>
[0461] The embodiments and application examples described above merely show examples, and various modifications and applications are possible.
[0462] For example, the control device that controls the information processing device 10, the base station 20, and the terminal device 40 of the above-described embodiments may be implemented by a dedicated computer system, or may be implemented by a general-purpose computer system.
[0463] For example, a communication program for implementing the operations described above is stored in a computer-readable recording medium and distributed, such as an optical disk, a semiconductor memory, a magnetic tape, or a flexible disk. Subsequently, the control device is implemented, for example, by installing the program in a computer and implementing the processing described above. At this time, the control device may be a device (such as a personal computer) outside the information processing device 10, the base station 20, and the terminal device 40. In addition, the control device may be a device (such as control units 13, 24, and 45) inside the information processing device 10, the terminal device 40, and the base station 20.
[0464] In addition, the communication program may be stored in a disk device included in a server device on a network such as the Internet, and may be downloaded to a computer. In addition, the functions described above may be implemented by cooperation between an operating system (OS) and application software. In this case, the portion other than the OS may be stored in a medium and distributed, or the portion other than the OS may be stored in a server device and downloaded to a computer.
[0465] In addition, among the corresponding processes described in the embodiments described above, all or part of the processes described as being automatically implemented can be implemented manually. Alternatively, all or part of the processes described as being manually implemented can be automatically implemented by known methods. In addition, unless otherwise indicated, the processing procedures, specific names, and information including various data and parameters shown in this specification and the accompanying drawings can be changed arbitrarily. For example, the various information shown in the accompanying drawings is not limited to the information shown in the accompanying drawings.
[0466] In addition, each of the components shown in each device is a functional concept and does not have to be physically configured as shown in the figure. That is, the specific mode of distribution / integration of each device is not limited to the form shown in the drawings. According to various loads or usage conditions, etc., all or part of the equipment can be distributed / integrated in any unit in terms of function or physics. It should be noted that this configuration through distribution and integration can be implemented dynamically.
[0467] Furthermore, the embodiments described above may be appropriately combined in the case where the processing contents do not contradict each other. Furthermore, the order of the respective steps shown in the sequence diagrams of the embodiments described above may be appropriately changed.
[0468] In addition, the present embodiment can be implemented as any component included in a device or system, such as a processor as a system large-scale integration (LSI), a module using multiple processors, a unit using multiple modules, a set obtained by further adding other functions to the unit, etc. (that is, some components of the device).
[0469] It should be noted that in the present embodiment, a system means a collection of a plurality of components (devices, modules (components), etc.), and it is not important whether all the components are in the same housing. Therefore, a plurality of devices housed in separate housings and connected via a network and one device housing a plurality of modules in one housing are both systems.
[0470] Furthermore, the present embodiment may adopt a cloud computing configuration, for example, in which a function is collaboratively shared and processed by multiple devices over a network.
[0471] <<7. Conclusion>>
[0472] Although the embodiments of the present disclosure are described above, the technical scope of the present disclosure is not limited to the embodiments described above, and various modifications may be made without departing from the scope of the present disclosure. In addition, components of different embodiments and modified examples may be appropriately combined.
[0473] In addition, the effects in each embodiment described in this specification are merely examples. The effects of the present disclosure are not limited thereto, and other effects may be obtained.
[0474] It should be noted that the present technology may also have the following configurations.
[0475] (1) An information processing device comprising:
[0476] The control unit performs the following operations:
[0477] obtaining first information about the terminal device from the core network via a service-based interface (SBI),
[0478] acquiring second information, wherein the second information includes at least one of measurement information measured based on the first information or terminal related information acquired from the terminal device directly or through the SBI,
[0479] specifying the terminal device from the second information or by associating the first information and the second information with each other, and
[0480] The client device is notified of at least one of the first information or the second information associated with the specified terminal device.
[0481] (2) The information processing device according to (1), wherein the terminal-related information includes information included in an application layer of the terminal device.
[0482] (3) An information processing device according to (1) or (2), wherein the terminal-related information includes at least one of scheduling information about a registration schedule, power information about power consumption of the terminal device, or location information about a location of the terminal device.
[0483] (4) The information processing device according to (3), wherein the position information is measured using equipment installed on a terminal device.
[0484] (5) The information processing device according to (3) or (4), wherein
[0485] The location information includes at least one of current location information, past location information, or future location information.
[0486] (6) The information processing device according to any one of (3) to (5), wherein
[0487] The first information includes registration information about registration of the terminal device, and
[0488] The client device determines a terminal device to be accessed based on the power information and the registration information.
[0489] (7) The information processing device according to any one of (3) to (6), wherein
[0490] The first information includes registration information about registration of the terminal device, and
[0491] The client device determines the terminal device to be accessed based on the location information and the registration information.
[0492] (8) The information processing device according to any one of (1) to (7), wherein the control unit notifies the client device of group information including at least one item of information on the terminal device satisfying a condition specified by the client device.
[0493] (9) An information processing device according to (8), wherein the condition includes at least one of the following conditions: a registration condition that specifies a registration state of the terminal device, a power condition that specifies a power consumption state of the terminal device, or a location condition that specifies a location of the terminal device.
[0494] (10) The information processing device according to (9), wherein the location condition includes a condition that specifies at least one of a current location, a past location, or a future location of the terminal device.
[0495] (11) The information processing device according to any one of (1) to (10), wherein
[0496] The first information includes registration information about registration of the terminal device, and
[0497] The measurement information includes information on a transition interval of registration of a terminal device calculated based on the registration information.
[0498] (12) The information processing device according to (11), wherein the measurement information includes information about an idle transition time until the terminal device transitions to an idle state.
[0499] (13) The information processing device according to (12), wherein the client device communicates with the terminal device before a timing at which the terminal device transitions to an idle state based on the measurement information.
[0500] (14) An information processing method comprising:
[0501] obtaining first information about the terminal device from a core network via a service-based interface (SBI);
[0502] Acquire second information, where the second information includes at least one of measurement information measured based on the first information or terminal related information acquired from the terminal device directly or through the SBI;
[0503] specifying the terminal device from the second information or by associating the first information and the second information with each other; and
[0504] The client device is notified of at least one of the first information or the second information associated with the specified terminal device.
[0505] (15) A terminal device comprising:
[0506] The control unit notifies the information processing device of the terminal related information directly or through a service-based interface (SBI), wherein
[0507] The information processing device implements the following operations:
[0508] Obtain the first information about the terminal device from the core network through SBI,
[0509] specifying the terminal device from the terminal related information or by associating the first information and the terminal related information with each other, and
[0510] The client device is notified of at least one of the first information associated with the specified terminal device or the terminal-related information.
[0511] (16) A system comprising: a first information processing device; a second information processing device that functions as a network function of a core network; and a terminal device, wherein
[0512] The first information processing device includes a control unit, which performs the following operations:
[0513] acquiring first information about the terminal device from the second information processing device through a service-based interface (SBI),
[0514] acquiring second information, wherein the second information includes at least one of measurement information measured based on the first information or terminal related information acquired from the terminal device directly or through the SBI,
[0515] specifying the terminal device from the second information or by associating the first information and the second information with each other, and
[0516] The client device is notified of at least one of the first information or the second information associated with the specified terminal device.
[0517] Reference numerals list
[0518] 1——Information Processing System
[0519] 10——Information processing equipment
[0520] 11 - Communication unit
[0521] 12, 22, 42 - storage unit
[0522] 13, 24, 45 - Control unit
[0523] 20——Base Station
[0524] 21, 41——Signal processing unit
[0525] 23——Network Communication Unit
[0526] 40——Terminal equipment
[0527] 44 - Input / output unit
Claims
1. An information processing device, comprising: One or more network interfaces; as well as A circuit configured to: using the one or more network interfaces, obtaining first information about the terminal device from a core network via a service-based interface (SBI), acquiring second information using the one or more network interfaces, wherein the second information includes terminal related information acquired from the terminal device directly or through the SBI, wherein the terminal related information is application layer information of the terminal device, specifying the terminal device from the second information or by associating the first information and the second information with each other, and The client device is notified of the first information and the second information associated with the specified terminal device.
2. The information processing device according to claim 1, wherein: The terminal related information is behavior information of the terminal device originating from the application layer of the terminal device.
3. The information processing device according to claim 1, wherein: The terminal related information includes at least one of schedule information about a registration schedule, power information about power consumption of a terminal device, or location information about a location of a terminal device.
4. The information processing device according to claim 3, wherein: The position information is measured using equipment installed on the terminal device.
5. The information processing device according to claim 3, wherein The location information includes at least one of current location information, past location information, or future location information.
6. The information processing device according to claim 3, wherein The first information includes registration information about registration of the terminal device, and The terminal device is accessed by the client device based on the power information and the registration information.
7. The information processing device according to claim 3, wherein The first information includes registration information about registration of the terminal device, and The terminal device is accessed by the client device based on the location information and the registration information.
8. The information processing device according to claim 1, wherein: The circuit is also configured to implement the following operations: The client device is notified of group information, where the group information includes at least one item of information about terminal devices that meet a condition specified by the client device.
9. The information processing device according to claim 8, wherein: The condition includes at least one of: a registration condition specifying a registration state of the terminal device, a power condition specifying a power consumption state of the terminal device, or a location condition specifying a location of the terminal device.
10. The information processing device according to claim 9, wherein: The location condition includes a condition specifying at least one of a current location, a past location, or a future location of the terminal device.
11. The information processing device according to claim 1, wherein The first information includes registration information about registration of the terminal device, and The measurement information includes information on a transition interval of registration of a terminal device calculated based on the registration information.
12. The information processing device according to claim 11, wherein: The measurement information includes information about an idle transition time until the terminal device transitions to an idle state.
13. The information processing device according to claim 12, wherein: The terminal device receives communication from the client device before the timing at which the terminal device transitions to the idle state based on the measurement information.
14. An information processing method, comprising: Using one or more network interfaces, obtaining first information about the terminal device from a core network via a service-based interface (SBI); Acquire second information using the one or more network interfaces, where the second information includes terminal related information acquired from the terminal device directly or through the SBI, where the terminal related information is application layer information of the terminal device; specifying the terminal device from the second information or by associating the first information and the second information with each other; as well as The client device is notified of the first information and the second information associated with the specified terminal device.
15. A terminal device, comprising: A circuit configured to: notifying a core network of the first information via a service-based interface (SBI), and The information processing device is notified of second information including terminal related information directly or through SBI, where the terminal related information is application layer information of the terminal device.
16. A system comprising: a first information processing device; A second information processing device that serves as a network function of the core network; as well as Terminal equipment, where The first information processing device includes one or more network interfaces and circuits configured to implement the following operations: using the one or more network interfaces, acquiring first information about the terminal device from the second information processing device through a service-based interface (SBI), acquiring second information using the one or more network interfaces, wherein the second information includes terminal related information acquired from the terminal device directly or through the SBI, wherein the terminal related information is application layer information of the terminal device, specifying the terminal device from the second information or by associating the first information and the second information with each other, and The client device is notified of the first information and the second information associated with the specified terminal device.
