Mobile communication networks and wireless devices

Abstract

It suppresses congestion in control signaling even as the number of wireless devices increases. [Solution] The mobile communication network comprises a core network including a plurality of network nodes, a plurality of base station devices connected to the core network, and a management device for transmitting topic data and managing sessions associated with a topic. When the management device receives a request for a first session associated with a first topic from a first base station device among the plurality of base station devices, it performs processing to establish the first session from the first base station device to a first network node among the plurality of network nodes, and transmits first session information relating to the first session to the first base station device for storage.

Description

Technical Field

[0001] The present disclosure relates to a mobile communication network and a wireless device.

Background Art

[0002] A mobile communication network is composed of a radio access network (RAN) and a core network (CN). The RAN establishes a radio link with a wireless device (WD), also called a user equipment (UE). The CN connects to an external data network (DN) such as the Internet. As disclosed in Non-Patent Document 1, the mobile communication network establishes a connection that connects the WD and the Internet via the RAN and the CN. In the fifth-generation (5G) network defined by 3GPP (registered trademark), this connection is called a PDU session. Internet Protocol (IP) packets transmitted and received between the WD and the Internet are carried on the PDU session.

[0003] In a 5G network, the RAN includes a base station device (BS) denoted as a g-node B (gNB). The base station device can be realized as one device. Also, the base station device can be functionally divided into radio units (RUs), distributed units (DUs), and central units (CUs) that can be arranged at different positions. Further, the CU can be functionally divided into a control plane (CP) unit (CU-CP) and a user plane (UP) unit (CU-UP).

[0004] The CN includes the network functions (NF) of the control plane and the NF of the user plane. The NF of the control plane includes, for example, the access and mobility management function (AMF) that manages the mobility of the WD, the session management function (SMF) that manages PDU sessions to the WD, and the unified data management (UDM) that stores subscriber information of the WD. The NF of the user plane includes the user plane function (UPF) that forwards user packets sent and received by the WD. The UPF that terminates a PDU session is called the PDU session anchor UPF (PSA-UPF), and the UPF that is between the PSA-UPF and the RAN and forwards user packets is called the intermediate UPF (I-UPF). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 23.502 V17.11.0, December 2023 [Overview of the project] [Problems that the invention aims to solve]

[0006] WDs (Working Devices) include those designed for human operation, such as smartphones and tablets, and those that do not require human operation, also known as IoT devices. IoT stands for Internet of Things. IoT devices, for example, read the amount of electricity used from an energy meter and send the reading data to a server on the internet. Alternatively, IoT devices may have sensors that measure temperature, etc., and send the measurement results to a server on the internet. Because the fields in which IoT devices can be applied are very broad, it is predicted that a very large number of IoT devices will be used in the future.

[0007] When the number of Work Devices (WDs) using a mobile communication network becomes very large, the number of PDU sessions that the mobile communication network needs to process also becomes very large, which can cause congestion in control signaling. When congestion occurs in control signaling, the time it takes to set up a PDU session can increase, and the time between when data to be sent to a WD is generated and when the WD actually sends the data can increase. Furthermore, because the number of PDU sessions that the UPF needs to process also becomes very large, the amount of information that the UPF needs to maintain regarding PDU sessions also increases. This can lead to increased processing delays in the UPF.

[0008] This disclosure provides a technology that can suppress congestion in control signaling even when the number of wireless devices increases, or that can suppress the increase in processing delay at data transfer nodes. [Means for solving the problem]

[0009] According to one aspect of this disclosure, a mobile communication network comprises a core network including a plurality of network nodes, a plurality of base station devices connected to the core network, and a management device for transmitting topic data and managing sessions associated with a topic. When the management device receives a request for a first session associated with a first topic from a first base station device among the plurality of base station devices, it performs processing to establish the first session from the first base station device to a first network node among the plurality of network nodes, and transmits first session information relating to the first session to the first base station device for storage. [Effects of the Invention]

[0010] According to this disclosure, congestion in control signaling can be suppressed even as the number of wireless devices increases, or the increase in processing delay at data transfer nodes can be suppressed. [Brief explanation of the drawing]

