System and method for providing network service to user equipment

Abstract

Systems and methods for providing network services to user equipment are described. A method includes receiving a control plane (CP) message at an interface function of an access network (AN). The method further includes selecting a CP interface from a plurality of CP interfaces between the AN and a core network (CN) of a mobile network based on the CP message. The method also includes transmitting the CP message to the CN using the selected CP interface. Selecting a CP interface may include selecting a CP interface based on an indicator included in the CP message. Selecting the CP interface may include selecting a CP interface between a first CP interface for device-centric CP signaling and a second CP interface for network-centric CP signaling.

Description

Technical Field

[0001] The present invention relates to the field of communication networks, and in particular to a system and method for providing network services to user equipment. Background Art

[0002] The fifth generation (5G) mobile network provides various services for mobile devices and provides data connections between one or more mobile devices and one or more data networks (DN). However, as the number of services increases, the 5G network architecture may not be able to efficiently adapt to the increasing number of services. For example, the 5G network architecture may not be flexible enough to support certain new services, such as services that may be delay-sensitive. Under the existing 5G network architecture, all data packets from mobile devices may need to pass through the user plane (UP) to reach the DN, even if the data packets are to be sent to the mobile network. This limitation may cause excessive delays in delay-sensitive applications. In addition, the 5G network architecture may limit the control method of control plane (CP) signaling.

[0003] Therefore, there is a need for systems and methods for providing network services to user devices that eliminate or reduce one or more limitations of the prior art.

[0004] The purpose of providing this background information is to disclose information that the applicant believes may be relevant to the present invention. It is not necessarily intended, nor should it be interpreted, that any of the above information constitutes prior art against the present invention. Summary of the invention

[0005] The present invention provides a system and method for providing network services to user equipment.

[0006] According to one aspect, a method is provided, the method comprising: receiving a CP message at an interface function of an access network (AN). The method further comprises: selecting a CP interface from a plurality of CP interfaces between the AN and a core network (CN) of a mobile network based on the CP message. The method further comprises: sending the CP message to the CN using the selected CP interface. The method can reduce the traffic load on the CP interface by separating traffic based on the CP message.

[0007] Selecting a CP interface may include: selecting a CP interface based on an indicator included in the CP message. Selecting a CP interface may include: selecting a CP interface between a first interface and a second interface. The first interface may be an interface for CP signaling centered on an electronic device (ED), and the ED-centric CP signaling includes an application IDCP message. The second interface may be an interface for network-centric CP signaling. The CP message may include a message for discovering network services. In some embodiments of the first aspect, selecting a CP interface includes selecting the first interface. The CP message may include a message for accessing a network service, and selecting a CP interface may include selecting the second interface. The method may improve security protection for one or more of ED-centric data connection services and network-centric services because the associated CP interfaces are separated from each other. The method may also support separate mobility processing for ED-centric data connection services and network-centric data based on separate CP interfaces.

[0008] Receiving a CP message may include receiving a CP message from an ED, and sending the CP message to the CN may include sending the CP message to a service provider function (SPF) associated with the CN. Receiving a CP message may include receiving the CP message at an ED-AN interface function (EAIF).

[0009] In one aspect, a method for providing a service from an EAIF to an electronic device (ED) is disclosed. The method includes: the EAIF receives a request for a service from the ED, wherein the service is provided by a service provider function (SPF) in a core network (CN) of a mobile network, and wherein the EAIF is associated with an access network (AN); sending the request for the service through a first interface between the AN and the CN. The method also includes: receiving a first response indicating that the ED is authorized to use the service; allocating one or more AN resources to service data communications between the ED and the SPF; and sending a second response to the ED based on the first response. The method can support the ED to discover and request one or more services of the network.

[0010] In the method, receiving the request may include: receiving a request including one or more of the following: an ED identifier (ID), an ED location, an application ID, a service ID, destination information, a data network name (DNN), a network slice ID, the location of the requested service, data to be analyzed, a driving path, a waypoint, a location and a corresponding time window, the accuracy of the road analysis information, and the type of the road analysis information. Sending the request for the service may include: sending the request for the service through one or more of an AN ED-centric interface function (ECIF) and a CN ECIF. Receiving the first response may include: receiving the first response through one or more of an AN ECIF and a CN ECIF. Receiving a first response may include: receiving a first response including one or more of the following: an ED identifier (ID), an ED location, an indication of service acceptance or service rejection, a service rejection reason when there is an indication of service rejection, a service location, a time window of the service, a network function (NF) ID of the SPF, address information of the SPF, a service ID, an application ID, a data network name (DNN), network slice information, a selected CN network-centric interface function (NCIF) NF ID, a selected AN NCIF NF ID, and an EAIF NF ID.

[0011] Sending a second response may include: sensing a second response including one or more of the following: an ED identifier (ID), an indication of service acceptance or service rejection, a reason for service rejection when there is an indication of service rejection, a service location, a time window for the service, a network function (NF) ID of the SPF, address information of the SPF, a service ID, an application ID, a data network name (DNN), and network slice information.

[0012] The method may further include: receiving a data message associated with the service from the ED; sending the data message to the SPF; receiving a service result message from the SPF based on the data message; and sending the service result message to the ED. Receiving the data message may include: receiving a data message including one or more of the following: destination information associated with the SPF, a data network name (DNN), a network slice identifier (ID), and a service container message. Sending the data message to the SPF may include: sending the data message to the SPF through one or more of an AN NCIF and a CN NCIF. The method may support requesting a service of the network and sending the request directly to the CN function that provides the service. Receiving the service result message may include: receiving a service result message including one or more of the following: destination information associated with the EAIF, an ED identifier, and an ED container message, wherein the ED container message includes one or more of the following: an ED ID, a service request ID, a service confirmation indicating that the requested service has been completed, a list of detected objects and their corresponding attributes, the accuracy (or reliability) of object detection, and a timestamp of the service result message. Receiving the service result message may include: receiving the service result message through one or more of the AN NCIF and the CN NCIF. The corresponding attributes of the detected object include one or more of the following: a description of the object, a description of the size of the object, a location of the object, a 2D relative distance to the ED, and a 3D relative distance to the ED. The method may support the separation of mobility management and service management.

[0013] In another aspect, a method of an EAIF is described. The method includes: the EAIF receives a service request from an electronic device (ED); determines whether the request is directed to a service provider function (SPF) in a core network (CN) of a mobile network. The method also includes: sending the request for the service to the SPF; receiving a service response from the SPF based on the request; and sending the service response to the ED. The method may support the ED directly requesting one or more services of the network. The method may also support the ED accessing the one or more services of the network.

[0014] Receiving a service request may include: receiving a service request including one or more of the following: an ED identifier (ID), an ED location, an application ID, a service ID, destination information, a data network name (DNN), a network slice ID, a location of the requested service, data to be analyzed, a timestamp, and a deadline. Sending the request for the service to the SPF may include: sending the request for the service to the SPF through one or more of an AN NCIF and a CN NCIF. Receiving a service response may include: receiving a service response from the SPF including one or more of the following: an ED identifier (ID), an ED location, a network slice ID, return data, a service request ID, a network function (NF) ID of the SPF. Receiving a service response may include: receiving a service response through one or more of an AN NCIF and a CN NCIF.

[0015] The method may also include: receiving a message to unsubscribe from the service from the ED, the message including a service request identifier (ID) associated with the request for the service; sending the unsubscribe message to the SPF; receiving a confirmation response from the SPF based on the unsubscribe message; and sending the confirmation response to the ED.

[0016] In one aspect, a method implemented by a network function (NF) in an access network (AN) is described. The method includes: sending an AN NF registration message to a NF database in a core network (CN) of a mobile network, the message including a request to register a service in the NF database; and receiving a registration response from the NF database. Sending the AN NF registration message may include: sending an AN NF registration message including one or more of the following: a network ID associated with the mobile network, an access technology (AT) type, an ATID, an AN ID, a network slice ID, an ID of the NF, an address of the NF, a type of data, location information, and an operating time indicating a time window. Sending the AN NF registration message may include: sending the AN NF registration message through one or more of an AN NCIF and a CN NCIF. The method may enable the AN NF to register its services in the CN NF database. The method may also enable the NF in the CN to request and access services provided by the AN NF.

[0017] Sending the AN NF registration message may include sending an AN NF registration message including one or more of the following: a geographic location, a type of collected data, and a type of service. Sending the AN NF registration message including the geographic location may include sending an AN NF registration message including one or more of the following: a two-dimensional location, a three-dimensional location, a common address, the AN ID, and a cell ID. Sending the AN NF registration message including the type of collected data may include sending an AN NF registration message including one or more of the following: images, videos, vehicle networking messages, radar, LIDAR, temperature, vehicle traffic counts, and non-vehicle traffic counts.

[0018] Sending an AN NF registration message including the type of service may include sending an AN NF registration message indicating one or more of: perception data collection service, artificial intelligence service, machine learning service, federated learning, segmentation learning, supervised learning, unsupervised learning, and reinforcement learning.

[0019] Receiving a registration response from the NF database may include receiving a registration response from the NF database indicating that the NF is registered in the NF database.

[0020] In one aspect, a method for providing a service to an electronic device (ED) by a service provider function (SPF) in a core network (CN) of a mobile network is disclosed. The method includes: receiving a request for the service, the request being associated with the ED and being received from an EAIF; sending a request to a service authorization function to authorize the ED to use the service; receiving a response from the service authorization function indicating that the ED is authorized to use the service; and sending a service response to the EAIF.

[0021] Receiving a request for the service may include: receiving a request for the service through one or more of an AN ECIF and a CN ECIF. Receiving a response may include: receiving a response including one or more of the following: a location where the ED can use the service and a time window in which the ED uses the service. The method may also include selecting one or more of an AN NCIF and a CN NCIF, wherein sending the service response includes: sending the service response indicating the selection of the one or more of the AN NCIF and the CNNCIF. The method may also include: receiving a service data transmission associated with the service from the EAIF; processing the service data transmission; and sending a service result to the ED based on the processed service data transmission. Sending the service result may include: sending a service result including one or more of the following: a destination selection, an identification of the ED, and an ED container message.

[0022] In another aspect, the present invention provides a method performed by a data processing function (DPF) in a core network (CN) of a mobile network. The method includes: receiving a request for data from a data consumer function (DCF) in the CN of the mobile network; based on the request for data, selecting a data source from one or more of the following: an access network (AN), a network function (NF) in the AN, and an electronic device (ED). The method also includes: sending the request for data to the selected data source; and receiving data based on the sent request for data; and sending the received data to the DCF. Receiving the request for data may include: receiving a request for data including one or more of the following: an identifier (ID) of the DCF, a service request ID associated with the request, a geographic location, a type of object to be detected, a type of data, an observation time window, a sampling time period, and a moving direction of the object. The method may enable a function in the CN (e.g., a data consumer function) to request or subscribe to one or more types of data in one or more of the following: another network, an AN, a NF, and an ED.

[0023] Selecting a data source may include: sending a request to a database NF to determine a NF that can provide the requested data, the request including one or more of the following: location information, type of data, observation window, network identifier (ID), and AN ID; and receiving a response from the database NF, the response indicating that the NF can provide the requested data. Sending the request for data may include: sending the request for data through one or more of AN NCIF and CN NCIF. Receiving data may include: receiving data including one or more of the following: a service request identifier (ID) associated with the request for data, a timestamp of the received data, AN ID, AN node ID, AN cell ID, ID of the AN DGF, network ID, network slice ID, CN ID, ID of the ED, location ID, type of data, the data, and parameters for reading the data. Sending the received data may include: processing the received data to generate processed data, wherein processing includes one or more of the following: deleting private information from the received data, storing the received data in a data storage function, and storing the processed data in the data storage function; and sending the processed data to the DCF.

[0024] According to another aspect, an apparatus is provided, comprising means for performing one or more of the methods described herein.

[0025] According to one aspect, a device is provided, wherein the device includes: a memory for storing a program; a processor for executing the program stored in the memory, and when the program stored in the memory is executed, the processor is used to execute one or more methods described in this document.

[0026] According to another aspect, a computer-readable medium is provided, wherein the computer-readable medium stores a program code, the program code is executed by a device and is used to perform one or more of the methods described herein.

[0027] According to one aspect, a chip is provided, the chip comprising a processor and a data interface, the processor reading instructions stored in a memory through the data interface to execute one or more of the methods described herein.

