[go: up one dir, main page]

WO2025148848A1 - Procédé de communication et dispositif et système associés - Google Patents

Procédé de communication et dispositif et système associés

Info

Publication number
WO2025148848A1
WO2025148848A1 PCT/CN2025/070871 CN2025070871W WO2025148848A1 WO 2025148848 A1 WO2025148848 A1 WO 2025148848A1 CN 2025070871 W CN2025070871 W CN 2025070871W WO 2025148848 A1 WO2025148848 A1 WO 2025148848A1
Authority
WO
WIPO (PCT)
Prior art keywords
perception
request
service
requirement
area
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2025/070871
Other languages
English (en)
Chinese (zh)
Inventor
雷骜
吴义壮
应江威
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025148848A1 publication Critical patent/WO2025148848A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring

Definitions

  • wireless communication systems In addition to communication capabilities, wireless communication systems also have perception capabilities. Wireless communication systems with perception capabilities can perceive and identify specific areas, objects or events, and meet perception needs in many scenarios, such as perception prediction of people or objects in the environment.
  • the present application provides a communication method and related devices and systems, in order to flexibly respond to perception requests according to perception areas, and meet the restrictions on business requirements of different perception areas.
  • the present application provides a communication method, which can be applied to a communication device.
  • the communication device can be a perception function network element, or a component (such as a chip, a chip system, etc.) configured in the perception function network element, or a logic module or software capable of implementing all or part of the functions of the perception function network element, which is not limited by the present application.
  • the method is described below by taking the perception function network element as an example of a communication device.
  • the sensing request indicates the sensing area.
  • target service requirements are determined according to the perception area, that is, the service requirements corresponding to the perception area requested to be perceived by the perception request are called target service requirements.
  • the perception function network element after receiving a perception request for requesting perception of a perception area, can use the perception area as input to obtain the target service requirements corresponding to the perception area. That is to say, after receiving different perception requests for requesting perception of different perception areas, the perception function network element can flexibly respond to the perception requests according to the perception areas to meet the restrictions on service requirements of different perception areas, thereby solving the problem that all service requirements are the same when perceiving the same service requirements of different perception areas.
  • the method further includes: receiving a correspondence between N service requirements and N intervals of the number of terminals from the data management function network element.
  • obtaining the target business requirement includes: determining the N business requirements based on the perception areas and the mapping relationship, the mapping relationship indicating a correspondence between at least one perception area and at least one business requirement, and N is a positive integer; and obtaining the target business requirement from the N business requirements.
  • the N service requirements correspond to the N intervals of the number of terminals
  • a unique service requirement can be obtained from the N service requirements according to the number of terminals included in the sensing area, and the service requirement is the target service requirement.
  • the identification of the application function network element, the indication of the perception area, the requested service type and the requested service requirement are carried in the perception request, as long as one or more of the identification of the application function network element, the perception area, the requested service type and the requested service requirement meet the above conditions, it is determined that the perception area is allowed to be sensed. For example, if the identification of the application function network element and the perception area meet the above conditions, but the requested service type and the requested service requirement do not meet the above conditions, it is determined that the perception area is allowed to be sensed.
  • the perception request carries at least one of the following: an identifier of an application function network element, an indication of the perception area, a requested service type, and a requested service requirement; before obtaining the target service requirement, the method further includes: obtaining the target service requirement when it is determined that at least one of the following conditions is met: the perception area belongs to a predefined area range, the service type belongs to a predefined service type that is allowed to be triggered, the perception KPI corresponding to the requested service requirement belongs to a predefined perception KPI interval, the time information of the perception request belongs to a predefined time interval, or the application function network element identified by the identifier of the application function network element belongs to a predefined application function network element that is allowed to be triggered.
  • the target service requirement is obtained. For example, when the identification of the application function network element and the perception area meet the above conditions, but the requested service type and the requested service requirement do not meet the above conditions, the target service requirement is obtained.
  • the perception request comes from an application function network element, and the perception request carries the requested service requirements.
  • the method also includes: sending a service requirement confirmation request to the application function network element, the service requirement confirmation request is used to request the adoption of the target service requirements, and the target service requirements are different from the requested service requirements; receiving a service requirement confirmation reply from the application function network element, and the service requirement confirmation reply indicates agreement or disagreement to adopt the target service requirements.
  • the method further includes: receiving a parameter configuration request, the parameter configuration request including a correspondence between at least one perception area and at least one service requirement; and determining the mapping relationship according to the parameter configuration request.
  • the data management network element can obtain at least one business requirement corresponding to the perception area based on the perception area and the mapping relationship, and send the obtained at least one business requirement to the perception function network element, so that the perception function network element obtains the target business requirement corresponding to the perception area from the received business requirement. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solves the problem that all business requirements are the same when perceiving the same business requirement of different perception areas.
  • the N service requirements are the target service requirements.
  • N 1.
  • determining N business requirements based on the perception area and the mapping relationship includes: determining at least one business requirement based on the perception area and the mapping relationship; determining the N business requirements from the at least one business requirement based on the correspondence between at least one business requirement and at least one time period, and time information of the business requirement request.
  • the present application provides a communication method, which can be applied to a communication device.
  • the communication device can be a data management network element, or a component configured in the data management network element (such as a chip, a chip system, etc.), or a logic module or software capable of implementing all or part of the functions of the data management network element, which is not limited by the present application.
  • the method is described below by taking the data management network element as an example of a communication device.
  • N 1
  • the method further includes: sending the correspondence between the N service requirements and N intervals of the number of terminals to the network capability exposure function network element.
  • the perception authorization request carries an identifier of an application function network element
  • the method further includes: determining whether to authorize or not to authorize the perception request based on the identifier of the application function network element.
  • the data management network element determines to authorize the perception request based on the identifier of the application function network element, it further determines whether the service requirements of the request meet the service requirements corresponding to the perception area included in the above mapping relationship.
  • the present application provides a communication method, which is applied to a system including a data management network element, a network open function network element and a perception function network element, the method comprising: NEF sends a perception authorization request to the data management network element, the perception authorization request is used to request authorization of the perception request from the AF, and the perception request is used to request perception of the perception area; when the data management network element determines to authorize the perception request, N service requirements are determined according to the perception area and the mapping relationship, and the mapping relationship indicates the correspondence between at least one perception area and at least one service requirement; the data management network element sends the N service requirements to the network capability exposure function network element; the network open function network element sends a perception request to the perception function network element, and the perception request carries the N service requirements; the perception function network element determines the target service requirement from the N service requirements, and the target service requirement is used to determine the KPI.
  • the present application provides a communication device, comprising a module or unit for implementing the method in the first to fourth aspects and any possible implementation of the first to fourth aspects. It should be understood that each module or unit can implement the corresponding function by executing a computer program.
  • the device may further include a memory for storing a computer program and/or a configuration file of the logic circuit.
  • the memory is coupled to the processor, and when the processor executes instructions stored in the memory, the methods described in the above aspects may be implemented.
  • SF in the converged architecture, SF can be deployed in the traditional 5G core network (5G core network, 5GC) and connected to other network elements using the SBA interface.
  • 5G core network 5G core network
  • SBA SBA interface
  • SF is connected to NEF and can interact with servers outside 5GC through NEF, such as receiving perception request messages from external servers.
  • SF can also be connected to the user plane function (UPF), and base stations and other radio access network (RAN) devices can send the received perception data to SF through the user plane for processing.
  • UPF user plane function
  • RAN radio access network
  • SF deployment can be outside the traditional 5GC.
  • SF cannot be connected to other network elements using the SBA interface, and may need to interact with other 5GC network elements through NEF.
  • SF can also be connected to NEF to interact with external servers through NEF, or SF can also interact directly with external servers without NEF.
  • SF can be connected to RAN equipment to interact with terminal devices.
  • FIG3 is a schematic diagram of the network architecture of SBA in the 5G network provided in an embodiment of the present application.
  • the 5G network architecture may include three parts, namely, a terminal, a data network (DN), and an operator network.
  • a terminal may also be called user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal equipment, wireless communication equipment, user agent or user device.
  • UE user equipment
  • access terminal user unit
  • user station mobile station
  • mobile station mobile station
  • remote station remote terminal
  • mobile device user terminal
  • terminal equipment wireless communication equipment
  • wireless communication equipment user agent or user device.
  • the device for realizing the function of the terminal may be a terminal, or a device capable of supporting the terminal to realize the function, such as a chip system, which may be installed in the terminal or used in combination with the terminal.
  • the chip system may be composed of a chip, or may include a chip and other discrete devices.
  • only the terminal is used as an example for explanation, and the solution of the embodiment of the present application is not limited.
  • the terminal in the present application can be a hardware device, or a software function running on dedicated hardware, or a software function running on general-purpose hardware, or a virtualized device, for example, implemented by general-purpose hardware and instantiated virtualization functions, or dedicated hardware and instantiated virtualization functions.
  • the general-purpose hardware can be a server, such as a cloud server.
  • the RAN node can be a central unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU).
  • the CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU).
  • BBU baseband unit
  • the RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).
  • SF is mainly responsible for the related processing of perception services, such as determining the perception results based on the acquired perception data, such as whether there is an intrusion, or calculating the distance, direction and position of reflective objects in the perception area.
  • AMF is mainly responsible for terminal authentication, terminal mobility management (MM), network slice selection, and SMF selection. It serves as the anchor point for N1 and N2 signaling connections and provides routing for N1/N2 session management (SM) messages for SMF. It maintains and manages terminal status information.
  • MM terminal mobility management
  • SMF session management
  • UPF is responsible for terminal data packet filtering, data transmission/forwarding, rate control, and billing information generation.
  • UDR is mainly used to store user data, including contract data called by UDM, policy information called by PCF, structured data for capability exposure, and application data called by NEF.
  • UDM is mainly used to manage and control user data, such as contract information management, including obtaining contract information from UDR and providing it to other network elements (such as AMF); generating 3GPP authentication credentials for the terminal; and registering and maintaining the network elements currently serving the terminal (for example, the AMF represented by AMF ID1 is the terminal's current serving AMF, serving AMF)).
  • contract information management including obtaining contract information from UDR and providing it to other network elements (such as AMF); generating 3GPP authentication credentials for the terminal; and registering and maintaining the network elements currently serving the terminal (for example, the AMF represented by AMF ID1 is the terminal's current serving AMF, serving AMF)).
  • NEF is used to connect other internal network elements of the core network and the application function (AF) network elements corresponding to the application server (AS) outside the core network, so as to provide network open capabilities to AF, or provide the information provided by AF to the core network elements.
  • AF application function
  • AS application server
  • the AUSF authentication server function is used to perform security authentication on the terminal when the terminal accesses the network.
  • DN mainly provides business services to users.
  • the base station can perform serial-to-parallel conversion, phase shift keying, inverse fast Fourier transform (IFFT), parallel-to-serial conversion, digital-to-analog conversion, etc. on the signal to be sent, and the base station can also perform analog-to-digital conversion, parallel-to-serial conversion, fast Fourier transform (fast Fourier transform), serial-to-parallel conversion, demodulation, etc. on the received echo signal.
  • the signal to be sent may also be sent to the radar processor so that the radar processor can obtain the sensing data according to the signal to be sent and the received echo signal (it can be understood that the echo signal here is the echo signal after the above processing). It should be understood that the processing performed by the base station shown in FIG4 on the signal to be sent and the received echo signal is only an example and should not constitute any limitation to the present application.
  • V2X and unmanned aerial vehicle (VAU) scenarios for example, since the perception distance of vehicles or drones is short or non-line of sight (NLOS) paths cannot be perceived, dynamic maps can be generated based on perception data. For example, during the driving of vehicles or drones, there may be traffic hazards such as the sudden appearance of pedestrians or non-motor vehicles, or pedestrians or non-motor vehicles are in blind spots. Dangerous events can be identified based on perception data and the vehicle or drone can be notified to perform emergency operations. For another example, in vehicle or drone autonomous driving assistance, customized high-precision dynamic maps can be generated based on perception data to assist vehicles or drones in autonomous driving.
  • NLOS non-line of sight
  • Figure 5 is a schematic diagram of parameters that affect perception accuracy and resolution. Taking the Internet of Vehicles scenario as an example, Figure 5 shows several parameters of the key performance indicators (KPIs) that affect perception, including perception positioning accuracy (including vertical and horizontal), perception speed accuracy (including vertical and horizontal), and perception resolution (including area and speed).
  • KPIs key performance indicators
  • Range resolution ⁇ The ability to distinguish adjacent targets at distance, usually measured as the minimum resolvable distance interval, used to identify different vehicles.
  • Velocity resolution ⁇ the ability to distinguish targets in radial velocity.
  • Horizontal field of view 120°.
  • the width of a two-way road is 30 meters
  • the two-way blind spot range is less than 18 meters
  • the blind spot area ratio is ⁇ 1%.
  • the sensing nodes in 5G can be RAN and terminal. According to the combination of different sensing nodes, multiple sensing modes can be obtained. According to the role of the sensing node in the sensing process: transmitter or receiver, and the type of sensing node: RAN or terminal, six sensing modes can be obtained as shown in Table 1.
  • the six sensing modes shown in Table 1 are distinguished for the transmitter and receiver of the sensing signal, specifically: RAN node sends and receives, RAN node A sends and RAN node B receives, RAN node sends and terminal receives, terminal sends and RAN node receives, terminal sends and receives, terminal sends and terminal receives, and terminal A sends and terminal B receives.
  • the transmitter can be a terminal or a RAN node
  • the receiver can be a terminal or a RAN node.
  • the AF sends a sensing request to the SF.
  • the SF receives the sensing request from the terminal.
  • the AF does not send the sensing request to the AF through the NEF.
  • the perception request indicates the above-mentioned perception area.
  • the perception area is used to describe the area that needs to be perceived, and the perception area can be described by an identifier of the area to be perceived in the communication system or outside the communication system.
  • the perception area may include one or more of the following: coordinate information, geographic area identifier, address information, tracking area identifier (TAI), cell identifier (cell ID). It should be noted that the perception area can be other information, and this application does not limit this.
  • the perception request from NEF is referred to as perception request #1
  • the perception area indicated in perception request #1 is referred to as perception area #1. That is, perception request #1 is used to request perception of perception area #1.
  • the perception request from AF is referred to as perception request #2
  • the perception area indicated in perception request #2 is referred to as perception area #2. That is, perception request #2 is used to request perception of perception area #2.
  • the perception request received by the SF may also carry at least one of the following: the AF identifier, the requested service type (hereinafter referred to as service type #1 for convenience of description) and the requested service requirement (hereinafter referred to as service requirement #1 for convenience of description).
  • the AF identifier may be an AF ID or other information that can identify the AF.
  • Service type #1 is the perception service type information corresponding to the perception request (for example, intrusion detection, traffic flow monitoring, etc.).
  • Service type #1 may be one or more of at least one predefined service type.
  • the at least one service type may include, but is not limited to, drone intrusion detection, autonomous driving, safety supervision, family health, or weather monitoring, etc., and the present application includes but is not limited to these.
  • SF obtains target service requirements, where the target service requirements are determined according to the sensing area.
  • the target service requirement may be a KPI, or may include information for determining the KPI. If the target service requirement includes information for determining the KPI, the SF may convert the target service requirement into a KPI.
  • one possible implementation method for the SF to determine the KPI for perceiving the perception area based on the target service requirement is to determine the target service requirement as a KPI for perceiving the terminal, and another possible implementation method is to convert the target service requirement into a KPI for perceiving the perception area.
  • the sensing area is a residential area
  • the target service requirement can be determined as a service requirement with lower sensing accuracy. This method of determining the target service requirement in combination with the sensing area can effectively prevent the exposure of user privacy, reduce the leakage of sensitive information, and effectively and flexibly provide network openness.
  • Table 2 shows an example of a first mapping relationship.
  • Position 1, position 2, and position 3 shown in Table 2 represent three different perception areas, and the first mapping relationship is used to represent the service requirements corresponding to the three positions of the same service type.
  • the level of the default service requirement is higher than the medium service requirement
  • the level of the medium service requirement is higher than the minimum service requirement.
  • the perceived location accuracy in the indicator corresponding to the minimum business requirement is 1m
  • the perceived location accuracy in the indicator corresponding to the medium business requirement is 1cm
  • the perceived location accuracy in the indicator corresponding to the default business requirement is 1mm.
  • the level of the default business requirement is higher than the medium business requirement, and the level of the medium business requirement is higher than the minimum business requirement; for another example, the perceived resolution in the indicator corresponding to the minimum business requirement is 1m, the perceived resolution in the indicator corresponding to the medium business requirement is 1cm, and the perceived resolution in the indicator corresponding to the default business requirement is 1mm.
  • the method 600 also includes: the NEF sends a perception authorization request to the UDM, the perception authorization request is used to request authorization for a perception request from the AF (hereinafter, for the convenience of description, the perception request from the AF is referred to as perception request #2), the perception request #2 is used to request perception of perception area #2 (for example, a specific location or geographical range); the UDM receives the perception authorization request from the NEF, and determines whether to authorize or not to authorize the perception request #2; if it is determined to be authorized, the UDM sends an authorization message to the NEF, the authorization message is used to authorize the perception request; or, if it is determined not to be authorized, the UDM sends a rejection of authorization message to the NEF, the rejection of authorization message is used to reject the authorization of the perception request.
  • the NEF sends a perception authorization request to the UDM
  • the perception authorization request is used to request authorization for a perception request from the AF
  • the perception request #2 is used to request perception of perception area #2 (for example, a
  • the NEF may continue to execute S601 when the UDM determines that the awareness request is authorized.
  • sensing authorization request indicates sensing area #1
  • sensing request #2 indicates sensing area #2. It should be understood that the sensing areas indicated by sensing request #1 and sensing request #2 correspond to the same geographical location, except that the geographical location indicated by sensing request #1 is in a form that can be recognized by the operator network.
  • the perception authorization request carries the identifier of the AF; the above-mentioned UDM determines whether to authorize or not the perception request, which may include: determining whether to authorize or not the perception request based on the identifier of the AF.
  • the UDM may determine to authorize the perception request; otherwise, the UDM determines not to authorize the perception request.
  • SF obtains the target service requirement from the N service requirements according to the time information of the perception request, including: SF obtains the target service requirement from the N service requirements according to the correspondence between the N service requirements and the N time periods and the time information of the perception request.
  • the number of terminals included in the perception area #1 in the embodiment of the present application can be obtained from the AMF.
  • SF obtains the target service requirement from the N service requirements, including: SF obtains the target service requirement from the N service requirements according to the number of terminals included in the sensing area #1 and the time information of the sensing request.
  • SF obtains the target service requirement from N service requirements based on the number of terminals included in perception area #1 and the time information of the perception request, including: SF determines M service requirements from the N service requirements based on the third mapping relationship and the number of terminals included in perception area #1; SF obtains the target service requirement from the M service requirements based on the correspondence between the M service requirements and the M time periods, and the time information of the perception request.
  • SF can determine multiple service requirements from N service requirements based on the third mapping relationship and the number of terminals included in the perception area #1, and the first interval is the interval to which the number of terminals included in the perception area #1 belongs.
  • Table 5 shows an example of a second mapping relationship. As shown in the example in Table 5, it indicates the service requirements corresponding to the time period and the number of terminals of a specific service type in a specific sensing area.
  • SF obtains the target service requirement from N service requirements based on the number of terminals included in perception area #1 and the time information of the perception request, including: SF obtains the target service requirement from N service requirements based on a fourth mapping relationship, the time information of the perception request and the number of terminals included in perception area #1, and the fourth mapping relationship indicates the correspondence between at least one time period, at least one interval of the number of terminals, and at least one service requirement.
  • the above-mentioned UDM determines N business requirements based on the perception area #1 and the first mapping relationship, which may include: UDM determines P (P is a positive integer) business requirements based on the perception area #1 indicated by the business requirement request and the first mapping relationship; further, when P>1, the method 600 may also include: UDM determines N business requirements from P business requirements based on the time information of the business requirement request.
  • the perception authorization request also carries service type #1.
  • the method 600 Before the UDM determines N service requirements based on the perception area #1 from the NEF and the first mapping relationship, the method 600 also includes: the UDM determines at least one perception area based on the service type #1; and determines the perception area #1 from the at least one perception area.
  • the method 600 before SF obtains the target service requirement from N service requirements based on the correspondence between N service requirements and N intervals of the number of terminals, and the number of terminals contained in the perception area, the method 600 also includes: SF sends an acquisition request to AMF, where the acquisition request is used to request the number of terminals contained in the perception area; AMF receives the acquisition request and sends an acquisition reply to SF, where the acquisition reply indicates the number of terminals contained in the perception area; SF receives the acquisition reply and determines the number of terminals contained in the perception area based on the acquisition reply.
  • the SF may continue to execute S602.
  • Example 1 When at least one of the following conditions is met, SF determines that perception of perception area #1 is allowed; or, when all of the following conditions are not met, SF determines that perception of perception area #1 is allowed: perception area #1 belongs to a predefined area range, service type #1 belongs to a predefined service type that is allowed to be triggered, the perception accuracy corresponding to service requirement #1 belongs to a predefined perception accuracy range, the time of the perception request belongs to a predefined time interval, or the AF identified by the AF identifier belongs to a predefined AF that is allowed to be triggered.
  • the indication of the above-mentioned perception area #1, service type #1, service requirement #1 and the identifier of AF can be carried in the perception request #1 and sent to the SF.
  • the perception accuracy corresponding to the service requirement #1 belongs to the predefined perception accuracy range, for example, any one or more parameters included in the KPI determined according to the service requirement #1 may belong to the range of any one or more predefined perception accuracies.
  • the SF determines whether to allow the perception of the perception area #1, if there is a parameter that can meet the above corresponding conditions, the SF can determine to allow the perception of the perception area. It should be noted that whether other parameters other than the parameters that meet the above conditions meet the above conditions is not the focus of this application.
  • the predefined area range is described by the area information used by the operator.
  • the predefined area range may refer to an area where an important person or a motorcade passes through.
  • the predefined service type that is allowed to be triggered may be described by a service ID.
  • the predefined service type that is allowed to be triggered may be sensing the time when a user in a residential area goes out or comes home.
  • the above-mentioned predefined time interval can be, for example, a peak period of traffic. It should be noted here that: if it is for the detection of the peak period of highway, it can be triggered by the time dimension alone, that is, as long as the time information of the perception request belongs to the predefined time interval, it can be triggered; if it is the peak period detection of traffic intersections, it may also need to be triggered in combination with other conditions.
  • the above-mentioned predefined AFs that are allowed to be triggered may be, for example, AF 1 and AF 2, and the predefined AFs that are not allowed to be triggered may be, for example, a public safety AF, or an authority/regulatory agency AF.
  • the business requirements carried in the perception request #1 are perceived.
  • the method 600 further includes: the SF sends a business requirement confirmation request to the AF, where the business requirement confirmation request is used to request the adoption of the target business requirements, which are different from the business requirement #1; the AF sends a business requirement confirmation reply to the SF, where the business requirement confirmation reply indicates agreement or disagreement to adopt the target business requirements.
  • the SF when the business requirement confirmation reply indicates agreement to adopt the target business requirement, the SF initiates a perception process based on the target business requirement; or, when the business requirement confirmation reply indicates disagreement to adopt the target business requirement, the SF determines that it does not agree to perform perception.
  • the target business requirement may be a KPI, or include a KPI, or may also include information used to determine the KPI, such as an identifier or parameter corresponding to the KPI, and so on.
  • KPI is used to describe the accuracy with which the perception data needs to be acquired.
  • the KPI may include one or more of the following indicators: confidence interval, perception positioning accuracy (including vertical and horizontal), perception speed accuracy (including vertical and horizontal), perception resolution (including area and speed), maximum perception service delay or refresh rate. These indicators are only an example of KPI, and this application does not limit the specific indicators included in the KPI.
  • the conversion can be based on the correspondence between predefined business requirements and KPIs.
  • the target business requirement is a specific identifier
  • SF has a predefined KPI corresponding to the specific identifier.
  • the parameters in the perception requirement can be translated into KPI parameters.
  • the parameters in the perception requirement correspond to the parameters of the KPI one by one
  • SF determines the parameters in the perception requirement as the corresponding KPI parameters.
  • the perception requirement can also be equivalent to the KPI, that is, no translation is required by SF.
  • SF when the target service requirement is different from service requirement #1, SF sends a service requirement confirmation request to AF; or, when the target service requirement is the same as service requirement #1, SF initiates a perception process based on the target service requirement.
  • the above target business requirement is different from business requirement #1 means that the level of the target business requirement is different from the level of business requirement #1.
  • the level of the target business requirement is lower than the level of business requirement #1; for another example, the level of the target business requirement is higher than the level of business requirement #1.
  • the fact that the target business requirement is downgraded compared to business requirement #1 means that the level of the target business requirement is lower than the level of business requirement #1.
  • the target business requirement obtained by SF is the minimum business requirement
  • business requirement #1 is the medium business requirement. Then it can be considered that the target business requirement is downgraded compared to business requirement #1.
  • the level of the business requirement can be determined according to the values of the various indicators in the KPI determined by it.
  • the following shows several examples where the level of the target business requirement is lower than the level of business requirement #1:
  • the perceived location accuracy in the indicator corresponding to the target business requirement is 1m
  • the perceived location accuracy in the indicator corresponding to business requirement #1 is 1mm. Since the accuracy of 1mm is higher than the accuracy of 1m, it can be considered that the level of the target business requirement is lower than the level of business requirement #1.
  • the perceived resolution in the indicator corresponding to the target business requirement is 5m
  • the perceived resolution in the indicator corresponding to business requirement #1 is 1m.
  • the level of the target business requirement is lower than the level of business requirement #1.
  • the maximum perceived service delay in the indicator corresponding to the target business requirement is 0.5ms
  • the maximum perceived service delay in the indicator corresponding to business requirement #1 is 0.2ms. Since the delay of 0.2ms is shorter than the delay of 0.5ms, it can be considered that the level of the target business requirement is lower than the level of business requirement #1.
  • the target business requirement being upgraded compared to business requirement #1 means that the level of the target business requirement is higher than the level of business requirement #1.
  • the target business requirement obtained by SF is a medium business requirement and business requirement #1 is a minimum business requirement, then it can be considered that the target business requirement is upgraded compared to business requirement #1.
  • Fig. 7 is another schematic flow chart of the communication method provided by the embodiment of the present application. As shown in Fig. 7, the method 700 may include S701 to S716. The steps in the method 700 are described below.
  • the external area information can be understood as the above-mentioned perception area #2
  • the first perception request can be understood as the previous perception request #2.
  • the internal perception area information refers to the area information used by the operator network, which can be understood as the perception area #1 mentioned above.
  • the NEF sends a sensing authorization request to the UDM.
  • the UDM receives the sensing authorization request from the NEF.
  • UDM determines whether to authorize or not authorize the perception request.
  • the UDM can determine whether to authorize the perception request from the AF based on the AF's identifier; in another possible case, the UDM can further determine whether the business requirements carried in the perception request from the AF meet the business requirements included in the corresponding relationship pre-stored in the UDM; if so, determine to authorize; or, if not, determine not to authorize.
  • the acquisition request includes internal area information.
  • AF sends a first perception request to NEF.
  • NEF receives the first perception request from AF.
  • the internal perception area information refers to area information used by the operator network.
  • the internal perception area information can be understood as the above-mentioned perception area #1
  • the external area information can be understood as the above-mentioned perception area #2.
  • UDM determines whether to authorize or not the perception request.
  • a rejection authorization message is sent to the NEF, where the rejection authorization message is used to reject authorization for the perception request.
  • the UDM determines at least one new service requirement corresponding to the internal area information according to the first mapping relationship and the internal area information.
  • This process may refer to S709 in method 700 and will not be described in detail here.
  • the authorization message when N is greater than 1, the authorization message also carries a correspondence between N service requirements and N intervals of the number of terminals.
  • the second perception request also carries the correspondence between N service requirements and N intervals of the number of terminals.
  • sensing area #1 If it is determined that the sensing area #1 is allowed to be sensed, some steps from S809 to S815 are continued to be executed; otherwise, the second sensing request is rejected.
  • the description of determining that the sensing area #1 is allowed to be sensed can refer to the related description above.
  • S813 is continued to be executed, and SF initiates the perception process based on the target business requirements.
  • the UDM can, when authorizing the perception request from the AF, determine the business requirements corresponding to the perception area based on the perception area carried in the perception authorization request and the first mapping relationship, and send the acquired business requirements to the NEF, which then sends the acquired business requirements to the SF, so that the SF obtains the target business requirements corresponding to the perception area from the received business requirements. Therefore, the method provided in the embodiment of the present application can flexibly respond to the perception request according to the perception area to meet the restrictions on business requirements of different perception areas, and solves the problem that all business requirements are the same when perceiving the same business requirements of different perception areas.
  • the following takes the first mapping relationship pre-stored in SF as an example and describes in detail the method provided in the embodiment of the present application in combination with FIG. 9 .
  • Fig. 9 is another schematic flow chart of the communication method provided by the embodiment of the present application. As shown in Fig. 9, the method 900 may include S901 to S914. The steps in the method 900 are described below.
  • AF sends a first perception request to NEF.
  • NEF receives the perception request from AF.
  • NEF converts the external perception area information into internal perception area information.
  • the NEF sends a perception authorization request to the UDM.
  • the UDM receives the perception authorization request from the NEF.
  • UDM determines whether to authorize or not authorize the perception request.
  • a rejection authorization message is sent to the NEF, where the rejection authorization message is used to reject authorization for the perception request.
  • UDM sends an authorization message to NEF.
  • NEF receives the authorization message from the UDM.
  • This process can refer to the above process of SF determining N service requirements according to the first mapping relationship and perception area #1, which will not be repeated here.
  • This process may refer to the process of obtaining the target business requirements in the first possible implementation of method 600 above, and will not be described in detail here.
  • the processing module 1020 is further used to: determine the N service requirements according to the perception area and the mapping relationship; and obtain the target service requirement from the N service requirements.
  • the processing module 1020 is further used to: when N>1, obtain the target service requirement from the N service requirements according to the correspondence between the N service requirements and the N intervals of the number of terminals, and the number of terminals included in the sensing area.
  • processing module 1020 is further used to: determine whether to allow sensing of the sensing area.
  • the transceiver module 1010 is also used to: send a service requirement confirmation request to the application function network element; and receive a service requirement confirmation reply from the application function network element; the processing module 1020 is also used to: when the service requirement confirmation reply indicates agreement to adopt the target service requirement, initiate a perception process based on the target service requirement; or, when the service requirement confirmation reply indicates disagreement to adopt the target service requirement, determine disagreement to perform perception.
  • the transceiver module 1010 is also used to: when it is determined that the perception is not agreed, send a rejection message to the application function network element, where the rejection message is used to reject the perception request.
  • transceiver module 1010 and the processing module 1020 can be directly obtained by referring to the relevant descriptions in the embodiments shown in FIG. 6 to FIG. 9 , and will not be repeated here.
  • the apparatus 1000 is used to implement the functions of the UDM in the above method 600 and the method embodiments shown in FIG. 7 to FIG. 9 .
  • the transceiver module 1010 is further used to: send the corresponding relationship between the N service requirements and the N intervals of the number of terminals to the perception function network element.
  • the transceiver module 1010 is further used to: receive a parameter configuration request; the transceiver module 1010 is further used to: determine the mapping relationship according to the parameter configuration request.
  • the transceiver module 1010 is used to: receive a perception authorization request from a network capability exposure function network element; the processing module 1020 is used to: when determining to authorize the perception request, determine N service requirements based on the perception areas and the mapping relationship, and the mapping relationship indicates the correspondence between at least one perception area and at least one service requirement; the transceiver module 1010 is also used to: send the N service requirements to the network capability exposure function network element.
  • the transceiver module 1010 is further used to: send the corresponding relationship between the N service requirements and the N intervals of the number of terminals to the network capability exposure function network element.
  • the processing module 1020 is further used to determine whether to authorize or not to authorize the perception request based on the identifier of the application function network element.
  • the device 1000 may include a sending module but not a receiving module.
  • the device 1000 may include a receiving module but not a sending module. Specifically, it may depend on whether the above solution executed by the device 1000 includes a sending action and a receiving action. It is understandable that since the device 1000 has a communication function, it can also be called a communication device.
  • FIG11 is another schematic block diagram of a communication device provided in an embodiment of the present application.
  • the communication device 1100 includes at least one processor 1110.
  • the at least one processor 1110 may be used to execute a computer program or instruction in a memory to implement the steps performed by the SF, the steps performed by the UDM, or the steps performed by the AF in any of the method embodiments shown in FIG600 and FIG7 to FIG9.
  • the interface circuit 1130 can be a transceiver, which can specifically include a transmitter and a receiver, the transmitter is used to send signals, and the receiver is used to receive signals.
  • the interface circuit 1130 can be an input-output circuit, a bus, a module, a pin, or other types of interface circuits, wherein the input circuit in the input-output circuit can be used for receiving, and the output interface can be used for sending.
  • the processor 1110 may correspond to the processing module 1020 in the above communication device 1000
  • the interface circuit 1130 may correspond to the transceiver module 1010 in the above communication device 1000 .
  • the processors mentioned above may be general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components or any combination thereof.
  • DSP digital signal processors
  • ASIC application specific integrated circuits
  • FPGA field programmable gate arrays
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc.
  • the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the nonvolatile 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), which is used as an external cache.
  • RAM random access memory
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchlink DRAM
  • DR RAM direct rambus RAM
  • the method provided in the above embodiment can be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software When implemented by software, it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product may include one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network or other programmable device.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital user (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic disk), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)).
  • An embodiment of the present application also provides a communication system, which includes the aforementioned SF and UDM.
  • An embodiment of the present application also provides a computer program product, which includes: a computer program (also referred to as code, or instruction), which, when executed, enables a computer to execute a method executed by an SF network element in any of the embodiments shown in FIGS. 6 to 9 , or enables a computer to execute a method executed by an UDM network element in any of the embodiments shown in FIGS. 7 to 9 .
  • a computer program also referred to as code, or instruction
  • the embodiment of the present application further provides a computer-readable storage medium, which stores a computer program (also referred to as code or instruction).
  • a computer program also referred to as code or instruction.
  • the computer executes the method executed by the SF network element in any of the embodiments shown in Figures 6 to 9, or the computer executes the method executed by the UDM network element in any of the embodiments shown in Figures 7 to 9.
  • An embodiment of the present application also provides a chip system, which includes at least one processor, used for implementing the method executed by the SF network element in any of the embodiments shown in Figures 6 to 9, or for implementing the method executed by the UDM network element in any of the embodiments shown in Figures 7 to 9.
  • the chip system also includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.
  • the chip system also includes an interface circuit and/or a power supply circuit, the interface circuit is used to transmit data, and the power supply circuit is used to power the chip system.
  • the interface circuit is used to transmit data
  • the power supply circuit is used to power the chip system.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande concerne un procédé de communication et un dispositif et un système associés, qui peuvent répondre de manière flexible à des demandes de détection sur la base de régions de détection, répondant aux conditions de service de différentes régions de détection. Le procédé comprend les étapes suivantes : un élément de réseau de fonction de détection reçoit des demandes de détection, les demandes de détection étant utilisées pour demander de détecter des régions de détection ; et l'élément de réseau de fonction de détection acquiert une condition de service cible, la condition de service cible étant déterminée sur la base des régions de détection, et la condition de service cible étant utilisée pour déterminer un KPI détecté.
PCT/CN2025/070871 2024-01-12 2025-01-06 Procédé de communication et dispositif et système associés Pending WO2025148848A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202410056545.8 2024-01-12
CN202410056545.8A CN120321627A (zh) 2024-01-12 2024-01-12 通信方法及相关装置、系统

Publications (1)

Publication Number Publication Date
WO2025148848A1 true WO2025148848A1 (fr) 2025-07-17

Family

ID=96332168

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2025/070871 Pending WO2025148848A1 (fr) 2024-01-12 2025-01-06 Procédé de communication et dispositif et système associés

Country Status (2)

Country Link
CN (1) CN120321627A (fr)
WO (1) WO2025148848A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020147760A1 (fr) * 2019-01-15 2020-07-23 华为技术有限公司 Procédé, dispositif, et système de communication de réseau local
CN115734200A (zh) * 2021-09-01 2023-03-03 华为技术有限公司 对终端设备进行感知的方法和通信装置
CN116193500A (zh) * 2021-11-29 2023-05-30 维沃移动通信有限公司 感知业务实现方法、装置、网络侧设备及终端

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020147760A1 (fr) * 2019-01-15 2020-07-23 华为技术有限公司 Procédé, dispositif, et système de communication de réseau local
CN115734200A (zh) * 2021-09-01 2023-03-03 华为技术有限公司 对终端设备进行感知的方法和通信装置
CN116193500A (zh) * 2021-11-29 2023-05-30 维沃移动通信有限公司 感知业务实现方法、装置、网络侧设备及终端

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PENGTAI QIN, CHINA MOBILE COM. CORPORATION: "pCR on update KPI of use case sensing for UAV intrusion detection", 3GPP DRAFT; S1-230208; TYPE PCR; FS_SENSING, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG1, no. Athens, GR; 20230220 - 20230224, 10 February 2023 (2023-02-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052236932 *

Also Published As

Publication number Publication date
CN120321627A (zh) 2025-07-15

Similar Documents

Publication Publication Date Title
WO2023030368A1 (fr) Procédé de détection d'équipement utilisateur, et appareil de communication
EP4564862A1 (fr) Procédé et appareil de détection de communication
WO2023061412A1 (fr) Procédé et appareil de transmission d'informations, et système
WO2023143569A1 (fr) Procédé et appareil de communication sans fil
EP2523421A1 (fr) Procédé et système de protection de la confidentialité de communication de machine à machine, et couche de capacité de service de communication de machine à machine et dispositif correspondant
US20240098680A1 (en) Tag locating method and system, and related apparatus
WO2020156127A1 (fr) Procédé de communication sans fil et appareil de communication
US20240205652A1 (en) Sensory data transmission method, apparatus, and system
KR20190129679A (ko) 차량 통신 서비스를 수행하는 장치 및 방법
WO2025148848A1 (fr) Procédé de communication et dispositif et système associés
WO2025077215A1 (fr) Procédé et appareil de communication, et support de stockage
EP4468780A1 (fr) Procédé et appareil de communication
WO2024140741A1 (fr) Procédé d'enregistrement et dispositif associé
CN119676854A (zh) 一种通信方法及装置
WO2025149036A1 (fr) Procédé de détection, appareil de communication et système
WO2025167841A1 (fr) Procédé et appareil de communication
CN120166428B (en) Information transmission method, device and storage medium
WO2025044806A1 (fr) Procédé et appareil de communication
EP4668812A1 (fr) Procédé de communication et appareil de communication
WO2024199072A1 (fr) Procédé de communication et appareil de communication
CN120075754A (zh) 一种通信方法及装置
WO2024140766A1 (fr) Procédé d'enregistrement et dispositif associé
WO2024230559A1 (fr) Procédé et appareil de communication
WO2025228145A1 (fr) Procédé et appareil de communication, ainsi que support de stockage lisible par ordinateur
WO2025044497A1 (fr) Procédé de communication et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 25738379

Country of ref document: EP

Kind code of ref document: A1