[0011] [Figure 1]Exemplary system configuration diagram. [Figure 2] Diagram showing an example of the configuration of a mobile communication network. [Figure 3] Diagram showing an example of management information. [Figure 4] Sequence diagram of the initial process for SS setting. [Figure 5] Diagram showing the state after completion of the process in FIG. 4. [Figure 6] Sequence diagram of SS setting process. [Figure 7] Diagram showing the state after completion of the process in FIG. 6. [Figure 8] Sequence diagram of data transmission by WD. [Figure 9] Sequence diagram of SS setting process. [Figure 10] Diagram showing the state after completion of the process in FIG. 10. [Figure 11] Sequence diagram of SS setting process. [Figure 12] Diagram showing the state after completion of the process in FIG. 11. [Figure 13] Sequence diagram of SS setting process. [Figure 14] Diagram showing the state after completion of the process in FIG. 13. [Figure 15] Sequence diagram of SS release process.

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of the features described in the embodiments are essential for the invention. Two or more of the features described in the embodiments may be arbitrarily combined. Also, the same or similar configurations are given the same reference numerals, and duplicate descriptions are omitted.

[0013] In this embodiment, a server on the internet collects data from a WD. The WD is, for example, an IoT device, in which case the server collects data read by the WD from predetermined devices such as sensors or energy meters. Alternatively, the WD may be a device intended for user operation, such as a smartphone, and the server collects data entered by the user of the WD, as well as data that the WD can acquire. In the following description, the data collected by the server from the WD will also be referred to as "collected data".

[0014] In this embodiment, collected data is associated with a "topic". For example, if business operators A and B each attach a WD to an energy meter and collect energy consumption data from the WD, the energy consumption data collected by the WD used by a user contracted with business operator A is associated with topic #1, and the energy consumption data collected by the WD used by a user contracted with business operator B is associated with topic #2. Furthermore, if business operators A and B each install a WD with a temperature measuring function and collect temperature data, the temperature data collected by the WD installed by business operator A is associated with topic #3, and the temperature data collected by the WD installed by business operator B is associated with topic #4. Thus, a topic is used to identify the attributes of the collected data and can be identified by the content of the information the collected data represents, the business operator collecting the data from the WD, or a combination thereof. Each piece of collected data is associated with one of the topics.

[0015] FIG. 1 is an exemplary system configuration diagram used for the description of the present embodiment. BS1 has a function of communicating wirelessly with a WD (not shown). BS1 is configured to be communicable with a network node 2 provided in a core network. In the following description, the network node 2 is simply referred to as node 2. The two nodes 2 shown in FIG. 1 are each connected to the Internet 4. Further, two servers 3 are connected to the Internet 4. In FIG. 1, four BS1s, two nodes 2, and two servers 3 are shown, but these numbers are exemplary, and the numbers of BS1, node 2, and server 3 are not limited to the numbers shown in FIG. 1. In the following description, when distinguishing a plurality of BS1s, they are denoted as BS#1, BS#2, ···, when distinguishing a plurality of nodes 2, they are denoted as node#1, node#2, ···, and similarly, when distinguishing a plurality of servers 3, they are denoted as server#1, server#2, ···.

[0016] For example, server#1 and server#2 in FIG. 1 each collect data on different topics. Therefore, the mobile communication network sets a connection that is referred to as a service session (SS) associated with the topic. The SS associated with the topic is used for transporting the collected data of the topic. Note that the SS associated with the topic is a one-way connection in the direction from BS1 to the server 3 that collects the data of the topic. It is also possible to configure one server 3 to collect data on a plurality of topics.

[0017] Figure 2 is a diagram of the configuration of a mobile communication network according to this embodiment. As shown in Figure 2, the mobile communication network has a plurality of BS1 and a CN10 connected to the plurality of BS1. The CN10 has a plurality of nodes 2, an AMF5 and an SS management function (SSMF)6. The AMF5 and SSMF6 are NFs of the control plane, and the nodes 2 are NFs of the user plane. The SSMF6 manages SSs for each topic. The SSMF6 holds the management information shown in Figure 3. Alternatively, the SSMF6 is configured to be able to access the management information by accessing an NF, such as a UDM, that holds the management information shown in Figure 3.