[0028] Other aspects of the present invention provide apparatus and systems for implementing the method according to the first aspect disclosed herein. For example, a wireless station and an access point may be configured with a machine-readable memory, the machine-readable memory including instructions, which, when executed by a processor of these devices, cause the device to perform one or more of the methods disclosed herein.

[0029] Embodiments are described above in conjunction with various aspects of the present invention, and these embodiments can be implemented based on these aspects. It will be appreciated by those skilled in the art that embodiments can be implemented in conjunction with the aspects describing these embodiments, but can also be implemented together with other embodiments of this aspect. When the embodiments are mutually exclusive or incompatible with each other, it will be apparent to those skilled in the art. Some embodiments can be described in conjunction with an aspect, but can also be applied to other aspects, which will be apparent to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] Further features and advantages of the present invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

[0031] Figure 1 A mobile network architecture provided by one aspect of the present invention is shown.

[0032] Figure 2 An example of network deployment provided by one aspect of the present invention is shown.

[0033] Figure 3 A communication protocol between an access network (AN) and a core network (CN) provided by one aspect of the present invention is shown.

[0034] Figure 4A process for registering a network function of an access network in a core network provided by one aspect of the present invention is shown.

[0035] Figure 5 One aspect of the present invention provides a network with additional network functions and services. Figure 1 Mobile network architecture.

[0036] Figure 6 The present invention shows a process in which a function in a CN receives sensing data from an AN, provided by one aspect of the present invention.

[0037] Figure 7 A communication protocol between an electronic device (ED) and a mobile network provided by one aspect of the present invention is shown.

[0038] Fig. 8A and Figure 8B The invention shows a process of an ED acquiring a real-time service from a mobile network, provided by one aspect of the present invention.

[0039] Fig. 9A and Fig. 9B A process of an ED acquiring services from a mobile network provided by one aspect of the present invention is shown.

[0040] Fig.10 Different aspects of the present invention provide apparatuses that can perform any or all operations of the above methods and features explicitly or implicitly described herein.

[0041] Fig.11 A method for communication between an AN and a CN provided by one aspect of the present invention is shown.

[0042] It should be noted that throughout the drawings, like features are identified by like reference numerals. DETAILED DESCRIPTION

[0043] The fifth generation (5G) mobile network can provide diversified services for mobile devices. The network can provide high-speed data connections, low packet latency, and multi-edge computing (MEC) support. The network can also provide network information to third parties, such as real-time network performance, network data analysis, etc., so that third parties can choose better communication parameters to improve the quality of data communication services. For example, a 5G mobile network can provide network quality of service (QoS) statistics or predictions in a cell of the radio access network. QoS information can be used by communication devices in the network (such as sensor-equipped vehicles) to select a suitable transmission data rate for the sensors installed in the vehicle.

[0044] In the future, the network may also provide enhanced sensing services and artificial intelligence (AI) and / or machine learning (ML) services to user devices and third-party application servers.

[0045] For example, vehicles with data connectivity to application servers can use these services to implement advanced driving control, coordination, and safety improvements. As the number of vehicles increases, it may be more ideal to use enhanced sensing services and AI / ML services. Vehicle travel time may depend on vehicular and non-vehicular traffic, including pedestrians, cyclists, car drivers, etc. Estimating the number of vehicles on the road can be used to determine travel time and other applications. There are currently some methods for estimating the number of vehicles on the road, but these methods need to be improved.

[0046] In addition, the map service provider may provide information about the number of vehicles currently using the map service and the number of vehicles connected to the map server. However, the information provided by the map service provider (e.g., the number of vehicle and non-vehicle traffic) may be inaccurate for a variety of reasons: some GPS devices may not have an Internet connection or may be in offline mode, or some non-vehicle users may not have an Internet connection.

[0047] In addition, intelligent transport systems (ITS) can use wireless connectivity to control traffic lights and provide information such as traffic and road condition updates to vehicles. ITS can use cameras and sensors in lamp posts, for example, for a variety of applications, including counting the number of vehicles on the road. ITS can be exploited through an extensive network of wireless base stations (and possibly other radars and sensors integrated with antennas) that can provide information including position estimates with high accuracy. Therefore, mobile network operators may have an advantage in deploying new systems to support ITS and vehicles choosing improved travel paths.

[0048] Therefore, it may be necessary to provide systems and methods for providing sensing and AI / ML services to user devices and third-party application entities. These systems (including network functions) can support low-latency data communication and can also provide methods for collecting sensing data. The data format can be any type of data such as data packets, voice data, video data, etc. These systems can also provide methods for providing AI / ML services.

[0049] This proliferation of additional services may also put more pressure on the network architecture. Therefore, it may be beneficial to provide additional interfaces to support this additional data traffic. For example, the core network (CN) and the access network (AN) may have three interfaces: two logical control plane (CP) interfaces and one logical user plane (UP) interface. One of the two CP interfaces may support device-centric services, such as data connections with third-party services. The other CP interface may support network-centric services provided by the mobile network, such as sensing and AI / ML services. This may be in contrast to existing networks (such as 5G networks), which include only a single logical CP interface, namely the N2 interface between the AN and the CN. This improved network architecture can be used to provide a wide variety of services, such as collecting data to be used for road traffic analytics (RTA).

[0050] Figure 1 A mobile network architecture 100 provided by one aspect of the present invention is shown. The network architecture 100 includes an AN 102 and a CN 104.

[0051] AN 102 may provide a data connection between an electronic device (ED) 140 and CN 104 via a wired or wireless connection. AN 102 may also provide services to ED 140. CN 104 may provide control and service functions for ED 140. CN 104 may also provide ED 140 with a data connection to a third-party data network (DN) 156 (e.g., the Internet).

[0052] ED 140 may be any networked device. For example, ED 140 may be a user device, such as a smartphone, smartwatch, television, or other device, or may be another type of device, such as a video camera or camera mounted in a residence, shopping mall, office building, vehicle, street, or highway, etc. ED 140 may also be another type of networked device, such as a radar or light detection and ranging (LIDAR) device mounted on a vehicle, lamp post, or other location. ED 140 may also include a variety of other types of devices.

[0053] AN 102 may be a radio access network (RAN) using wireless technologies such as Wi-Fi, fourth-generation (4G), fifth generation (5G), or other wireless technologies. AN 102 may use cables (e.g., optical fibers, coaxial cables, copper cables) to provide wired connections for ED 140.

[0054] The network architecture 100 includes three logical interfaces between the AN and the CN. The first logical interface C1 146 may be a control plane (CP) interface for ED-centric connection services. The ED-centric connection services may be used to control data connections between the ED 140 and third-party application servers in the data network 156. The second logical interface C2 148 may be another CP interface for new services that may be provided by the NFs of the CN 104. The third logical interface C3 150 may be a UP interface for data transmission between the AN and the CN. The term interface may be used interchangeably with logical interface, as will be appreciated by those skilled in the art.

[0055] Having two separate CP interfaces 146, 148 can provide advantages over having a single CP interface. The separate CP interfaces can improve the security protection of the data connection service centered on the ED. The second interface C2 148 can provide services to the CN and further provide services to third parties. The C2 interface 148 can be isolated from the first interface 146, thereby preventing or reducing the possibility of affecting the data connection service when the C2 interface 148 is unavailable due to service interruption, overload or other reasons.

[0056] Having separate CP interfaces 146, 148 can separate the control traffic load of network-centric data from the control traffic load of ED-centric data. This can improve the routing and management of traffic flows.

[0057] Having separate CP interfaces 146, 148 can separate the mobility processing of ED-centric data connection services from the mobility processing of network-centric data. For example, when a highly mobile ED 140 has a data connection with a third-party data network, the data gateway and CP 104 functions can be selected to be located away from the ED 140 to avoid frequent switching when the ED 140 moves to a new location. At the same time, the ED 140 can use local services provided by the mobile network, such as data analysis. The mobile network can select network functions that are closer to the ED 140 (e.g., physically co-located with the AN 102 node serving the ED 140).

[0058] The network architecture 100 may also include a network management function (NMF) 106. The NMF 106 may provide functions for managing the lifecycle of network functions in the CN 104 and the AN 102.

[0059] The NMF 106 may communicate with the CN 104 via the M1 interface 108. The NMF 106 may communicate with the AN 102 via the M2 interface 110. The NMF 106 may provide interface configuration information for the C1 interface 146 and the C2 interface 148 so that the AN and CN functions may communicate. For example, the NMF 106 may provide one or more address information (e.g., including IP addresses and port numbers, fully qualified domain names (FQDNs)) of the CN network-centric interface function (NCIF) 112 and the CN ED-centric interface function (ECIF) 114 to the AN 102 (e.g., to the AN NCIF 116 and the AN ECIF 118). Similarly, the NMF 106 may provide one or more addresses (e.g., including IP addresses and port numbers) of the AN network-centric interface function (NCIF) 116 and the AN ED-centric interface function (ECIF) 118 to the CN 104 (e.g., to the CN NCIF 112 and the CN UCIF 114). Based on the interface configuration information received from NMF 106, CN NCIF 112 may support or authorize one or more AN functions to send messages to one or more CN functions through AN NCIF 116 or through AN NCIF 116 and CN NCIF 112. Thus, the AN function may send messages to the CN function directly through AN NCIF 116 or through AN NCIF 116 and CN NCIF 112.

[0060] AN 102 may include one or more of: AN network service function 120, AN NCIF 116, EAIF 122, AN ECIF 118, AN ED-centric service function 124, and AN UP service function 126. CN 104 may include one or more of: network function (NF) database 128, CN NCIF 112, CN ECIF 114, CN ED-centric service function 130, mobile network (MN) service open interface 132, CN UP service function 134, and network-centric service function 136. CN 104 may provide a logical UP interface C4 152 to provide a data connection between CN 104 and an application server in a data network 156. Application server 156 may also exchange control information with CN 104 via C5 154 logical CP interface (may be via MN service interface 132).

[0061] AN 102 may have two interfaces with ED 140: A1C 142 and A1D 144. A1C interface 142 may carry control messages exchanged between ED 140 and AN 102. Control messages may include messages for one or more of managing connections between ED 140 and mobile networks, managing data connections between ED 140 and one or more data networks, and managing connections between ED 140 and network functions of one or more mobile networks.

[0062] A1D interface 144 may carry data packets sent to or received from mobile networks and other third-party data networks by ED 140. CN 104 may have two interfaces with third-party application servers or data networks 156: C4 152 and C5 154.

[0063] In the AN 102, an AN network function (e.g., the EAIF 122) may be used to transmit control messages and data with the ED 140. For example, the EAIF 122 may receive a control message sent from the ED 140 via the A1C interface 142. The EAIF 122 may determine whether the message is for managing a data connection between the ED 140 and a data network, or for managing a data connection between the ED 140 and a mobile network. If the control message is for managing a data connection, the EAIF 122 may forward the received message to one or more of the AN ED-centric service functions 124. In some aspects, the EAIF 122 may receive a control message sent from the ED 140 and check whether the message is to access a service provided by the network. If the control message is to access a service provided by the network, the EAIF 122 may forward the message to one or more of the AN network-centric service functions 120.

[0064] In some aspects, control messages received by the EAIF 122 may be directed to the CN 104. The EAIF 122 may forward the control message to the CN 104 directly or through an appropriate CP interface (eg, C1 146 or C2 148), depending on the nature of the control message.

[0065] Figure 2 An example of a network deployment provided by one aspect of the present invention is shown. The networked vehicles 202, 204 and the EDs of the passengers on these vehicles can use services provided by a data network 256, including the Internet or services provided by a mobile network operator (MNO).

[0066] MNO can provide local AI / ML services, where vehicles 202, 204 can send perception data such as LIDAR, radar, images, videos, vehicle-to-everything (V2X) message transmission data 220, 222 to servers in local CN 205, 206 installed near radio stations 208, 210 of AN. At the same time, vehicles 202, 204 can send maintenance data 212, 214 to data servers in maintenance centers located in data network 256. V2X messages can be messages sent between vehicles, between vehicles and pedestrians, between vehicles and road infrastructure (such as road side units (RSU)), and between vehicles and mobile networks.

[0067] By separating the interfaces for CN network-centric functions from the interfaces for CN ED-centric functions, the AN can forward messages sent between EDs 202, 204 and local CN functions 205, 206 or central CN functions 230. This interface separation can help reduce delayed transmission of packets for local services that may not need to be transmitted to the central CN 230.

