Method, device and equipment for opening capability of awareness service
In the synesthesia service data capability open architecture, the first device sends the perceived service capability open information to the second device, solving the problem of difficult access to perceived service data, realizing the effective use of data and access control of consumer devices.
Patent Information
- Application Number
- CN202310497702.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-04
- Publication Date
- 2024-11-05
AI Technical Summary
In the existing synesthesia business data capability open architecture, perceived business data is difficult to be effectively accessed and used.
Through a method of opening the ability of perceived services, the first device sends the ability of perceived services to the second device, so that the second device stores the information, thereby realizing the control of the consumer device accessing the first device and ensuring the perceived service data Effective access and use.
It realizes effective access and use of perceived business data, provides access control to consumer devices, and ensures reasonable allocation and use of data.
Smart Images

Figure CN118900403A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to a method, device and equipment for opening the capability of a perception service. Background Art
[0002] In the current open architecture of synaesthesia service data capability, a sensing function (SF) is added for synaesthesia service to manage the synaesthesia service and process the synaesthesia data.
[0003] However, the perception business data generated by SF can be accessed and used, which becomes a technical problem that needs to be solved urgently. Summary of the invention
[0004] The embodiments of the present application provide a method, apparatus and device for opening the capability of a perception service, so as to enable the perception service data to be effectively accessed and used.
[0005] In a first aspect, a method for exposing a capability of a perception service is provided, including:
[0006] The first device sends a first message to the second device, where the first message includes perception service capability exposure information of the first device.
[0007] Second, a method for exposing service-aware capabilities is provided, including:
[0008] The second device receives a first message sent by the first device, where the first message includes the perception service capability opening information of the first device;
[0009] The second device stores the perception service capability exposure information of the first device.
[0010] The third aspect provides a method for exposing the capability of a perception service, including:
[0011] The fourth device sends a third message to the second device, where the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device.
[0012] In a fourth aspect, a capability opening device for sensing services is provided, including:
[0013] The first sending module is configured to send a first message to a second device, where the first message includes the perception service capability exposure information of the first device.
[0014] In a fifth aspect, a capability opening device for sensing services is provided, including:
[0015] A first receiving module, configured to receive a first message sent by a first device, where the first message includes perception service capability exposure information of the first device;
[0016] The storage module is used to store the perception service capability exposure information of the first device.
[0017] In a sixth aspect, a capability opening device for sensing services is provided, including:
[0018] The second sending module is used to send a third message to the second device, where the third message is used to request information of a fifth device, and the fifth device supports opening the perception service data to the fourth device.
[0019] In a seventh aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the third aspect are implemented.
[0020] In an eighth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is used to send a third message to a second device, the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device.
[0021] In the ninth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect, the second aspect, or the third aspect are implemented.
[0022] In a tenth aspect, a network side device is provided, including a processor and a communication interface, wherein the network side device is a first device, and the communication interface is used to send a first message to a second device, wherein the first message includes perception service capability exposure information of the first device;
[0023] Alternatively, the network side device is a second device, the communication interface is used to receive a first message sent by a first device, the first message includes the perception service capability exposure information of the first device; the processor is used to store the perception service capability exposure information of the first device;
[0024] Alternatively, the network side device is a fourth device, the communication interface is used to send a third message to the second device, the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device.
[0025] In the tenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.
[0026] In the eleventh aspect, a wireless communication system is provided, comprising: a first device, a second device or a fourth device, wherein the first device can be used to execute the steps of the method described in the first aspect, the second device can be used to execute the steps of the method described in the second aspect, and the fourth device can be used to execute the steps of the method described in the third aspect.
[0027] In the twelfth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the fourth aspect.
[0028] In the thirteenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method as described in the ... aspect.
[0029] In an embodiment of the present application, the exposure information of its own perception service capability is informed to the second device so that the second device stores the information, and can control the access of the consumer device to the first device, so that the perception service data can be effectively accessed and used. BRIEF DESCRIPTION OF THE DRAWINGS
[0030] Figure 1 is a block diagram of a wireless communication system;
[0031] Figure 2 This is a schematic diagram of the architecture for opening up the data capabilities of the Tonga business;
[0032] Figure 3 This is one of the method flow diagrams of the embodiment of the present application;
[0033] Figure 4 This is the second schematic diagram of the method flow of the embodiment of the present application;
[0034] Figure 5 This is the third schematic diagram of the method flow of the embodiment of the present application;
[0035] Figure 6 This is one of the schematic diagrams of the method application of the embodiment of the present application;
[0036] Figure 7 This is the second schematic diagram of the method application of the embodiment of the present application;
[0037] Figure 8 yes Figure 3 The corresponding schematic diagram of the device module structure;
[0038] Fig. 9 yes Figure 4 The corresponding schematic diagram of the device module structure;
[0039] Fig.10 yes Figure 5 The corresponding schematic diagram of the device module structure;
[0040] Fig.11 is a schematic diagram of the structure of a communication device according to an embodiment of the present application;
[0041] Fig.12 is a schematic diagram of the structure of a terminal in an embodiment of the present application;
[0042] Fig.13 is a schematic diagram of the structure of a network side device in an embodiment of the present application;
[0043] Fig.14 It is a structural diagram of a network side device according to another embodiment of the present application. DETAILED DESCRIPTION
[0044] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0045] The terms "first", "second", etc. of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0046] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
[0047] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.
[0048] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
[0049] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.
[0050] Some concepts related to the embodiments of the present application are described below:
[0051] 1. Communication and perception integration / synaesthesia integration:
[0052] Wireless communications and radar sensing (C&S) have been developing in parallel for decades, but with limited overlap. They have a lot in common in terms of signal processing algorithms, equipment, and to some extent, system architecture. In recent years, the two systems have attracted more and more attention from researchers in terms of coexistence, cooperation, and joint design.
[0053] In the early days, people conducted extensive research on the coexistence of communication systems and radar systems, focusing on developing effective interference management techniques to enable two separately deployed systems to operate smoothly without interfering with each other. Although radar and communication systems may be co-located or even physically integrated, they transmit two different signals in the time / frequency domain. They share the same resources through cooperation to minimize the interference between each other when working simultaneously. Corresponding measures include beamforming, cooperative spectrum sharing, primary and secondary spectrum sharing, dynamic coexistence, etc. However, effective interference elimination usually has strict requirements on the mobility of nodes and the information exchange between nodes, so the improvement of spectrum efficiency is actually limited. Since the interference in the coexistence system is caused by the transmission of two independent signals, it is natural to ask whether we can use one transmission signal for communication and radar sensing at the same time. Radar systems usually use specially designed waveforms, such as short pulses and chirps, which enable high-power radiation and simplified receiver processing. However, these waveforms are not necessary for radar detection. Passive radar or passive sensing using different radio signals as sensing signals is a good example.
[0054] Machine learning, especially deep learning technology, further promotes the potential of non-dedicated radio signals for radar sensing. With these technologies, traditional radar is moving towards more general wireless sensing. Wireless sensing here can broadly refer to retrieving information from received radio signals instead of communication data modulated into the signal at the transmitter. For wireless sensing related to sensing the location of the target, the target signal reflection delay, angle of arrival (AoA), angle of departure (AoD), Doppler and other dynamic parameters can be estimated through common signal processing methods; for sensing the physical characteristics of the target, it can be achieved by measuring the inherent pattern signals of the device, object, and living things. The two sensing methods can be called perception parameter estimation and pattern recognition respectively. In this sense, wireless sensing refers to more general sensing technologies and applications using radio signals.
[0055] Integrated Sensing and Communication (ISAC) has the potential to integrate wireless sensing into large-scale mobile networks, becoming a perceptive mobile network.
[0056] Perceptual Mobile Networks (PMNs) can evolve from the current 5G mobile networks and are expected to become a ubiquitous wireless sensor network while providing stable and high-quality mobile communication services. It can be built on top of the existing mobile network infrastructure without major changes to the network structure and equipment. It will unleash the maximum capacity of mobile networks and avoid the high infrastructure costs of building new wide-area wireless sensor networks separately. With the expansion of coverage, the integrated communication and sensing capabilities are expected to enable many new applications. Perceptual mobile networks are able to provide both communication and wireless sensing services and have the potential to become a ubiquitous wireless sensing solution due to their large broadband coverage and strong infrastructure. Their jointly coordinated communication and sensing capabilities will improve the productivity of our society and help to spawn a large number of new applications that cannot be effectively implemented by existing sensor networks. Some early work on passive sensing using mobile signals has demonstrated its potential. For example, traffic monitoring, weather forecasting, and rainfall remote sensing based on GSM radio signals. Perceptual mobile networks can be widely used for communication and sensing in the fields of transportation, communication, energy, precision agriculture, and security, where existing solutions are either not feasible or inefficient. It can also provide complementary sensing capabilities to existing sensor networks, with unique day and night operation capabilities and the ability to penetrate fog, foliage and even solid objects.
[0057] 2. Architecture of Open Data Capabilities of Synaesthesia Business
[0058] like Figure 2 As shown, in this architecture, SF is a new network element for synaesthesia service, which is responsible for managing and controlling synaesthesia service and processing synaesthesia data. SF can be a network element, that is, it is responsible for both the user plane and the control plane; it can also be two network elements, that is, the user plane and the control plane are separated, for example, the control plane is the sensing function control plane device (Sensing Function Control plane, SF-C), and the user plane is the sensing function user plane device (Sensing Function User plane, SF-U). Exemplarily, the sensing measurement (Sensing Measurement) includes delay, Doppler, angle, intensity, and their multi-dimensional combinations. The sensing result (Sensing Result) is the result obtained after SF processes the Sensing Measurement, such as intermediate processing results such as speed, distance, direction, acceleration, position, trajectory, and action. The sensing target (SensingObjective) is the final result obtained by the application function (Application Function, AF), for example, car violations, road congestion, etc.
[0059] The control plane is responsible for receiving and processing the related signaling of the perception service, and realizing the corresponding selection and control of the perception service equipment, mode selection, processing method, etc. The user plane is responsible for receiving and processing the related perception service data, and generating the corresponding processing results.
[0060] The capability opening method of the perception service provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.
[0061] like Figure 3 As shown, a capability opening method of a perception service in an embodiment of the present application includes:
[0062] Step 301: A first device sends a first message to a second device, where the first message includes awareness service capability exposure information of the first device.
[0063] Through this step, the first device informs the second device of its own perception service capability exposure information, so that the second device stores the information and can control the consumer device to access the first device, thereby achieving effective access and use of perception service data.
[0064] In one implementation, the first device includes SF, or other network elements with a sensing function; the second device includes NRF, NEF, UDM or AMF, or other network elements with an information storage function.
[0065] Taking the first device as SF and the second device as NRF as an example, SF sends a first message including the exposure information of the SF's perception service capability to NRF. The first message may be a network element registration message, a network element capability reporting and update message, etc.
[0066] Optionally, in this embodiment, the sensing service capability exposure information includes at least one of the following:
[0067] The first information is used to indicate the open scope of the sensing service;
[0068] The second information is used to indicate the usage scope of the sensing service;
[0069] The third information is used to indicate the purpose of using the perception service.
[0070] The open scope of the sensing service is the information of the devices (objects) that the sensing service data of the first device allows to be open. The information of the devices (objects) that the sensing service data of the first device allows to be open includes the information of the third device.
[0071] Optionally, the first information or the information of the third device includes at least one of the following:
[0072] identification information of the third device;
[0073] Consumer type or device type information to which the third device belongs;
[0074] Manufacturer information of the third device;
[0075] Token information of the third device;
[0076] Public Land Mobile Network (PLMN) information of the third device;
[0077] Slice information corresponding to the third device;
[0078] The data network name (Data Network Name, DNN) corresponding to the third device;
[0079] The third device refers to a device to which the perception service data of the first device is allowed to be opened.
[0080] Here, the identification information of the third device is used to indicate that the perceived service data of the first device is allowed to be opened to the device (object) corresponding to the identification information. The consumer type or device type information to which the third device belongs is used to indicate that the perceived service data of the first device is allowed to be opened to the device (object) corresponding to the consumer type or device type. The vendor (Vendor) information of the third device is used to indicate that the perceived service data of the first device is allowed to be opened to the device (object) from the vendor. The token information of the third device is used to indicate that the perceived service data of the first device is allowed to be opened to the device (object) holding the token. The PLMN information of the third device is used to indicate that the perceived service data of the first device is allowed to be opened to the object in the PLMN. The slice information corresponding to the third device is used to indicate that the perceived service data of the first device is allowed to be opened to the device (object) in the slice. The DNN corresponding to the third device is used to indicate that the perceived service data of the first device is allowed to be opened to the device (object) connected to the DNN.
[0081] In addition, the usage scope of the perception service is the scope in which the perception service data of the first device is used, including at least one of a time range and an area range. The time range can be a specific period of time, or a periodic time period. The area range can be an area indicated by a network area identifier (such as an area indicated by a tracking area identity (TAI) (s) or a cell ID (cell ID(s))), or it can be a geographical area representation, or other representations.
[0082] The purpose of use of the perception service is the purpose for which the perception service data of the first device is allowed to be used or the purpose for which it is prohibited to be used. For example, the purposes allowed to be used include: weather forecast, crowd flow forecast, drone intrusion detection, etc.; the purposes prohibited to be used include: monitoring a single human activity posture, user privacy detection, etc. Among them, the purpose of use can be expressed in the form of text or a string; or, it can be expressed in the form of digital symbols, and different digital symbols represent different purposes, for example, 0001 represents weather forecast, and 0010 represents human activity posture detection.
[0083] Optionally, in this embodiment, the perception service capability exposure information corresponds to at least one of the following information:
[0084] Identification information of the sensing service;
[0085] The fourth information is used to indicate the perception range of the perception service.
[0086] It can be understood that the first message also includes the identification information of the perception service and at least one of the fourth information.
[0087] In one implementation, the identification information of the sensing service refers to the type of sensing service that the first device can support. For different sensing services, the first device may have the same or different sensing service capability exposure information. The identification information of the sensing service may be represented in different ways such as sensing service type or sensing service ID.
[0088] In one implementation, the first device may send the awareness service capability opening information to the second device based on the granularity of the awareness service.
[0089] In one implementation, the sensing range of the sensing service refers to a range of the sensing service that can be provided by the first device.
[0090] Optionally, the perception scope of the perception service includes at least one of the following: a perception time scope; a perception area scope.
[0091] Among them, the perception time range refers to the time period or time point in which the first device can provide the perception service; the perception area range refers to the area in which the first device can provide the perception service, which area can be the service area of the first device, or a sub-area under the service area of the first device.
[0092] In one implementation, the awareness service capability exposure information in the first message corresponds to one or more awareness services that can be supported by the first device, or corresponds to one or more awareness ranges of awareness services that can be provided by the first device.
[0093] Optionally, the first message further includes at least one of the following:
[0094] identification information of the sensing service;
[0095] The fourth information.
[0096] That is, when the first message includes the awareness service capability exposure information, it may also indicate the type or awareness range of the awareness service corresponding to the awareness service capability exposure information.
[0097] Optionally, the first message further includes at least one of the following:
[0098] identification information of the first device;
[0099] Network element type information of the first device, where the network element type information is used to indicate that the first device is a network element that supports a perception service control function;
[0100] The name of the service supported by the first device, where the service includes a perception capability exposure service.
[0101] In one implementation, the identification information of the first device may be in the form of a network element instance identifier, a fully qualified domain name (FQDN), an Internet Protocol (IP) address, or the like. The network element type information of the first device may be information indicating a sensing function type (SF type), that is, the network function (NF) type (type) in the first message is set to information indicating SF type, such as NFtype=SF type. The name of the service supported by the first device may be setting the supported service name (supported service name) in the first message to information indicating that the first device supports sensing management service, such as supported service name=sensing management, indicating that the first device supports sensing control service.
[0102] In one implementation, the second device stores the perception service capability opening information of the first device in the first message. Of course, the second device can store the perception service capability opening information of multiple different first devices. Therefore, when the fourth device (i.e., the consumer device) requests a device to open perception service data to, the second device determines the fifth device for the fourth device according to the stored perception service capability opening information, so that the fourth device can obtain the required perception service data.
[0103] In one implementation, the fifth device is the device registered / updated / stored in one or more first devices in the second device.
[0104] Optionally, in this embodiment, the method further includes:
[0105] The first device receives a second message sent by a fourth device, where the second message is used to request a sensing service;
[0106] The first device senses the service according to the second message, and sends the obtained sensed service data to the fourth device.
[0107] At this time, the first device is the fifth device determined by the second device for the fourth device. After receiving the second message from the fourth device, the first device senses the service and notifies the fourth device of the obtained sensed service data.
[0108] Optionally, the second message includes at least one of the following:
[0109] The type of the requested sensing service, such as a specific sensing service type (Specific sensing service type), is used to indicate the sensing service data corresponding to the request for the Specific sensing service type;
[0110] Identification information of the requested sensing service, such as a specific sensing service identifier (Specific sensing service ID), used to indicate the sensing service data corresponding to the request for the Specific sensing service ID;
[0111] The purpose of use of the requested perception service data is used to indicate the purpose of the fourth device requesting to obtain the perception service data;
[0112] The usage scope of the requested perception service data is used to indicate that the fourth device requests to obtain the usage scope of the perception service data;
[0113] The identification information of the fourth device is used to uniquely identify the fourth device;
[0114] The manufacturer information of the fourth device is used to indicate the manufacturer corresponding to the fourth device, or is provided by a certain manufacturer;
[0115] The token information of the fourth device is used to indicate information of a perception service calling token held by the fourth device, and the token information may be obtained from a service agreement between the fourth device and the operator network, or from an offline docking and debugging process between the first device and the fourth device in advance;
[0116] PLMN information of the fourth device, such as a PLMN ID, used to indicate the PLMN ID where the fourth device is located;
[0117] The slice information corresponding to the fourth device is used to indicate the slice in which the fourth device is located, such as single network slice selection assistance information (S-NSSAI), network slice instances (NSI) ID, etc.;
[0118] The DNN corresponding to the fourth device.
[0119] In this way, after receiving the second message, the first device can execute the corresponding perception service and feed back the required perception service data to the fourth device.
[0120] Optionally, the first information performs at least one of the following according to the second message: sensing mode selection, sensing device selection, sensing task signaling, sensing service data acquisition and collection. For example, the first device performs corresponding processing according to the Specific sensing service type, including but not limited to: selecting a specific sensing mode, selecting a specific sensing device, sensing task signaling, sensing service data acquisition and collection.
[0121] Optionally, the second message includes fifth information, where the fifth information corresponds to at least one of the following information in the first device:
[0122] Perceive how the business is being performed;
[0123] Perceive how business data is processed;
[0124] Perceive how business data is sent;
[0125] Perceive the format of business data.
[0126] Here, the execution method of the perception service includes limiting the service quality requirements, perception mode, measurement quantity, measurement method, etc. of the perception service; the processing method of the perception service data includes whether to perform security encryption / desensitization, encryption / desensitization method, etc.; the sending method of the perception service data includes limiting the sending of the perception service data in a container manner, and further, it can also be used to limit the feedback time, feedback conditions, number of feedbacks, and minimum / maximum data volume of a single feedback of the perception service data; the format of the perception service data includes limiting the format expression method of the perception service data (such as text, string, binary, etc.).
[0127] The fifth information may be obtained from the service agreement between the fourth device and the operator network; or obtained from the offline docking and debugging process between the fifth device and the fourth device in advance. The purpose of the fifth information is to negotiate and synchronize the above information between the fifth device and the consumer device, but the specific processing and implementation are transparent or imperceptible to other devices and are only known privately by both parties. For example, the second message includes the fifth information, and the fifth information is a token, a string, or a set of digital combinations.
[0128] Optionally, the sending method includes sending the perception service data in a container manner.
[0129] That is, the first device uses the corresponding container method to send the required perception service data to the fourth device according to the fifth information. The container method enables the sender and receiver to know the content of the perception service data, while other devices cannot parse the data content in the container, ensuring the security of the data. In addition, the container method does not require standardization of the method and format of sending and receiving data, and only the sender and receiver can negotiate privately, which is conducive to improving the efficiency of perception service data transmission.
[0130] Optionally, the container method includes at least one of the following:
[0131] Preset container mode;
[0132] The container mode corresponding to the value of the fifth information.
[0133] That is to say, if the container mode is a preset container mode, even if the value of the fifth information is different, the first device sends the perception service data corresponding to different fifth information through the same container mode; if the container mode is a container mode corresponding to the value of the fifth information, the first device will send the perception service data in different container modes for different values of the fifth information. For example, if the fifth information is the token information of the fourth device, the first device can send the perception service data corresponding to different tokens through the same container mode regardless of the value of the token; or, the first device can send the perception service data in different container modes for different values of the token.
[0134] Optionally, the first device senses the service according to the second message, and sends the obtained sensed service data to the fourth device, including:
[0135] The first device determines, according to the second message, whether the fourth device is allowed to be opened to corresponding perception service data;
[0136] In a case where the corresponding perception service data of the fourth device is allowed to be opened, the first device performs the perception service and sends the obtained perception service data to the fourth device.
[0137] That is to say, at this time, the first device is considered by the second device to be the fifth device that matches the fourth device, that is, the first device can open the perception service data to the fourth device. For example, the PLMN ID of the first device matches the PLMN ID of the device expected by the fourth device, the vendor information of the first device matches the vendor information of the device expected by the fourth device, the token information of the first device matches the token information of the device expected by the fourth device, the DNN corresponding to the first device matches the DNN corresponding to the device expected by the fourth device, the slice information corresponding to the first device matches the slice information corresponding to the device expected by the fourth device, the purpose of use of the perception service defined by the first device matches the purpose of use of the perception service data requested by the fourth device, or the scope of use of the perception service defined by the first device matches the scope of use of the perception service data requested by the fourth device.
[0138] Optionally, after receiving the second message (Specific sensing service type), the first device determines whether the corresponding sensing service data of the fourth device is allowed to be opened according to the information in the second message, and only when the corresponding sensing service data of the fourth device is allowed to be opened, the corresponding sensing service data (such as the sensing service data corresponding to the Specific sensing service type) is sent to the fourth device. In this way, the second judgment of the fourth device by the first device is conducive to more accurate access control.
[0139] Optionally, the fourth device sends a third message to the second device, the third message is used to request information of the fifth device, and the fifth device supports opening the perception service data to the fourth device; the second device can determine whether the fifth device exists according to the third message and the stored perception service capability opening information of the first device. That is, the second device will match the fifth device for the fourth device.
[0140] Optionally, when it is determined that the fifth device exists, the second device sends a fifth message to the fourth device, that is, relevant information of the fifth device, so that the fourth device can request the fifth device to perform a sensing service. However, when it is determined that the fifth device does not exist, the second device sends a fourth message to the fourth device, indicating that the fifth device does not exist or the reason why the fifth device does not exist.
[0141] In this embodiment, the fourth device refers to a consumer device that perceives the service, which may include an AF, a NF, a terminal, a base station, and the like.
[0142] Among them, if the second device is NRF, the fourth device can be AF, and when AF is a trusted service server, AF directly sends a third message to NRF, and the third message can be a network element query request message, such as Nnrf_NFDiscovery_Requestservice operation, and the third message can also be a network element status acquisition request message, such as nrf_NFManagement_NFStatusSubscribe.
[0143] If the second device is NRF, the fourth device can be AF, and when AF is a non-trusted third-party service server, NEF sends the third message to NRF instead of AF. Specifically, AF can send a perception network element query message (used to request to find SF instances corresponding to a specific perception service) or a perception service request message (directly used to request to obtain perception information for a specific perception service) to NEF; NEF sends a third message to NRF according to AF's request, and the third message is a network element query request message, such as Nnrf_NFDiscovery_Request service operation, or the third message is a network element discovery request message.
[0144] If the second device is an NRF and the fourth device is a terminal or a base station, the terminal or the base station may send a third message to the NRF via the AMF. If the second device is an AMF and the fourth device is a terminal or a base station, the terminal or the base station may send the third message directly to the AMF.
[0145] like Figure 4 As shown, a capability opening method of a perception service in an embodiment of the present application includes:
[0146] Step 401: A second device receives a first message sent by a first device, where the first message includes awareness service capability exposure information of the first device;
[0147] Step 402: The second device stores the awareness service capability exposure information of the first device.
[0148] That is, the second device receives the first message from the first device, and stores the perception service capability opening information of the first device, thereby preparing for the subsequent control of the consumer device accessing the first device, and realizing the effective access and use of the perception service data.
[0149] The second device can store the perception service capability exposure information of one or more different first devices.
[0150] Optionally, the perception service capability exposure information includes at least one of the following:
[0151] The first information is used to indicate the open scope of the sensing service;
[0152] The second information is used to indicate the usage scope of the sensing service;
[0153] The third information is used to indicate the purpose of using the perception service.
[0154] Optionally, the first information includes at least one of the following:
[0155] identification information of the third device;
[0156] Consumer type or device type information to which the third device belongs;
[0157] Manufacturer information of the third device;
[0158] Token information of the third device;
[0159] Public land mobile network PLMN information of the third device;
[0160] Slice information corresponding to the third device;
[0161] The data network name DNN corresponding to the third device;
[0162] The third device refers to a device to which the perception service data of the first device is allowed to be opened.
[0163] Optionally, in this embodiment, the method further includes:
[0164] The second device receives a third message sent by the fourth device, where the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device;
[0165] The second device determines whether the fifth device exists according to the third message and the stored awareness service capability opening information of the first device.
[0166] That is, the second device can match the fifth device for the third message of the fourth device. For example, the second device, such as the NRF, determines whether there are one or more SF entities, and the one or more SF entities can open the perception service data to the fourth device, such as the AF.
[0167] Optionally, the third message includes at least one of the following:
[0168] The type of the requested sensing service, such as a specific sensing service type, is used to instruct the fourth device to request to obtain the first device corresponding to the specific sensing service type;
[0169] Identification information of the requested sensing service, such as a specific sensing service ID, is used to instruct the fourth device to request to obtain the first device corresponding to the specific sensing service ID;
[0170] The purpose of use of the requested perception service data is used to indicate the purpose of the fourth device requesting to obtain the perception service data;
[0171] The usage scope of the requested perception service data is used to indicate that the fourth device requests to obtain the usage scope of the perception service data;
[0172] The identification information of the fourth device is used to uniquely identify the fourth device;
[0173] The manufacturer information of the fourth device is used to indicate the manufacturer corresponding to the fourth device, or is provided by a certain manufacturer;
[0174] The token information of the fourth device is used to indicate information of a perception service calling token held by the fourth device, and the token information may be obtained from a service agreement between the fourth device and the operator network, or from an offline docking and debugging process between the first device and the fourth device in advance;
[0175] PLMN information of the fourth device, such as a PLMN ID, used to indicate a PLMN ID where the fourth device is located;
[0176] The slice information corresponding to the fourth device is used to indicate the slice where the fourth device is located, such as S-NSSAI, NSIID, etc.;
[0177] The DNN corresponding to the fourth device.
[0178] Here, the third message includes relevant information of the fourth device.
[0179] Optionally, the third message includes at least one of the following:
[0180] The manufacturer information of the fifth device is used to indicate the manufacturer corresponding to the device expected by the fourth device, or is provided by a certain manufacturer;
[0181] The PLMN information of the fifth device, such as the PLMN ID, is used to indicate the PLMN ID of the device desired by the fourth device;
[0182] The slice information corresponding to the fifth device is used to indicate the slice where the device desired by the fourth device is located, such as S-NSSAI, NSI ID, etc.;
[0183] The DNN corresponding to the fifth device is used to indicate the DNN corresponding to the device expected by the fourth device;
[0184] The network element type information of the fifth device, the network element type information is used to indicate that the fifth device is a network element supporting the perception service control function, and is used to indicate that the device expected by the fourth device is a network element supporting the perception service control function, such as setting the NF type in the third message to SF type, such as NF type=SF type;
[0185] The identification information of the fifth device is used to uniquely identify the device desired by the fourth device.
[0186] That is, the third message includes the relevant information of the device expected by the fourth device. Of course, the third message may also include the token information of the device expected by the fourth device.
[0187] Optionally, the second device determines whether a fifth device exists according to the third message and the stored perception service capability exposure information of the first device, including:
[0188] Determining whether the perception service capability exposure information of the first device matches the target information of the fourth device;
[0189] In a case where the perception service capability exposure information of the first device matches the target information of the fourth device, determining that the fifth device exists;
[0190] In a case where the perception service capability exposure information of the first device does not match the target information of the fourth device, determining that the fifth device does not exist;
[0191] The target information includes at least one of the following:
[0192] Manufacturer information;
[0193] Token information;
[0194] The purpose of using the requested perception service data;
[0195] The usage scope of the requested perception service data.
[0196] Therefore, in the process of matching judgment, one or more of the following may be performed: judging whether the manufacturer information of the fourth device matches the perception service capability exposure information of the first device;
[0197] Determine whether the token information of the fourth device matches the perception service capability exposure information of the first device;
[0198] Determining whether the usage purpose of the requested perception service data matches the perception service capability exposure information of the first device;
[0199] Determine whether the usage scope of the requested perception service data matches the perception service capability exposure information of the first device. As an implementation mode, the target information may also include one or more of the following: identification information of the fourth device, PLMN information of the fourth device, slice information corresponding to the fourth device, PLMN information of the device expected by the fourth device, vendor information of the device expected by the fourth device, token information of the device expected by the fourth device, DNN corresponding to the device expected by the fourth device, and slice information corresponding to the device expected by the fourth device.
[0200] As an implementation mode, when the target information includes one of the above contents, if the perceived service capability exposure information of one or some of the first devices matches the information, it is determined that there is a fifth device, and this or these first devices are the fifth devices; if the perceived service capability exposure information of all the first devices does not match the information, it is determined that there is no fifth device. When the target information includes multiple items of the above contents, if the perceived service capability exposure information of one or some of the first devices matches the multiple items of information, it is determined that there is a fifth device, and this or these first devices are the fifth devices; if the perceived service capability exposure information of all the first devices does not match any of the multiple items of information, it is determined that there is no fifth device.
[0201] As an implementation manner, at least one of the following judgments is performed based on the third message and the stored perception service capability exposure information of the first device:
[0202] Determine whether the identification information of the fourth device matches the perception service capability exposure information of the first device;
[0203] Determine whether the PLMN information of the fourth device matches the perception service capability exposure information of the first device;
[0204] Determine whether the slice information corresponding to the fourth device matches the perception service capability exposure information of the first device;
[0205] Determine whether the DNN corresponding to the fourth device matches the perception service capability exposure information of the first device;
[0206] Determine whether the PLMN information of the device expected by the fourth device matches the perception service capability opening information of the first device;
[0207] Determine whether the vendor information of the device expected by the fourth device matches the perception service capability exposure information of the first device;
[0208] Determine whether the token information of the device expected by the fourth device matches the perception service capability exposure information of the first device;
[0209] Determine whether the DNN corresponding to the device expected by the fourth device matches the perception service capability exposure information of the first device;
[0210] Determine whether the slice information corresponding to the device expected by the fourth device matches the perception service capability exposure information of the first device.
[0211] Thus, after the above determination, the matched first device can be used as the fifth device.
[0212] For example, the second device NRF determines that a specific SF entity as a fifth device can open the perception data to the fourth device such as AF, which may include at least one of the following:
[0213] If the NRF determines that the identification information of the AF matches the open range information of the sensing service of a certain SF;
[0214] If the NRF determines that the vendor information of the AF matches the open scope information of the sensing service of a certain SF;
[0215] If the NRF determines that the token information of the AF matches the open scope information of the sensing service of a certain SF;
[0216] If the NRF determines that the PLMN ID of the AF matches the open scope information of the sensing service of a certain SF;
[0217] If the NRF determines that the DNN corresponding to the AF matches the open range information of the perception service of a certain SF;
[0218] If the NRF determines that the slice information corresponding to the AF matches the open range information of the sensing service of a certain SF;
[0219] If the NRF determines that the PLMN ID of the desired SF matches the open range information of the perception service of a certain SF,
[0220] If the NRF determines that the vendor information of the desired SF matches the open range information of the sensing service of a certain SF;
[0221] If the NRF determines that the token information of the desired SF matches the open scope information of the sensing service of a certain SF;
[0222] If the NRF determines that the DNN corresponding to the desired SF matches the open range information of the perception service of a certain SF;
[0223] If the NRF determines that the slice information corresponding to the desired SF matches the open range information of the sensing service of a certain SF;
[0224] If the NRF determines that the purpose of using the requested perception service data matches the usage scope of the perception service defined by a certain SF;
[0225] If the NRF determines that the usage scope of the requested perception service data matches the usage scope of the perception service defined by a certain SF.
[0226] Optionally, in this embodiment, the fifth device satisfies at least one of the following:
[0227] The manufacturer information of the fifth device matches the manufacturer information of the fourth device;
[0228] The token information of the device allowed to be opened by the sensing service data of the fifth device matches the token information of the fourth device;
[0229] The usage purpose of the perception service data of the fifth device matches the usage purpose of the perception service data requested by the fourth device;
[0230] The usage scope of the perception service data of the fifth device matches the usage scope of the perception service data requested by the fourth device.
[0231] Of course, the limitations of the target information are different, and the conditions satisfied by the fifth device are also different, which are not listed here one by one.
[0232] Optionally, in this embodiment, the perceived service capability opening information of the first device matches the target information of the fourth device, which can be understood as the perceived service capability opening information of the first device is consistent with the target information of the fourth device, or can be understood as the target information of the fourth device is within the coverage of the perceived service capability opening information of the first device. For example, the token information of the device allowed to be opened by the perceived service data of the first device matches the token information of the fourth device, that is, the token information of the device allowed to be opened by the perceived service data of the first device includes the token information of the fourth device; the manufacturer information of the first device matches the manufacturer information of the fourth device, that is, the manufacturer information of the first device is consistent with the manufacturer information of the fourth device.
[0233] Optionally, the embodiment further includes:
[0234] When it is determined that the fifth device does not exist, the second device sends a fourth message to the fourth device, where the fourth message includes at least one of the following:
[0235] Sixth information, used to indicate that the fifth device does not exist;
[0236] seventh information, used to indicate reason information that the fifth device does not exist;
[0237] Among them, the reason information includes at least one of the following: the fourth device does not belong to the device corresponding to the perception service capability opening information of the first device; the purpose of use of the requested perception service data is not allowed by the first device; the scope of use of the requested perception service data does not match the perception service capability opening information of the first device.
[0238] Here, the sixth information may indicate that no first device is found or does not exist that can open the perception service data to the fourth device; the seventh information may indicate the reason why no first device is found or does not exist that can open the perception service data to the fourth device, for example, the fourth device is not within the permitted scope (for example, the manufacturer of the fourth device is A, and the open scope of the perception services of all first devices does not include the manufacturer A); the purpose of use of the perception service data of the fourth device is not permitted (for example, the fourth device expects to use the perception service data for weather forecasting, and the use scope of the perception services of all first devices does not include weather forecasting); the use scope of the fourth device is not permitted (for example, the fourth device is in area A, and the open scope of the perception services of all first devices does not include area A), etc.
[0239] Optionally, the method further comprises:
[0240] In a case where it is determined that the fifth device exists, the second device sends a fifth message to the fourth device, where the fifth message includes at least one of the following:
[0241] The manufacturer information of the fifth device is used to indicate the manufacturer corresponding to the fifth device, or is provided by a certain manufacturer;
[0242] PLMN information of the fifth device, such as PLMN ID, used to indicate the PLMN ID where the fifth device is located;
[0243] The slice information corresponding to the fifth device is used to indicate the slice where the fifth device is located, such as S-NSSAI, NSIID, etc.;
[0244] The DNN corresponding to the fifth device;
[0245] The network element type information of the fifth device, the network element type information is used to indicate that the fifth device is a network element supporting the perception service control function, and is used to indicate that the fifth device is a network element supporting the perception service control function, such as setting the NF type in the fifth message to SF type, such as NF type=SF type;
[0246] The identification information of the fifth device is used to uniquely identify the fifth device;
[0247] The usage purpose of the perception service data of the fifth device is used to indicate the usage purpose of the perception service data of the fifth device;
[0248] The usage scope of the perception service data of the fifth device is used to indicate the usage scope of the perception service data of the fifth device;
[0249] The fifth device senses the service of the device.
[0250] That is, the second device informs the fourth device of relevant information of its matched fifth device, so that the fourth device can request the fifth device to perform a sensing service.
[0251] Among them, if the second device is NRF and the fourth device is AF, when AF is a trusted service server, NRF can directly send the fourth message or the fifth message to AF, such as a network element query response message; when AF is an untrusted third-party service server, NRF can first send the fourth message or the fifth message to NEF, such as a network element query response message, and then NEF sends the fourth message or the fifth message to AF, such as a network element query response message or a perception service response message.
[0252] like Figure 5 As shown, a capability opening method of a perception service in an embodiment of the present application includes:
[0253] Step 501: The fourth device sends a third message to the second device, where the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device.
[0254] That is, the fourth device will send the third message to the second device, so that the second device can respond to the consumer device accessing the first device for control, so as to achieve effective access and use of the perception service data.
[0255] In this embodiment, the fourth device refers to a consumer device that perceives the service, which may include an AF, a NF, a terminal, a base station, and the like.
[0256] Optionally, the third message includes at least one of the following:
[0257] The type of the requested sensing service, such as a specific sensing service type, is used to instruct the fourth device to request to obtain the first device corresponding to the specific sensing service type;
[0258] Identification information of the requested sensing service, such as a specific sensing service ID, is used to instruct the fourth device to request to obtain the first device corresponding to the specific sensing service ID;
[0259] The purpose of use of the requested perception service data is used to indicate the purpose of the fourth device requesting to obtain the perception service data;
[0260] The usage scope of the requested perception service data is used to indicate that the fourth device requests to obtain the usage scope of the perception service data;
[0261] The identification information of the fourth device is used to uniquely identify the fourth device;
[0262] The manufacturer information of the fourth device is used to indicate the manufacturer corresponding to the fourth device, or is provided by a certain manufacturer;
[0263] The token information of the fourth device is used to indicate information of a perception service calling token held by the fourth device, and the token information may be obtained from a service agreement between the fourth device and the operator network, or from an offline docking and debugging process between the first device and the fourth device in advance;
[0264] PLMN information of the fourth device, such as a PLMN ID, used to indicate a PLMN ID where the fourth device is located;
[0265] The slice information corresponding to the fourth device is used to indicate the slice where the fourth device is located, such as S-NSSAI, NSIID, etc.;
[0266] The DNN corresponding to the fourth device.
[0267] Optionally, the third message includes at least one of the following:
[0268] The manufacturer information of the fifth device is used to indicate the manufacturer corresponding to the device expected by the fourth device, or is provided by a certain manufacturer;
[0269] The PLMN information of the fifth device, such as the PLMN ID, is used to indicate the PLMN ID of the device desired by the fourth device;
[0270] The slice information corresponding to the fifth device is used to indicate the slice where the device desired by the fourth device is located, such as S-NSSAI, NSI ID, etc.;
[0271] The DNN corresponding to the fifth device is used to indicate the DNN corresponding to the device expected by the fourth device;
[0272] The network element type information of the fifth device, the network element type information is used to indicate that the fifth device is a network element supporting the perception service control function, the network element type information is used to indicate that the fifth device is a network element supporting the perception service control function, and is used to indicate that the device expected by the fourth device is a network element supporting the perception service control function, such as setting the NF type in the third message to SF type, such as NF type=SF type;
[0273] The identification information of the fifth device is used to uniquely identify the device desired by the fourth device.
[0274] Optionally, it also includes:
[0275] The fourth device receives a fourth message sent by the second device, where the fourth message includes at least one of the following:
[0276] Sixth information, used to indicate that the fifth device does not exist;
[0277] seventh information, used to indicate reason information that the fifth device does not exist;
[0278] Among them, the reason information includes at least one of the following: the fourth device does not belong to the device corresponding to the perception service capability opening information of the first device; the purpose of use of the requested perception service data is not allowed by the first device; the scope of use of the requested perception service data does not match the perception service capability opening information of the first device.
[0279] Here, the fourth message sent by the second device is sent when the second device determines that the fifth device does not exist.
[0280] The sixth information may indicate that no first device is found or does not exist that can open the perception service data to the fourth device; the seventh information may indicate the reason why no first device is found or does not exist that can open the perception service data to the fourth device, for example, the fourth device is not within the permitted scope (for example, the manufacturer of the fourth device is A, and the open scope of the perception services of all first devices does not include the manufacturer A); the purpose of use of the perception service data of the fourth device is not permitted (for example, the fourth device expects to use the perception service data for weather forecasting, and the use scope of the perception services of all first devices does not include weather forecasting); the use scope of the fourth device is not permitted (for example, the fourth device is in area A, and the open scope of the perception services of all first devices does not include area A), etc.
[0281] Optionally, it also includes:
[0282] The fourth device receives a fifth message sent by the second device, where the fifth message includes at least one of the following:
[0283] The manufacturer information of the fifth device is used to indicate the manufacturer corresponding to the fifth device, or is provided by a certain manufacturer;
[0284] PLMN information of the fifth device, such as PLMN ID, used to indicate the PLMN ID where the fifth device is located;
[0285] The slice information corresponding to the fifth device is used to indicate the slice where the fifth device is located, such as S-NSSAI, NSIID, etc.;
[0286] The DNN corresponding to the fifth device;
[0287] The network element type information of the fifth device, the network element type information is used to indicate that the fifth device is a network element supporting the perception service control function, and is used to indicate that the fifth device is a network element supporting the perception service control function, such as setting the NF type in the fifth message to SF type, such as NF type=SF type;
[0288] The identification information of the fifth device is used to uniquely identify the fifth device;
[0289] The usage purpose of the perception service data of the fifth device is used to indicate the usage purpose of the perception service data of the fifth device;
[0290] The usage scope of the perception service data of the fifth device is used to indicate the usage scope of the perception service data of the fifth device;
[0291] The fifth device senses the service of the device.
[0292] That is, the fourth device receives the relevant information of the fifth device matched by the second device, so that the fourth device can request the fifth device to perform the perception service.
[0293] Optionally, it also includes:
[0294] The fourth device sends a second message to the fifth device, where the second message is used to request a sensing service;
[0295] The fourth device receives the perception service data sent by the fifth device.
[0296] It should be noted that the fourth device can send the second message and the third message in any order, and can send the second message first and then the third message, or can send the third message first and then the second message, or can send them simultaneously. That is, the fourth device does not necessarily need to query the fifth device before requesting to execute the perception service.
[0297] Optionally, the second message includes at least one of the following:
[0298] The type of sensing service requested;
[0299] Identification information of the requested sensing service;
[0300] The purpose of using the requested perception service data;
[0301] The usage scope of the requested perception service data;
[0302] identification information of the fourth device;
[0303] Manufacturer information of the fourth device;
[0304] Token information of the fourth device;
[0305] PLMN information of the fourth device;
[0306] Slice information corresponding to the fourth device;
[0307] The DNN corresponding to the fourth device.
[0308] Optionally, the second message includes fifth information, where the fifth information corresponds to at least one of the following information in the first device:
[0309] Perceive how the business is being performed;
[0310] Perceive how business data is processed;
[0311] Perceive how business data is sent;
[0312] Perceive the format of business data.
[0313] Optionally, the sending method includes sending the perception service data in a container manner.
[0314] Optionally, the container method includes at least one of the following:
[0315] Preset container mode;
[0316] The container mode corresponding to the value of the fifth information.
[0317] The following describes the application of the method in the embodiment of the present application in combination with specific scenarios:
[0318] Scenario 1: Take the first device as SF and the second device as NRF or UDM as an example. Figure 6 As shown, the method includes:
[0319] Step 1: SF sends a first message (such as a network element registration / update message) to NRF or UDM. The first message includes its own identification information (such as SF ID), identification information of the sensing service (sensing service ID) and sensing service capability exposure information, such as: first information (such as sensing result exposure information (such as consumer IDs or consumer vendor list)), second information (such as usage time or area), and third information (such as usage purpose).
[0320] Step 2: NRF or UDM saves the information reported by SF through the first message.
[0321] In step 3a, AF sends a third message to NRF to find the SF network element entity corresponding to the sensing service. When AF is a trusted service server, AF directly sends the third message to NRF, which is not shown in the figure. When AF is an untrusted third-party service server, NEF sends the third message to NRF instead of AF. Specifically, in step 3a1, AF sends a sensing service request message to NEF; in step 3a2, NEF sends a network element discovery request message to NRF or UDM, including sensing service ID, AF ID / venderID. After receiving the sensing service request message, NEF performs Sensing service ID mapping and service requirement translation.
[0322] Step 3b, AMF or NF sends a third message (such as a network element discovery request message) to NRF to find the SF network element entity corresponding to the perception service. Of course, UE or base station is a consumer device, and sends the third message to NRF via AMF; or, NF is a consumer device.
[0323] Step 4, NRF or UDM determines whether AF (or NF) is in the perception result open whitelist. Here, the perception result open whitelist is obtained based on the first message of all SFs. Taking NRF as an example, NRF determines whether there are one or more SF entities that can open perception data to the AF. Specifically, NRF determines whether there are one or more SF entities that can open perception data to the AF based on the saved perception service capability opening information. If the perception service capability opening information of one or more SFs matches the AF information contained in the network element query message and the expected SF information, the NRF determines that the one or more SF entities can open perception data to the AF. Otherwise, NRF determines that no SF entity can open perception data to the AF.
[0324] Corresponding to steps 3a1 and 3a2, in step 5a, the NRF or UDM sends a fourth message or a fifth message to the AF, such as a network element discovery response message. Among them, it is determined that one or more SF entities can open perception data to the AF, and the network element discovery response message includes usage time / area scope, usage purpose; conversely, the network element discovery response message includes the seventh information (cause codes). Afterwards, step 6a, the perception service process, the AF requests the matching SF to perform the perception service and obtain the required perception service data. If the AF obtains the information of one or more SF entities, the AF can initiate a perception service process to one of the SFs (send a second message), or the AF selects an SF according to its own business logic to initiate the actual perception service process (send a second message).
[0325] Corresponding to step 3b, step 5b, NRF or UDM sends a fourth message or a fifth message to NF (or AMF), such as a network element discovery response message. Among them, it is determined that one or more SF entities can open perception data to the NF (or AMF), and the network element discovery response message includes usage time / area scope, usage purpose; conversely, the network element discovery response message includes the seventh information (cause codes). Afterwards, step 6b, the perception service process, the NF (or AMF) requests the matching SF to perform the perception service and obtain the required perception service data.
[0326] Scenario 2: Take the first device as SF and the second device as NRF as an example. Figure 7 As shown, the method includes:
[0327] Steps 1 to 5 in this scenario are the same as steps 1 to 5 in scenario 1. The difference is that, in the perception service process, the second message sent by the consumer device includes fifth information, such as the consumer device token information.
[0328] For the third message sent by AF to NRF:
[0329] In step 6a1, AF (non-trusted third-party service server) sends a second message, such as a sensing service request message (Sensing request), to the selected SF through NEF to trigger the sensing service process. The Sensing request includes the AF token. The AF token may be obtained from the service agreement between AF and the operator network; or obtained from the offline docking and debugging process between SF and AF in advance. The purpose of the second token information is to negotiate between SF and consumer devices the processing method for synchronizing the above-mentioned sensing services and sensing data, but the specific processing and implementation are transparent or imperceptible to other devices and are only known privately by both parties.
[0330] In step 6a2, the SF obtains the perception service data according to the token of the AF, the execution mode of the corresponding perception service, the processing mode of the perception service data, the sending mode of the perception service data, and the format of the perception service data.
[0331] Step 6a3: SF sends a fourth message or a fifth message to AF, such as a sensing service response (Sensing result). The Sensing result includes a token and a container (sensing service data) of AF.
[0332] For AMF or NF sending the third message to NRF, step 6b of perceiving the business process is similar to step 6a and will not be repeated here.
[0333] In summary, in the method of the embodiment of the present application, the first device reports its own perception service capability exposure information to a unified second device, namely, an information storage and management network element, which obtains the scope, usage scope and purpose of the first device's perception service capability exposure based on the perception service capability exposure information, and the second device controls the access of the consumer device to the first device according to this information, thereby realizing effective limited authority management and access control.
[0334] It should be noted that the capability opening methods of the perception services executed by the first device, the second device, and the fourth device are implemented in coordination, and the implementation methods of the above method embodiments are applicable to each other and will not be described one by one.
[0335] The capability opening method of the perception service provided in the embodiment of the present application can be executed by a capability opening device of the perception service. The capability opening method of the perception service performed by the capability opening device of the perception service is taken as an example to illustrate the capability opening device of the perception service provided in the embodiment of the present application.
[0336] like Figure 8 As shown, a capability opening device for sensing services in an embodiment of the present application includes:
[0337] The first sending module 810 is configured to send a first message to a second device, where the first message includes the perception service capability opening information of the first device.
[0338] Optionally, the perception service capability exposure information includes at least one of the following:
[0339] The first information is used to indicate the open scope of the sensing service;
[0340] The second information is used to indicate the usage scope of the sensing service;
[0341] The third information is used to indicate the purpose of using the perception service.
[0342] Optionally, the first information includes at least one of the following:
[0343] identification information of the third device;
[0344] Consumer type or device type information to which the third device belongs;
[0345] Manufacturer information of the third device;
[0346] Token information of the third device;
[0347] Public land mobile network PLMN information of the third device;
[0348] Slice information corresponding to the third device;
[0349] The data network name DNN corresponding to the third device;
[0350] The third device refers to a device to which the perception service data of the first device is allowed to be opened.
[0351] Optionally, the first message further includes at least one of the following:
[0352] identification information of the first device;
[0353] Network element type information of the first device, where the network element type information is used to indicate that the first device is a network element that supports a perception service control function;
[0354] The name of the service supported by the first device, where the service includes a perception capability exposure service.
[0355] Optionally, the perception service capability exposure information corresponds to at least one of the following information:
[0356] Identification information of the sensing service;
[0357] The fourth information is used to indicate the perception range of the perception service.
[0358] Optionally, the first message further includes at least one of the following:
[0359] identification information of the sensing service;
[0360] The fourth information.
[0361] Optionally, the perception scope of the perception service includes at least one of the following: a perception time scope; a perception area scope.
[0362] Optionally, the device further comprises:
[0363] A second receiving module, used to receive a second message sent by a fourth device, where the second message is used to request a sensing service;
[0364] The first processing module is used to sense the service according to the second message and send the obtained sensed service data to the fourth device.
[0365] Optionally, the second message includes at least one of the following:
[0366] The type of sensing service requested;
[0367] Identification information of the requested sensing service;
[0368] The purpose of using the requested perception service data;
[0369] The usage scope of the requested perception service data;
[0370] identification information of the fourth device;
[0371] Manufacturer information of the fourth device;
[0372] Token information of the fourth device;
[0373] PLMN information of the fourth device;
[0374] Slice information corresponding to the fourth device;
[0375] The DNN corresponding to the fourth device.
[0376] Optionally, the second message includes fifth information, where the fifth information corresponds to at least one of the following information in the first device:
[0377] Perceive how the business is being performed;
[0378] Perceive how business data is processed;
[0379] Perceive how business data is sent;
[0380] Perceive the format of business data.
[0381] Optionally, the sending method includes sending the perception service data in a container manner.
[0382] Optionally, the container method includes at least one of the following:
[0383] Preset container mode;
[0384] The container mode corresponding to the value of the fifth information.
[0385] Optionally, the first processing module is further used for:
[0386] Determine, according to the second message, whether the fourth device is allowed to be opened to corresponding perception service data;
[0387] In the case that the corresponding perception service data is allowed to be opened to the fourth device, the perception service is performed, and the obtained perception service data is sent to the fourth device.
[0388] The device informs the second device of its own perception service capability opening information, so that the second device stores the information, and can control the access of the consumer device to the first device, so as to realize the effective access and use of the perception service data.
[0389] It should be noted that the device applies the capability opening method of the perception service executed by the first device, and the implementation method of the above method embodiment is applicable to the device and can achieve the same technical effect.
[0390] like Fig. 9 As shown, a capability opening device for sensing services in an embodiment of the present application includes:
[0391] A first receiving module 910 is configured to receive a first message sent by a first device, where the first message includes perception service capability exposure information of the first device;
[0392] The storage module 920 is used to store the awareness service capability exposure information of the first device.
[0393] Optionally, the perception service capability exposure information includes at least one of the following:
[0394] The first information is used to indicate the open scope of the sensing service;
[0395] The second information is used to indicate the usage scope of the sensing service;
[0396] The third information is used to indicate the purpose of using the perception service.
[0397] Optionally, the first information includes at least one of the following:
[0398] identification information of the third device;
[0399] Consumer type or device type information to which the third device belongs;
[0400] Manufacturer information of the third device;
[0401] Token information of the third device;
[0402] Public land mobile network PLMN information of the third device;
[0403] Slice information corresponding to the third device;
[0404] The data network name DNN corresponding to the third device;
[0405] The third device refers to a device to which the perception service data of the first device is allowed to be opened.
[0406] Optionally, the device further comprises:
[0407] A third receiving module, configured to receive a third message sent by a fourth device, wherein the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device;
[0408] The second processing module is used to determine whether the fifth device exists according to the third message and the stored perception service capability exposure information of the first device.
[0409] Optionally, the third message includes at least one of the following:
[0410] The type of sensing service requested;
[0411] Identification information of the requested sensing service;
[0412] The purpose of using the requested perception service data;
[0413] The usage scope of the requested perception service data;
[0414] identification information of the fourth device;
[0415] Manufacturer information of the fourth device;
[0416] Token information of the fourth device;
[0417] PLMN information of the fourth device;
[0418] Slice information corresponding to the fourth device;
[0419] The DNN corresponding to the fourth device.
[0420] Optionally, the third message includes at least one of the following:
[0421] Manufacturer information of the fifth device;
[0422] PLMN information of the fifth device;
[0423] Slice information corresponding to the fifth device;
[0424] The DNN corresponding to the fifth device;
[0425] Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function;
[0426] The identification information of the fifth device.
[0427] Optionally, the second processing module is further used to determine whether the perception service capability exposure information of the first device matches the target information of the fourth device;
[0428] In a case where the perception service capability exposure information of the first device matches the target information of the fourth device, determining that the fifth device exists;
[0429] In a case where the perception service capability exposure information of the first device does not match the target information of the fourth device, determining that the fifth device does not exist;
[0430] The target information includes at least one of the following:
[0431] Manufacturer information;
[0432] Token information;
[0433] The purpose of using the requested perception service data;
[0434] The usage scope of the requested perception service data.
[0435] Optionally, the fifth device satisfies at least one of the following:
[0436] The manufacturer information of the fifth device matches the manufacturer information of the fourth device;
[0437] The token information of the device allowed to be opened by the sensing service data of the fifth device matches the token information of the fourth device;
[0438] The usage purpose of the perception service data of the fifth device matches the usage purpose of the perception service data requested by the fourth device;
[0439] The usage scope of the perception service data of the fifth device matches the usage scope of the perception service data requested by the fourth device.
[0440] Optionally, the device further comprises:
[0441] A third sending module is configured to send a fourth message to the fourth device when it is determined that the fifth device does not exist, where the fourth message includes at least one of the following:
[0442] Sixth information, used to indicate that the fifth device does not exist;
[0443] seventh information, used to indicate reason information that the fifth device does not exist;
[0444] Among them, the reason information includes at least one of the following: the fourth device does not belong to the device corresponding to the perception service capability opening information of the first device; the purpose of use of the requested perception service data is not allowed by the first device; the scope of use of the requested perception service data does not match the perception service capability opening information of the first device.
[0445] Optionally, the device further comprises:
[0446] A fourth sending module is configured to send a fifth message to the fourth device when it is determined that the fifth device exists, where the fifth message includes at least one of the following:
[0447] Manufacturer information of the fifth device;
[0448] PLMN information of the fifth device;
[0449] Slice information corresponding to the fifth device;
[0450] The DNN corresponding to the fifth device;
[0451] Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function;
[0452] identification information of the fifth device;
[0453] Purpose of using the sensing service data of the fifth device;
[0454] A usage scope of the sensing service data of the fifth device;
[0455] The fifth device senses the service of the device.
[0456] The device receives a first message from a first device, and stores the perception service capability opening information of the first device, thereby preparing for the subsequent control of the access of the consumer device to the first device, and realizing effective access and use of the perception service data.
[0457] It should be noted that the device applies the capability opening method of the perception service executed by the second device, and the implementation method of the above method embodiment is applicable to the device and can achieve the same technical effect.
[0458] like Fig.10 As shown, a capability opening device for sensing services in an embodiment of the present application includes:
[0459] The second sending module 1010 is used to send a third message to the second device, where the third message is used to request information of a fifth device, and the fifth device supports opening the perception service data to the fourth device.
[0460] Optionally, the third message includes at least one of the following:
[0461] The type of sensing service requested;
[0462] Identification information of the requested sensing service;
[0463] The purpose of using the requested perception service data;
[0464] The usage scope of the requested perception service data;
[0465] identification information of the fourth device;
[0466] Manufacturer information of the fourth device;
[0467] Token information of the fourth device;
[0468] PLMN information of the fourth device;
[0469] Slice information corresponding to the fourth device;
[0470] The DNN corresponding to the fourth device.
[0471] Optionally, the third message includes at least one of the following:
[0472] Manufacturer information of the fifth device;
[0473] PLMN information of the fifth device;
[0474] Slice information corresponding to the fifth device;
[0475] The DNN corresponding to the fifth device;
[0476] Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function;
[0477] The identification information of the fifth device.
[0478] Optionally, the device further comprises:
[0479] A fourth receiving module is configured to receive a fourth message sent by the second device, where the fourth message includes at least one of the following:
[0480] Sixth information, used to indicate that the fifth device does not exist;
[0481] seventh information, used to indicate reason information that the fifth device does not exist;
[0482] Among them, the reason information includes at least one of the following: the fourth device does not belong to the device corresponding to the perception service capability opening information of the first device; the purpose of use of the requested perception service data is not allowed by the first device; the scope of use of the requested perception service data does not match the perception service capability opening information of the first device.
[0483] Optionally, the device further comprises:
[0484] A fifth receiving module is configured to receive a fifth message sent by the second device, where the fifth message includes at least one of the following:
[0485] Manufacturer information of the fifth device;
[0486] PLMN information of the fifth device;
[0487] Slice information corresponding to the fifth device;
[0488] The DNN corresponding to the fifth device;
[0489] Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function;
[0490] identification information of the fifth device;
[0491] Purpose of using the sensing service data of the fifth device;
[0492] A usage scope of the sensing service data of the fifth device;
[0493] The fifth device senses the service of the device.
[0494] Optionally, the device further comprises:
[0495] A fifth sending module, configured to send a second message to the fifth device, where the second message is used to request a perception service;
[0496] The sixth receiving module is used to receive the perception service data sent by the fifth device.
[0497] Optionally, the second message includes at least one of the following:
[0498] The type of sensing service requested;
[0499] Identification information of the requested sensing service;
[0500] The purpose of using the requested perception service data;
[0501] The usage scope of the requested perception service data;
[0502] identification information of the fourth device;
[0503] Manufacturer information of the fourth device;
[0504] Token information of the fourth device;
[0505] PLMN information of the fourth device;
[0506] Slice information corresponding to the fourth device;
[0507] The DNN corresponding to the fourth device.
[0508] Optionally, the second message includes fifth information, where the fifth information corresponds to at least one of the following information in the first device:
[0509] Perceive how the business is being performed;
[0510] Perceive how business data is processed;
[0511] Perceive how business data is sent;
[0512] Perceive the format of business data.
[0513] Optionally, the sending method includes sending the perception service data in a container manner.
[0514] Optionally, the container method includes at least one of the following:
[0515] Preset container mode;
[0516] The container mode corresponding to the value of the fifth information.
[0517] The apparatus will send a third message to the second device, so that the second device can respond to the consumer device accessing the first device for control, thereby realizing that the perception service data is effectively accessed and used.
[0518] It should be noted that the device applies the capability opening method of the perception service executed by the fourth device, and the implementation method of the above method embodiment is applicable to the device and can achieve the same technical effect.
[0519] The capability opening device for sensing services in the embodiment of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal, or may be a device other than a terminal. Exemplarily, the terminal may include but is not limited to the types of terminals 11 listed above, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.
[0520] The capability opening device of the perception service provided in the embodiment of the present application can realize Figures 3 to 5 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.
[0521] like Fig.11 As shown, the embodiment of the present application further provides a communication device 1100, including a processor 1101 and a memory 1102, and the memory 1102 stores a program or instruction that can be run on the processor 1101. For example, when the communication device 1100 is a terminal, the program or instruction is executed by the processor 1101 to implement the various steps of the above-mentioned perception service capability opening method embodiment, and can achieve the same technical effect. When the communication device 1100 is a network side device, the program or instruction is executed by the processor 1101 to implement the various steps of the above-mentioned perception service capability opening method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0522] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 5 The steps in the method embodiment shown. This terminal embodiment corresponds to the fourth device side method embodiment described above, and each implementation process and implementation method of the above method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Fig.12 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
[0523] The terminal 1200 includes but is not limited to: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209 and at least some of the components of the processor 1210.
[0524] Those skilled in the art will appreciate that the terminal 1200 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1210 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.12 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0525] It should be understood that in the embodiment of the present application, the input unit 1204 may include a graphics processing unit (GPU) 12041 and a microphone 12042, and the graphics processor 12041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1206 may include a display panel 12061, and the display panel 12061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1207 includes a touch panel 12071 and at least one of other input devices 12072. The touch panel 12071 is also called a touch screen. The touch panel 12071 may include two parts: a touch detection device and a touch controller. Other input devices 12072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
[0526] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 1201 can transmit the data to the processor 1210 for processing; in addition, the RF unit 1201 can send uplink data to the network side device. Generally, the RF unit 1201 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0527] The memory 1209 can be used to store software programs or instructions and various data. The memory 1209 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1209 may include a volatile memory or a non-volatile memory 12. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 1209 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.
[0528] The processor 1210 may include one or more processing units; optionally, the processor 1210 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1210.
[0529] The radio frequency unit 1201 is used to send a third message to the second device, where the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device.
[0530] Optionally, the third message includes at least one of the following:
[0531] The type of sensing service requested;
[0532] Identification information of the requested sensing service;
[0533] The purpose of using the requested perception service data;
[0534] The usage scope of the requested perception service data;
[0535] identification information of the fourth device;
[0536] Manufacturer information of the fourth device;
[0537] Token information of the fourth device;
[0538] PLMN information of the fourth device;
[0539] Slice information corresponding to the fourth device;
[0540] The DNN corresponding to the fourth device.
[0541] Optionally, the third message includes at least one of the following:
[0542] Manufacturer information of the fifth device;
[0543] PLMN information of the fifth device;
[0544] Slice information corresponding to the fifth device;
[0545] The DNN corresponding to the fifth device;
[0546] Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function;
[0547] The identification information of the fifth device.
[0548] Optionally, the radio frequency unit is further used for:
[0549] receiving a fourth message sent by the second device, where the fourth message includes at least one of the following:
[0550] Sixth information, used to indicate that the fifth device does not exist;
[0551] seventh information, used to indicate reason information that the fifth device does not exist;
[0552] Among them, the reason information includes at least one of the following: the fourth device does not belong to the device corresponding to the perception service capability opening information of the first device; the purpose of use of the requested perception service data is not allowed by the first device; the scope of use of the requested perception service data does not match the perception service capability opening information of the first device.
[0553] Optionally, the radio frequency unit is further used for:
[0554] receiving a fifth message sent by the second device, where the fifth message includes at least one of the following:
[0555] Manufacturer information of the fifth device;
[0556] PLMN information of the fifth device;
[0557] Slice information corresponding to the fifth device;
[0558] The DNN corresponding to the fifth device;
[0559] Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function;
[0560] identification information of the fifth device;
[0561] Purpose of using the sensing service data of the fifth device;
[0562] A usage scope of the sensing service data of the fifth device;
[0563] The fifth device senses the service of the device.
[0564] Optionally, the radio frequency unit is further used for:
[0565] Sending a second message to the fifth device, where the second message is used to request a perception service;
[0566] Receive the perception service data sent by the fifth device.
[0567] Optionally, the second message includes at least one of the following:
[0568] The type of sensing service requested;
[0569] Identification information of the requested sensing service;
[0570] The purpose of using the requested perception service data;
[0571] The usage scope of the requested perception service data;
[0572] identification information of the fourth device;
[0573] Manufacturer information of the fourth device;
[0574] Token information of the fourth device;
[0575] PLMN information of the fourth device;
[0576] Slice information corresponding to the fourth device;
[0577] The DNN corresponding to the fourth device.
[0578] Optionally, the second message includes fifth information, where the fifth information corresponds to at least one of the following information in the first device:
[0579] Perceive how the business is being performed;
[0580] Perceive how business data is processed;
[0581] Perceive how business data is sent;
[0582] Perceive the format of business data.
[0583] Optionally, the sending method includes sending the perception service data in a container manner.
[0584] Optionally, the container method includes at least one of the following:
[0585] Preset container mode;
[0586] The container mode corresponding to the value of the fifth information.
[0587] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.
[0588] The embodiment of the present application also provides a network side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 3 or Figure 4 or Figure 5 The steps of the method embodiment shown. This network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation mode of the above method embodiment can be applied to this network side device embodiment and can achieve the same technical effect.
[0589] Specifically, the embodiment of the present application also provides a network side device. Fig.13 As shown, the network side device 1300 includes: an antenna 131, a radio frequency device 132, a baseband device 133, a processor 134 and a memory 135. The antenna 131 is connected to the radio frequency device 132. In the uplink direction, the radio frequency device 132 receives information through the antenna 131 and sends the received information to the baseband device 133 for processing. In the downlink direction, the baseband device 133 processes the information to be sent and sends it to the radio frequency device 132. The radio frequency device 132 processes the received information and sends it out through the antenna 131.
[0590] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 133, which includes a baseband processor.
[0591] The baseband device 133 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.13 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 135 through a bus interface to call the program in the memory 135 to execute the network device operations shown in the above method embodiment.
[0592] The network side device may further include a network interface 136, which is, for example, a Common Public Radio Interface (CPRI).
[0593] Specifically, the network side device 1300 of the embodiment of the present application further includes: instructions or programs stored in the memory 135 and executable on the processor 134, and the processor 134 calls the instructions or programs in the memory 135 to execute. Fig.10 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0594] Specifically, the embodiment of the present application also provides a network side device. Fig.14 As shown, the network side device 1400 includes: a processor 1401, a network interface 1402 and a memory 1403. The network interface 1402 is, for example, a common public radio interface (CPRI).
[0595] Specifically, the network side device 1400 of the embodiment of the present application further includes: instructions or programs stored in the memory 1403 and executable on the processor 1401, and the processor 1401 calls the instructions or programs in the memory 1403 to execute Figure 8 or Fig. 9 or Fig.10 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0596] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned perception service capability opening method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
[0597] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.
[0598] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned perception service capability opening method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0599] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0600] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned service perception capability opening method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
[0601] An embodiment of the present application also provides a capability opening system for a perception service, including: a first device, a second device and a third device, wherein the first device can be used to execute the steps of the capability opening method for the perception service as performed by the first device above, the second device can be used to execute the steps of the capability opening method for the perception service as performed by the second device above, and the fourth device can be used to execute the steps of the capability opening method for the perception service as performed by the fourth device above.
[0602] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.
[0603] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.
[0604] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.
Claims
1. A method for opening the capability of a sensing service, characterized in that: include: The first device sends a first message to the second device, where the first message includes perception service capability exposure information of the first device.
2. The method according to claim 1, characterized in that The perception service capability exposure information includes at least one of the following: The first information is used to indicate the open scope of the sensing service; The second information is used to indicate the usage scope of the sensing service; The third information is used to indicate the purpose of using the perception service.
3. The method according to claim 2, characterized in that The first information includes at least one of the following: identification information of the third device; Consumer type or device type information to which the third device belongs; Manufacturer information of the third device; Token information of the third device; Public land mobile network PLMN information of the third device; Slice information corresponding to the third device; The data network name DNN corresponding to the third device; The third device refers to a device to which the perception service data of the first device is allowed to be opened.
4. The method according to any one of claims 1 to 3, characterized in that: The first message also includes at least one of the following: identification information of the first device; Network element type information of the first device, where the network element type information is used to indicate that the first device is a network element that supports a perception service control function; The name of the service supported by the first device, where the service includes a perception capability exposure service.
5. The method according to any one of claims 1 to 3, characterized in that: The perception service capability exposure information corresponds to at least one of the following information: Identification information of the sensing service; The fourth information is used to indicate the perception range of the perception service.
6. The method according to claim 5, characterized in that , the first message also includes at least one of the following: identification information of the sensing service; The fourth information.
7. The method according to claim 5 or 6, characterized in that ,The perception range of the perception service includes at least one of the following: perception time range; perception area range.
8. The method according to any one of claims 1 to 7, characterized in that: Also includes: The first device receives a second message sent by a fourth device, where the second message is used to request a sensing service; The first device senses the service according to the second message, and sends the obtained sensed service data to the fourth device.
9. The method according to claim 8, characterized in that The second message includes at least one of the following: The type of sensing service requested; Identification information of the requested sensing service; The purpose of using the requested perception service data; The usage scope of the requested perception service data; identification information of the fourth device; Manufacturer information of the fourth device; Token information of the fourth device; PLMN information of the fourth device; Slice information corresponding to the fourth device; The DNN corresponding to the fourth device.
10. The method according to claim 8 or 9, characterized in that: The second message includes fifth information, where the fifth information corresponds to at least one of the following information in the first device: Perceive how the business is being performed; Perceive how business data is processed; Perceive how business data is sent; Perceive the format of business data.
11. The method according to claim 10, characterized in that The sending method includes sending the perception service data in a container manner.
12. The method according to claim 11, characterized in that The container method includes at least one of the following: Preset container mode; The container mode corresponding to the value of the fifth information.
13. The method according to any one of claims 8 to 12, characterized in that: The first device senses the service according to the second message, and sends the obtained sensed service data to the fourth device, including: The first device determines, according to the second message, whether the fourth device is allowed to be opened to corresponding perception service data; In a case where the corresponding perception service data of the fourth device is allowed to be opened, the first device performs the perception service and sends the obtained perception service data to the fourth device.
14. A method for opening the capability of a sensing service, characterized in that: include: The second device receives a first message sent by the first device, where the first message includes the perception service capability opening information of the first device; The second device stores the perception service capability exposure information of the first device.
15. The method according to claim 14, characterized in that The perception service capability exposure information includes at least one of the following: The first information is used to indicate the open scope of the sensing service; The second information is used to indicate the usage scope of the sensing service; The third information is used to indicate the purpose of using the perception service.
16. The method according to claim 15, characterized in that The first information includes at least one of the following: identification information of the third device; Consumer type or device type information to which the third device belongs; Manufacturer information of the third device; Token information of the third device; Public land mobile network PLMN information of the third device; Slice information corresponding to the third device; The data network name DNN corresponding to the third device; The third device refers to a device to which the perception service data of the first device is allowed to be opened.
17. The method according to any one of claims 14 to 16, characterized in that Also includes: The second device receives a third message sent by the fourth device, where the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device; The second device determines whether the fifth device exists according to the third message and the stored awareness service capability opening information of the first device.
18. The method according to claim 17, characterized in that The third message includes at least one of the following: The type of sensing service requested; Identification information of the requested sensing service; The purpose of using the requested perception service data; The usage scope of the requested perception service data; identification information of the fourth device; Manufacturer information of the fourth device; Token information of the fourth device; PLMN information of the fourth device; Slice information corresponding to the fourth device; The DNN corresponding to the fourth device.
19. The method according to claim 17 or 18, characterized in that The third message includes at least one of the following: Manufacturer information of the fifth device; PLMN information of the fifth device; Slice information corresponding to the fifth device; The DNN corresponding to the fifth device; Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function; The identification information of the fifth device.
20. The method according to claim 18 or 19, characterized in that The second device determines whether a fifth device exists according to the third message and the stored perception service capability exposure information of the first device, including: Determining whether the perception service capability exposure information of the first device matches the target information of the fourth device; In a case where the perception service capability exposure information of the first device matches the target information of the fourth device, determining that the fifth device exists; In a case where the perception service capability exposure information of the first device does not match the target information of the fourth device, determining that the fifth device does not exist; The target information includes at least one of the following: Manufacturer information; Token information; The purpose of using the requested perception service data; The usage scope of the requested perception service data.
21. The method according to any one of claims 18 to 20, characterized in that The fifth device satisfies at least one of the following: The manufacturer information of the fifth device matches the manufacturer information of the fourth device; The token information of the device allowed to be opened by the sensing service data of the fifth device matches the token information of the fourth device; The usage purpose of the perception service data of the fifth device matches the usage purpose of the perception service data requested by the fourth device; The usage scope of the perception service data of the fifth device matches the usage scope of the perception service data requested by the fourth device.
22. The method according to any one of claims 17 to 21, characterized in that Also includes: When it is determined that the fifth device does not exist, the second device sends a fourth message to the fourth device, where the fourth message includes at least one of the following: Sixth information, used to indicate that the fifth device does not exist; seventh information, used to indicate reason information that the fifth device does not exist; Among them, the reason information includes at least one of the following: the fourth device does not belong to the device corresponding to the perception service capability opening information of the first device; the purpose of use of the requested perception service data is not allowed by the first device; the scope of use of the requested perception service data does not match the perception service capability opening information of the first device.
23. The method according to any one of claims 17 to 22, characterized in that Also includes: In a case where it is determined that the fifth device exists, the second device sends a fifth message to the fourth device, where the fifth message includes at least one of the following: Manufacturer information of the fifth device; PLMN information of the fifth device; Slice information corresponding to the fifth device; The DNN corresponding to the fifth device; Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function; identification information of the fifth device; Purpose of using the sensing service data of the fifth device; A usage scope of the sensing service data of the fifth device; The fifth device senses the service of the device.
24. A method for opening the capability of a sensing service, characterized in that: include: The fourth device sends a third message to the second device, where the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device.
25. The method according to claim 24, characterized in that The third message includes at least one of the following: The type of sensing service requested; Identification information of the requested sensing service; The purpose of using the requested perception service data; The usage scope of the requested perception service data; identification information of the fourth device; Manufacturer information of the fourth device; Token information of the fourth device; PLMN information of the fourth device; Slice information corresponding to the fourth device; The DNN corresponding to the fourth device.
26. The method according to claim 24 or 25, characterized in that The third message includes at least one of the following: Manufacturer information of the fifth device; PLMN information of the fifth device; Slice information corresponding to the fifth device; The DNN corresponding to the fifth device; Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function; The identification information of the fifth device.
27. The method according to any one of claims 24 to 26, characterized in that Also includes: The fourth device receives a fourth message sent by the second device, where the fourth message includes at least one of the following: Sixth information, used to indicate that the fifth device does not exist; seventh information, used to indicate reason information that the fifth device does not exist; Among them, the reason information includes at least one of the following: the fourth device does not belong to the device corresponding to the perception service capability opening information of the first device; the purpose of use of the requested perception service data is not allowed by the first device; the scope of use of the requested perception service data does not match the perception service capability opening information of the first device.
28. The method according to any one of claims 24 to 27, characterized in that Also includes: The fourth device receives a fifth message sent by the second device, where the fifth message includes at least one of the following: Manufacturer information of the fifth device; PLMN information of the fifth device; Slice information corresponding to the fifth device; The DNN corresponding to the fifth device; Network element type information of the fifth device, where the network element type information is used to indicate that the fifth device is a network element that supports a perception service control function; identification information of the fifth device; Purpose of using the sensing service data of the fifth device; A usage scope of the sensing service data of the fifth device; The fifth device senses the service of the device.
29. The method according to any one of claims 24 to 28, characterized in that Also includes: The fourth device sends a second message to the fifth device, where the second message is used to request a sensing service; The fourth device receives the perception service data sent by the fifth device.
30. The method according to claim 29, characterized in that The second message includes at least one of the following: The type of sensing service requested; Identification information of the requested sensing service; The purpose of using the requested perception service data; The usage scope of the requested perception service data; identification information of the fourth device; Manufacturer information of the fourth device; Token information of the fourth device; PLMN information of the fourth device; Slice information corresponding to the fourth device; The DNN corresponding to the fourth device.
31. The method according to claim 29 or 30, characterized in that The second message includes fifth information, where the fifth information corresponds to at least one of the following information in the first device: Perceive how the business is being performed; Perceive how business data is processed; Perceive how business data is sent; Perceive the format of business data.
32. The method according to claim 31, characterized in that The sending method includes sending the perception service data in a container manner.
33. The method according to claim 32, characterized in that The container method includes at least one of the following: Preset container mode; The container mode corresponding to the value of the fifth information.
34. A capability opening device for sensing services, characterized in that: include: The first sending module is used to send a first message to the second device, where the first message includes the perception service capability opening information of the first device.
35. A capability opening device for sensing services, characterized in that: include: A first receiving module, configured to receive a first message sent by a first device, where the first message includes perception service capability exposure information of the first device; The storage module is used to store the perception service capability exposure information of the first device.
36. A capability opening device for sensing services, characterized in that: include: The second sending module is used to send a third message to the second device, where the third message is used to request information of a fifth device, and the fifth device supports opening perception service data to the fourth device.
37. A communication device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the method implements the steps of the capability opening method of the perception service as described in any one of claims 1 to 13, or the steps of the capability opening method of the perception service as described in any one of claims 14 to 23, or the steps of the capability opening method of the perception service as described in any one of claims 24 to 33.
38. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the capability opening method of the perception service as described in any one of claims 1 to 13, or the steps of the capability opening method of the perception service as described in any one of claims 14 to 23, or the steps of the capability opening method of the perception service as described in any one of claims 24 to 33.
Citation Information
Cited By
Communication method, device and system, storage medium, and program product
WO2026102660A1