[0018] Management information includes a topic identifier, Service System Information (SSI) associated with the topic, and service provider information regarding the service provider that collects data for the topic. The topic's SSI includes authentication data. The topic's SSI may further include information about the Quality of Service (QoS) applied to the SS for the topic. The topic's service provider information may include the identifier of the service provider that collects data for the topic, and authentication information. According to Figure 3, the topic identified by TP#1 is collected by the service provider identified by OP#1. The SSI associated with TP#1 also shows CD#1 as authentication data.

[0019] In the following, the topic with identifier TP#1 shown in Figure 3 will be referred to as "Topic TP#1," and the method for configuring the SS of topic TP#1 will be explained. The SSI of topic TP#1 will be referred to as "SSI#1." Furthermore, the business operator identified by OP#1 that collects data for TP#1 will be referred to as "Business Operator OP#1."

[0020] Figure 4 shows the initial sequence. In Figure 4, Server #1 is Server 3 located on Internet 4, which is used by Operator OP #1 to collect data for topic TP #1. In S100, Server #1 sends an SS request message to SSMF6. When SSMF6, which is the NF of the CN10 control plane, communicates with devices on an external network such as Internet 4, it may be configured to go through the Network Exposure Function (NEF), which is the NF of the CN10 control plane. In other words, communication between Server #1 and the NF of the CN control plane may be performed indirectly via the NEF, or directly without going through the NEF.

[0021] The SS request message includes TP#1, which is the identifier of topic TP#1 collected by server #1. Although omitted in the sequence shown in Figure 4, SSMF6 responds to the SS request message by authenticating server #1 using the authentication information AUTH#1 contained in the carrier information of topic TP#1. If authentication is unsuccessful, SSMF6 does not proceed with processing from S101 onward.

[0022] Upon successful authentication, SSMF6 selects one node from among multiple nodes 2 to send data for topic TP#1 to server #1. The selected node 2 must be connected to the Internet 4. How SSMF6 selects the node 2 from among multiple nodes 2 connected to the Internet 4 to send data for topic TP#1 to server #1 is arbitrary. In this embodiment, it is assumed that SSMF6 has selected node #1.

[0023] In S101, SSMF6 sends the identifier TP#1 of topic TP#1, along with the SSI#1 associated with topic TP#1, to node #1. In S103, node #1 stores the SSI#1 associated with TP#1. Also, in S102, SSMF6 notifies server #1 of the selected node #1. In S104, server #1 sends a message to node #1 to subscribe to topic TP#1. As a result, node #1 forwards any data received from topic TP#1 to server #1. In other words, as shown in Figure 5, an SS from node #1 to server #1 is established.

[0024] Figure 6 shows the process when WD#1, which collects data for topic TP#1, is powered on. It is assumed that the subscriber information for WD#1 stored in the NF within CN10 of the mobile communication network indicates that WD#1 will collect data for topic TP#1. Upon power-on, WD#1 establishes a wireless link with BS#1 in S200. After the wireless link is established, WD#1 sends a registration request message to AMF5 via BS#1 in S201 and S202. Although omitted in the sequence in Figure 6, upon receiving the registration request message, AMF5 authenticates WD#1 based on the subscriber information. If authentication is successful, AMF5 sends a registration response message to BS#1 in S203. Since the subscriber information for WD#1 indicates that WD#1 will collect data for topic TP#1, AMF5 includes information in the registration response message indicating that WD#1 will collect data for topic TP#1.

[0025] When BS#1 receives a registration response message containing information indicating that WD#1 will collect data for topic TP#1, it determines whether it holds SSI#1, which is the SSI for topic TP#1. In this example, BS#1 does not hold SSI#1, so in S204, BS#1 sends an SS request message to SSMF6 via AMF5 requesting the configuration of SSI#1 and SS for topic TP#1. In response to the SS request message, SSMF6 sends SSI#1 to BS#1 via AMF5 in S205. Also, in S207, SSMF6 notifies node #1 that BS#1 will subscribe to topic TP#1.