[0068] Figure 3 1 and 2. The communication protocol between an access network (AN) 302 and a core network (CN) 304 provided by one aspect of the present invention is shown. Each of the AN 302 and the CN 304 may have an AN-CN protocol layer stack 306, 308, respectively. Generally, the AN 302 may include interface functions 316, 318 associated with the CN 304 via interfaces 348, 346. The AN 302 may include one or more AN network functions 310. The CN 304 may also include interface functions 312, 314 associated with the AN 302 via interfaces 348, 346.

[0069] Figure 4 A process 400 for registering a network function of an access network in a core network provided by one aspect of the present invention is shown. The process 400 may enable an AN network function 420 to register its services in a network function database 426 of a CN. After the AN NF 420 registers its services, other devices and NFs in the AN and CN may access the services provided by the AN NF 420.

[0070] The process 400 includes: the AN NF 420 sends an AN NF registration message 402 to the NF database function 426. The message 402 may include information such as a service request ID-1 and an NF profile for identifying the message sent from the AN NF 420. The NF profile may include one or more of the following information: NF name, address of the AN NF 420 (e.g., IP address, port number, FQDN, etc.), AN NF 420 ID, AN ID, access technology (AT) type, AT ID, and network ID. As shown in the figure, the message may be sent through one or more of the AN NCIF 422 and the CN NCIF 424. The AT type may indicate the type of wireless access technology such as 4G, 5G, 6G, WiFi, satellite, etc., and may also indicate the type of wired access technology such as optical fiber.

[0071] The NF profile included in the message 402 may include one or more of the following information: a geographic location that can be represented by a two-dimensional (2D) or three-dimensional (3D) location, a common address, an AN ID, a cell ID. The NF profile may include the type of service (e.g., a perception data collection service), the type of collected data (e.g., images, videos, vehicle-to-everything (V2X) messages, radar, LIDAR, environmental data such as temperature and humidity, vehicle and / or non-vehicle traffic counts). The NF profile may include the type of AI / ML service (e.g., federated learning, segmented learning, supervised learning, unsupervised learning, and reinforcement learning).

[0072] If the message 402 is sent via the AN NCIF 422, the AN NCIF 422 may check whether the AN NF 420 is authorized to register its services. If the AN NCIF 422 determines that the AN NF 420 is authorized to register its services, the AN NCIF 422 may forward the message received from the AN NF 420 to the NF database function 426, for example, by forwarding the message via the CN NCIF 424.

[0073] In some aspects, AN NCIF 422 may add service request ID-2 to message 404 to identify message 404 being sent from ANNCIF 422. AN NCIF 422 may store service request ID-1 included in received messages and may not include service request ID-1 in messages sent to CN NCIF 424.

[0074] If the AN NCIF 422 sends the AN NF registration message to the CN NCIF 424, the CN NCIF 424 may check whether the ANNF 422 is authorized to register its services in the NF database function 426. The CN NCIF 424 may use the information received from the AN NCIF 422 to make a decision. For example, certain AN IDs or certain AT types or NF names may be authorized. If the CNNCIF 424 determines that the AN NF 422 is authorized to register its services, the CN NCIF 424 may store the service request ID-2 and may forward the AN NF registration message 406 to the NF database function 426. In some aspects, the service request ID-2 may not be sent to the NF database function 426. The CN NCIF 424 may include a service request ID-3 in the AN NF registration message sent to the NF database function 426, which may be used to identify the message.

[0075] The AN NF information included in the message 406 may be stored in the NF database function 426 and may be used to discover and select the AN NF 420. The NF database function 426 may send an AN NF registration confirmation (ACK) 408 to the AN NF 420 to confirm that the AN NF 420 is registered in the mobile network or CN. The NF database function 426 may send the confirmation message 408 to the CN NCIF 424. The message may include the service request ID-3 sent from the CN NCIF 424.

[0076] CN NCIF 424 may receive AN NF Registration ACK message 408. CN NCIF 424 may use service request ID-3 to identify the associated AN NCIF 422. CN NCIF 422 may remove service request ID-3 from AN NF Registration ACK message 408 and then send AN NF Registration ACK message 410 with service request ID-2 to AN NCIF 422.

[0077] Upon receiving the AN NF Registration ACK message 410, the AN NCIF 422 may use the service request ID-2 to identify the associated AN NF 420. The AN NCIF 422 may remove the service request ID-2 from the AN NF Registration ACK message 410 and forward the message to the AN NF 420 together with the service request ID-1 412. The AN NF 420 may use the service request ID-1 to determine that its services have been registered in the CN.

[0078] As described herein, a network architecture can support separation of control of device-centric services from control of network-centric services. Thus, deployment of network services can be decoupled from device-centric services. Furthermore, management of ED mobility can be decoupled from management of network-centric services.

[0079] Figure 5 A mobile network architecture 500 with additional network functions and services provided by one aspect of the present invention is shown. The mobile network architecture 500 is generally similar to the mobile network architecture 100 except that a network-centric service function 536 is added.

[0080] In one aspect, the network architecture 500 may include an NMF 506 , which may be similar to the NMF 106 .

[0081] The NMF 506 may communicate with the CN 504 via the M1 interface 508. The NMF 506 may communicate with the AN 502 via the M2 interface 510. The NMF 506 may provide interface configuration information for the C1 interface 546 and the C2 interface 548 so that the AN and CN functions may communicate. The third logical interface C3 550 may be a UP interface for data transmission between the AN and the CN. Based on the interface configuration information received from the NMF 506, the CN NCIF 512 may support or authorize one or more AN functions to send messages to one or more CN functions via the AN NCIF 516 or via the AN NCIF 516 and the CN NCIF 512. Therefore, the AN function may send messages to the CN function directly via the ANNCIF 516 or via the AN NCIF 516 and the CN NCIF 512.

[0082] AN 502 may include one or more of the following: AN network service function 520, AN NCIF 516, EAIF 522, AN ECIF 518, AN ED-centric service function 524, and AN UP service function 526. CN 504 may include one or more of the following: network function (NF) database 528, CN NCIF 512, CN ECIF 514, CN ED-centric service function 530, mobile network (MN) service open interface 532, CN UP service function 534, and one or more network-centric service functions 536. CN 504 may provide a logical UP interface C4 552 to provide a data connection between CN 504 and an application server in a data network 556. The application server may also exchange control information with CN 504 via a C5 554 logical CP interface (which may be via the MN service interface 532).

[0083] AN 502 may have two interfaces with ED 540: A1C 542 and A1D 544. A1C interface 542 may carry control messages exchanged between ED 540 and AN 502. Control messages may include messages for one or more of: managing connections between ED 540 and mobile networks, managing data connections between ED 540 and one or more data networks, and managing connections between ED 540 and network functions of one or more mobile networks.

[0084] In some aspects, the network-centric service function 536 may include a sensing data processing function (SDPF) 562, a street mapping function 564, a real-time traffic analytics service (RTAS) function 566, a data storage function 568, a local distribution function 570, and a spectrum utilization strategy function 572.

[0085] SDPF 562 can perform one or more functions to support ITS and other applications. For example, SDPF 562 can estimate the number of non-vehicle users (e.g., pedestrians) crossing the road. SDPF 562 can further estimate the number of bus passengers waiting at bus stations and bus stops. SDPF can use AI / ML methods to generate past traffic statistics and future traffic forecasts.

[0086] Figure 6 The process of receiving sensing data from an AN by a function in a CN provided by one aspect of the present invention is shown. The process 600 may provide that the CN collects sensing data from an ED connected to the AN.

[0087] In one aspect, in step 602, a data consumer function (DCF) 642 may send a data request or subscription message to a data processing function (DPF) 644. For example, the DCF 642 may be the RTAS function 566, and the DPF 644 may be the SDPF 502. The message may include one or more of the following information: NF ID of the DCF, a service request ID identifying the message sent from the DCF, a geographic location where data is collected, a type of object to be detected, a type of data, an observation time window, a sampling time period, and a moving direction of the object.

[0088] In step 602, the geographic location included in the data request or subscription message can be represented by one or more of a geographic area identifier (ID), a sensor device ID, a name of an intersection segment or an intersection ID, and a street (or road, or highway) name of a street ID.

[0089] The type of object included in the data request or subscription message may be represented by an object ID. The object may be one or more of a vehicle, a truck, a bus, a car, a train, a drone, a bicycle, a motorcycle, a pedestrian, etc. The type of data included in the data request or subscription message may include sensory data. The sensory data may include one or more of the location of the object, the number of objects in the geographic location, environmental information (e.g., temperature, humidity, rainfall, air quality level, and air pollution level), etc. The observation time window included in the data request or subscription message may be a time period for collecting data. Among them, the sampling time period included in the data request or subscription message may be a time period for counting the number of detected objects. For example, the sampling time period may refer to sensory data including the number of passenger cars entering the geographic area within a sampling time period of 5 minutes. The moving direction of the object included in the data request or subscription message may be represented by, for example, a starting geographic location and an ending geographic location. In some aspects, if the location is an intersection, the moving direction may be represented by one or more of the following: the street name where the movement starts (e.g., the street where the moving direction starts), which may include the corresponding lane number; and the street name where the turn occurs (e.g., the turning street), which may include the corresponding lane number. In some aspects, if the object is one or more pedestrians, the direction of movement can be an indication for crossing a street in a direction such as from east to west or from west to east. In some aspects, if the object is a pedestrian, the location can be a bus stop and the direction of movement can be an indication of how many pedestrians can enter the bus.

[0090] In step 604, process 600 includes DPF 644 receiving the message sent from DCF 642 in step 602. Thereafter, DPF 644 may discover one or more data sources. For example, DPF 644 may discover one or more of the following that may provide the requested data (e.g., sensing data): network ID, network slice ID, AN ID, AT type, AT ID, NF ID, and ED ID. DPF 644 may use pre-configured information to discover one or more of a network, network slice, AN, AT, NF, and ED that may provide the requested data.

[0091] Optionally, in some aspects, the DPF 644 may send a request message to a NF database function (e.g., NF database 128) to discover NFs that can provide data. The DPF 644 may include one or more of the following information in its request message to the NF database: location information, type of data (e.g., type of sensing data), observation window, network ID, network slice ID, AN ID, AT type, AT ID, and other relevant information.

[0092] In response, the NF database function may send a response to the DPF 644, which may include NF information that may be used to select an entity that may provide the requested data. The response from the NF database may include one or more of the following information that may provide the sensing data: network ID, network slice ID, AT ID, AT type, AN ID, NF profile, ED ID (or ED profile).

[0093] The NF profile or ED profile of the NF that can provide data may include one or more of the following information: network ID, ANID, network slice ID, AT type, AT ID, NF ID (for the case of NF profile), device ID (for the case of ED profile), address of NF, type of data, location information and operation time. Network ID may refer to an identifier that can be used to identify a network (including a mobile network). AN ID may refer to an identifier of an AN that can provide the requested sensing data. Network slice ID may refer to the network slice ID of the network, or may refer to the network slice ID of the AN. The address of the NF may include one or more of the following information: IP address, port number and FQDN. The type of data may refer to the type of sensing data that can be generated. Location information may refer to the location where sensing data can be collected. Operation time may refer to a time window in which sensing data can be generated. Operation time may be represented by a start time and an end time, and each of the start time and the end time may be indicated, for example, by hours, minutes and seconds of a certain day. In some aspects, the operation time may be an interval indicated by the start time and the end time, wherein each of the start time and the end time may be indicated by hours, minutes and seconds and corresponding years, months and dates.

[0094] Based on the information included in the message in 602, DPF 644 can select one or more data sources. For example, DPF can select one or more of the following that can provide the requested data: network, AN, AT, NF, ED. In one aspect, DPF 644 can select a data source with an ID (e.g., AN ID1) for providing radar sensing data, such as detecting a vehicle object or a passenger. DPF 644 can also select a data source for providing LIDAR sensing data, which can be used to detect whether an object is a passenger car, bus, truck, or pedestrian. DPF 644 can also select a data source for providing location information of a mobile device. AN ID4 can provide video data or photo data or a V2X message.

[0095] After identifying one or more networks, ANs, ATs, NFs, EDs that can provide relevant sensing data, in step 606, the DPF 644 may send a message to the identified AN or NF directly or through one or more of the AN NCIF 660 and the CN NCIF 662 to request data or subscribe to sensing data. The data request or subscription message may include one or more of the following information: network ID, AN ID, network slice ID, NF ID of the AN data generation function (DGF), NF ID of the DPF requesting sensing data, ED ID, ED location, CN ID, network slice ID of the CN, service request ID, type of sensing data, location information, and other information, which may be the same as the information received in the message in step 602 or a subset of the information.