[0026] In S206, BS#1 stores SSI#1 received from SSMF6, associating it with TP#1. Also, in response to the notification in S207, node #1 sends a message to BS#1 in S208 to subscribe to topic TP#1. The message to subscribe to topic TP#1 notifies the destination device that, upon receiving data from topic TP#1, will send the received data to the sender of the message. In S208, node #1 subscribes to topic TP#1 from BS#1, and BS#1 then forwards any data received from topic TP#1 to node #1. Thus, as shown in Figure 7, an SS from BS#1 to node #1 is established.

[0027] Upon obtaining SSI#1 and establishing SS for topic TP#1, BS#1 sends a registration response message to WD#1 in S209. The registration response message sent to WD#1 includes SSI#1. In S210, WD#1 stores SSI#1 associated with TP#1. WD#1 retains SSI#1 while registered with the mobile communication network. In other words, WD#1 continues to retain SSI#1 without discarding it, even if it transitions to an idle state without a radio link with BS1 of the mobile communication network.

[0028] At point S210, WD#1 has established a wireless link with BS#1. Therefore, if WD#1 has the data for topic TP#1 to send to server#1 at this point, at S300 in Figure 8, WD#1 sends the data for topic TP#1 to BS#1. BS#1 sends the data for topic TP#1 to node#1 at S301. Node#1 sends the data for topic TP#1 to server#1 at S302.

[0029] The transfer of data for topic TP#1 at BS#1 and node#1 may be performed based on the QoS information contained in SSI#1. The data for topic TP#1 transmitted by WD#1 includes the identifier TP#1 and collected data such as temperature collected by WD#1, but it does not need to be in IP packet format within the mobile communication network. Node#1 stores the data for topic TP#1 transmitted by WD#1 in the payload of an IP packet and sends it to server#1.

[0030] Furthermore, once the transmission of TP#1 data is complete in S300, WD#1 can release the wireless link with BS#1 and enter an idle state, regardless of whether BS#1 has started or completed the transmission of topic TP#1 data to node#1. As shown in Figure 8, WD#1 enters an idle state in S303.

[0031] Subsequently, when data for topic TP#1 to be sent to server #1 is generated, WD#1 establishes a wireless link with BS#1 in S304 and requests BS#1 to send the data for topic TP#1 in S305. At this time, WD#1 also sends the authentication information CD#1 contained in SSI#1 to BS#1. In response to the request to send the data for topic TP#1, BS#1 checks whether it holds the SSI#1 associated with topic TP#1. Since BS#1 holds the SSI#1, it determines whether the CD#1 received from WD#1 matches the authentication information contained in the SSI#1 it holds. If they do not match, BS#1 rejects the transmission request from WD#1. In this example, they match, so BS#1 sends a transmission response to WD#1 in S306.

[0032] Upon receiving the send response, WD#1 sends the data for topic TP#1 to BS#1 in S307, BS#1 sends the data for topic TP#1 to node#1 in S308, and node#1 sends the data for topic TP#1 to server#1 in S309.

[0033] Assume that after the sequence in Figure 6 is completed, the power to WD2, which collects data for topic TP#1 within the service area of ​​BS#1, is turned on. In this case, since BS#1 has already stored SSI#1, processing S204 to S208 is skipped.

[0034] Figure 9 shows the sequence of events when WD#1, which is idle within the service area of ​​BS#1, moves into the service area of ​​BS#2 while remaining idle, and when data for topic TP#1, which should be sent to server#1, is generated within the service area of ​​BS#2. Note that BS#2 does not have SSI#1.

[0035] WD#1 establishes a wireless link with BS#2 at S400 and requests BS#2 to transmit data for topic TP#1 at S401. At this time, WD#1 also sends authentication information CD#1, which is included in SSI#1, to BS#2. Since BS#2 does not hold SSI#1 associated with topic TP#1, at S402 it sends an SS request message to SSMF6 via AMF5 requesting the configuration of SSI#1 and SS for topic TP#1. In response to the SS request message, SSMF6 sends SSI#1 to BS#2 via AMF5 at S403 and notifies node #1 at S405 that BS#2 will subscribe to topic TP#1.

[0036] In S404, BS#2 stores SSI#1 received from SSMF6, associating it with TP#1. Also, in response to the notification in S405, node #1 sends a message to BS#2 in S406 to subscribe to topic TP#1. In S406, node #1 subscribes to topic TP#1 from BS#2, and as a result, BS#2 forwards any data received from topic TP#1 to node #1. In other words, as shown in Figure 10, an SS from BS#2 to node #1 is established.

[0037] BS#2 determines whether the authentication information contained in SSI#1 received from SSMF6 matches the authentication information CD#1 received from WD#1 in S401. In this example, they match, so BS#2 sends a transmit response to WD#1 in S407. Upon receiving the transmit response, WD#1 sends the data for topic TP#1 to BS#2 in S408, BS#2 sends the data for topic TP#1 to node#1 in S409, and node#1 sends the data for topic TP#1 to server#1 in S410. If the authentication information contained in SSI#1 received from SSMF6 does not match the authentication information CD#1 received from WD#1 in S401, BS#2 will, for example, not send a transmit response, or send a rejection response to WD#1 to refuse to relay the data for topic TP#1.

[0038] Furthermore, after the sequence in Figure 9 is completed, if WD#2, which is idle and holding SSI#1, sends data for topic TP#1 to server#1, then because BS#2 is holding SSI#1, processing S402 to S406 will be skipped.

[0039] In the sequences shown in Figures 6 and 9, SSMF6 established an SS from BS1 to node #1 in response to an SS request from BS1. However, SSMF6 can also establish multiple SSs between BS1 and node #1, not just an SS connecting BS1 and node #1, via one or more other nodes 2.

[0040] Figure 11 shows the sequence of events when WD#1, which is idle within the service area of ​​BS#2, moves into the service area of ​​BS#3 while remaining idle, and when data for topic TP#1 to be sent to server#1 is generated within the service area of ​​BS#3. Note that BS#3 does not have SSI#1.

[0041] S500-S502 are the same as S400-S402 in Figure 9. In response to the SS request message, SSMF6 determines that BS#3 should send the data for topic TP#1 to node #1 via node #2. This determination is based, for example, on the placement of BS1 and node 2, and the number of SS already set up on node 2. For this reason, in S503, SSMF6 sends SSI#1 to node #2, and in S505, notifies node #1 that node #2 will subscribe to topic TP#1. Also, in S507, SSMF6 sends SSI#1 to BS#3, and in S509, notifies node #2 that BS#3 will subscribe to topic TP#1.

[0042] Node #2 stores SSI#1 received from SSMF6 in association with TP#1 in S504, and BS#3 stores SSI#1 received from SSMF6 in association with TP#1 in S508. Also, in response to the notification in S505, Node #1 sends a message to Node #2 in S506 to subscribe to topic TP#1. Similarly, in response to the notification in S509, Node #2 sends a message to BS#3 in S510 to subscribe to topic TP#1.

[0043] In S506, node #1 subscribes to topic TP#1 from node #2, so when node #2 receives data from topic TP#1, it forwards it to node #1. Similarly, in S510, node #2 subscribes to topic TP#1 from BS#3, so when BS#3 receives data from topic TP#1, it forwards it to node #2. Therefore, as shown in Figure 12, an SS from BS#3 to node #2 and an SS from node #2 to node #1 are established.

[0044] BS#3 receives authentication information in SSI#1 from SSMF6, which matches authentication information CD#1 received from WD#1 in S501. Therefore, in S511, BS#3 sends a transmit response to WD#1. Upon receiving the transmit response, WD#1 sends the data for topic TP#1 to BS#3 in S512. BS#3 sends the data for topic TP#1 to node#2 in S513. Node#2 sends the data for topic TP#1 to node#1 in S514. Node#1 sends the data for topic TP#1 to server#1 in S515.

[0045] Figure 13 shows the sequence when WD#1, which has established a wireless link with BS#3, moves to the service area of ​​BS#4, that is, the sequence for handing over WD#1 from BS#3 to BS#4. Note that BS#4 does not store SSI#1. Also, in this example, SSMF6 will determine that BS#4 will also set up an SS via node#2.