[0096] AN ID may be an identifier of an AN that can provide the requested sensing data. NF ID may be an identifier of a NF in the AN that can provide the requested sensing data. ED ID may be an ID of an ED that can provide the requested sensing data. ED location may refer to the location of the ED, such as an AN node ID, an AN cell ID. CN ID may be an identifier of the CN to which the DPF belongs. The network slice ID of the CN may be the network slice ID of the DPF. The service request ID may be an identifier that identifies a data request or a subscription message. The type of sensing data may include one or more of the following sensing data: LIDAR, radar, photos, videos, V2X messages, and / or location information. In some aspects, the location information may be one or more of the following: 2D, 3D location, an indication of the distance to a point (e.g., the location of a radio device such as an antenna), a bounding box, and azimuth and altitude angles.

[0097] The location information may be the same as or a subset of the location information received in the message at step 602. In some aspects, the AN may provide data for an area smaller than the location indicated in the message at step 602, and then in such aspects, the DPF 644 may include location information identifying an area smaller than the geographic area indicated in the message at step 602.

[0098] If the CN NCIF 662 receives the data request or subscription message sent from the DPF 644 in step 606, the CN NCIF 662 may check whether the CN or the CN DPF 644 or both are authorized to send the message to the AN. If the CN NCIF 662 determines that the DPF, the CN, or both are authorized, the CN NCIF 662 may send the data request or subscription message to one or more data sources that can provide the requested sensing data. The CN NCIF 662 may send the message directly to one or more data sources (e.g., NFs in the AN) or send the message through the AN NCIF 660 corresponding to the AN ID received in step 606. The CN NCIF 662 may include its NF ID in step 608.

[0099] If the AN NCIF 660 receives the message sent from the DPF 644 in step 606 or the message sent from the CN NCIF 662 in step 608, the AN NCIF 660 may check whether the CN or the DPF 644 or both are authorized to send a sensing data request or subscription message to the AN. If the CN or the DPF 644 or both are authorized to send a data request or subscription, in step 610, the AN NCIF 660 may send a sensing data request or subscription to an AN data generation function (DGF) 640, which is, for example, a sensing data generation function (SDGF) corresponding to one or more of the following information received from the DPF: for example, the AN ID, ED location, AN DGF ID received in step 606.

[0100] In step 612, the AN DGF 640 receives a data request or subscription message from the AN NCIF 660 or from the CN NCIF 662. In some aspects, the AN DGF 640 may request the collection and provision of requested sensor data from one or more sensors (e.g., cameras, video cameras, radars, LIDARs, V2X message receivers), including sensory data for locations of interest. The one or more sensors may be mounted in a fixed location or any suitable location, such as a light pole, a radio tower, a wall, a rooftop of a building, or even in a mobile object such as a vehicle.

[0101] In some aspects, if the ED ID is provided in the data request or subscription message, the AN DFG 640 can send a data request or subscription message to the ED via the EAIF. The EAIF can identify the ED location, such as a serving AN node, to forward the data request or subscription message to the ED.

[0102] In some aspects, if a data request or subscription message indicates a location of interest where an ED, such as a mobile data source (e.g., a LIDAR device installed in a vehicle), will collect sensory data, then when the ED enters the location of interest (e.g., an interaction), the AN DGF 640 can request the ED to collect sensory data. The AN DGF 640 can be aware of one or more mobile sensor devices currently located at the location of interest. If the mobile sensor communicates with the network using a wireless connection, the AN DGF 640 can send the request via the EAIF.

[0103] After collecting the requested data (e.g., sensory data) in step 614, the AN DGF 640 can process the data to perform one or more of the following operations: remove irrelevant information, protect data privacy (e.g., by anonymizing the data or other techniques for maintaining or protecting privacy), compress the data (e.g., compressing raw images or raw video data), and maintain or improve the security of the data. For example, if the requested sensory data indicates LIDAR data for counting passenger vehicles, then after collecting such data, the AN DGF 640 can remove information identifying the type of vehicle (e.g., minivan or sedan). In another example, the AN DGF 640 can remove the vehicle color and mask the license plate number from one or more of the video camera and the camera.

[0104] In step 616, the AN DGF 640 may send a data response or notification including the collected data to the DPF 644 directly or through one or more of the AN NCIF 660 and the CN NCIF 662. The AN DGF 640 may include one or more of the following information in the data response or notification: the service request ID sent from the DPF in step 606, the timestamp of the sensed data, the AN ID, the AT type, the AT ID, the AN node ID, the AN cell ID, the AN DGF ID, the network ID, the network slice ID, the CNID, the ED ID, the location ID, the location information, the type of data, the data, and the parameters of the read data.

[0105] The ED ID in the data response or notification may refer to an identifier that can be used to identify an ED (e.g., a sensing device that provides data). The location ID in the data response or notification may indicate the geographic location where the data was acquired, or the geographic location associated with the acquired data. The location information may include an AN cell ID, a common address, a 2D or 3D geographic location. The type of data in the data response or notification may refer to one or more of the following: LIDAR, radar, images, video data, V2X messages, etc. The data in the data response or notification may refer to the data requested by the DPF644.

[0106] If the AN NCIF 660 receives a data response or notification message, then in step 618, based on one of the received information elements, including the service request ID, CN ID, and DPF ID, the AN NCIF 660 may identify one or both of the CN NCIF 662 and the DPF 642 that requested the data. Thereafter, the AN NCIF 662 may send the service request ID and one or more information received from the AN DGF 640 in step 616 to the DPF 644 directly or through the CN NCIF 662.

[0107] If the CN NCIF 662 receives a data response or notification message from the AN NCIF 660, based on the received one or more information elements, including the service request ID, the CN ID, and the DPF ID, the CN NCIF 662 may identify the DPF 642 requesting the sensing data in step 620. Thereafter, the CN NCIF 662 may send one or more of the following information to the DPF 642: the service request ID and the one or more information received from the AN DGF 640.

[0108] In step 622, the DPF 644 may receive some or all of the collected sensing data from one or more of the following: the AN, the AN DGF 640, the AN NCIF 660, the CN NCIF 662. The DPF 644 may process the collected data to generate the information requested in the data request or subscription received in step 602. The DPF 644 may remove information such as identification information to protect privacy. Some examples of identification information include faces, license plates, etc. in image and video data. The DPF 644 may store the collected data received in 620 in a data storage function. The DPF may also store the processed data in the data storage function.

[0109] For sensing purposes, in some aspects, the DPF 644 can use data from different sensing sources to detect one or more objects. For example, the DPF 644 can use: LIDAR and radar signals to detect vehicle objects, and use photo data and LIDAR to detect people.

[0110] In response to the data request or subscription message received in step 602, DPF 644 may send one or more data response or notification messages to DCF 642 (e.g., RTAS function 506) in step 624. The one or more data responses or notifications may include data, such as an ED location response or ED location notification.

[0111] In step 626, DCF 642 may receive data included in one or more data responses or notification messages. DCF 642 may use mathematical tools (e.g., AI and ML) to perform data analysis on the received data to derive desired information. The desired information may include one or more of past statistics and future predictions, such as vehicle traffic patterns, pedestrian traffic patterns, bus or subway passenger patterns, etc. Each desired pattern information may be associated with one or more of the following: a target time or time window and a geographic location.

[0112] In step 628, DCF 642 may send the processed sensed data and derived analysis data to data storage function 664. In step 630, data storage function 664 may send a response message to DCF 642 to acknowledge the received message in step 628. The response message may indicate whether the data has been received and / or whether the data has been successfully stored.

[0113] Figure 7 1 shows a communication protocol between an ED and a mobile network provided by one aspect of the present invention. ED 740 may include an AN protocol layer stack 704, a network-centric service protocol 708, and an ED-centric service protocol 706. AN 742 may include an AN-CN protocol layer stack 746 and an AN protocol layer stack 702. Each of the network-centric service protocol 708 and the ED-centric service protocol 706 may have an A1C interface 748, 750 with AN 742 (via EAIF 752).

[0114] In some aspects, the AN 742 may also include an AN NCIF 754 and an AN ECIF 756. In some aspects, the CN 744 includes an AN-CN protocol layer stack 766, a CN NCIF 764, and a CN ECIF 762. The AN 742 may have one or more interfaces C1 760 and C2 758 with the CN 744. As shown, the C1 760 interface may be between the AN ECIF 756 and the CN ECIF 762, and the C2 758 interface may be between the AN NCIF 754 and the CN NCIF 764.

[0115] In one aspect, when an application in ED 740 wishes to access a service provided by a mobile network, the application may generate a service request or service subscription message and send it to a network-centric service protocol (NCSP) unit 708 of ED 740. The service request or subscription message may include one or more of the following information: an application ID identifying the application, a service request ID, an ED ID, an address of an application server in the mobile network, a service ID, data to be analyzed, a timestamp, a deadline, a type of network information, a service location, a data time window, and a subscription time window.

[0116] The application ID in the service request or subscription message can identify the application. The service request ID in the service request or subscription message can identify the transaction between the ED and the mobile network. The ED ID in the service request or subscription message can refer to an ID that identifies the device, such as a temporary mobile subscriber identity (TMSI), a subscription concealed identifier (SUCI), a subscription permanent identifier (SUPI), etc.

[0117] The address of the application server in the mobile network may include one or more of the following: an IP address or an IP prefix, an associated port number, and an FQDN. The service ID in the service request or subscription message may identify the type of service: for example, a data analysis service (e.g., past statistics or future predictions), a network information request, etc. The data to be analyzed may be related to the type of service requested. For example, if the ED requests a data analysis service of the mobile network, such as to detect objects in one or more of a photo, a video, a LIDAR data file, and a radar data file, the ED may send the data file in the service request or subscription message. The timestamp in the service request or subscription message may indicate the time when the service request or subscription message was created.

[0118] The deadline in a service request or subscription message may indicate the time at which the ED expects to receive a response from a service provider function (SPF). In some aspects, the deadline may indicate an absolute time, such as in the format of year-month-day-hour-minute-second-millisecond. In some aspects, the deadline may indicate a relative time to a timestamp, such as indicating how long (expressed in hours, minutes, seconds, or milliseconds) after the timestamp the ED expects to receive a response from the SPF.

[0119] The type of network information may include analytical information, for example, one or more of statistics and predictions of traffic density. The type of network information may be represented by one or more of a network information ID and an analytical information ID.

[0120] The service location included in the service request or subscription message may refer to the location of the requested network information. The data time window may refer to a time window in which relevant data may be collected to generate past data statistics or future data predictions. The data time window may be represented by a start time and an end time, wherein the time may include one or more of year, month, day, hour, minute, second, and millisecond.

[0121] The subscription time window may refer to a time period during which the ED needs network services. The subscription time window may be represented by a start time and an end time, wherein the time may include one or more of year, month, day, hour, minute, and second.

[0122] In one aspect, the NCSP 708 may read the service request or subscription message and send the service request or subscription message to the AN protocol layer stack 704 in the ED 740. The AN layer protocol layer stack 704 in the ED 740 may forward the service request or subscription message to the AN protocol layer stack 702 in the AN 742 via a wireless or wired physical medium 710. The wireless or wired physical medium 710 may be a channel that carries control messages (a physical channel in the case of a wired physical medium). The AN protocol layer stack 702 may also forward the ED service request or subscription to the EAIF 752 in the AN 742. The EAIF 752 may read the ED service request or subscription message and forward the message directly to a service provider function (SPF) in the CN 744 using the information provided in the message, or forward the message to the service provider function via one or more of the AN NCIF 754 and the CN NCIF 764.

[0123] In some aspects, the MNO may provide real-time services to the ED 740, such as road traffic information.

[0124] Fig. 8A and Figure 8B The process of ED 801 acquiring real-time services from a mobile network provided by one aspect of the present invention is shown. Process 800 can provide a configuration for a user device (eg, ED 801) to acquire, for example, local sensing information and AI / ML services.

[0125] In step 802, process 800 includes ED 801 receiving a control message from an application in an application layer of a user device. ED 801 may read the control message, for example, ED 801 may read one or more of a header of the control message, an application ID carried in the message, an IP address, and a port number of a target server. In one aspect, the control message may be a request for a service provided by a mobile network. For example, the control message may carry an indication that the message is to request a service provided by a mobile network (e.g., an MEC service), such as an MNO MEC service request.

[0126] In some aspects, ED 801 may request data analytics services, such as services for obtaining real-time vehicular and non-vehicular traffic density updates.

[0127] In some aspects, ED 801 may be a device in an autonomous vehicle, and the request may be a request for a service to detect one or more objects in a perception data file, such as images, videos, LIDAR, or radar signals collected from the environment around the vehicle. ED 801 may send a service request or a service subscription in a control message, and the control message may be sent in a control channel between ED 801 and an AN node. The control channel may be carried by a wireless or wired medium.

[0128] A service request or service subscription may include one or more of the following information: ED ID, ED location, application ID, service ID, destination information, data network name (DNN), network slice ID, location of the requested service, data to be analyzed by the mobile network service.

[0129] The ED location may be one or more of a 2D or 3D GPS location, an AN node ID, and a cell ID. The application ID may be an ID used to identify an application request made by ED 801. The service ID may be an ID used to identify a service provided by the mobile network. The destination information may be represented by an IP address and a port number of a server in a mobile network or an external network. The location of the requested service may include one or more of the following: a geographic area ID, a road segment ID, an AN node ID, a cell ID, etc. The data to be analyzed by the mobile network service may include one or more of the following: LIDAR data, radar data, images, videos, etc.

[0130] In one aspect, ED 801 may send a service request, such as an RTAS request or RTAS subscription message, to the mobile network to obtain a service (eg, a service for road traffic analysis information). The service request may be sent from ED to EAIF via control channel A1C.

[0131] In one aspect, if ED 801 sends an RTAS request, ED 801 may wish to receive and therefore request to receive road traffic analysis information once (e.g., in one response, in one transmission, or in one continuous transmission). In some aspects, if ED 801 sends an RTAS subscription, ED 801 may wish to receive and therefore request to receive road traffic analysis information multiple times.

[0132] An RTAS request or RTAS subscription may include one or more of the following information: a driving path between two points, a location, waypoints, accuracy of the requested road analysis information, type of road analysis information, an indication to receive RTA updates.

[0133] A driving path between two points may be indicated by a start point and an end point. A driving path may include one or more of the following: a start point, an end point, and a list of waypoints. Each point may be represented by a point in 2-dimensional (2D) or 3-dimensional (3D) coordinates, or a list of intersection points. Each point in the driving path may be associated with a time or time window in which the ED 801 may arrive, leave, or stay.

[0134] The location can be associated with a time window, which can be represented by a start time and an end time. The time can be described by one or more of year, month, day, hour, minute, and second, such as 2021-10-10 10-10-10. The accuracy of the road analysis information can be represented by a percentage (e.g., 90% accuracy) or other indication.

[0135] Types of road analysis information may include the number of vehicles traveling on a road segment (or between two waypoints) in an observation window. The observation window may be represented by a start time and an end time.

[0136] The type of road analysis information may also include the vehicle traffic density of the road section between two points. In some aspects, the vehicle traffic density may be measured by the number of vehicles entering the road section divided by the length of the observation time. In some aspects, the vehicle traffic density may be measured by the number of vehicles entering the road section divided by the length of the observation time divided by the number of lanes in the direction of travel divided by the length of the road section. It will be appreciated by those skilled in the art that there are other appropriate methods to measure the vehicle traffic density.

[0137] The type of road analysis information may also include non-vehicle traffic density. Non-vehicle traffic density may be measured by the number of non-vehicle road users entering the road segment divided by the observation window (or observation period). Non-vehicle road users may include one or more of the following: cyclists, car drivers, pedestrians, or any other road users.

[0138] The type of road analysis information may also include the number of pedestrians passing through one or more roads at an intersection. An intersection may be one or more starting points, or one or more end points of one or more road segments. In some aspects, an intersection may be between a starting point and an end point of a road segment.

[0139] In some aspects, if ED 801 sends an RTAS SUBSCRIBE message, then the indication of receiving RTA updates may be omitted.

[0140] In step 804, EAIF 803 may receive a service request from ED 801. EAIF may forward the service request message to AN ECIF 805 or CN ECIF 807. If AN ECIF 805 receives the service request message in step 804, then in step 806, AN ECIF 805 may forward the service request message to CN ECIF 807.

[0141] In step 808, CN ECIF 807 may receive a service request from ED 801. CN EICF 807 may read the service request message. CN EICF 807 may use one or more information carried in the service request message to discover and select SPF function 860 to service the ED request.

[0142] In some aspects, the CN ECIF 807 may send a request to a NF database (e.g., NF database 128) to discover the SPF. The CN ECIF 807 may include one or more of the following information in the request to the NF database: ED ID, ED location, application ID, service ID, destination information, DNN, network slice ID, location of the requested service. The NF database may respond to the CN ECIF 807 with a response message including the SPF 860 information. The response message may include information indicating the NF profile of the SPF 860 that can provide the requested service. The CN ECIF 807 may then select the SPF from the information of the SPFs received from the NF database.

[0143] In some aspects, the CN ECIF 807 may have pre-configured information about the SPF, such as one or more NF profiles for the SPF stored in the CN ECIF 807. The CN ECIF 807 may use the pre-configured information to select the SPF.

[0144] The CN ECIF 807 may store the SPF information selected to serve the ED service request. The SPF information may include one or more of the following: NF ID of the SPF, ED ID, service ID, application ID, ED location, and other related information.

[0145] In step 810 , the CN ECIF 807 may forward the service request to the selected SPF 860 .

[0146] In step 812, SPF 860 may receive a service request message from ED 801 via CN ECIF 807. SPF 860 may then send a service authorization request message to service authorization function 862 to check whether ED 801 is authorized to use the requested service. SPF 860 may include one or more information elements received from the service request message in the service authorization request message.

[0147] In step 814, the service authorization function 862 may determine whether ED 801 is authorized to use the requested service based on one or more of the following: ED data (e.g., ED profile, ED subscription service) and information received from SPF. The service authorization function 862 may send a service authorization response message to SPF 860. The service authorization response message may indicate whether ED 801 is allowed to use the requested service. If ED 801 is allowed to use the requested service, the service authorization function 862 may include one or more of the following in the service authorization response message: the location where ED 801 can use the service, the time window in which ED 801 can use the service. If ED 801 is not allowed to use one or more requested services, the service authorization function may send one or more reasons why the requested service was denied.

[0148] If ED 801 is authorized to use the one or more requested services, then in step 816 , SPF 860 may select one or more interface functions (eg, CN NCIF 811 and AN NCIF 809 ) to communicate with AN and ED 801 .

[0149] In some aspects, the SPF 860 may send a request to the NF database function to discover one or more available interface functions (e.g., CN NCIF 811 and AN NCIF 809). The request message may include one or more of the following information: ED ID, ED location, service ID, application ID, service location, SPF NF ID, DNN, network slice ID, AN ID, cell ID, AT type, and AT ID. The NF database function may send a response message to the SPF 860. The response message may include one or more NF profiles of one or more of the CN NCIF 811 and the AN NCIF 809.

[0150] In step 818, SPF 860 may send a service response message to ED 801. In some aspects, SPF 860 may send the service response message to ED 801 via EAIF 803. In some aspects, SPF 860 may send the service response message to ED via one or more of CN ECIF 807 and AN ECIF 805.

[0151] In the service response, SPF 860 may include one or more of the following information: ED ID, ED location, service acceptance or service rejection indication, reason for service rejection (in case the requested service is rejected), service location of the accepted service, time window of the accepted service, NF ID of SPF, address information of SPF (such as IP address and port number, FQDN), service ID, application ID, DNN, network slice information, NF ID of the selected CN NCIF, NF ID of the selected AN NCIF, EAIFNF ID.

[0152] In some aspects, the SPF may include two messages in the service response: a network-centric (NC) service response message to be sent to the EAIF 803 and an ED service response message to be sent to the ED 801 .

[0153] In some aspects, the NC service response message may include one or more of the following information: ED ID, ED location, service location of the accepted service, time window of the accepted service, NF ID of the SPF, address information of the SPF (e.g., IP address and port number), service ID, application ID, DNN, network slice information, NF ID of the selected CN NCIF 811, NF ID of the selected ANNCIF 809, and EAIF NF ID.

[0154] In some aspects, the ED service response message may include one or more of the following information: ED ID, service acceptance or service rejection indication, reason for service rejection (in the event that the requested service is rejected), service location of the accepted service, time window of the accepted service, NF ID of SPF, address information of SPF (e.g., IP address and port number), service ID, application ID, DNN, and network slice information.

[0155] If CN ECIF 807 receives a service response message from SPF 860 , then in step 820 , CN ECIF 807 may forward the service response message to EAIF 803 directly or through AN ECIF 805 .

[0156] If the AN ECIF 805 receives a service response message from the SPF 860 , then in step 822 , the AN ECIF 805 may forward the service response message to the EAIF 803 .

[0157] In step 824, the EAIF 803 may receive a service response message from the SPF 860 directly or through one or more of the AN ECIF 805 and the CN ECIF 807. In some aspects, if the SPF 860 sends the NC service response message to the EAIF 803, the EAIF 803 may store one or more of the information elements of the NC service response message in an ED service profile in a local memory accessible to the EAIF 803. The ED service profile may include one or more of the following information: EDID, ED location, service location of the accepted service, time window of the accepted service, NF ID of the SPF 860, address information of the SPF 860 (e.g., IP address and port number), service ID, application ID, DNN, network slice information, NF ID of the selected CN NCIF, NF ID of the selected AN NCIF, and EAIF NF ID.

[0158] In some aspects, the EAIF 803 may allocate AN resources to serve data transmission between the ED 801 and the SPF 860. For example, the AN 102 may allocate a radio service channel between the ED 801 and the AN 102 to transmit messages between the ED 801 and the SPF 860.

[0159] In step 826, EAIF 803 may forward the ED service response message received from SPF 860 to ED 801. In one aspect, if the ED service response message includes a service rejection indication, ED may, in step 828 (see Figure 8B ) does not send service data transmission, and the operations in steps 830 to 844 are not performed.

[0160] If the ED service response message includes a service acceptance indication, then in step 828 , ED 801 may send a service data transfer message to EAIF 803 toward SPF 860 .

[0161] In one aspect, ED 801 may receive a message from an application in an application layer of a user device. ED 801 may read the message, for example, ED 801 may read one or more of: a header of the message, an application ID carried in the message, address information (e.g., IP address, port number, FQDN) of a target server (e.g., SPF). In some aspects, the message may be sent to an SPF in a mobile network. For example, the message may carry an indication, such as an indication that the message is to be sent to, for example, MNO MEC service data of an MEC service provided by a mobile network. ED 801 may request a data analysis service, such as a service for obtaining real-time vehicle and non-vehicle traffic density updates.

[0162] In some aspects, ED 801 may be a device in an autonomous vehicle, wherein ED 801 may request services for detecting one or more objects in LIDAR or radar data collected from a road.

[0163] In some aspects, the service data transmission message in step 828 may include one or more of the following information: destination information, DNN, network slice ID, and service container message.

[0164] The destination information may include information related to the SPF 860. For example, the destination information may include one or more of the following information: a network ID, an address of the SPF (eg, an IP address and a port number of a server), and an FQDN of the SPF.

[0165] The service container message may include one or more of the following information: ED ID, destination information, service request ID, ED location, application ID, service ID, location of the requested service, data to be analyzed or collected by the SPF of the mobile network, and attributes of the data.

[0166] ED ID may be an ID for identifying a device, such as one or more of the following: a sensor device ID and a temporary mobile subscriber ID (TMSI). Service request ID may be an ID for identifying a service request sent from ED 801. ED location may include one or more of the following: 2D or 3D GPS location, network ID, AT type, AT ID, AN ID, AN node ID, and cell ID. Application ID may be an ID that identifies an application request made by ED 801. Service ID may be an ID that identifies a service provided by the network. The location of the requested service may include one or more of the following: geographic area ID, segment ID, network ID, AT type, AT ID, AN ID, AN node ID, and cell ID.

[0167] The data to be analyzed or collected by SPF 860 may include one or more of the following: LIDAR data, radar data, images, video, V2X messages, and any sensed data to be analyzed. In some aspects, the ED may provide the sensed data to SPF 860. The sensed data may include one or more of the following: LIDAR data of a road surface, radar data of a road surface, images of a highway, videos of a highway, environmental data (e.g., temperature, rainfall, humidity levels, and air quality levels), and any sensed data.