[0046] Following the movement of WD#1, BS#3 determines that WD#1 should be handed over to BS#4, and therefore, BS#3 notifies BS#4 of the handover of WD#1 to BS#4 via S600. Since WD#1 collects data from topic TP#1, BS#3 notifies BS#4 that WD#1 will collect data from topic TP#1 by including the identifier TP#1 in the notification via S600. Since BS#4 does not hold SSI#1 associated with topic TP#1, it sends an SS request message via AMF5 to SSMF6 via S601 requesting the configuration of SS#1 and SS for topic TP#1. In response to the SS request message, SSMF6 sends SSI#1 to BS#4 via AMF5 via S602, and also notifies node #2 via S604 that BS#4 will subscribe to topic TP#1.

[0047] In S603, BS#4 stores SSI#1 received from SSMF6, associating it with TP#1. Also, in response to the notification from S604, node #2 sends a message to BS#4 in S605 to subscribe to topic TP#1. In S605, node #2 subscribes to topic TP#1 from BS#4, and as a result, BS#4 forwards any data received from topic TP#1 to node #2. Thus, as shown in Figure 14, an SS (Service Station) is established from BS#4 to node #2.

[0048] Having established a Service Station (SS) for topic TP#1 and obtained the SS information associated with topic TP#1, BS#4 sends a response to BS#3 in S600 in S606. Having received the response from BS#4 in S606, BS#3 instructs WD#1 to hand over to BS#4 in S607. In response to the handover instruction, WD#1 establishes a radio link with BS#4 in S608. Thereafter, WD#1 transmits topic TP#1 data to BS#4.

[0049] In this example, SSMF6 established an SS from BS#4 to node #2 through a handover from BS#3 to BS#4. However, even if an SS from BS#4 to node #1 is established, it is also possible to establish an SS from BS#4 to node #3 and an SS from node #3 to node #1.

[0050] Note that if BS#4 already holds SSI#1 before the start of the sequence in Figure 13, and therefore an SS for topic TP#1, which ultimately leads from BS#4 to node #1, is established, then processing S601-S605 will be skipped.

[0051] Furthermore, in the sequence shown in Figure 13, at S600, BS#3 notified BS#4 of the identifier TP#1. However, the configuration can be changed to send SSI#1, which is associated with topic TP#1, to BS#4. In this case, the processing at S602 can be omitted.

[0052] When WD#1 becomes idle and then moves to the service area of ​​BS#4, and transmits data for topic TP#1 within the service area of ​​BS#4, the sequence will be similar to that shown in Figure 11. However, in this case, SSMF6 can establish an SS from BS#4 to node #2 only, or an SS from BS#4 to node #1, or an SS from BS#4 to node #3 and an SS from node #3 to node #1.

[0053] In this embodiment, the SS established for topic TP#1 is maintained, for example, while server #1 is collecting data for topic TP#1. Maintaining the SS for topic Z from device X to device Y means that device X is operating to transfer data for topic Z to device Y, and that device Y is aware of receiving data for topic Z from device X. When server #1 stops collecting data for topic TP#1, the SS for topic TP#1 and SSI#1 stored in node 2 and BS1 are deleted.

[0054] For example, if Server #1 decides to stop collecting data for topic TP#1, it sends a message to SSMF6 indicating this. SSMF6 manages the SS established for topic TP#1. Therefore, in response to this message from Server #1, SSMF6 notifies each node that is subscribed to topic TP#1 to unsubscribe from it, i.e., to stop subscribing. For example, in the state shown in Figure 14, SSMF6 notifies nodes #1 and #2 to unsubscribe from topic TP#1. In response to this notification, node #1 sends messages to BS#1, BS#2, and node #2 to stop subscribing to topic TP#1. Node #2 also sends messages to BS#3 and node #4 to stop subscribing to topic TP#1. Nodes #1, #2, and BS#1-BS#4 then delete SSI#1.

[0055] Furthermore, BS1 can be configured to delete SSI#1 if it does not receive and transfer (transmit) TP#1 data from WD for a predetermined period of time or longer. Figure 15 shows the sequence when BS#1 deletes SSI#1.

[0056] BS#1 sends a message to SSMF6 in S700 requesting the release of the SS for topic TP#1. SSMF6 determines which node 2 is subscribed to topic TP#1 from BS#1. In this example, node 2 is node #1, so in S701, SSMF6 notifies node #1 that it will stop subscribing to topic TP#1 from BS#1. In response to this notification, node #1 sends a message to BS#1 in S702 to unsubscribe from topic TP#1. The message to unsubscribe from topic TP#1 notifies or requests that the destination device of the message, even if it receives data from topic TP#1, will not transmit the received data to the sender of the message. In response to this message, BS#1 stops transferring data from topic TP#1 to node #1 and deletes SSI#1 in S703.

[0057] As described above, according to this embodiment, SS is set on a topic-by-topic basis. The SS between node 2 connected to the Internet 4 and server 3 that collects topic data is established when server 3 starts collecting data. However, SS within the mobile communication network is established as needed, triggered by the registration process of the WD that collects data for the topic, the handover process, or the data transmission request for the topic. Furthermore, SS established within the mobile communication network is maintained even if the WD that triggered the establishment of the SS transitions to an idle state. The SSI is also maintained at node 2 and BS1 where the SS is established.

[0058] This configuration ensures that no matter how many WDs send data for a given topic, the information stored on Node 2 and BS1, where the topic's SS is configured, will only be one SSI per topic. Therefore, even if the number of WDs sending data increases, the amount of information that BS1 and Node 2 need to store to transfer the data does not increase, thus preventing increased processing delays on Node 2 and BS1.

[0059] When a WD transmits data for a topic, the only thing a BS (Band Station) with an already configured SS (Service Station) needs to do is establish a wireless link with the WD and determine, based on its stored SSI (Service Station Indicator), whether the WD is authorized to transmit data for that topic. It does not need to send or receive control signaling to establish connections (SS) with other nodes in the mobile communication network. Therefore, even if the number of WDs transmitting data increases, congestion of control signaling can be suppressed.

[0060] Furthermore, the WD according to this embodiment does not need to perform IP packetization to transmit topic data, thereby reducing the processing load on the WD. In this embodiment, the WD transmits data to server 3 on the Internet 4, and therefore node 2 connected to the Internet 4 performs IP packetization of messages. However, when CN10 connects to an external data network that does not use IP, such as a Content-Centric Network (CCN), and transmits data to a server on that external data network, IP packetization is not necessary for node 2 connected to the external data network. In this case, node 2 connected to the external data network transmits the message to the server according to the protocol used by that external data network.

[0061] The WD according to this disclosure transmits data for topic TP#1 to server 3, for example, via a mobile communication network. The WD also has a processing unit that receives SSI#1, which contains information used by BS1 to determine whether the WD is permitted to transmit data for topic TP#1, as a response to a registration request transmitted to the mobile communication network. The processing unit retains SSI#1 even when the WD transitions to an idle state.

[0062] Note that Node 2 and SSMF6 can each be implemented as a single device. Alternatively, Node 2 and SSMF6 can each be implemented as multiple devices capable of communicating with one another. Furthermore, Node 2 and SSMF6 can be implemented by having one or more processors in a device, and having those one or more processors execute an appropriate computer program. In addition, BS1 may be implemented as a single device, or it may consist of multiple devices located in different locations, such as a radio unit (RU), a distributed unit (DU), and a central unit (CU), or a baseband unit (BBU) and a remote radio unit (RRU).

[0063] Furthermore, the present disclosure provides a program executable on one or more processors. The program, when executed on one or more processors of the device, includes instructions that cause the device to function, for example, as BS1, Node 2, SSMF6, or WD as described in the embodiments. Furthermore, the present disclosure provides a non-temporary computer-readable storage medium storing the above program. Furthermore, the present disclosure provides methods that BS1, Node 2, AMF5, SSMF6, and WD perform for the processes illustrated in Figures 4, 6, 8, 9, 11, 13, and 15. Furthermore, the present disclosure provides a program for causing a device having one or more processors to perform these methods, and a non-temporary computer-readable storage medium storing the above program.

[0064] The invention is not limited to the embodiments described above, and various modifications and changes are possible within the scope of the gist of the invention.

[0065] With the above configuration, congestion in control signaling can be suppressed even as the number of wireless devices increases. Therefore, it becomes possible to contribute to Goal 9 of the United Nations-led Sustainable Development Goals (SDGs), "Build resilient infrastructure, promote sustainable industrialization and foster innovation." [Explanation of Symbols]