[0168] The attributes of the data may refer to the attributes of the sensed data. For example, the sensed data may have one or more of the following attributes: the location of the device that collected the sensed data (e.g., 2D or 3D GPS location), the timestamp of the data (which may indicate the time when the data was created or collected).

[0169] In step 830, the EAIF 803 may receive a service data transfer message from the ED 801. The EAIF 803 may check the ED service profile and may read information carried in the service data transfer message to determine the destination of the message. For example, the EAIF 803 may read one or more of the service ID, application ID, and destination information. If the ED service profile includes the destination information received from the SPF, the EAIF 803 may forward the service data transfer message to the SPF 860 directly or through one or more of the AN NCIF 809 and the CN NCIF 811.

[0170] In some aspects, if the EAIF 803 forwards the service data transfer message to the AN NCIF 809, the EAIF 803 may include the CN NCIF address information (eg, one or more of the NCIF NF ID, corresponding IP address, and port number) in the message.

[0171] If AN NCIF 809 receives a service data transfer message from EAIF 803 , then in step 832 , AN NCIF 809 may send the service data transfer message to SPF 860 directly or through AN NCIF 809 .

[0172] If CN NCIF 807 receives a service data transfer message from EAIF 803 or AN NCIF 809, in step 834, CN NCIF 807 may send the service data transfer message to SPF 860. In step 836, SPF 860 may receive the service data sent from ED 801.

[0173] In some aspects, if ED 801 requests data analysis, SPF 860 may use AI / ML methods to analyze the data. For example, ED 801 may request services for detecting one or more objects in one or more of the following: LIDAR data, radar data, video, and images. SPF may use one or more processing techniques to detect one or more objects.

[0174] In some aspects, SPF 860 may store the data in a database function if the ED 801 provides the data. For example, ED 801 may provide data related to one or more of: updates on the road surface, environmental data (e.g., temperature, wind speed, rainfall).

[0175] After processing the service data, SPF 860 may send a service result to ED 801 in step 838. The service result message may be sent to EAIF 803 directly or through one or more of CN NCIF 811 and AN NCIF 809. The service result message may include one or more of the following information: destination information, ED ID, ED container information.

[0176] The destination information may include one or more of the following information of EAIF 803: NF ID of EAIF 803, address of EAIF (eg, IP address and port number), FQDN of EAFI, network ID of EAIF 803 (used to identify the network of EAIF 803), and AN ID of EAIF 803.

[0177] The ED container message may include one or more of the following information to be sent to ED 801: ED ID, service request ID, service confirmation, a list of detected objects and their corresponding attributes, accuracy of object detection, timestamp of service results.

[0178] The service request ID included in the ED container message may be the same as the service request ID sent from ED 801 in step 828. The service confirmation may indicate that the service request has been completed.

[0179] The list of detected objects and their corresponding attributes may include one or more of: object description (e.g., people, vehicles, pedestrians, cyclists, motorists, cars, and trucks), object size description, object location (e.g., absolute 2D or 3D location in a map, a bounding box surrounding the detected object (with location description)), and 2D or 3D relative distance from ED 801.

[0180] The accuracy of object detection can be one or more of the following: a percentage of accuracy (e.g., 80% accuracy), a percentage of inaccuracy (e.g., 20% inaccuracy), a percentage of reliability (e.g., 80% reliability), and other methods or techniques for indicating the accuracy of object detection. The timestamp of the service result can indicate one or more of the following: the time when the service request was completed, the time when the service result was sent from SPF 860, the time when the object was detected by SPF 860, or the timestamp of the data included in the message 828.

[0181] If CN NCIF 811 receives the service result message from SPF 860, CN NCIF 811 may check the destination information to which to forward the message in step 840. For example, CN NCIF 811 may forward the service result message to EAIF 803 directly or through AN NCIF 809.

[0182] If AN NCIF 809 receives the service result message, then in step 842 AN NCIF 809 may check the destination information to identify EAIF 803 . Thereafter, AN NCIF 809 may forward the service result message to EAIF 803 .

[0183] In step 844, EAIF 803 may receive a service result message from SPF 860. EAIF 803 may check the EDID to identify the ED to which the message is sent. Thereafter, EAIF 803 may forward the ED container message to ED 801.

[0184] The aspects described herein may enable user devices to discover and request services of the network. In some aspects, ED service requests may be identified by the EAIF 803, and the EAIF 803 may direct the message to the CN function that provides the service. Compared to 5G, all ED control messages are forwarded from the AN to the CN via the AMF, which does not separate mobility management and service management.

[0185] Fig. 9A and Fig. 9B The process of ED 901 obtaining services from a mobile network provided by one aspect of the present invention is shown. Process 900 may enable ED 901 to obtain sensing information and AI / ML services from a mobile network. In some aspects, process 900 may enable ED 901 to obtain real-time services or data information from a mobile network by communicating with SPF (e.g., RTAS function) via a CP interface.

[0186] According to one aspect, in step 902, ED 901 may receive a control message from an application in an application layer of a user device. ED 901 may read the control message. For example, ED 901 may read one or more of the following: a header of the control message, an application ID carried in the message, an IP address of a target server, and a port number of the target server.

[0187] In some aspects, the control message may carry an indication indicating that the control message is to request a service provided by a mobile network (e.g., an MEC service), such as an MNO MEC service request. ED 901 may request a data analytics service, such as a service for obtaining real-time vehicular and non-vehicular traffic density updates.

[0188] In some aspects, ED 901 may be a device in an autonomous vehicle, and the request may be a request for a service to detect one or more objects in a LIDAR signal, a radar signal, an image, a video, or a V2X message collected from a road. For example, ED 901 may send a service request or a service subscription in a control message, and send the control message in a control channel between ED 901 and an AN node. The control channel may be carried by a wireless or wired medium. For example, ED 901 may send a control message including a service request or a subscription to EAIF 903.

[0189] A service request or subscription may include one or more of the following information: ED ID, ED location, application ID, service ID, destination information, DNN, network slice ID, location of the requested service, data to be analyzed by the mobile network service, timestamp, and deadline.

[0190] The ED 901 location may be one or more of the following: 2D or 3D GPS location, AN node ID, and cell ID. The application ID may be an ID that identifies an application request made by the ED 901. The service ID may be an ID that identifies a service provided by the network. The destination information may be represented by an IP address and port number or FQDN of a server in a mobile network or an external network.

[0191] The location of the requested service may include one or more of the following: geographic area ID, road segment ID, AN node ID, cell ID. The data to be analyzed by the mobile network service may include one or more of the following: LIDAR data, radar data, images, video, and V2X messages or sensing data.

[0192] The timestamp may indicate the time when the service request message was created. The deadline may refer to the time when the ED 901 expects to receive a response from the SPF 909. In some aspects, the deadline may represent an absolute time, for example, in the format of year-month-day-hour-minute-second-millisecond. In some aspects, the deadline may indicate a relative time to the timestamp, for example, how long (in seconds or milliseconds) after the timestamp the ED 901 expects to receive a response from the SPF 909.

[0193] In step 904, the EAIF 903 of the AN node may receive a message from the ED 901. The EAIF 903 may read the message. For example, the EAIF 903 may read the message header and other information to determine whether the message can be forwarded to an NF in the AN or an NF in the CN that handles network-centric services. In some aspects, if the message is a request or subscription to a service provided by the CN, the EAIF 903 may forward the message to the SPF 909 directly or through one or more of the AN NCIF 905 and the CN NCIF 907.

[0194] In step 906, EAIF 903 may send the message received in step 902 to AN NCIF 905. EAIF 903 may include one or more of the information in the message in step 906: AN ID, network ID, AT type, AT ID, location of ED 901.

[0195] In step 908, AN NCIF 905 may receive a message from EAIF 903. AN NCIF 905 may check whether ED 901 is authorized to request the service. AN NCIF 905 may have ED context information including authorization information indicating which services of the network ED 901 may access. If ED 901 is authorized to use the requested service, ANNCIF 905 may forward the message received in step 906 to CN NCIF 907. If ED 901 is not authorized, AN NCIF 905 may send a service rejection message to ED 901. The service rejection message may be sent to EAIF 903, and then EAIF 903 may send a service rejection message to ED 901.

[0196] In step 910, the CN NCIF 907 may receive the message from the AN NCIF 905 in step 908. The CN NCIF 907 may check whether the ED 901 is authorized to use the requested service. The CN NCIF 907 may have an ED context of the ED 901 including authorization information. The authorization information may include information about which services the ED 901 may access. If the ED 901 is authorized to use the requested service, the CN NCIF 907 may forward the message received in step 908 to the corresponding SPF 909. If the ED 901 is not authorized to use the service, the CN NCIF 907 may send a rejection message to the ED 901 through one or more of the AN NCIF 905 and the EAIF 903.

[0197] In step 912, SPF 909 may receive the service request or service subscription message sent from CN NCIF 907 in step 910. SPF 909 may send a message, such as a service authorization request, to an authorization function, such as service authorization function 911. The message may include one or more of the following information received from EAIF 903: ED ID, requested service (which may be represented by a service ID), network ID, AT type, AT ID, AN ID, AN node ID, network slice ID, and location (e.g., one or more of a geographic area ID and an AN node ID).

[0198] In step 914, the service authorization function 911 may have an ED context or ED 901 profile indicating services that ED 901 may access. The authorization function (e.g., service authorization function 911) may use the information provided in the message from SPF 909 in step 910 and the ED context to determine whether ED 901 is authorized to use the service. Service authorization function 911 may send a service authorization response message to SPF 909. The message may indicate whether ED 901 is authorized to use the service and, if ED 901 is not authorized to use the service, why.

[0199] If ED 901 is authorized to use the requested service, in step 916 , SPF 909 may provide the service requested by ED 901 .

[0200] The SPF 909 may then process the provided data. For example, the SPF 909 may process the provided data to detect one or more objects in one or more of the following: photos, videos, LIDAR, radar files, V2X messages, or any sensory data.

[0201] In some aspects, if ED 901 requests data analysis information, SPF 909 may need and may collect necessary data from one or more data sources, such as sensory data from one or more of the AN nodes and other EDs. SPF 909 may then process the collected data and generate the requested analysis information.

[0202] After processing the data provided by ED 901, or after generating the requested information, SPF 909 may send a message to ED 901 through CN NCIF 907 in step 918. In some aspects, if ED 901 sends a service request message in step 902, SPF 909 may send a service response. In some aspects, if ED 901 sends a service subscription message in step 902, SPF 909 may send a service notification. Each of the service response message and the service notification message may include one or more of the following information: ED ID, ED location, network slice ID, return data, real-time analytics (RTA) update, service request ID, NF ID of SPF 909.

[0203] The ED location may include one or more of the following information: AN ID, AN node ID (e.g., wireless base station ID, cell ID, RAN ID, network ID, AT ID). The return data may refer to data provided by the SPF 909 in response to a service request or subscription from the ED 901. For example, the return data may include one or more of the following: an object detected from data provided by the ED 901 (where the provided data may include one or more of photos, videos, LIDAR, radar signals), the location of the detected object, and a timestamp indicating the time when the object was detected.

[0204] In some aspects, if ED 901 subscribed to RTA notifications in step 902, the SPF includes one or more RTA updates to ED 901 in the service response or notification message.

[0205] The service request ID in the service response or notification message may be the same as the service request ID sent from ED 901 in step 902. The NF ID of SPF may be used to identify the SPF 909 providing services to ED 901. The NF ID may be one or more of an IP address and a FQDN.

[0206] In step 920, the CN NCIF 907 may receive the message sent from the SPF 909 in step 918. The CN NCIF 907 may use at least one information element (e.g., ED ID, AN ID, AN node ID, cell ID, service request ID) carried in the message to identify the destination of the message. Then, the CN NCIF 907 may forward the message to the EAIF 903 directly or through the AN NCIF 905.

[0207] If the CN NCIF 907 sends a service response or service notification to the AN NCIF 905 in step 920, the AN NCIF 905 may use at least one information element (e.g., ED ID, AN ID, AN node ID, cell ID, and service request ID) carried in the message to identify the EAIF 903 in step 922. Then, the AN NCIF 903 may forward the message to the EAIF 903.

[0208] In step 924 , the EAIF 903 may receive a service response or a service notification sent from the SPF 909 , and forward the message to the ED 901 .

[0209] If ED 901 sends a service subscription message in step 902 , SPF 909 may continue to perform data processing for the newly available data, as shown in step 926 .

[0210] If new data analysis results are available after sending the service response or notification in step 918, SPF 909 may send a service notification message to ED 901 via CN NCIF 907 in step 928. The message may include part or all of the information included in the service response or notification message sent in step 918.