[0066] 1: Base station equipment, 2: Network node, 6: SSMF

Claims

1. A core network including multiple network nodes, Multiple base station devices connected to the aforementioned core network, A management device for sending topic data and managing sessions associated with a topic, Equipped with, A mobile communication network in which, upon receiving a request for a first session associated with a first topic from a first base station device among the plurality of base station devices, the management device performs processing to establish the first session from the first base station device to a first network node among the plurality of network nodes, and transmits first session information relating to the first session to the first base station device for storage.

2. The mobile communication network according to claim 1, wherein the first session information includes information used by the first base station device to determine whether a wireless device wirelessly connected to the first base station device is permitted to transmit data of the first topic.

3. The mobile communication network according to claim 1, wherein the management device causes the first network node to notify the first base station device that it will transmit data of the first topic to the first network node in order to establish the first session from the first base station device to the first network node.

4. The mobile communication network according to claim 1, wherein when the first base station device does not store the first session information, it receives a data transmission request for the first topic from the first wireless device and transmits a request for the first session to the management device.

5. The mobile communication network according to claim 4, wherein the first base station device, after establishing a first session from the first base station device to the first network node, transmits data of the first topic received from the first wireless device to the first network node, and even after releasing the wireless link with the first wireless device, stores the first session information and maintains the first session from the first base station device to the first network node.

6. If the first base station device fails to transmit data of the first topic to the first network node for a predetermined period of time or longer, it requests the management device to release the first session from the first base station device to the first network node. The mobile communication network according to claim 5, wherein the management device, upon receiving a request from the first base station device for the release of the first session destined for the first network node from the first base station device, performs processing to release the first session destined for the first network node from the first base station device.

7. The mobile communication network according to claim 6, wherein the management device causes the first network node to notify the first base station device that it will not transmit data of the first topic to the first network node in order to release the first session going from the first base station device to the first network node.

8. The mobile communication network according to claim 4, wherein the first base station device, after establishing the first session from the first base station device to the first network node and before releasing the radio link with the first radio device, determines that it should hand over the first radio device to a second base station device among the plurality of base station devices, and notifies the second base station device that the first radio device will collect data on the first topic.

9. The mobile communication network according to claim 4, wherein the first base station device, after establishing a first session from the first base station device to the first network node and before releasing the radio link with the first radio device, determines to hand over the first radio device to a second base station device among the plurality of base station devices, transmits first session information to the second base station device.

10. The mobile communication network according to claim 4, wherein the first base station device stores the first session information and maintains the first session going from the first base station device to the first network node, and when it receives a data transmission request for the first topic from the first wireless device or a second wireless device different from the first wireless device, it transmits the data of the first topic received from the first wireless device or the second wireless device to the first network node without transmitting a request for the first session to the management device.

11. The mobile communication network according to claim 1, wherein the first base station device is notified by the core network that the first wireless device will collect data for the first topic in response to the first base station device transmitting a registration request for the first wireless device to the core network, and if it does not store the first session information, it transmits a request for the first session to the management device.

12. The mobile communication network according to claim 11, wherein the first base station device is notified by the core network that the first wireless device is collecting data for the first topic, and has not stored the first session information, and therefore transmits a request for the first session to the management device, transmits the first session information received from the management device to the first wireless device for storage.

13. The mobile communication network according to any one of claims 1 to 12, wherein the first network node is configured to transfer data of the first topic to a server on an external network of the mobile communication network.

14. The first network node is configured to transfer the data of the first topic to the second network node among the plurality of network nodes. The mobile communication network according to any one of claims 1 to 12, wherein the second network node is configured to transfer data of the first topic to a server on an external network of the mobile communication network.

15. A wireless device that transmits data of a first topic to a server via a mobile communication network, The processing means includes a first session information that, as a response to a registration request transmitted to the mobile communication network, is used by the base station equipment of the mobile communication network to determine whether the wireless device is permitted to transmit data of the first topic, The processing means is a wireless device that retains the first session information even when the wireless device transitions to an idle state.

Images