[0211] In some aspects, if ED 901 subscribes to RTA notification 902, SPF 909 may send RTA updates to ED 901 in a service notification message. In some aspects, the RTA update may include real-time traffic density information and time information. The time information (e.g., a timestamp) may indicate the time when the RTA update is applied, such as the current time / duration, or a time / time period in the past or future. In some aspects, if the current road traffic analysis indicates a difference from the real-time road traffic density previously sent, the real-time traffic density information for the current time is sent. In some aspects, the difference in the road traffic analysis may be a percentage difference (x%) compared to the RTA that has been previously sent to the ED (in step 918), such as 10%.

[0212] In step 930, the CN NCIF 907 may receive the service notification message sent from the SPF 909 in step 928. The CN NCIF 907 may use at least one information element (e.g., ED ID, network ID, AT type, AT ID, AN ID, AN node ID, cell ID, service request ID) carried in the message to identify the destination of the message. Then, the CN NCIF 907 may forward the message to the EAIF 903 directly or through the AN NCIF 905.

[0213] If the CN NCIF 907 sends a service notification to the AN NCIF 905 in step 930, the ANNCIF 905 may use at least one information element (e.g., ED ID, network ID, AT type, AT ID, AN ID, AN node ID, cell ID, and service request ID) carried in the message to identify the EAIF 903 in step 932. Then, the AN NCIF 903 may forward the message to the EAIF 903.

[0214] In step 934 , EAIF 903 may receive the service notification sent from SPF 909 and forward the message to ED 901 .

[0215] In some aspects, if ED 901 sends a service subscription message in step 902, and ED 901 may wish to stop the service subscription when the service is no longer needed, then, in step 936, ED 901 may determine that the service is no longer needed.

[0216] In step 938, ED 901 may send an unsubscribe request message to SPF 909 via EAIF 903. The unsubscribe request message may indicate a request to unsubscribe from a service of SPF 909. The message may include a service request ID similar to the service request sent in step 902, an indication to stop the service, and other relevant information.

[0217] In step 940, the EAIF 903 may receive a cancel subscription request message from the ED 901. Based on the received cancel subscription request message, the EAIF 903 may determine that the message will be forwarded to the SPF 909. For example, the EAIF 903 may read and use the information carried in the cancel subscription request message (e.g., at least one of the service request ID, the ED ID, and the SPF ID) to determine the destination of the forwarded message. Thereafter, the EAIF 903 may then send the cancel subscription request message to the SPF 909 directly or through one or more of the AN NCIF 905 and the CN NCIF 907.

[0218] When AN NCIF 905 receives the unsubscribe request message from EAIF 903, AN NCIF 905 may read the message and use the information (e.g., at least one of the service request ID, ED ID, and SPF ID) carried in the unsubscribe request message to determine the destination of the forwarded message in step 942. Thereafter, EAIF 903 may send the unsubscribe request message to SPF 909 directly or through CN NCIF 907.

[0219] If CN NCIF 907 receives a cancel subscription request message from EAIF 903 or AN NCIF 905, in step 944, CN NCIF 907 may read the cancel subscription request message and use the information carried in the message (e.g., at least one of the service request ID, ED ID, and SPF ID) to determine the destination of the forwarded message. Thereafter, EAIF 903 may send a cancel subscription request message to SPF 909.

[0220] In step 946, SPF 909 may receive a unsubscribe request message from CN NCIF 907. Thereafter, SPF 909 may stop collecting and stop processing data used to generate the service. In some aspects, SPF 909 may send an unsubscribe confirmation (ACK) message to ED 901. SPF 909 may send an unsubscribe ACK message to EAIF 903 directly or through one or more of NC NCIF 907 and AN NCIF905. The unsubscribe ACK message may include one or more of the following information: ED ID, a service subscription stop ACK for confirming that the service subscription is terminated, the service request ID received by SPF 909 in 902, SPF ID, AN ID, and ED location.

[0221] If the CN NCIF 907 receives the unsubscribe ACK message from the SPF 909 in step 946, the CN NCIF 907 may read the unsubscribe ACK message and use the information carried in the message (e.g., one or more of the service request ID, ED ID, AN ID, ED location, and SPF ID) to determine the destination of the forwarded message in step 948. Thereafter, the CN NCIF 907 may send a message to the EAIF 903 directly or through the AN NCIF 905.

[0222] If the AN NCIF 905 receives the unsubscribe ACK message from the SPF 909 directly or through the CN NCIF 907, then in step 950, the AN NCIF 905 may read the unsubscribe ACK message and use the information carried in the message (e.g., one or more of the service request ID, ED ID, AN ID, ED location, and SPF ID) to determine the destination of the forwarded message. Thereafter, the AN NCIF 905 may send the unsubscribe ACK message to the ED 901 through the ENIF 903.

[0223] In step 952, the EAIF 903 may receive an unsubscribe ACK message from the SPF 909 directly or through one or more of the CN NCIF 907 and the AN NCIF 905. The EAIF 903 may read the unsubscribe ACK message and use the information carried in the message (e.g., one or more of the service request ID, ED ID, AN ID, ED location, and SPF ID) to determine the ED 901 that should receive the unsubscribe ACK message. Thereafter, the EAIF 903 may send the unsubscribe ACK message to the ED 901 via a medium such as a wireless or wired interface. Thereafter, the ED 901 may receive the unsubscribe ACK message.

[0224] Aspects described herein may provide a method for ED 901 to directly request a service provided by a mobile network. In some aspects, ED 901 may be configured with application information so that ED 901 is aware of available network services. Thus, ED 901 may be used to send a message to access the network service. Aspects described herein may also provide AN to detect a message to be sent to a NF in a CN that provides the requested service.

[0225] The aspects described herein may provide an enhanced network architecture and interface that separates ED-centric services from network-centric services. The aspects described herein may provide that NFs in an AN register their services in a CN NF database by using network-centric services.

[0226] As described herein, a profile of an AN NF or ED that may provide data (e.g., sensing data) may include one or more of the following information: network ID, AT type, AT ID, AN ID, network slice ID, NF ID (in the case of an AN NF profile), device ID (in the case of an ED profile), address of the NF, type of data, location information, and operation time.

[0227] The network ID may be an ID that can be used to identify a mobile network. The AT type may indicate the type of access technology such as 4G, 5G, 6G, WiFi, fiber, etc. The AT ID may be an identifier of the AT type. The AN ID may be an identifier of the AN that can provide the requested sensing data. The network slice ID may refer to one or more of the following: an ID of a network slice of a network or an ID of a network slice of an AN.

[0228] The address of the NF may include one or more of the following information: an IP address, a port number, and a FQDN. The type of data may indicate the type of sensing data that may be generated. The location information may refer to the location of the sensing data to be collected.

[0229] The operation time may indicate a time window in which the sensing data may be generated. The operation time may be represented by a start time and an end time, wherein each of the start time and the end time may be associated with a day and represented by one or more of hours, minutes, and seconds. In some aspects, the operation time may be an interval having a start time and an end time, wherein each of the start time and the end time may be represented by one or more of hours, minutes, seconds, years, months, and days.

[0230] Aspects described herein may provide a CN NCIF 907 that may receive an AN NF registration message from an AN NF. The CNNCIF 907 may then forward the registration message to a NF database, such as the NF database 128.

[0231] The aspects described herein may provide a method for separating mobility management and network service access of ED 901. For example, the aspects described herein may provide a NF interface function in the AN (e.g., EAIF 903 via AN NCIF 905 or AN ECIF) to forward one or more CP messages to AN ECIF or CN NCIF 907 in the CN.

[0232] As can be appreciated by those skilled in the art, the aspects described herein (including enhanced network architecture, separate CP interface, and corresponding methods related thereto) may be applicable to 6G mobile networks.

[0233] Fig.10The device 1000 provided by different aspects of the present invention can perform any or all operations of the above methods and features explicitly or implicitly described herein. For example, a computer equipped with network functions can be used as the device 1000. In some aspects, the device 1000 can be an ED, such as ED 140. In some aspects, the device 1000 can be a device connected to a network infrastructure via a wireless interface, such as a mobile phone, a smart phone, or other such devices that can be classified as user equipment (UE). In some aspects, the device 1000 can be a machine type communication (MTC) device (also called a machine-to-machine (M2M) device) or other such devices that can be classified as UE (although no direct services are provided to users). In some aspects, the device 1000 can be used to implement one or more aspects described herein. For example, the device 1000 can be used to perform operations performed by one or more of the ED 140 and the functions described herein.

[0234] As shown, the device 1000 may include a processor 1010, such as a central processing unit (CPU) or a special processor, such as a graphics processing unit (GPU) or other such processor unit, a memory 1020, a non-transient mass storage 1030, an input-output interface 1040, a network interface 1050, and a transceiver 1060, all of which are coupled by a bidirectional bus 1070 communication. According to certain aspects, any or all of the described elements may be used, or only a subset of the elements may be used. In addition, the device 1000 may include multiple instances of certain elements, such as multiple processors, multiple memories, or multiple transceivers. In addition, the elements of the hardware device may be directly coupled to other elements without a bidirectional bus. In addition to or in place of a processor and a memory, other electronic devices (e.g., integrated circuits) may be used to perform the desired logic operations.

[0235] The memory 1020 may include any type of non-transient memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or any combination thereof. The mass storage element 1030 may include any type of non-transient storage device, such as a solid state drive, a hard disk drive, a disk drive, an optical drive, a USB drive, or any computer program product for storing data and machine executable program code. According to certain aspects, the memory 1020 or the mass storage 1030 may record thereon statements and instructions executable by the processor 1010 for performing any of the above-described method operations.

[0236] Fig.11 A method 1100 for communicating between an AN and a CN provided by one aspect of the present invention is shown. In some aspects, the method 1100 may be performed by an EAIF (e.g., EAIF 122). The method 1100 includes: in box 1102, receiving a CP message at an interface function of an access network (AN). The method 1100 also includes: in box 1104, based on the CP message, selecting a CP interface from a plurality of CP interfaces between the AN and a CN of a mobile network. The method 1100 also includes: in box 1106, sending a CP message to the CN using the selected CP interface.

[0237] In some aspects, selecting the CP interface includes selecting the CP interface based on an indicator included in the CP message. In some aspects, selecting the CP interface includes selecting the CP interface between a first interface (e.g., C1 146) for electronic device (ED)-centric CP signaling and a second interface (e.g., C2 148) for network-centric CP signaling, wherein the ED-centric CP signaling includes access and mobility CP messages.

[0238] In some aspects, the CP message comprises a message for discovering a network service, and wherein selecting the CP interface comprises selecting a first interface (eg, C1 146).

[0239] In some aspects, the CP message comprises a message for accessing a network service, and wherein selecting the CP interface comprises selecting a second interface (eg, C2 148).

[0240] In some aspects, receiving the CP message includes receiving the CP message from an ED, such as ED 140. In some aspects, sending the CP message to the CN includes sending the CP message to an SPF associated with the CN.

[0241] In some aspects, receiving the CP message includes receiving the CP message at the EAIF 122 .

[0242] Aspects of the present invention may be implemented using electronic hardware, software, or a combination thereof. In some aspects, this may be implemented by one or more computer processors executing program instructions stored in a memory. In some aspects, the present invention may be implemented in part or in whole in hardware, for example, using one or more field programmable gate arrays (FPGA) or application specific integrated circuits (ASIC) to quickly perform processing operations.

[0243] It should be understood that although specific aspects of the technology have been described herein for illustrative purposes, various modifications may be made without departing from the scope of the technology. Therefore, the specification and drawings are only to be regarded as an illustration of the invention as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents within the scope of the invention. Specifically, a computer program product or program element for storing machine-readable signals, or a program storage or storage device such as a magnetic wire, tape, disk or light, optical tape or optical disk is provided, within the scope of the present technology, for controlling the operation of a computer according to the method of the present technology and / or constructing some or all of its components according to the system of the present technology.

[0244] The actions associated with the methods described herein may be implemented as coded instructions in a single computer program product. In other words, the computer program product is a computer-readable medium on which software codes are recorded to perform the methods when the computer program product is loaded into a memory and executed on a microprocessor of the wireless communication device.

[0245] In addition, each operation of the method can be performed on any computing device (such as a personal computer, server, PDA, etc.), and can be performed according to one or more program elements, modules or objects generated from any programming language (such as C++, Java, etc.) or a part of one or more program elements, modules or objects. In addition, each operation or a file or object that implements each operation can be performed by dedicated hardware or a circuit module designed for this purpose.

[0246] Through the description of the above aspects, the present invention can be implemented only by hardware, or by software and necessary general hardware platforms. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product. The software product can be stored in a non-volatile or non-transient storage medium, which can be a compact disk read-only memory (CD-ROM), a USB flash drive, or a removable hard disk. The software product includes many instructions that enable a computer device (a personal computer, a server, or a network device) to perform the method provided in the aspects of the present invention. For example, this execution can correspond to the simulation of the logical operations described herein. According to aspects of the present invention, the software product may additionally or alternatively include multiple instructions that enable a computer device to perform operations to configure or program a digital logic device.

[0247] Although the present invention has been described with reference to specific features and aspects of the present invention, it is apparent that various modifications and combinations of the present invention may be made without departing from the present invention. Therefore, the specification and drawings are only regarded as an explanation of the present invention as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents within the scope of the present invention.

Claims

1. A method, characterized in that include: receiving a control plane (CP) message at an interface function of an access network (AN); selecting a CP interface from a plurality of CP interfaces between the AN and a core network (CN) of a mobile network based on the CP message; and The CP message is sent to the CN using the selected CP interface.

2. The method according to claim 1, characterized in that Selecting the CP interface includes selecting the CP interface based on an indicator included in the CP message.

3. The method according to claim 1 or 2, characterized in that: Selecting the CP interface includes selecting the CP interface between a first interface for electronic device (ED)-centric CP signaling and a second interface for network-centric CP signaling, wherein the ED-centric CP signaling includes access and mobility CP messages.

4. The method according to claim 3, characterized in that: The CP message includes a message for discovering a network service, and selecting a CP interface includes selecting the first interface.

5. The method according to claim 3, characterized in that: The CP message includes a message for accessing a network service, and selecting the CP interface includes selecting the second interface.

6. The method according to any one of claims 1 to 5, characterized in that Receiving the CP message includes receiving the CP message from an ED, and sending the CP message to the CN includes sending the CP message to a service provider function (SPF) associated with the CN.

7. The method according to any one of claims 1 to 6, characterized in that Receiving the CP message includes receiving the CP message at an ED-AN interface function (EAIF).

8. The method according to any one of claims 1 to 7, characterized in that Sending the CP message to the CN using the selected CP interface includes sending the CP message using one of an AN network-centric interface function and an AN ED-centric interface function.

9. A method for providing a service from an electronic device-access network interface function (EAIF) to an electronic device (ED), characterized in that: The method comprises: The EAIF receives a request for a service from the ED, wherein the service is provided by a Service Provider Function (SPF) in a Core Network (CN) of a mobile network, and wherein the EAIF is associated with an Access Network (AN); sending the request for service via a first interface between the AN and the CN; receiving a first response indicating that the ED is authorized to use the service; allocating one or more AN resources to service data communications between the ED and the SPF; and Based on the first response, a second response is sent to the ED.

10. The method according to claim 9, characterized in that Receiving a request includes: receiving a request including one or more of the following: ED identifier (ID), ED location, application ID, service ID, destination information, data network name (DNN), network slide ID, location of the requested service, data to be analyzed, driving path, waypoints, location and corresponding time window, accuracy of road analysis information, and type of road analysis information.

11. The method according to claim 9 or 10, characterized in that: Sending the request for the service includes sending the request for the service through one or more of an AN ED-centric interface function (ECIF) and a CN ECIF.

12. The method according to any one of claims 9 to 11, characterized in that Receiving the first response includes: receiving the first response through one or more of an AN ECIF and a CN ECIF.

13. The method according to any one of claims 9 to 12, characterized in that Receiving a first response includes: receiving a first response including one or more of the following: an ED identifier (ID), an ED location, an indication of service acceptance or service rejection, a service rejection reason when there is an indication of service rejection, a service location, a time window of the service, a network function (NF) ID of the SPF, address information of the SPF, a service ID, an application ID, a data network name (DNN), network slice information, a selected CN network-centric interface function (NCIF) NF ID, a selected AN NCIF NF ID, and an EAIF NF ID.

14. The method according to any one of claims 9 to 13, characterized in that Sending a second response includes: sensing a second response including one or more of the following: an ED identifier (ID), an indication of service acceptance or service rejection, a reason for service rejection when there is an indication of service rejection, a service location, a time window for the service, a network function (NF) ID of the SPF, address information of the SPF, a service ID, an application ID, a data network name (DNN), and network slice information.

15. The method according to any one of claims 9 to 14, characterized in that Also includes: receiving a data message associated with the service from the ED; Sending the data message to the SPF; receiving a service result message from the SPF based on the data message; as well as The service result message is sent to the ED.

16. The method according to claim 15, characterized in that Receiving a data message includes: receiving a data message including one or more of the following: destination information associated with the SPF, a data network name (DNN), a network slice identifier (ID), and a service container message.

17. The method according to claim 15 or 16, characterized in that Sending the data message to the SPF includes: sending the data message to the SPF through one or more of an AN NCIF and a CN NCIF.

18. The method according to any one of claims 15 to 17, characterized in that Receiving a service result message includes: receiving a service result message including one or more of the following: destination information associated with the EAIF, an ED identifier, and an ED container message, wherein the ED container message includes one or more of the following: ED ID, service request ID, service confirmation indicating that the requested service has been completed, a list of detected objects and their corresponding attributes, detection accuracy of object detection, and a timestamp of the service result message.

19. The method according to any one of claims 15 to 18, characterized in that Receiving the service result message includes: receiving the service result message through one or more of the AN NCIF and the CN NCIF.

20. A method performed by an electronic device-access network interface function (EAIF), characterized in that: The method comprises: The electronic device-access network interface function (EAIF) receives a service request from an electronic device (ED); determining whether the request is directed to a Service Provider Function (SPF) in a Core Network (CN) of the mobile network; Sending the request for service to the SPF; receiving a service response from the SPF based on the request; and The service response is sent to the ED.

21. The method according to claim 20, characterized in that Receiving a service request includes: receiving a service request including one or more of the following: an ED identifier (ID), an ED location, an application ID, a service ID, destination information, a data network name (DNN), a network slide ID, the location of the requested service, data to be analyzed, a timestamp, and a deadline.

22. The method according to claim 20 or 21, characterized in that Sending the request for service to the SPF includes: sending the request for service to the SPF through one or more of an AN NCIF and a CN NCIF.

23. The method according to any one of claims 20 to 22, characterized in that Receiving a service response includes: receiving a service response including one or more of the following from the SPF: an ED identifier (ID), an ED location, a network slide ID, return data, a service request ID, and a network function (NF) ID of the SPF.

24. The method according to any one of claims 20 to 23, characterized in that Receiving the service response includes: receiving the service response through one or more of the AN NCIF and the CN NCIF.

25. The method according to any one of claims 20 to 24, characterized in that Also includes: receiving a message from the ED to unsubscribe from the service, the message including a service request identifier (ID) associated with the request for the service; Sending the unsubscribe message to the SPF; receiving a confirmation response from the SPF based on the unsubscribe message; as well as The confirmation response is sent to the ED.

26. A method performed by a network function (NF) in an access network (AN), characterized in that: The method comprises: sending an AN NF registration message to a NF database in a core network (CN) of a mobile network, the message including a request to register a service in the NF database; and A registration response is received from the NF database.

27. The method according to claim 26, characterized in that Sending an AN NF registration message includes: sending an AN NF registration message including one or more of the following: a network ID associated with the mobile network, an AN ID, a network slice ID, an ID of the NF, an address of the NF, a type of data, location information, and an operation time indicating a time window.

28. The method according to claim 26 or 27, characterized in that Sending the AN NF registration message includes sending the AN NF registration message including one or more of: a geographic location, a type of collected data, and a type of service.

29. The method according to claim 28, characterized in that Sending the AN NF registration message including the geographic location includes sending the AN NF registration message including one or more of the following: a two-dimensional location, a three-dimensional location, a common address, the AN ID, and a cell ID.

30. The method according to claim 28 or 29, characterized in that Sending an ANNF registration message including the type of collected data includes: sending an AN NF registration message including one or more of the following: images, videos, connected vehicle messages, radar, LIDAR, temperature, vehicle traffic counts, and non-vehicle traffic counts.

31. The method according to any one of claims 28 to 30, characterized in that Sending an ANNF registration message including the type of service includes: sending an AN NF registration message indicating one or more of the following: perception data collection service, artificial intelligence service, machine learning service, federated learning, segmentation learning, supervised learning, unsupervised learning, and reinforcement learning.

32. The method according to any one of claims 26 to 31, characterized in that Sending the AN NF registration message includes sending the AN NF registration message through one or more of the AN NCIF and the CN NCIF.

33. The method according to any one of claims 26 to 32, characterized in that Receiving a registration response from the NF database includes receiving a registration response from the NF database indicating that the NF is registered in the NF database.

34. A method for providing services to an electronic device (ED) by a service provider function (SPF) in a core network (CN) of a mobile network, characterized in that: The method comprises: receiving a request for the service, the request being associated with the ED and received from an EAIF; Sending a request to the service authorization function to authorize the ED to use the service; receiving a response from the service authorization function indicating that the ED is authorized to use the service; and A service response is sent to the EAIF.

35. The method according to claim 34, characterized in that Receiving the request for the service includes: receiving the request for the service through one or more of the ANECIF and the CN ECIF.

36. The method according to claim 34 or 35, characterized in that The receiving a response includes receiving a response including one or more of: a location where the ED can use the service and a time window for the ED to use the service.

37. The method according to any one of claims 34 to 36, characterized in that The method further comprises selecting one or more of an AN NCIF and a CN NCIF, and wherein sending the service response comprises sending the service response indicating the selection of the one or more of the AN NCIF and the CN NCIF.

38. The method according to any one of claims 34 to 37, characterized in that The method further comprises: receiving, from the EAIF, a service data transmission associated with the service; Processing the service data transmission; and Based on the processed service data transmission, a service result is sent to the ED.

39. The method according to claim 38, characterized in that Sending the service result includes sending a service result including one or more of: a destination selection, an identification of the ED, and an ED container message.

40. A method performed by a data processing function (DPF) in a core network (CN) of a mobile network, characterized in that: The method comprises: receiving a request for data from a data consumer function (DCF) in the CN of the mobile network; Based on the request for data, selecting a data source from one or more of: an access network (AN), a network function (NF) in the AN, and an electronic device (ED); sending the request for data to the selected data source; receiving data based on the transmitted request for data; and The received data is sent to the DCF.

41. The method according to claim 40, characterized in that Receiving a request for data includes: receiving a request for data including one or more of the following: an identifier (ID) of the DCF, a service request ID associated with the request, a geographic location, a type of object to be detected, a type of data, an observation time window, a sampling time period, and a moving direction of the object.

42. The method according to claim 40 or 41, characterized in that Select data sources include: Sending a request to a database NF to determine a NF that can provide the requested data, the request including one or more of: location information, type of data, observation window, network identifier (ID), and AN ID; and A response is received from the database NF, the response indicating that the NF can provide the requested data.

43. The method according to any one of claims 40 to 42, characterized in that Sending the request for data includes sending the request for data through one or more of the AN NCIF and the CN NCIF.

44. The method according to any one of claims 40 to 43, characterized in that Receiving data includes: receiving data including one or more of the following: a service request identifier (ID) associated with the request for data, a timestamp of the received data, an AN ID, an AN node ID, an AN cell ID, an ID of the AN DGF, a network ID, a network slice ID, a CN ID, an ID of the ED, a location ID, a type of data, the data, and parameters for reading the data.

45. The method according to any one of claims 40 to 44, characterized in that Sending the received data comprises: processing the received data to generate processed data, wherein processing comprises one or more of: removing private information from the received data, storing the received data in a data storage function, and storing the processed data in the data storage function; and The processed data is sent to the DCF.

46. ​​A computer-readable medium comprising instructions, characterized in that: When the instructions are executed by a processor of a device, the device is caused to perform a method according to any one of claims 1 to 45.

47. A computer program comprising instructions, characterized in that When the program is executed by a processor of a computer, the instructions cause the computer to perform the method according to any one of claims 1 to 45.

48. A device, characterized in that The device comprises: at least one processor; and At least one machine-readable medium storing executable instructions, which, when executed by the at least one processor, cause the apparatus to perform the method of any one of claims 1 to 45.

Images