WO2024007271A1 - 感知服务的切换方法和装置、电子设备和存储介质 - Google Patents
感知服务的切换方法和装置、电子设备和存储介质 Download PDFInfo
- Publication number
- WO2024007271A1 WO2024007271A1 PCT/CN2022/104474 CN2022104474W WO2024007271A1 WO 2024007271 A1 WO2024007271 A1 WO 2024007271A1 CN 2022104474 W CN2022104474 W CN 2022104474W WO 2024007271 A1 WO2024007271 A1 WO 2024007271A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- access network
- message
- functional entity
- sensing
- network functional
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 87
- 230000006870 function Effects 0.000 claims description 87
- 230000008447 perception Effects 0.000 claims description 62
- 238000004891 communication Methods 0.000 claims description 52
- 230000004044 response Effects 0.000 claims description 30
- 238000012545 processing Methods 0.000 claims description 14
- 230000008569 process Effects 0.000 abstract description 18
- 238000010586 diagram Methods 0.000 description 19
- 238000005516 engineering process Methods 0.000 description 13
- 238000007726 management method Methods 0.000 description 12
- 230000005540 biological transmission Effects 0.000 description 4
- 238000005259 measurement Methods 0.000 description 4
- 238000012546 transfer Methods 0.000 description 4
- 238000004590 computer program Methods 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000010354 integration Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000002452 interceptive effect Effects 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 101000741965 Homo sapiens Inactive tyrosine-protein kinase PRAG1 Proteins 0.000 description 1
- 102100038659 Inactive tyrosine-protein kinase PRAG1 Human genes 0.000 description 1
- 101150119040 Nsmf gene Proteins 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000003190 augmentative effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000007639 printing Methods 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/08—Reselecting an access point
Definitions
- the present disclosure relates to the field of wireless communication technology, and in particular, to a sensing service switching method and device, electronic equipment, and storage media.
- wireless sensing technology has become a hot research topic.
- wireless sensing technology can be combined with communication technologies such as fifth generation (5G) mobile communication technology to provide sensing services based on communication systems.
- 5G fifth generation
- the number of terminal devices is getting larger and larger, and the coverage range is getting wider and wider. Therefore, terminal devices naturally become sensing devices for wireless sensing to achieve wireless sensing of the surrounding environment.
- the location of the terminal device is not fixed. When the location of the terminal device changes, it may be necessary to switch the base station, that is, switch from the source base station to the target base station. Since the terminal device is processing the sensing service, it needs to consider whether the target base station supports the sensing service during handover. However, this is not supported in the current switching process.
- the present disclosure provides a sensing service switching method and device, electronic equipment, and storage media to achieve continuity of base station support for sensing services during the switching process.
- the present disclosure provides a service-aware switching method, which can be applied to a first access network functional entity.
- the method includes: a first access network functional entity sends a first message to a second access network functional entity, the first message carries sensing information of sensing services, and the sensing information is used by the second access network functional entity to determine whether to accept it.
- Switching the first access network functional entity receives the second message, and the second message is used to instruct the second access network functional entity to accept or reject the switching.
- the operation of the first access network function entity sending the first message to the second access network function entity may include: the first access network function entity sends the first message to the second access network function entity through the Xn reference point. The entity sends the first message; or, the first access network function entity sends the first message to the second access network function entity through the N2 reference point.
- the first message may be a handover request message.
- the operation of the first access network functional entity receiving the second message may include: the first access network functional entity receiving the second message from the second access network functional entity through the Xn reference point; or , the first access network functional entity receives the second message from the second access network functional entity through the N2 reference point.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the above method may further include: The network access function entity sends a third message to the second access network function entity, where the third message carries sensing service configuration parameters.
- the operation of the first access network function entity sending the third message to the second access network function entity may include: the first access network function entity sends the third message to the second access network function entity through the Xn reference point. The entity sends the third message; or, the first access network function entity sends the third message to the second access network function entity through the N2 reference point.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- the present disclosure provides a service-aware switching method, which can be applied to the second access network functional entity.
- the method includes: the second access network functional entity receives a first message from the first access network functional entity, where the first message carries sensing information of the sensing service; the second access network functional entity responds to the sensing information and the second access network functional entity.
- the sensing capability of the network access functional entity determines whether to accept the handover; the second access network functional entity sends a second message, and the second message is used to instruct the second access network functional entity to accept or reject the handover.
- the operation of the second access network functional entity receiving the first message sent from the first access network functional entity may include: the second access network functional entity receives the first message sent from the first access network functional entity through the Xn reference point. The first message from the network access functional entity; or, the second access network functional entity receives the first message from the first access network functional entity through the N2 reference point.
- the first message may be a handover request message.
- the operation of the second access network functional entity sending the second message may include: the second access network functional entity sending the second message to the first access network functional entity through the Xn reference point; or , a second message sent by the second access network functional entity to the first access network functional entity through the N2 reference point.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the second access network functional entity determines whether to accept the handover based on the sensing information and the sensing capability of the second access network functional entity. In the case where the sensing capability meets the sensing information, the second access network functional entity determines whether to accept the handover. The second access network functional entity determines to accept the handover; or, if the sensing capability does not meet the sensing information, the second access network functional entity determines to reject the handover.
- the perception information that the perception capability meets the requirements may include: the perception capability indicates that wireless perception is supported, or the perception capability indicates that wireless perception is supported and the perception service requirements are met; the perception information that the perception capability does not satisfy may include at least one of the following: Perception Capability indicates that wireless sensing is not supported, and perception capability indicates that wireless sensing is supported but does not meet sensing service requirements.
- the above method may further include: the second access network function entity The entity receives a third message from the first access network function entity, where the third message carries sensing service configuration parameters.
- the operation of the second access network function entity receiving the third message from the first access network function entity may include: the second access network function entity receives the third message from the first access network function entity through the Xn reference point. The third message from the network function entity; or, the second access network function entity receives the third message from the first access network function entity through the N2 reference point.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- the present disclosure provides a service-aware switching device, which is provided in the first access network functional entity.
- the device includes: a sending module configured to send a first message to the second access network functional entity, where the first message carries sensing information of the sensing service, and the sensing information is used for the second access network functional entity to determine whether to accept the handover;
- the receiving module is configured to receive a second message, where the second message is used to instruct the second access network functional entity to accept or reject the handover.
- the sending module may be configured to: send the first message to the second access network functional entity through the Xn reference point; or send the first message to the second access network functional entity through the N2 reference point.
- the first message may be a handover request message.
- the receiving module may be configured to: receive the second message from the second access network functional entity through the Xn reference point; or receive the second message from the second access network functional entity through the N2 reference point. information.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the sending module may also be configured to: in the case where the sensing information includes a sensing service switching indication and/or a sensing service requirement, and the second message indicates that the second access network functional entity accepts the switching, send a message to the third access network functional entity.
- the second access network functional entity sends a third message, and the third message carries sensing service configuration parameters.
- the sending module may be configured to: send the third message to the second access network functional entity through the Xn reference point; or send the third message to the second access network functional entity through the N2 reference point.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- the present disclosure provides a service-aware switching device, which is provided in the second access network functional entity.
- the device includes: a receiving module, receiving a first message from a first access network functional entity, where the first message carries sensing information of sensing services; a processing module, based on the sensing information and the sensing capability of the second access network functional entity, Determine whether to accept the handover; the sending module sends a second message, where the second message is used to instruct the second access network functional entity to accept or reject the handover.
- the receiving module may be configured to: receive the first message from the first access network functional entity through the Xn reference point; or receive the first message from the first access network functional entity through the N2 reference point. information.
- the first message may be a handover request message.
- the sending module may be configured to: send the second message to the first access network functional entity through the Xn reference point; or send the second message to the first access network functional entity through the N2 reference point. information.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the processing module may be configured to: determine to accept the switch if the perceptual capability satisfies the perceptual information; or determine to reject the switch if the perceptual capability does not satisfy the perceptual information.
- the perception information that the perception capability meets the requirements may include: the perception capability indicates that wireless perception is supported, or the perception capability indicates that wireless perception is supported and the perception service requirements are met; the perception information that the perception capability does not satisfy may include at least one of the following: perception Capability indicates that wireless sensing is not supported, and awareness capability indicates that wireless sensing is supported but does not meet sensing service requirements.
- the receiving module may also be configured to: when the sensing information includes a sensing service switching indication and/or a sensing service requirement, and the second access network functional entity determines to accept the switching, receive the message from the first access network.
- the third message of the network access functional entity carries the sensing service configuration parameters.
- the receiving module may be configured to: receive the third message from the first access network functional entity through the Xn reference point; or, receive the third message from the first access network functional entity through the N2 reference point. information.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- the present disclosure provides an electronic device, including: a memory; a processor connected to the memory and configured to execute computer-executable instructions stored on the memory to implement the first aspect, the second aspect, and the like.
- the present disclosure provides a computer storage medium that stores computer-executable instructions. After the computer-executable instructions are executed by a processor, the computer-executable instructions can implement the first aspect, the second aspect, and possible implementations thereof.
- the first access network functional entity sends a first message carrying sensing information to the second access network functional entity; the second access network functional entity determines whether to accept the handover based on the sensing information, and sends a message to the first access network functional entity.
- the network access function entity sends a second message to indicate whether the second access network function entity accepts the handover.
- the first access network functional entity can determine the second access network functional entity that supports the sensing service before the handover, so that the second access network functional entity still supports the sensing service after the handover, thereby ensuring the handover.
- Figure 1 is a schematic structural diagram of a communication system in an embodiment of the present disclosure
- Figure 2 is a schematic diagram of an architecture represented by reference points in a non-roaming 5G network in an embodiment of the present disclosure
- Figure 3 is a schematic diagram of an architecture based on service-based interfaces in a non-roaming 5G network in an embodiment of the present disclosure
- Figure 4 is a schematic diagram of an interaction flow of a sensing service switching method in an embodiment of the present disclosure
- Figure 5 is a schematic diagram of an interaction flow of another sensing service switching method in an embodiment of the present disclosure.
- Figure 6 is a schematic flowchart of a sensing service switching method in an embodiment of the present disclosure
- Figure 7 is a schematic flowchart of another sensing service switching method in an embodiment of the present disclosure.
- Figure 8 is a schematic structural diagram of a service-aware switching device in an embodiment of the present disclosure.
- Figure 9 is a schematic structural diagram of a service-aware switching device in an embodiment of the present disclosure.
- Figure 10 is a schematic structural diagram of a communication device in an embodiment of the present disclosure.
- Figure 11 is a schematic structural diagram of an access network functional entity in an embodiment of the present disclosure.
- first, second, third, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, “first information” may also be called “second information”, and similarly, “second information” may also be called “first information”. Depending on the context, the word “if” as used herein may be interpreted as “when” or “when” or “in response to determining.”
- FIG. 1 is a schematic structural diagram of a communication system in an embodiment of the present disclosure.
- the above-mentioned communication system 100 may include a 5G access network (AN) and a 5G core network (5GC).
- the 5G access network may include a next generation radio access network (NG-RAN) 101.
- the NG-RAN 101 communicates with the terminal device 102 through the Uu interface.
- the 5G core network 103 may include: access and mobility management function (AMF) 1031, user plane function (UPF) 1032, session management function (SMF) 1033, policy Policy control function (PCF) 1034, unified data management (UDM) 1035, etc.
- AMF access and mobility management function
- UPF user plane function
- SMF session management function
- PCF policy Policy control function
- UDM unified data management
- the above-mentioned communication system 100 may also include other network elements, which is not specifically limited in this embodiment of the present disclosure.
- the terminal device 102 can access the 5G core network through the third generation partnership project (3rd generation partnership project, 3GPP) technology.
- terminal equipment can access the 5G core network through 3GPP access network equipment.
- PCF 1034 has a policy control function and is mainly responsible for policy decisions related to billing strategies for sessions and business flows, quality of service (QoS) bandwidth guarantees and policies, etc.
- QoS quality of service
- SMF 1033 has a session management function, which mainly performs session management, execution of control policies issued by PCF 1034, selection of UPF 1032, Internet Protocol (IP) address allocation of UE 102 and other functions.
- session management function which mainly performs session management, execution of control policies issued by PCF 1034, selection of UPF 1032, Internet Protocol (IP) address allocation of UE 102 and other functions.
- AMF 1031 has access and mobility management functions, mainly performing mobility management, access authentication/authorization and other functions. In addition, it is also responsible for transmitting user policies between UE 102 and PCF 1034.
- UPF 1032 is the user plane functional entity, which serves as the interface with the data network and completes functions such as user plane (UP) data forwarding, session/flow level-based billing statistics, bandwidth limitation, etc.
- UP user plane
- N7 The interface between PCF 1034 and SMF 1033, used to issue control policies for packet data unit (packet data unit, PDU) session granularity and business data flow granularity.
- packet data unit packet data unit, PDU
- N3 Communication interface between UPF 1032 and NG-RAN 101.
- N15 The interface between PCF 1034 and AMF 1031, used to deliver UE policies and access control related policies.
- N4 The interface between SMF 1033 and UPF 1032. It is used to transfer information between the control plane and UP, including controlling the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. for UP and reporting of UP information.
- N11 The interface between SMF 1033 and AMF 1031, used to transfer PDU session tunnel information between NG-RAN 101 and UPF 1032, transfer control messages sent to UE 102, and transfer radio resource control sent to NG-RAN 101 Information etc.
- N2 The interface between AMF 1031 and NG-RAN 101, used to transmit wireless bearer control information from the core network side to NG-RAN 101, etc.
- N1 The interface between AMF 1031 and UE 102, has nothing to do with access, and is used to transmit QoS control rules to UE 102, etc.
- N8 The interface between AMF 1031 and UDM 1035. It is used for AMF 1031 to obtain subscription data and authentication data related to access and mobility management from UDM 1035, and for AMF 1031 to register UE current mobility management related information with UDM 1035.
- N10 The interface between SMF 1033 and UDM 1035. It is used for SMF 1033 to obtain session management-related contract data from UDM 1035, and for SMF 1033 to register UE current session-related information with UDM 1035.
- the above terminal device may be a terminal device with a wireless communication function, and may also be called user equipment (UE).
- Terminal devices can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; they can also be deployed on water (such as ships, etc.); they can also be deployed in the air (such as aircraft, balloons, satellites, etc.).
- the above-mentioned terminal equipment can be a mobile phone (mobile phone), tablet computer (Pad), computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, industrial control (industrial) Wireless terminals in control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and transportation safety Wireless terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
- the terminal device may also be a handheld device with wireless communication capabilities, a vehicle-mounted device, a wearable device, a computing device, or other processing device connected to a wireless modem, etc.
- the terminal device can also be called by different names in different networks, for example: terminal device, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G network or terminal equipment in future evolution networks, etc.
- terminal device access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G network or terminal equipment in future evolution networks, etc.
- SIP session initiation protocol
- WLL wireless local loop
- PDA personal digital processing
- the above-mentioned access network equipment also called an access network functional entity, may be a device or functional entity used by the access network side to support terminal access to the wireless communication system.
- it can be the next generation base station (next generation NodeB, gNB), transmission reception point (TRP), relay node (relay node), access point (AP) in the 5G access technology communication system )wait.
- next generation base station nodeB, gNB
- TRP transmission reception point
- relay node relay node
- AP access point
- each device is only exemplary, and not all functions of each device are necessary when applied in the embodiments of the present disclosure. All or part of the equipment of the core network may be physical equipment or virtualized equipment, which is not limited here. Of course, the communication system in the embodiment of the present disclosure may also include other devices not shown in Figure 1, which are not limited here.
- the above communication system 100 may be, but is not limited to, a 5G network adopting the following architecture.
- FIG. 2 is a schematic diagram of an architecture represented by reference points in a non-roaming 5G network in an embodiment of the present disclosure.
- the 5G core network in addition to the above-mentioned AMF, SMF, PCF and UDM, can also include: user plane function (UPF), data network (data network) network (DN), application function (AF), authentication server function (AUSF), network slice selection function (NSSF), specific network slice authentication and authentication function (network slice-specific and SNPN authentication and authorization function (NSSAAF), network slice admission control function (NSACF), etc.
- UPF user plane function
- DN data network
- AF application function
- AUSF authentication server function
- NSSF network slice selection function
- NSSAAF network slice-specific and SNPN authentication and authorization function
- NSACF network slice admission control function
- N7 is the communication interface between SMF and PCF
- N5 is the communication interface between PCF and AF
- N6 is the communication interface between UPF and DN
- N9 is the communication between any two UPFs.
- Interface is the communication interface between AMF and AUSF
- N22 is the communication interface between AMF and NSSF
- N14 is the communication interface between any two AMFs
- N58 is the communication interface between AMF and NSSAAF
- N59 is NSSAAF Communication interface with UDM
- N80 is the communication interface between NSACF and AMF
- N81 is the communication interface between NSACF and SMF
- N13 is the communication interface between AUSF and UDM.
- PCF communicates with UDR.
- Figure 3 is a schematic diagram of an architecture based on service-based interfaces in a non-roaming 5G network in an embodiment of the present disclosure.
- service-oriented interfaces are used to interact between each network element.
- NSSAAF network exposure function
- NSSF network repository function
- PCF network repository function
- UDM User Data Management Function
- the service-oriented interface provided by NSSAAF to the outside world can be Nnssaaf
- the service-oriented interface provided by ASUF to the outside world can be Nausf
- the service-oriented interface provided by AMF to the outside world can be Namf
- the service-oriented interface provided by SMF to the outside world can be Nsmf
- the service-oriented interface provided by NSACF to the outside world can be The service interface can be Nnsacf.
- the external service interface provided by NSSF can be Nnssf
- the external service interface provided by NEF can be Nnef
- the external service interface provided by NRF can be Nnrf
- the external service interface provided by PCF can be Npcf
- the external service interface provided by UDM can be The interface can be Nudm
- the service-oriented interface provided by AF can be Naf.
- a service communication proxy can also be deployed in the 5G core network, which can be used between network function (NF) and network function service (NF service) indirect communication.
- NF network function
- NF service network function service
- wireless sensing technology has become a hot research topic.
- wireless sensing technology can be combined with communication technologies such as fifth generation (5G) mobile communication technology to provide sensing services based on communication systems.
- 5G fifth generation
- the number of terminal devices is getting larger and larger, and the coverage range is getting wider and wider. Therefore, terminal devices naturally become sensing devices for wireless sensing to achieve wireless sensing of the surrounding environment.
- the base station needs to serve as a sensing service node to support the sensing service.
- the base station can realize the communication of wireless sensing data between terminal equipment and core network equipment.
- the base station may also provide other support for sensing services.
- the location of the terminal device is not fixed. When the location of the terminal device changes, it may be necessary to switch the base station, that is, switch from the source base station to the target base station. Since the terminal device is processing the sensing service, it needs to consider whether the target base station supports the sensing service during handover, so as to confirm that the target base station of the handover supports the sensing service.
- the terminal device may be a UE
- the first access network function entity may be the source gNB
- the second access network function entity may be the target gNB
- the first core network function entity may be the source AMF
- the second core network function entity may be the source gNB.
- the entity can be the target AMF.
- FIG. 4 is a schematic interactive flow diagram of a sensing service switching method in an embodiment of the present disclosure. This method can be applied to Xn-based inter-base station handover (Xn based inter NG-RAN handover) process.
- Xn based inter NG-RAN handover Xn-based inter NG-RAN handover
- the Xn interface is the interface defined between two gNBs in the 5G network and is used to provide interconnection for NG-RAN.
- the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface.
- the Xn-U interface is used to provide unguaranteed delivery of user plane PDUs and can support functions such as data forwarding and flow control.
- the Xn-C interface is used to provide point-to-point transmission of signaling PDUs and can support Xn interface management, mobility management, dual connectivity and other functions.
- the above method may include: S401 to S404.
- the source gNB sends a handover request message to the target gNB.
- the handover request message (which may also be called the first message) carries sensing information of the sensing service, and the sensing information is used for the gNB to determine whether to accept the handover.
- the source gNB and the target gNB are associated with the same AMF.
- the Xn interface can be used to implement communication between the source gNB and the target gNB. Therefore, the source gNB can send a handover request message to the target gNB through the Xn interface.
- the source gNB is the base station currently providing services to the UE.
- the UE can move from the coverage area of the source gNB to the coverage area of the target gNB.
- the UE measures the parameters of the source gNB and the target gNB, and reports the measurement report to the source gNB.
- the source gNB can determine to perform handover based on the content in the measurement report. Specific details can be found in the 3GPP TS38.300 standard.
- the handover request message may carry sensing information.
- the sensing information may include at least one of the following: sensing service switching instructions, sensing service requirements, and sensing service configuration parameters.
- the sensing service switching indication may indicate a request to gNB for switching of sensing services.
- the aware service switching indication may be carried in a specific field in the switching request message.
- one bit in the handover request message may be used as a sensing service handover indication. For example, a value of "1" for this bit indicates that switching of the sensing service is requested, and a value of "0" for this bit indicates that switching of the sensing service is not requested.
- the sensing service requirement may be demand information supporting the sensing service.
- the gNB (including the source gNB and the target gNB) that provides services to the UE needs to meet specific software and hardware requirements.
- the sensing service requirements in the sensing information may be the software and hardware requirements of the sensing service itself for the gNB.
- the sensing service configuration parameters may be configuration parameters for the gNB to support the sensing service.
- the sensing service configuration parameters may be configuration parameters of the source gNB for the sensing service.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- the transmission resource configuration information indicates the configuration of resources used by the source gNB to transmit sensing signals.
- the received resource configuration information identifies the configuration of resources used by the source gNB to receive sensing signals.
- the sensing service configuration information indicates the gNB's configuration for supported sensing services.
- the sensing service identification information identifies the sensing service.
- S402 The target gNB determines whether to accept the handover.
- the target gNB can obtain the sensing information from the handover request message, and can determine whether to accept the handover based on the sensing information.
- the target gNB may have sensing capabilities. In this way, the target gNB can determine whether to accept the handover based on the sensing information and sensing capabilities. In an embodiment, the target gNB may compare the sensing capability with the sensing information, and determine whether to accept the handover based on the comparison result. Specifically, if the sensing capability meets the sensing information, the gNB may determine to accept the handover; if the sensing capability does not satisfy the sensing information, the gNB may determine to reject (ie not accept) the handover.
- the sensing information includes sensing service switching instructions and/or sensing service requirements.
- the sensing capability may represent at least one of the following: whether the target gNB supports wireless sensing, and the sensing capability parameters of the target gNB.
- the sensing capability meeting the sensing information may include: the sensing capability indicates that wireless sensing is supported, or the sensing capability indicates that wireless sensing is supported and the sensing service requirements are met.
- the perception information that the perception capability does not meet the requirements may include at least one of the following: the perception capability indicates that wireless perception is not supported, and the perception capability indicates that wireless perception is supported but does not meet the perception service requirements.
- the sensing information may only include service switching indication.
- the target gNB can determine whether to accept the handover based on whether it supports wireless sensing. For example, if the target gNB supports wireless sensing, the gNB determines to accept the handover; if the target gNB does not support wireless sensing, the gNB determines not to accept the handover.
- the sensing information may only include sensing service requirements.
- the target gNB can determine whether to accept the handover based on whether it supports wireless sensing and the sensing capability parameters. For example, if the target gNB does not support wireless sensing, the gNB determines not to accept the handover; if the target gNB supports wireless sensing, but the sensing capability parameters do not meet the sensing service requirements, the gNB determines not to accept the handover; if the target gNB supports wireless sensing, and the sensing capability If the capability parameters meet the sensing service requirements, the gNB determines to accept the handover.
- the sensing information may include service switching indication and sensing service requirements.
- the target gNB determines whether to accept the handover in a manner similar to the case where the sensing information only includes sensing service requirements, which will not be described again here.
- the handover request message may also carry sensing service configuration parameters.
- the target gNB can use the sensing service configuration parameters to subsequently configure the sensing service.
- the source gNB receives a handover request response (handover ACK) message from the target gNB.
- handover ACK handover request response
- the handover request response message (which may also be called the second message) is used to instruct the target gNB to accept or reject the handover.
- the handover request response message may indicate the target gNB to accept the handover.
- the handover request response message may carry a handover command.
- the handover request response message may indicate that the target gNB rejects the handover.
- the target gNB may send a handover request negative response (handover NACK) message to the source gNB.
- handover NACK handover request negative response
- the target gNB may not send any message to the source gNB. That is to say, if the source gNB does not receive the second message from the gNB after sending the handover request message, it implicitly indicates that the target gNB rejects the handover.
- the second message may also carry the reason why the target gNB rejects the handover.
- the reasons may include, for example: the target gNB does not support wireless sensing, the sensing capability parameters of the target gNB do not meet sensing service requirements, etc.
- the source gNB also needs to send the sensing service configuration parameters to the target gNB.
- S404 The source gNB sends the Xn message to the target gNB.
- the Xn message (which may also be called the third message) carries the sensing service configuration parameters.
- S404 is optional. To be precise, the source gNB needs to perform S404 only when the handover request message of S401 does not carry the sensing service configuration parameters.
- the source gNB can know whether the target gNB accepts or rejects the handover, and the target gNB can obtain the sensing service configuration parameters. After the source gNB confirms that the target gNB accepts the handover, the handover process continues. The subsequent handover process can be found in the 3GPP TS23.502 standard.
- FIG. 5 is a schematic interactive flow diagram of another sensing service switching method in an embodiment of the present disclosure. This method can be applied to the N2-based inter-base station handover (inter NG-RAN node N2 based handover) process. As shown in Figure 5, the above method may include: S501 to S510.
- the source gNB sends a handover request (handover required) message to the source AMF.
- the handover request message carries sensing information of the sensing service, and the sensing information is used by the gNB to determine whether to accept the handover.
- the source gNB is the base station currently providing services to the UE.
- the UE can move from the coverage area of the source gNB to the coverage area of the target gNB.
- the UE measures the parameters of the source gNB and the target gNB, and reports the measurement report to the source gNB.
- the source gNB can determine to perform handover based on the content in the measurement report. Specific details can be found in the 3GPP TS38.300 standard.
- the source gNB and the target gNB are associated with different AMFs.
- the AMF that provides services for the source gNB may be called the source AMF
- the AMF that provides services for the target gNB may be called the target AMF.
- a source-to-target transparent container may be carried in the switching request message.
- Awareness information for an awareness service can be contained in a source-target transparent container.
- the source-target transparent container is transparent to the core network functional entity (for example, AMF, SMF or other core network functional entity) that implements communication between the source gNB and the target gNB. This means that these core network functional entities will not read or write content from the source-destination transparent container.
- the handover request message may carry sensing information.
- the sensing information may include at least one of the following: sensing service switching instructions, sensing service requirements, and sensing service configuration parameters.
- the sensing service switching indication may indicate a request to gNB for switching of sensing services.
- the aware service switching indication may be carried in a specific field in the switching request message.
- one bit in the handover request message may be used as a sensing service handover indication. For example, a value of "1" for this bit indicates that switching of the sensing service is requested, and a value of "0" for this bit indicates that switching of the sensing service is not requested.
- the sensing service requirement may be demand information supporting the sensing service.
- the gNB (including the source gNB and the target gNB) that provides services to the UE needs to meet specific software and hardware requirements.
- the sensing service requirements in the sensing information may be the software and hardware requirements of the sensing service itself for the gNB.
- the sensing service configuration parameters may be configuration parameters for the gNB to support the sensing service.
- the sensing service configuration parameters may be configuration parameters of the source gNB for the sensing service.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- the transmission resource configuration information indicates the configuration of resources used by the source gNB to transmit sensing signals.
- the received resource configuration information identifies the configuration of resources used by the source gNB to receive sensing signals.
- the sensing service configuration information indicates the gNB's configuration for supported sensing services.
- the sensing service identification information identifies the sensing service.
- the sent handover request message may also carry identification information of the target gNB.
- the identification information of the target gNB indicates the handover target of the handover request message.
- the source AMF sends a UE context creation request (Namf_Communication_CreateUEContext Request) message to the target AMF.
- the UE context creation request message carries sensing information.
- the source AMF may first determine the target AMF.
- the source AMF can determine the target AMF based on the identification information.
- the UE context creation request message may carry a source-target transparent container.
- the source AMF can directly add the source-target transparent container in the handover request message to the UE context creation request message. Therefore, the sensing information in the source-target transparent container is also carried in the UE context creation request message.
- the UE context creation request message may also carry identification information of the target gNB.
- the target AMF sends a handover request message to the target gNB.
- the handover request message carries sensing information.
- the handover request message may carry a source-target transparent container.
- the target AMF can directly add the source-target transparent container in the UE context creation request message to the handover request message. Therefore, the sensing information in the source-target transparent container is also carried in the handover request message.
- the target AMF can determine the target gNB based on the identification information.
- handover request message sent by the source gNB to the source AMF the UE context creation request message sent by the source AMF to the target AMF, and the handover request message sent by the target AMF to the target gNB are jointly used to carry the handover request message from the source gNB to the target gNB.
- Handover request (can be collectively referred to as the first message).
- the target AMF may send a handover request message to the target gNB through the N2 interface.
- S504 The target gNB determines whether to accept the handover.
- S505 The target gNB sends a handover request acknowledge message to the target AMF.
- the handover request response message is used to instruct the target gNB to accept or reject the handover.
- the handover request response message may be used to instruct the target gNB to receive the handover.
- the handover request response message may indicate that the target gNB rejects the handover.
- the target gNB when the target gNB determines to reject the handover, the target gNB can send a handover request non-acknowledge message to the target AMF.
- the target gNB may not send any message to the target AMF. That is to say, if the target AMF does not receive a handover request response message from the gNB after sending the handover request message, it implicitly indicates that the target gNB rejects the handover.
- the target gNB can send a handover request response message to the target AMF through the N2 interface.
- the target AMF sends a UE context creation response (Namf_Communication_CreateUEContext Response) message to the source AMF.
- the UE context creation response message is used to instruct the target gNB to accept or reject the handover.
- the source AMF sends a handover command message to the source gNB.
- the source AMF determines whether the source gNB accepts the handover.
- the source AMF may send a handover command message to the source gNB through the N2 interface.
- the source AMF sends a handover command message to the source gNB, it means entering the execution stage of handover from the source gNB to the target gNB. Therefore, after the source gNB receives the handover command message from the source AMF, the source gNB can implicitly determine that the target gNB accepts the handover.
- the source AMF may not send the handover command message to the source gNB. If the source gNB cannot receive the handover command message from the source AMF, it can know that the target gNB rejects the handover. In another embodiment, when the source AMF determines that the source gNB does not accept the handover, the source AMF may notify the source gNB through the N2 interface that the target gNB rejects the handover. In addition, the source AMF can also inform the source gNB through the N2 interface of the reason why the target gNB rejects the handover. The reason may include, for example: the target gNB does not support wireless sensing, the sensing capability of the target gNB does not meet the sensing information, and so on.
- the handover request response message sent by the target gNB to the target AMF the UE context creation response message sent by the target AMF to the source AMF, and the handover command message sent by the source AMF to the source gNB are jointly used to carry the target gNB to the source gNB.
- switching request response (can be collectively referred to as the second message).
- the source gNB also needs to send the sensing service configuration parameters to the target gNB.
- S508 The source gNB sends the N2 message to the source AMF.
- S509 The source AMF sends the N14 message to the target AMF.
- the target AMF sends the N2 message to the target gNB.
- the N2 message in S508, the N14 message in S509, and the N2 message in S510 all carry sensing service configuration parameters, and are jointly used to transmit the sensing service configuration parameters from the gNB to the target gNB (which can be collectively referred to as the third party). information).
- the source gNB can know whether the target gNB accepts or rejects the handover, and the target gNB can obtain the sensing service configuration parameters. After the source gNB confirms that the target gNB accepts the handover, the handover process continues. The subsequent handover process can be found in the 3GPP TS23.502 standard.
- the source gNB sends a first message carrying sensing information to the target gNB; the target gNB determines whether to accept the handover based on the sensing information, and sends a second message to the source gNB to indicate whether the target gNB accepts the handover.
- the source gNB can determine the target gNB that supports the sensing service before handover, so that the target gNB still supports the sensing service after the handover, thereby ensuring the continuity of the gNB's support for the sensing service during the handover process.
- embodiments of the present disclosure also provide a service-aware switching method. This method can be applied to the access network functional entity in the above communication system.
- FIG. 6 is a schematic flowchart of a method for switching sensing services in an embodiment of the present disclosure. As shown in Figure 6, the above method includes S601 and S602.
- the first access network functional entity sends the first message to the second access network functional entity.
- the first message carries sensing information of the sensing service, and the sensing information is used by the second access network functional entity to determine whether to accept the handover.
- the first access network functional entity receives the second message.
- the second message is used to instruct the second access network functional entity to accept or reject the handover.
- the operation S601 of the first access network functional entity sending the first message to the second access network functional entity may include: the first access network functional entity transmits the first message to the second access network through the Xn reference point.
- the functional entity sends the first message; or, the first access network functional entity sends the first message to the second access network functional entity through the N2 reference point.
- the first message may be a handover request message.
- the operation S602 of the first access network function entity receiving the second message may include: the first access network function entity receives the second message from the second access network function entity through the Xn reference point; Or, the first access network functional entity receives the second message from the second access network functional entity through the N2 reference point.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the above method may further include: S603, the second An access network functional entity sends a third message to the second access network functional entity, where the third message carries sensing service configuration parameters.
- the operation S603 of the first access network functional entity sending the third message to the second access network functional entity may include: the first access network functional entity sends the third message to the second access network through the Xn reference point.
- the functional entity sends the third message; or, the first access network functional entity sends the third message to the second access network functional entity through the N2 reference point.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- FIG. 7 is a schematic flowchart of another sensing service switching method in an embodiment of the present disclosure. As shown in Figure 7, the above method includes S701 to S703.
- the second access network functional entity receives the first message from the first access network functional entity.
- the first message carries sensing information of the sensing service.
- the second access network functional entity determines whether to accept the handover based on the sensing information and the sensing capability of the second access network functional entity.
- the second access network functional entity sends the second message.
- the second message is used to instruct the second access network functional entity to accept or reject the handover.
- the operation S701 of the second access network functional entity receiving the first message sent from the first access network functional entity may include: the second access network functional entity receives the first message sent from the first access network functional entity through the Xn reference point. The first message from the access network functional entity; or, the second access network functional entity receives the first message from the first access network functional entity through the N2 reference point.
- the first message may be a handover request message.
- the operation S703 of the second access network function entity sending the second message may include: the second access network function entity sends the second message to the first access network function entity through the Xn reference point; Or, the second access network functional entity sends a second message to the first access network functional entity through the N2 reference point.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the operation S702 of the second access network functional entity determining whether to accept the handover based on the sensing information and the sensing capability of the second access network functional entity may include: in the case where the sensing capability satisfies the sensing information, The second access network functional entity determines to accept the handover; or, when the sensing capability does not meet the sensing information, the second access network functional entity determines to reject the handover.
- the perception information that the perception capability meets the requirements may include: the perception capability indicates that wireless perception is supported, or the perception capability indicates that wireless perception is supported and the perception service requirements are met; the perception information that the perception capability does not satisfy may include at least one of the following: perception Capability indicates that wireless sensing is not supported, and awareness capability indicates that wireless sensing is supported but does not meet sensing service requirements.
- the above method may further include: S704, the second access network functional entity determines to accept the switching.
- the network function entity receives a third message from the first access network function entity, where the third message carries sensing service configuration parameters.
- the operation S704 of the second access network function entity receiving the third message from the first access network function entity may include: the second access network function entity receives the third message from the first access network function entity through the Xn reference point. The third message of the network access functional entity; or, the second access network functional entity receives the third message from the first access network functional entity through the N2 reference point.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- the present disclosure embodiments a service-aware switching device.
- the device may be a chip or a system-on-chip in the access network functional entity in the communication system, or may be a functional module in the access network functional entity for implementing the methods described in the above aspects.
- the device can realize the functions performed by the access network functional entity in the above aspects, and these functions can be realized by hardware executing corresponding software.
- These hardware or software include one or more modules corresponding to the above functions.
- FIG. 8 is a schematic structural diagram of a service-aware switching device in an embodiment of the present disclosure.
- the above-mentioned device 800 includes: a sending module 801 configured to send a first message to the second access network functional entity.
- the first message carries sensing information of the sensing service, and the sensing information is used for the second access network.
- the network function entity determines whether to accept the handover; the receiving module 802 is configured to receive a second message, and the second message is used to instruct the second access network function entity to accept or reject the handover.
- the sending module 801 may be configured to: send the first message to the second access network functional entity through the Xn reference point; or, send the first message to the second access network functional entity through the N2 reference point. .
- the first message may be a handover request message.
- the receiving module 802 may be configured to: receive the second message from the second access network functional entity through the Xn reference point; or receive the second message from the second access network functional entity through the N2 reference point. Two messages.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the sending module 801 may also be configured to: in the case where the sensing information includes a sensing service switching indication and/or a sensing service requirement, and the second message indicates that the second access network functional entity accepts the switching, send The second access network functional entity sends a third message, where the third message carries sensing service configuration parameters.
- the sending module 801 may be configured to: send the third message to the second access network functional entity through the Xn reference point; or, send the third message to the second access network functional entity through the N2 reference point. .
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- FIG. 9 is a schematic structural diagram of a service-aware switching device in an embodiment of the present disclosure.
- the above-mentioned device 900 includes: a receiving module 901, which receives a first message from the first access network functional entity, where the first message carries sensing information of the sensing service; and a processing module 902, which receives the sensing information and the second message according to the sensing information and the second message.
- the sensing capability of the access network functional entity determines whether to accept the handover; the sending module 903 sends a second message, and the second message is used to instruct the second access network functional entity to accept or reject the handover.
- the receiving module 901 may be configured to: receive the first message from the first access network functional entity through the Xn reference point; or receive the first message from the first access network functional entity through the N2 reference point. A message.
- the first message may be a handover request message.
- the sending module 903 may be configured to: send the second message to the first access network functional entity through the Xn reference point; or send the second message to the first access network functional entity through the N2 reference point. Two messages.
- the second message may be a handover request response message or a handover command message.
- the sensing information may include at least one of the following: sensing service switching indication, sensing service requirements, and sensing service configuration parameters.
- the processing module 902 may be configured to: determine to accept the switch if the perceptual capability satisfies the perceptual information; or, determine to reject the switch if the perceptual capability does not satisfy the perceptual information.
- the perception information that the perception capability meets the requirements may include: the perception capability indicates that wireless perception is supported, or the perception capability indicates that wireless perception is supported and the perception service requirements are met; the perception information that the perception capability does not satisfy may include at least one of the following: perception Capability indicates that wireless sensing is not supported, and awareness capability indicates that wireless sensing is supported but does not meet sensing service requirements.
- the receiving module 901 may also be configured to: when the sensing information includes sensing service switching indication and/or sensing service requirements, and the second access network functional entity determines to accept the switching, receive the message from the first The third message of the access network functional entity carries the sensing service configuration parameters.
- the receiving module 901 may be configured to: receive the third message from the first access network functional entity through the Xn reference point; or receive the third message from the first access network functional entity through the N2 reference point. Three messages.
- the sensing service configuration parameters may include at least one of the following: transmitting resource configuration information, receiving resource configuration information, sensing service configuration information, and sensing service identification information.
- FIG. 10 is a schematic structural diagram of a communication device in an embodiment of the present disclosure.
- the communication device 1000 uses general computer hardware, including a processor 1001, a memory 1002, a bus 1003, an input device 1004 and an output device 1005.
- memory 1002 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory.
- Memory 1002 may store an operating system, application programs, other program modules, executable code, program data, user data, and the like.
- Input device 1004 may be used to input commands and information to a communication device, such as a keyboard or a pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television dish, scanner, or similar device. These input devices may be connected to processor 1001 via bus 1003.
- a communication device such as a keyboard or a pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television dish, scanner, or similar device.
- processor 1001 may be connected to processor 1001 via bus 1003.
- the output device 1005 can be used for communication devices to output information.
- the output device 1005 can also be other peripheral output devices, such as speakers and/or printing devices. These output devices can also be connected to the processor 1001 through the bus 1003. .
- the communication device may be connected to a network through the antenna 1006, such as a local area network (LAN).
- LAN local area network
- the computer execution instructions stored in the control device can be stored in a remote storage device and are not limited to local storage.
- the communication device executes the sensing service switching method on the access network device in the above embodiment.
- the specific execution process refer to the above embodiment. , which will not be described in detail here.
- the above-mentioned memory 1002 stores computer execution instructions for realizing the functions of the sending module 801 and the receiving module 802 in FIG. 8 .
- the functions/implementation processes of the sending module 801 and the receiving module 802 in Figure 8 can be realized by the processor 1001 in Figure 10 calling the computer execution instructions stored in the memory 1002.
- the processor 1001 in Figure 10 calling the computer execution instructions stored in the memory 1002.
- the above-mentioned memory 1002 stores computer execution instructions for realizing the functions of the receiving module 901, the processing module 902 and the sending module 903 in Figure 9.
- the functions/implementation processes of the receiving module 901, the processing module 902 and the sending module 903 in Figure 9 can all be implemented by the processor 1001 in Figure 10 calling the computer execution instructions stored in the memory 1002.
- the processor 1001 in Figure 10 calling the computer execution instructions stored in the memory 1002.
- embodiments of the present disclosure provide an access network functional entity that is consistent with the access network functional entity in one or more of the above embodiments.
- FIG 11 is a schematic structural diagram of an access network functional entity in an embodiment of the present disclosure.
- the access network functional entity 1100 may include a processing component 1101, which further includes one or more processors, and a memory resource represented by a memory 1102 for storing instructions executable by the processing component 1101, Such as application.
- An application stored in memory 1102 may include one or more modules, each of which corresponds to a set of instructions.
- the processing component 1101 is configured to execute instructions to perform any of the foregoing methods applied to the access network functional entity.
- the access network functional entity 1100 may also include a power supply component 1103 configured to perform power management of the access network functional entity 1100, a wired or wireless network interface 1104 configured to connect the access network functional entity 1100 to the network, and a Input and output (I/O) interface 1105.
- the access network functional entity 1100 may operate based on an operating system stored in the memory 1202, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or similar.
- inventions of the present disclosure also provide an electronic device.
- the electronic device includes: a memory; a processor, connected to the memory, and configured to execute computer-executable instructions stored on the memory to implement sensing on the access network functional entity in one or more of the above embodiments. Service switching method.
- embodiments of the present disclosure also provide a computer-readable storage medium. Instructions are stored in the computer-readable storage medium; when the instructions are run on the computer, they are used to execute the connections in one or more of the above embodiments.
- embodiments of the present disclosure also provide a computer program or computer program product.
- the computer program product When executed on a computer, it causes the computer to implement the access network functional entity in one or more of the above embodiments. Aware service switching method.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
提供了一种感知服务的切换方法和装置、电子设备和存储介质。该方法可以包括:第一接入网功能实体向第二接入网功能实体发送第一消息,第一消息携带有感知服务的感知信息,感知信息用于供第二接入网功能实体确定是否接受切换;第一接入网功能实体接收第二消息,第二消息用于指示第二接入网功能实体接受或拒绝所述切换。以此方式,保证了切换流程中基站对感知服务的支持的连续性。
Description
本公开涉及无线通信技术领域,尤其涉及一种感知服务的切换方法和装置、电子设备和存储介质。
近年来,随着无线技术和感知方法不断发展和相互结合,无线感知(wireless sensing)技术成为研究的热点。特别是,无线感知技术能够与诸如第五代(5G)移动通信技术等通信技术相结合,以基于通信系统提供感知服务。特别是,终端设备的数量越来越庞大,能够覆盖的范围也越来越广。因此,终端设备自然而然地成为无线感知的感知设备,以实现对周围环境的无线感知。
但是,终端设备的位置并不是固定不变的。当终端设备的位置发生变化时,有可能需要对基站进行切换,即从源基站切换到目标基站。由于终端设备在对感知服务进行处理,则在切换时需要考虑目标基站是否支持感知服务。然而,目前的切换流程中对此并不支持。
那么,如何保证切换流程中基站对感知服务的支持的连续性是一个亟待解决的问题。
发明内容
本公开提供了一种感知服务的切换方法和装置、电子设备和存储介质,以实现切换流程中基站对感知服务的支持的连续性。
在第一方面,本公开提供一种感知服务的切换方法,可以应用于第一接入网功能实体。该方法包括:第一接入网功能实体向第二接入网功能实体发送第一消息,第一消息携带有感知服务的感知信息,感知信息用于供第二接入网功能实体确定是否接受切换;第一接入网功能实体接收第二消息,第二消息用于指示第二接入网功能实体接受或拒绝所述切换。
在一些可能的实施方式中,第一接入网功能实体向第二接入网功能实体发送第一消息的操作可以包括:第一接入网功能实体通过Xn参考点向第二接入网功能实体发送第一消息;或,第一接入网功能实体通过N2参考点向第二接入网功能实体发送第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,第一接入网功能实体接收第二消息的操作可以包括:第一接入网功能实体通过Xn参考点接收来自第二接入网功能实体的第二消息;或,第一接入网功能实体通过N2参考点接收来自第二接入网功能实体的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,在感知信息包括感知服务切换指示和/或感知服务需求、并且第二消息指示第二接入网功能实体接受切换的情况下,上述方法还可以包括:第一接入网功能实体向第二接入网功能实体发送第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,第一接入网功能实体向第二接入网功能实体发送第三消息的操作可以包括:第一接入网功能实体通过Xn参考点向第二接入网功能实体发送第三消息;或,第一接入网功能实体通过N2参考点向第二接入网功能实体发送第三消息。
在一些可能的实施方式中,感知业务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
在第二方面,本公开提供一种感知服务的切换方法,可以应用于第二接入网功能实体。该方法包括:第二接入网功能实体接收来自第一接入网功能实体的第一消息,第一消息携带有感知服务的感知信息;第二接入网功能实体根据感知信息和第二接入网功能实体的感知能力,确定是否接受切换;第二接入网功能实体发送第二消息,第二消息用于指示第二接入网功能实体接受或拒绝所述切换。
在一些可能的实施方式中,第二接入网功能实体接收来自第一接入网功能实体发送的第一消息的操作可以包括:第二接入网功能实体通过Xn参考点接收来自第一接入网功能实体的第一消息;或,第二接入网功能实体通过N2参考点接收来自第一接入网功能实体的第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,第二接入网功能实体发送第二消息的操作可以包括:第二接入网功能实体通过Xn参考点向第一接入网功能实体发送的第二消息;或,第二接入网功能实体通过N2参考点向第一接入网功能实体发送的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,第二接入网功能实体根据感知信息和第二接入网功能实体的感知能力,确定是否接受切换的操作可以包括:在感知能力满足感知信息的情况下,第二接入网功能实体确定接受切换;或,在感知能力不满足感知信息的情况下,第二接入网功能实体确定拒绝切换。
在一些可能的实施方式中,感知能力满足感知信息可以包括:感知能力表示支持无线感知,或者感知能力表示支持无线感知且满足感知业务需求;感知能力不满足感知信息可以包括以下至少之一:感知能力表示不支持无线感知,以及感知能力表示支持无线感知但不满足感知业务需求。
在一些可能的实施方式中,在感知信息包括感知服务切换指示和/或感知服务需求、并且第二接入网功能实体确定接受切换的情况下,上述方法还可以包括:第二接入网功能实体接收来自第一接入网功能实体的第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,第二接入网功能实体接收来自第一接入网功能实体的第三消息的操作可以包括:第二接入网功能实体通过Xn参考点接收来自第一接入网功能实体的第三消息;或,第二接入网功能实体通过N2参考点接收来自第一接入网功能实体的第三消息。
在一些可能的实施方式中,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资 源配置信息、感知服务配置信息、感知服务标识信息。
在第三方面,本公开提供一种感知服务的切换装置,设置于第一接入网功能实体。该装置包括:发送模块,配置为向第二接入网功能实体发送第一消息,第一消息携带有感知服务的感知信息,感知信息用于供第二接入网功能实体确定是否接受切换;接收模块,配置为接收第二消息,第二消息用于指示第二接入网功能实体接受或拒绝切换。
在一些可能的实施方式中,发送模块可以配置为:通过Xn参考点向第二接入网功能实体发送第一消息;或,通过N2参考点向第二接入网功能实体发送第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,接收模块可以配置为:通过Xn参考点接收来自第二接入网功能实体的第二消息;或,通过N2参考点接收来自第二接入网功能实体的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,发送模块还可以配置为:在感知信息包括感知服务切换指示和/或感知服务需求、并且第二消息指示第二接入网功能实体接受切换的情况下,向第二接入网功能实体发送第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,发送模块可以配置为:通过Xn参考点向第二接入网功能实体发送第三消息;或,通过N2参考点向第二接入网功能实体发送第三消息。
在一些可能的实施方式中,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
在第四方面,本公开提供一种感知服务的切换装置,设置于第二接入网功能实体。该装置包括:接收模块,接收来自第一接入网功能实体的第一消息,第一消息携带有感知服务的感知信息;处理模块,根据感知信息和第二接入网功能实体的感知能力,确定是否接受切换;发送模块,发送第二消息,第二消息用于指示第二接入网功能实体接受或拒绝切换。
在一些可能的实施方式中,接收模块可以配置为:通过Xn参考点接收来自第一接入网功能实体的第一消息;或,通过N2参考点接收来自第一接入网功能实体的第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,发送模块可以配置为:通过Xn参考点向第一接入网功能实体发送的第二消息;或,通过N2参考点向第一接入网功能实体发送的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,处理模块可以配置为:在感知能力满足感知信息的情况下,确定接受切换;或,在感知能力不满足感知信息的情况下,确定拒绝切换。
在一些可能的实施方式中,感知能力满足感知信息可以包括:感知能力表示支持无线感知,或者感 知能力表示支持无线感知且满足感知服务需求;感知能力不满足感知信息可以包括以下至少之一:感知能力表示不支持无线感知,以及感知能力表示支持无线感知但不满足感知服务需求。
在一些可能的实施方式中,接收模块还可以配置为:在感知信息包括感知服务切换指示和/或感知服务需求、并且第二接入网功能实体确定接受切换的情况下,接收来自第一接入网功能实体的第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,接收模块可以配置为:通过Xn参考点接收来自第一接入网功能实体的第三消息;或,通过N2参考点接收来自第一接入网功能实体的第三消息。
在一些可能的实施方式中,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
在第五方面,本公开提供一种电子设备,包括:存储器;处理器,与存储器连接,被配置为执行存储在存储器上的计算机可执行指令,以实现如第一方面、第二方面及其可能的实施方式中任一项所述的感知服务的切换方法。
在第六方面,本公开提供一种计算机存储介质,该计算机存储介质存储有计算机可执行指令,计算机可执行指令被处理器执行后能够实现如第一方面、第二方面及其可能的实施方式中任一项所述的感知服务的切换方法。
在本公开中,第一接入网功能实体向第二接入网功能实体发送携带有感知信息的第一消息;第二接入网功能实体根据感知信息确定是否接受切换,并且向第一接入网功能实体发送第二消息,以指示第二接入网功能实体是否接受切换。以此方式,第一接入网功能实体能够在切换之前确定支持感知服务的第二接入网功能实体,以便于在切换之后的第二接入网功能实体依然支持感知服务,从而保证了切换流程中基站对感知服务的支持的连续性。
应当理解的是,本公开的第三方面至第六方面与本公开的第一方面至第二方面的技术方案一致,各方面及对应的可行实施方式所取得的有益效果相似,不再赘述。
图1为本公开实施例中的通信系统的结构示意图;
图2为本公开实施例中的非漫游5G网络中使用参考点表示的架构示意图;
图3为本公开实施例中的非漫游5G网络中基于服务化接口的架构示意图;
图4为本公开实施例中的一种感知服务的切换方法的交互流程示意图;
图5为本公开实施例中的另一种感知服务的切换方法的交互流程示意图;
图6为本公开实施例中的一种感知服务的切换方法的流程示意图;
图7为本公开实施例中的另一种感知服务的切换方法的流程示意图;
图8为本公开实施例中的一种感知服务的切换装置的结构示意图;
图9为本公开实施例中的一种感知服务的切换装置的结构示意图;
图10为本公开实施例中的一种通信设备的结构示意图;
图11为本公开实施例中的一种接入网功能实体的结构示意图。
这里将详细地对示例性实施例进行说明,其示例表示在附图中。下面的描述涉及附图时,除非另有表示,不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开实施例相一致的所有实施方式。相反,它们仅是与如所附权利要求书中所详述的、本公开实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的,而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”和“该”也旨在包括多数形式,除非上下文清楚地表示其他含义。还应当理解,本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解,尽管在本公开实施例可能采用术语“第一”、“第二”、“第三”等来描述各种信息,但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如,在不脱离本公开实施例范围的情况下,“第一信息”也可以被称为“第二信息”,类似地,“第二信息”也可以被称为“第一信息”。取决于语境,如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
进一步地,在本公开实施例的描述中,“和/或”仅仅是一种描述关联对象的关联关系,表示可以存在三种关系。例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,在本公开实施例的描述中,“多个”可以指两个或多于两个。
本公开实施例提供一种通信系统。图1为本公开实施例中的通信系统的结构示意图。如图1所示,上述通信系统100可以包括5G接入网(AN)和5G核心网(5GC)。其中,5G接入网可以包括下一代无线接入网(next generation radio access network,NG-RAN)101,NG-RAN 101通过Uu接口与终端设备102通信。5G核心网103可以包括:接入和移动性管理功能(access and mobility management function,AMF)1031、用户面功能(user plane function,UPF)1032、会话管理功能(session management function,SMF)1033、策略控制功能(policy control function,PCF)1034、统一数据管理(unified data management,UDM)1035等。
在本公开实施例中,上述通信系统100还可以包括其他网元,本公开实施例对此不作具体限定。
其中,在上述通信系统中,终端设备102可以通过第三代伙伴计划(3rd generation partnership project,3GPP)技术接入5G核心网。具体的,终端设备可以通过3GPP接入网设备接入5G核心网。
PCF 1034具有策略控制功能,主要负责针对会话、业务流的计费策略、服务质量(quality of service,QoS)带宽保障及策略等相关的策略决策。
SMF 1033具有会话管理功能,主要进行会话管理、PCF 1034下发控制策略的执行、UPF 1032的选择、UE 102的互联网协议(internet protocol,IP)地址分配等功能。
AMF 1031具有接入和移动性管理功能,主要进行移动性管理、接入鉴权/授权等功能。此外,还负责在UE 102与PCF 1034间传递用户策略。
UPF 1032为用户面功能实体,作为和数据网络的接口,完成用户面(UP)数据转发、基于会话/ 流级的计费统计,带宽限制等功能。
其中各接口功能描述如下:
N7:PCF 1034与SMF 1033之间的接口,用于下发分组数据单元(packet data unit,PDU)会话粒度以及业务数据流粒度的控制策略。
N3:UPF 1032与NG-RAN 101之间的通信接口。
N15:PCF 1034与AMF 1031之间的接口,用于下发UE策略及接入控制相关策略。
N4:SMF 1033与UPF 1032之间的接口,用于控制面与UP之间传递信息,包括控制面向UP的转发规则、QoS控制规则、流量统计规则等的下发以及UP的信息上报。
N11:SMF 1033与AMF 1031之间的接口,用于传递NG-RAN 101和UPF 1032之间的PDU会话隧道信息、传递发送给UE 102的控制消息、传递发送给NG-RAN 101的无线资源控制信息等。
N2:AMF 1031与NG-RAN 101之间的接口,用于传递核心网侧至NG-RAN 101的无线承载控制信息等。
N1:AMF 1031与UE 102之间的接口,与接入无关,用于向UE 102传递QoS控制规则等。
N8:AMF 1031与UDM 1035间的接口,用于AMF 1031向UDM 1035获取接入与移动性管理相关签约数据与鉴权数据,以及AMF 1031向UDM 1035注册UE当前移动性管理相关信息等。
N10:SMF 1033与UDM 1035间的接口,用于SMF 1033向UDM 1035获取会话管理相关签约数据,以及SMF 1033向UDM 1035注册UE当前会话相关信息等。
上述终端设备可以是一种具有无线通信功能的终端设备,也可以称为用户设备(user equipment,UE)。终端设备可以部署在陆地上,包括室内或室外、手持、可穿戴或车载;也可以部署在水面上(如轮船等);还可以部署在空中(例如飞机、气球和卫星上等)。上述终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality,VR)终端装置、增强现实(augmented reality,AR)终端装置、工业控制(industrial control)中的无线终端、无人驾驶(self-driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。终端设备也可以是具有无线通信功能的手持设备、车载设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备等。可选的,在不同的网络中终端装置还可以叫做不同的名称,例如:终端装置、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置、蜂窝电话、无绳电话、会话启动协议(session initiation protocol,SIP)电话、无线本地环路(wireless local loop,WLL)站、个人数字处理(personal digital assistant,PDA)、5G网络或未来演进网络中的终端设备等。
上述接入网设备,也称为接入网功能实体,可以为接入网侧用于支持终端接入无线通信系统的设备或功能实体。例如,可以是5G接入技术通信系统中的下一代基站(next generation NodeB,gNB)、发送接收点(transmission reception point,TRP)、中继节点(relay node)、接入点(access point,AP)等。
需要说明的是,在图1所示的通信系统100中,各设备的功能以及接口仅为示例性的,各个设备 在应用于本公开实施例中时,并非全部功能都是必需的。核心网的全部或者部分设备可以是物理上的实体设备,也可以是虚拟化的设备,在此不做限定。当然,本公开实施例中的通信系统还可以包括未在图1中示出的其他设备,在此不做限定。
示例性的,上述通信系统100可以且不限于采用如下架构的5G网络。
第一种,图2为本公开实施例中的非漫游5G网络中使用参考点表示的架构示意图。如图2所示,在非漫游5G网络的核心网中,除了上述AMF、SMF、PCF以及UDM之外,5G核心网还可以包括:用户面功能(user plane function,UPF)、数据网络(data network,DN)、应用功能(application function,AF)、鉴权服务器功能(authentication server function,AUSF)、网络切片选择功能(network slice selection function,NSSF)、特定网络切片身份验证和鉴权功能(network slice-specific and SNPN authentication and authorization function,NSSAAF)、网络切片准入控制功能(network slice admission control function,NSACF)等。其中各接口功能描述如下:N7为SMF与PCF之间的通信接口;N5为PCF与AF之间的通信接口;N6为UPF与DN之间的通信接口;N9为任意两个UPF之间的通信接口;N12为AMF与AUSF之间的通信接口;N22为AMF与NSSF之间的通信接口;N14为任意两个AMF之间的通信接口;N58为AMF与NSSAAF之间的通信接口;N59为NSSAAF与UDM之间的通信接口;N80为NSACF与AMF之前的通信接口;N81为NSACF与SMF之间的通信接口;N13为AUSF与UDM之间的通信接口。PCF与UDR通信。
第二种,图3为本公开实施例中的非漫游5G网络中基于服务化接口的架构示意图。如图3所示,在非漫游5G网络的核心网中,各个网元之间采用服务化接口进行交互。例如,NSSAAF、AUSF、AMF、SMF、NSACF、NSSF、网络开放功能(network exposure function,NEF)、网络存储库功能(network repository function,NRF)、PCF、UDM或者AF采用服务化接口进行交互。其中,NSSAAF对外提供的服务化接口可以为Nnssaaf,ASUF对外提供的服务化接口可以为Nausf,AMF对外提供的服务化接口可以为Namf,SMF对外提供的服务化接口可以为Nsmf,NSACF对外提供的服务化接口可以为Nnsacf。NSSF对外提供的服务化接口可以为Nnssf,NEF对外提供的服务化接口可以为Nnef,NRF对外提供的服务化接口可以为Nnrf,PCF对外提供的服务化接口可以为Npcf,UDM对外提供的服务化接口可以为Nudm,AF对外提供的服务化接口可以为Naf。
可选的,仍参见图3所示,5G核心网中还可以部署服务通信代理(service communication proxy,SCP),可以用于网络功能(network function,NF)与网络功能服务(NF service)之间的间接通信。
应理解的,图2和图3中各种服务化接口的名称的相关描述可以参考3GPP TS 23.501标准中的5G系统架构(5G system architecture)图,在此不予赘述。
近年来,随着无线技术和感知方法不断发展和相互结合,无线感知(wireless sensing)技术成为研究的热点。特别是,无线感知技术能够与诸如第五代(5G)移动通信技术等通信技术相结合,以基于通信系统提供感知服务。
特别是,终端设备的数量越来越庞大,能够覆盖的范围也越来越广。因此,终端设备自然而然地成为无线感知的感知设备,以实现对周围环境的无线感知。在终端设备进行针对感知服务的无线感知的情况下,基站需要作为感知服务节点来支持该感知服务。例如,基站可以实现无线感知数据在终端设备 与核心网设备之间的通信。当然,基站还可能为感知服务提供其他支持。
终端设备的位置并不是固定不变的。当终端设备的位置发生变化时,有可能需要对基站进行切换,即从源基站切换到目标基站。由于终端设备在对感知服务进行处理,则在切换时需要考虑目标基站是否支持感知服务,以此确认切换的目标基站是支持感知服务的。
那么,如何保证切换流程中基站对感知服务的支持的连续性是一个亟待解决的问题。
为了解决上述问题,本公开实施例提供一种感知服务的切换方法,该通信方法可以应用于上述通信系统中。示例性的,终端设备可以为UE,第一接入网功能实体可以为源gNB,第二接入网功能实体可以为目标gNB,第一核心网功能实体可以为源AMF,第二核心网功能实体可以为目标AMF。
图4为本公开实施例中的一种感知服务的切换方法的交互流程示意图。该方法可以应用于基于Xn的基站间切换(Xn based inter NG-RAN handover)流程。
Xn接口是定义在5G网络中的两个gNB之间的接口,用于为NG-RAN提供互联。Xn接口可以包括Xn用户面(Xn-U)接口和Xn控制面(Xn-C)接口。Xn-U接口用于提供用户面PDU的无保障交付,并能够支持数据转发、流量控制等功能。Xn-C接口用于提供信令PDU的点对点传输,并能够支持Xn接口管理、移动性管理、双连接等功能。
如图4所示,上述方法可以包括:S401至S404。
S401,源gNB向目标gNB发送切换请求(handover request)消息。
其中,切换请求消息(也可以称为第一消息)携带有感知服务的感知信息,该感知信息用于供gNB确定是否接受切换。
可以理解的,源gNB与目标gNB关联到同一个AMF。在此情况下,源gNB与目标gNB之间存在Xn接口(也可以称为Xn参考点)。Xn接口可以用于实现源gNB和目标gNB之间的通信。由此,源gNB可以通过Xn接口向目标gNB发送切换请求消息。
需要说明的是,源gNB是当前为UE提供服务的基站。当UE的位置发生变化时,UE可以从源gNB的覆盖范围移动到目标gNB的覆盖范围。此时,UE对源gNB和目标gNB的参数进行测量,并向源gNB上报测量报告。源gNB则可以根据测量报告中的内容,确定进行切换。具体的细节可以参见3GPP TS38.300标准。
为了实现切换,切换请求消息可以携带有感知信息。感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。感知服务切换指示可以表示向gNB请求感知服务的切换。感知服务切换指示可以携带在切换请求消息中的特定字段内。在一实施例中,切换请求消息中的一个比特可以用作感知服务切换指示。例如,该比特取值为“1”则表示请求感知服务的切换,而该比特取值为“0”则表示不请求感知服务的切换。感知服务需求可以是支持感知服务的需求信息。虽然感知服务的无线感知是由UE进行的,但是为了对该感知服务进行支持,为UE提供服务的gNB(包括源gNB和目标gNB)需要满足特定的软硬件要求。例如,感知信息中的感知服务需求可以是感知服务自身对gNB的软硬件要求。感知服务配置参数可以是gNB支持感知服务的配置参数。例如,感知服务配置参数可以是源gNB针对感知服务的配置参数。
更具体地,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感 知服务配置信息、感知服务标识信息。发射资源配置信息表示源gNB用于发送感知信号的资源的配置。接收资源配置信息标识源gNB用于接收感知信号的资源的配置。感知服务配置信息表示gNB针对支持的感知服务的配置。感知服务标识信息对感知服务进行标识。
S402,目标gNB确定是否接受切换。
可以理解的,在S401中接收到切换请求消息后,目标gNB可以从切换请求消息中得到感知信息,并可以根据感知信息确定是否接受切换。
其中,目标gNB可以具有感知能力。如此,目标gNB可以根据感知信息和感知能力确定是否接受切换。在一实施例中,目标gNB可以将感知能力与感知信息进行比较,并根据比较结果确定是否接受切换。具体地,若感知能力满足感知信息,则gNB可以确定接受切换;若感知能力不满足感知信息,则gNB可以确定拒绝(即不接受)切换。
感知信息中包含感知服务切换指示和/或感知服务需求。感知能力可以表示以下至少之一:目标gNB是否支持无线感知、目标gNB的感知能力参数。如此,感知能力满足感知信息可以包括:感知能力表示支持无线感知,或者感知能力表示支持无线感知且满足感知业务需求。并且,感知能力不满足感知信息可以包括以下至少之一:感知能力表示不支持无线感知,以及感知能力表示支持无线感知但不满足感知业务需求。
在一实施例中,感知信息可以仅包括服务切换指示。此时,目标gNB可以根据自身是否支持无线感知来确定是否接受切换。例如,若目标gNB支持无线感知,则gNB确定接受切换;若目标gNB不支持无线感知,则gNB确定不接受切换。
在一实施例中,感知信息可以仅包括感知服务需求。此时,目标gNB可以根据自身是否支持无线感知、以及感知能力参数来确定是否接受切换。例如,若目标gNB不支持无线感知,则gNB确定不接受切换;若目标gNB支持无线感知、但感知能力参数不满足感知服务需求,则gNB确定不接受切换;若目标gNB支持无线感知、且感知能力参数满足感知服务需求,则gNB确定接受切换。
在一实施例中,感知信息可以包括服务切换指示和感知服无需求。此时,目标gNB确定是否接受切换的方式可以与感知信息仅包括感知服务需求的情况类似,在此不再赘述。
可以理解的,切换请求消息中还可以携带有感知服务配置参数。如此,目标gNB可以使用感知服务配置参数后续进行针对感知服务的配置。
S403,源gNB接收来自目标gNB的切换请求应答(handover ACK)消息。
其中,切换请求应答消息(也可以称为第二消息)用于指示目标gNB接受或拒绝切换。
在一实施例中,切换请求应答消息可以指示目标gNB接受切换。在此情况下,切换请求应答消息可以携带有切换命令(handover command)。在一实施例中,切换请求应答消息可以指示目标gNB拒绝切换。
作为切换请求应答的替选,在目标gNB确定拒绝切换的情况下,目标gNB可以向源gNB发送切换请求否定应答(handover NACK)消息。又或者,在目标gNB确定拒绝切换的情况下,目标gNB也可以不向源gNB发送任何消息。也就是说,若源gNB在发送切换请求消息之后并未接收到来自gNB的第二消息,则隐含表示目标gNB拒绝切换。
在一实施例中,在目标gNB确定拒绝切换的情况下,第二消息还可以携带有目标gNB拒绝切换的原因。该原因例如可以包括:目标gNB不支持无线感知、目标gNB的感知能力参数不满足感知服务需求等。
需要说明的是,在S401的切换请求消息中不携带感知服务配置参数的情况下,在S403之后,源gNB还需要将感知服务配置参数发送给目标gNB。
S404,源gNB向目标gNB发送Xn消息。
其中,Xn消息(也可以称为第三消息)中携带有感知服务配置参数。
可以理解的,S404是可选的。准确来说,只有在S401的切换请求消息中不携带感知服务配置参数的情况下,源gNB才需要执行S404。
至此,通过S401至S404,源gNB能够得知目标gNB接受或拒绝切换,并且目标gNB能够获得感知服务配置参数。在源gNB确认目标gNB接受切换之后,继续切换流程。后续的切换流程可以参见3GPP TS23.502标准。
图5为本公开实施例中的另一种感知服务的切换方法的交互流程示意图。该方法可以应用于基于N2的基站间切换(inter NG-RAN node N2 based handover)流程。如图5所示,上述方法可以包括:S501至S510。
S501,源gNB向源AMF发送切换请求(handover required)消息。
其中,切换请求消息携带有感知服务的感知信息,该感知信息用于供gNB确定是否接受切换。
需要说明的是,源gNB是当前为UE提供服务的基站。当UE的位置发生变化时,UE可以从源gNB的覆盖范围移动到目标gNB的覆盖范围。此时,UE对源gNB和目标gNB的参数进行测量,并向源gNB上报测量报告。源gNB则可以根据测量报告中的内容,确定进行切换。具体的细节可以参见3GPP TS38.300标准。
可以理解的,源gNB与目标gNB关联到不同的AMF。具体地,为源gNB提供服务的AMF可以称为源AMF,为目标gNB提供服务的AMF可以称为目标AMF。在从源gNB切换到目标gNB时,也需要从源AMF切换到目标AMF。在此情况下,源gNB和目标gNB之间不存在Xn接口,则源gNB和目标gNB之间的通信需要通过N2接口(也可以称为N2参考点)并经由源AMF和目标AMF实现。由此,源gNB可以经由N2接口向源AMF发送切换请求消息。
在一实施例中,发送切换请求消息中可以携带有源-目标透明容器(source to target transparent container)。感知服务的感知信息可以包含在源-目标透明容器中。需要说明的是,源-目标透明容器对于实现源gNB和目标gNB之间通信的核心网功能实体(例如,AMF、SMF或其他核心网功能实体)是透明的。这意味着这些核心网功能实体不会对源-目标透明容器进行内容的读取或写入。
为了实现切换,切换请求消息可以携带有感知信息。感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。感知服务切换指示可以表示向gNB请求感知服务的切换。感知服务切换指示可以携带在切换请求消息中的特定字段内。在一实施例中,切换请求消息中的一个比特可以用作感知服务切换指示。例如,该比特取值为“1”则表示请求感知服务的切换,而该比特取值为“0”则表示不请求感知服务的切换。感知服务需求可以是支持感知服务的需求信息。虽然感知服务 的无线感知是由UE进行的,但是为了对该感知服务进行支持,为UE提供服务的gNB(包括源gNB和目标gNB)需要满足特定的软硬件要求。例如,感知信息中的感知服务需求可以是感知服务自身对gNB的软硬件要求。感知服务配置参数可以是gNB支持感知服务的配置参数。例如,感知服务配置参数可以是源gNB针对感知服务的配置参数。
更具体地,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。发射资源配置信息表示源gNB用于发送感知信号的资源的配置。接收资源配置信息标识源gNB用于接收感知信号的资源的配置。感知服务配置信息表示gNB针对支持的感知服务的配置。感知服务标识信息对感知服务进行标识。
在一实施例中,发送切换请求消息中还可以携带有目标gNB的标识信息。目标gNB的标识信息表示切换请求消息的切换目标。
S502,源AMF向目标AMF发送UE上下文创建请求(Namf_Communication_CreateUEContext Request)消息。
其中,UE上下文创建请求消息携带有感知信息。
可以理解的,在源AMF发送UE上下文创建请求消息之前,源AMF可以先确定目标AMF。在一示例中,源AMF获取目标gNB的标识信息之后,源AMF可以根据标识信息确定目标AMF。
在一实施例中,UE上下文创建请求消息中可以携带有源-目标透明容器。例如,源AMF在接收到来自源gNB的切换请求消息之后,可以直接将切换请求消息中的源-目标透明容器加入到UE上下文创建请求消息中。因此,源-目标透明容器中的感知信息也携带在UE上下文创建请求消息中。
在一实施例中,UE上下文创建请求消息中还可以携带有目标gNB的标识信息。
S503,目标AMF向目标gNB发送切换请求消息。
其中,切换请求消息携带有感知信息。
在一实施例中,切换请求消息中可以携带有源-目标透明容器。例如,目标AMF在接收到来自源AMF的UE上下文创建请求消息之后,可以直接将UE上下文创建请求消息中的源-目标透明容器加入到切换请求消息中。因此,源-目标透明容器中的感知信息也携带在切换请求消息中。
可以理解的,在UE上下文创建请求消息中携带有目标gNB的标识信息的情况下,目标AMF可以根据标识信息确定目标gNB。
需要说明的是,源gNB向源AMF发送的切换请求消息、源AMF向目标AMF发送的UE上下文创建请求消息、以及目标AMF向目标gNB发送的切换请求消息共同用于承载源gNB向目标gNB的切换请求(可以统称为第一消息)。
在一实施例中,目标AMF可以通过N2接口向目标gNB发送切换请求消息。
S504,目标gNB确定是否接受切换。
需要说明的是,S504的实现方式与S402的实现方式相同。因此,可以参考前文中对S402的说明,并且在此不再赘述。
S505,目标gNB向目标AMF发送切换请求应答(handover request acknowledge)消息。
其中,切换请求应答消息用于指示目标gNB接收或拒绝切换。
在一实施例中,切换请求应答消息可以用于指示目标gNB接收切换。在一实施例中,切换请求应答消息可以指示目标gNB拒绝切换。
需要说明的是,作为切换请求应答的替选,在目标gNB确定拒绝切换的情况下,目标gNB可以向目标AMF发送切换请求否定应答(handover request non-acknowledge)消息。又或者,在目标gNB确定拒绝切换的情况下,目标gNB也可以不向目标AMF发送任何消息。也就是说,若目标AMF在发送切换请求消息之后并未接收到来自gNB的切换请求应答消息,则隐含表示目标gNB拒绝切换。
可以理解的,目标gNB可以通过N2接口向目标AMF发送切换请求应答消息。
S506,目标AMF向源AMF发送UE上下文创建响应(Namf_Communication_CreateUEContext Response)消息。
其中,UE上下文创建响应消息用于指示目标gNB接收或拒绝切换。
S507,源AMF向源gNB发送切换命令(handover command)消息。
其中,在S506之后,源AMF确定源gNB是否接受切换。
在一实施例中,在源AMF确定源gNB接收切换的情况下,源AMF可以通过N2接口向源gNB发送切换命令消息。
需要说明的是,源AMF向源gNB发送切换命令消息,则意味着进入到从源gNB到目标gNB的切换的执行阶段。因此,源gNB接收到来自源AMF的切换命令消息之后,源gNB能够隐含确定目标gNB接受切换。
在一实施例中,在源AMF确定源gNB不接受切换的情况下,源AMF可以不向源gNB发送切换命令消息。源gNB接收不到来自源AMF的切换命令消息,则可以知晓目标gNB拒绝切换。在另一实施例中,在源AMF确定源gNB不接受切换的情况下,源AMF可以通过N2接口向源gNB告知目标gNB拒绝切换。此外,源AMF还可以通过N2接口向源gNB告知目标gNB拒绝切换的原因。该原因例如可以包括:目标gNB不支持无线感知、目标gNB的感知能力不满足感知信息等。
需要说明的是,目标gNB向目标AMF发送的切换请求应答消息、目标AMF向源AMF发送的UE上下文创建响应消息、以及源AMF向源gNB发送的切换命令消息共同用于承载目标gNB向源gNB的切换请求响应(可以统称为第二消息)。
需要说明的是,在S503的切换请求消息中不携带感知服务配置参数的情况下,在S507之后,源gNB还需要将感知服务配置参数发送给目标gNB。
S508,源gNB向源AMF发送N2消息。
S509,源AMF向目标AMF发送N14消息。
S510,目标AMF向目标gNB发送N2消息。
可以理解的,S508中的N2消息、S509中的N14消息、以及S510中的N2消息均携带有感知服务配置参数,共同用于将感知服务配置参数从gNB传输至目标gNB(可以统称为第三消息)。
至此,通过S501至S510,源gNB能够得知目标gNB接受或拒绝切换,并且目标gNB能够获得感知服务配置参数。在源gNB确认目标gNB接受切换之后,继续切换流程。后续的切换流程可以参见3GPP TS23.502标准。
在本公开实施例中,源gNB向目标gNB发送携带有感知信息的第一消息;目标gNB根据感知信息确定是否接受切换,并且向源gNB发送第二消息,以指示目标gNB是否接受切换。以此方式,源gNB能够在切换之前确定支持感知服务的目标gNB,以便于在切换之后的目标gNB依然支持感知服务,从而保证了切换流程中gNB对感知服务的支持的连续性。
基于相同的发明构思,本公开实施例还提供一种感知服务的切换方法。该方法可以应用于上述通信系统中的接入网功能实体。
图6为本公开实施例中的一种感知服务的切换方法的流程示意图。如图6所示,上述方法包括S601和S602。
S601,第一接入网功能实体向第二接入网功能实体发送第一消息。
其中,第一消息携带有感知服务的感知信息,感知信息用于供第二接入网功能实体确定是否接受切换。
S602,第一接入网功能实体接收第二消息。
其中,第二消息用于指示第二接入网功能实体接受或拒绝所述切换。
在一些可能的实施方式中,第一接入网功能实体向第二接入网功能实体发送第一消息的操作S601可以包括:第一接入网功能实体通过Xn参考点向第二接入网功能实体发送第一消息;或,第一接入网功能实体通过N2参考点向第二接入网功能实体发送第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,第一接入网功能实体接收第二消息的操作S602可以包括:第一接入网功能实体通过Xn参考点接收来自第二接入网功能实体的第二消息;或,第一接入网功能实体通过N2参考点接收来自第二接入网功能实体的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,在感知信息包括感知服务切换指示和/或感知服务需求、并且第二消息指示第二接入网功能实体接受切换的情况下,上述方法还可以包括:S603,第一接入网功能实体向第二接入网功能实体发送第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,第一接入网功能实体向第二接入网功能实体发送第三消息的操作S603可以包括:第一接入网功能实体通过Xn参考点向第二接入网功能实体发送第三消息;或,第一接入网功能实体通过N2参考点向第二接入网功能实体发送第三消息。
在一些可能的实施方式中,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
图7为本公开实施例中的另一种感知服务的切换方法的流程示意图。如图7所示,上述方法包括S701至S703。
S701,第二接入网功能实体接收来自第一接入网功能实体的第一消息。
其中,第一消息携带有感知服务的感知信息。
S702,第二接入网功能实体根据感知信息和第二接入网功能实体的感知能力,确定是否接受切换。
S703,第二接入网功能实体发送第二消息。
其中,第二消息用于指示第二接入网功能实体接受或拒绝所述切换。
在一些可能的实施方式中,第二接入网功能实体接收来自第一接入网功能实体发送的第一消息的操作S701可以包括:第二接入网功能实体通过Xn参考点接收来自第一接入网功能实体的第一消息;或,第二接入网功能实体通过N2参考点接收来自第一接入网功能实体的第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,第二接入网功能实体发送第二消息的操作S703可以包括:第二接入网功能实体通过Xn参考点向第一接入网功能实体发送的第二消息;或,第二接入网功能实体通过N2参考点向第一接入网功能实体发送的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,第二接入网功能实体根据感知信息和第二接入网功能实体的感知能力,确定是否接受切换的操作S702可以包括:在感知能力满足感知信息的情况下,第二接入网功能实体确定接受切换;或,在感知能力不满足感知信息的情况下,第二接入网功能实体确定拒绝切换。
在一些可能的实施方式中,感知能力满足感知信息可以包括:感知能力表示支持无线感知,或者感知能力表示支持无线感知且满足感知服务需求;感知能力不满足感知信息可以包括以下至少之一:感知能力表示不支持无线感知,以及感知能力表示支持无线感知但不满足感知服务需求。
在一些可能的实施方式中,在感知信息包括感知服务切换指示和/或感知服务需求、并且第二接入网功能实体确定接受切换的情况下,上述方法还可以包括:S704,第二接入网功能实体接收来自第一接入网功能实体的第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,第二接入网功能实体接收来自第一接入网功能实体的第三消息的操作S704可以包括:第二接入网功能实体通过Xn参考点接收来自第一接入网功能实体的第三消息;或,第二接入网功能实体通过N2参考点接收来自第一接入网功能实体的第三消息。
在一些可能的实施方式中,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
基于相同的发明构思,本公开实施例一种感知服务的切换装置。该装置可以为上述通信系统中的接入网功能实体中的芯片或者片上系统,还可以为接入网功能实体中用于实现上述各个方面所述的方法的功能模块。该装置可以实现上述各方面中接入网功能实体所执行的功能,这些功能可以通过硬件执行相应的软件实现。这些硬件或软件包括一个或多个上述功能相应的模块。
图8为本公开实施例中的一种感知服务的切换装置的结构示意图。如图8所示,上述装置800包括:发送模块801,配置为向第二接入网功能实体发送第一消息,第一消息携带有感知服务的感知信息,感知信息用于供第二接入网功能实体确定是否接受切换;接收模块802,配置为接收第二消息,第二消息用于指示第二接入网功能实体接受或拒绝切换。
在一些可能的实施方式中,发送模块801可以配置为:通过Xn参考点向第二接入网功能实体发送第一消息;或,通过N2参考点向第二接入网功能实体发送第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,接收模块802可以配置为:通过Xn参考点接收来自第二接入网功能实体的第二消息;或,通过N2参考点接收来自第二接入网功能实体的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,发送模块801还可以配置为:在感知信息包括感知服务切换指示和/或感知服务需求、并且第二消息指示第二接入网功能实体接受切换的情况下,向第二接入网功能实体发送第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,发送模块801可以配置为:通过Xn参考点向第二接入网功能实体发送第三消息;或,通过N2参考点向第二接入网功能实体发送第三消息。
在一些可能的实施方式中,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
图9为本公开实施例中的一种感知服务的切换装置的结构示意图。如图9所示,上述装置900包括:接收模块901,接收来自第一接入网功能实体的第一消息,第一消息携带有感知服务的感知信息;处理模块902,根据感知信息和第二接入网功能实体的感知能力,确定是否接受切换;发送模块903,发送第二消息,第二消息用于指示第二接入网功能实体接受或拒绝切换。
在一些可能的实施方式中,接收模块901可以配置为:通过Xn参考点接收来自第一接入网功能实体的第一消息;或,通过N2参考点接收来自第一接入网功能实体的第一消息。
在一些可能的实施方式中,第一消息可以为切换请求消息。
在一些可能的实施方式中,发送模块903可以配置为:通过Xn参考点向第一接入网功能实体发送的第二消息;或,通过N2参考点向第一接入网功能实体发送的第二消息。
在一些可能的实施方式中,第二消息可以为切换请求应答消息或切换命令消息。
在一些可能的实施方式中,感知信息可以包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
在一些可能的实施方式中,处理模块902可以配置为:在感知能力满足感知信息的情况下,确定接受切换;或,在感知能力不满足感知信息的情况下,确定拒绝切换。
在一些可能的实施方式中,感知能力满足感知信息可以包括:感知能力表示支持无线感知,或者感知能力表示支持无线感知且满足感知服务需求;感知能力不满足感知信息可以包括以下至少之一:感知能力表示不支持无线感知,以及感知能力表示支持无线感知但不满足感知服务需求。
在一些可能的实施方式中,接收模块901还可以配置为:在感知信息包括感知服务切换指示和/或感知服务需求、并且第二接入网功能实体确定接受切换的情况下,接收来自第一接入网功能实体的第三消息,第三消息携带有感知服务配置参数。
在一些可能的实施方式中,接收模块901可以配置为:通过Xn参考点接收来自第一接入网功能实体的第三消息;或,通过N2参考点接收来自第一接入网功能实体的第三消息。
在一些可能的实施方式中,感知服务配置参数可以包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
基于相同的发明构思,本公开实施例提供一种通信设备,该通信设备可以为上述一个或者多个实施例中所述的接入网功能实体。图10为本公开实施例中的一种通信设备的结构示意图。如图10所示,通信设备1000,采用了通用的计算机硬件,包括处理器1001、存储器1002、总线1003、输入设备1004和输出设备1005。
在一些可能的实施方式中,存储器1002可以包括以易失性和/或非易失性存储器形式的计算机存储媒体,如只读存储器和/或随机存取存储器。存储器1002可以存储操作系统、应用程序、其他程序模块、可执行代码、程序数据、用户数据等。
输入设备1004可以用于向通信设备输入命令和信息,输入设备1004如键盘或指向设备,如鼠标、轨迹球、触摸板、麦克风、操纵杆、游戏垫、卫星电视天线、扫描仪或类似设备。这些输入设备可以通过总线1003连接至处理器1001。
输出设备1005可以用于通信设备输出信息,除了监视器之外,输出设备1005还可以为其他外围输出设各,如扬声器和/或打印设备,这些输出设备也可以通过总线1003连接到处理器1001。
通信设备可以通过天线1006连接到网络中,例如连接到局域网(local area network,LAN)。在联网环境下,控制备中存储的计算机执行指令可以存储在远程存储设备中,而不限于在本地存储。
当通信设备中的处理器1001执行存储器1002中存储的可执行代码或应用程序时,通信设备以执行以上实施例中的接入网设备上的感知服务的切换方法,具体执行过程参见上述实施例,在此不再赘述。
此外,上述存储器1002中存储有用于实现图8中的发送模块801和接收模块802的功能的计算机执行指令。图8中的发送模块801和接收模块802的功能/实现过程均可以通过图10中的处理器1001调用存储器1002中存储的计算机执行指令来实现,具体实现过程和功能参考上述相关实施例。
再者,上述存储器1002中存储有用于实现图9中的接收模块901、处理模块902和发送模块903的功能的计算机执行指令。图9中的接收模块901、处理模块902和发送模块903的功能/实现过程均可以通过图10中的处理器1001调用存储器1002中存储的计算机执行指令来实现,具体实现过程和功能参考上述相关实施例。
基于相同的发明构思,本公开实施例提供一种接入网功能实体,该接入网功能实体与上述一个或者多个实施例中的接入网功能实体一致。
图11为本公开实施例中的一种接入网功能实体的结构示意图。如图11所示,接入网功能实体1100可以包括处理组件1101,其进一步包括一个或多个处理器,以及由存储器1102所代表的存储器资源,用于存储可由处理组件1101的执行的指令,例如应用程序。存储器1102中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外,处理组件1101被配置为执行指令,以执行上述方法前述应用在所述接入网功能实体的任一方法。
接入网功能实体1100还可以包括一个电源组件1103被配置为执行接入网功能实体1100的电源管 理,一个有线或无线网络接口1104被配置为将接入网功能实体1100连接到网络,和一个输入输出(I/O)接口1105。接入网功能实体1100可以操作基于存储在存储器1202的操作系统,例如Windows Server TM,Mac OS XTM,UnixTM,LinuxTM,FreeBSDTM或类似。
基于相同的发明构思,本公开实施例还提供一种电子设备。该电子设备包括:存储器;处理器,与所述存储器连接,被配置为执行存储在所述存储器上的计算机可执行指令,以实现上述一个或者多个实施例中接入网功能实体上的感知服务的切换方法。
基于相同的发明构思,本公开实施例还提供一种计算机可读存储介质,计算机可读存储介质中存储有指令;当指令在计算机上运行时,用于执行上述一个或者多个实施例中接入网功能实体上的感知服务的切换方法。
基于相同的发明构思,本公开实施例还提供一种计算机程序或计算机程序产品,当计算机程序产品在计算机上被执行时,使得计算机实现上述一个或者多个实施例中接入网功能实体上的感知服务的切换方法。
本领域技术人员在考虑说明书及实践这里公开的发明后,将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化,这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的,本发明的真正范围和精神由下面的权利要求指出。
应当理解的是,本发明并不局限于上面已经描述并在附图中示出的精确结构,并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。
Claims (24)
- 一种感知服务的切换方法,包括:第一接入网功能实体向第二接入网功能实体发送第一消息,所述第一消息携带有感知服务的感知信息,所述感知信息用于供所述第二接入网功能实体确定是否接受切换;所述第一接入网功能实体接收第二消息,所述第二消息用于指示所述第二接入网功能实体接受或拒绝所述切换。
- 根据权利要求1所述的方法,其中,所述第一接入网功能实体向第二接入网功能实体发送第一消息,包括:所述第一接入网功能实体通过Xn参考点向所述第二接入网功能实体发送所述第一消息;或,所述第一接入网功能实体通过N2参考点向所述第二接入网功能实体发送所述第一消息。
- 根据权利要求2所述的方法,其中,所述第一消息为切换请求消息。
- 根据权利要求1所述的方法,其中,所述第一接入网功能实体接收第二消息,包括:所述第一接入网功能实体通过Xn参考点接收来自所述第二接入网功能实体的所述第二消息;或,所述第一接入网功能实体通过N2参考点接收来自所述第二接入网功能实体的所述第二消息。
- 根据权利要求4所述的方法,其中,所述第二消息为切换请求应答消息或切换命令消息。
- 根据权利要求1所述的方法,其中,所述感知信息包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
- 根据权利要求6所述的方法,其中,在所述感知信息包括感知服务切换指示和/或感知服务需求、并且所述第二消息指示所述第二接入网功能实体接受所述切换的情况下,所述方法还包括:所述第一接入网功能实体向所述第二接入网功能实体发送第三消息,所述第三消息携带有所述感知服务配置参数。
- 根据权利要求7所述的方法,其中,所述第一接入网功能实体向所述第二接入网功能实体发送第三消息,包括:所述第一接入网功能实体通过Xn参考点向所述第二接入网功能实体发送所述第三消息;或,所述第一接入网功能实体通过N2参考点向所述第二接入网功能实体发送所述第三消息。
- 根据权利要求6所述的方法,其中,所述感知服务配置参数包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
- 一种感知服务的切换方法,包括:第二接入网功能实体接收来自第一接入网功能实体的第一消息,所述第一消息携带有感知服务的感知信息;所述第二接入网功能实体根据所述感知信息和所述第二接入网功能实体的感知能力,确定是否接受切换;所述第二接入网功能实体发送第二消息,所述第二消息用于指示所述第二接入网功能实体接受或拒绝所述切换。
- 根据权利要求10所述的方法,其中,所述第二接入网功能实体接收来自第一接入网功能实体 发送的第一消息,包括:所述第二接入网功能实体通过Xn参考点接收来自所述第一接入网功能实体的所述第一消息;或,所述第二接入网功能实体通过N2参考点接收来自所述第一接入网功能实体的所述第一消息。
- 根据权利要求11所述的方法,其中,所述第一消息为切换请求消息。
- 根据权利要求10所述的方法,其中,所述第二接入网功能实体发送第二消息,包括:所述第二接入网功能实体通过Xn参考点向所述第一接入网功能实体发送的所述第二消息;或,所述第二接入网功能实体通过N2参考点向所述第一接入网功能实体发送的所述第二消息。
- 根据权利要求13所述的方法,其中,所述第二消息为切换请求应答消息或切换命令消息。
- 根据权利要求10所述的方法,其中,所述感知信息包括以下至少之一:感知服务切换指示、感知服务需求、感知服务配置参数。
- 根据权利要求15所述的方法,其中,所述第二接入网功能实体根据所述感知信息和所述第二接入网功能实体的感知能力,确定是否接受切换,包括:在所述感知能力满足所述感知信息的情况下,所述第二接入网功能实体确定接受所述切换;或,在所述感知能力不满足所述感知信息的情况下,所述第二接入网功能实体确定拒绝所述切换。
- 根据权利要求16所述的方法,其中,所述感知能力满足所述感知信息包括:所述感知能力表示支持无线感知,或者所述感知能力表示支持无线感知且满足所述感知业务需求;所述感知能力不满足所述感知信息包括以下至少之一:所述感知能力表示不支持无线感知,以及所述感知能力表示支持无线感知但不满足所述感知业务需求。
- 根据权利要求15所述的方法,其中,在所述感知信息包括感知服务切换指示和/或感知服务需求、并且所述第二接入网功能实体确定接受所述切换的情况下,所述方法还包括:所述第二接入网功能实体接收来自所述第一接入网功能实体的第三消息,所述第三消息携带有所述感知服务配置参数。
- 根据权利要求18所述的方法,其中,所述第二接入网功能实体接收来自所述第一接入网功能实体的第三消息,包括:所述第二接入网功能实体通过Xn参考点接收来自所述第一接入网功能实体的所述第三消息;或,所述第二接入网功能实体通过N2参考点接收来自所述第一接入网功能实体的所述第三消息。
- 根据权利要求15所述的方法,其中,所述感知服务配置参数包括以下至少之一:发射资源配置信息、接收资源配置信息、感知服务配置信息、感知服务标识信息。
- 一种感知服务的切换装置,包括:发送模块,配置为向第二接入网功能实体发送第一消息,所述第一消息携带有感知服务的感知信息,所述感知信息用于供所述第二接入网功能实体确定是否接受切换;接收模块,配置为接收第二消息,所述第二消息用于指示所述第二接入网功能实体接受或拒绝所述切换。
- 一种感知服务的切换装置,包括:接收模块,配置为接收来自第一接入网功能实体的第一消息,所述第一消息携带有感知服务的感知 信息;处理模块,配置为根据所述感知信息和所述第二接入网功能实体的感知能力,确定是否接受切换;发送模块,配置为发送第二消息,所述第二消息用于指示所述第二接入网功能实体接受或拒绝所述切换。
- 一种通信装置,包括:存储器;处理器,与所述存储器连接,被配置为执行存储在所述存储器上的计算机可执行指令,以实现如权利要求1至6、或者权利要求7至14中任一项所述的感知服务的切换方法。
- 一种计算机存储介质,所述计算机存储介质存储有计算机可执行指令,其特征在于,所述计算机可执行指令被处理器执行后能够实现如权利要求1至6、或者权利要求7至14中任一项所述的感知服务的切换方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202280002558.6A CN117678270A (zh) | 2022-07-07 | 2022-07-07 | 感知服务的切换方法和装置、电子设备和存储介质 |
PCT/CN2022/104474 WO2024007271A1 (zh) | 2022-07-07 | 2022-07-07 | 感知服务的切换方法和装置、电子设备和存储介质 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/104474 WO2024007271A1 (zh) | 2022-07-07 | 2022-07-07 | 感知服务的切换方法和装置、电子设备和存储介质 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2024007271A1 true WO2024007271A1 (zh) | 2024-01-11 |
Family
ID=89454556
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/104474 WO2024007271A1 (zh) | 2022-07-07 | 2022-07-07 | 感知服务的切换方法和装置、电子设备和存储介质 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN117678270A (zh) |
WO (1) | WO2024007271A1 (zh) |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101296481A (zh) * | 2007-04-27 | 2008-10-29 | 华为技术有限公司 | 一种网络切换方法、装置及系统 |
CN102761929A (zh) * | 2012-07-09 | 2012-10-31 | 中兴通讯股份有限公司 | Ims会话切换实现方法和接入切换控制功能 |
US20140010167A1 (en) * | 2011-01-19 | 2014-01-09 | Philip Hodges | Local Data Bi-Casting Between Core Network and Radio Access |
CN109219098A (zh) * | 2012-08-07 | 2019-01-15 | 华为技术有限公司 | 切换处理方法及基站 |
CN114554562A (zh) * | 2022-04-14 | 2022-05-27 | 中国联合网络通信集团有限公司 | 邻区切换方法、装置、基站及存储介质 |
-
2022
- 2022-07-07 CN CN202280002558.6A patent/CN117678270A/zh active Pending
- 2022-07-07 WO PCT/CN2022/104474 patent/WO2024007271A1/zh active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101296481A (zh) * | 2007-04-27 | 2008-10-29 | 华为技术有限公司 | 一种网络切换方法、装置及系统 |
US20140010167A1 (en) * | 2011-01-19 | 2014-01-09 | Philip Hodges | Local Data Bi-Casting Between Core Network and Radio Access |
CN102761929A (zh) * | 2012-07-09 | 2012-10-31 | 中兴通讯股份有限公司 | Ims会话切换实现方法和接入切换控制功能 |
CN109219098A (zh) * | 2012-08-07 | 2019-01-15 | 华为技术有限公司 | 切换处理方法及基站 |
CN114554562A (zh) * | 2022-04-14 | 2022-05-27 | 中国联合网络通信集团有限公司 | 邻区切换方法、装置、基站及存储介质 |
Also Published As
Publication number | Publication date |
---|---|
CN117678270A (zh) | 2024-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2017133231A1 (zh) | 一种传输路径的切换方法、终端和系统 | |
WO2022016948A1 (zh) | 一种通信方法及装置 | |
WO2020155906A1 (zh) | 一种通信系统切换方法、网络侧设备、装置和介质 | |
WO2021218563A1 (zh) | 用于传输数据的方法与装置 | |
WO2021238882A1 (zh) | 一种实现业务连续性的方法及装置 | |
EP4354770A1 (en) | Method and apparatus for transmitting data | |
WO2021218832A1 (zh) | 传输设备接入网络的方法、装置、设备及存储介质 | |
WO2022017403A1 (zh) | 通信方法及装置 | |
WO2024007271A1 (zh) | 感知服务的切换方法和装置、电子设备和存储介质 | |
WO2024020760A1 (zh) | 一种QoS流的控制方法、装置及计算机存储介质 | |
CN117769825A (zh) | 一种QoS流的控制方法、装置及计算机存储介质 | |
WO2024050838A1 (zh) | 一种通信方法及装置 | |
EP4274301A1 (en) | Communication method and apparatus | |
EP4408067A1 (en) | Indication information transmission method, message transmission method, and related apparatus | |
WO2022222736A1 (zh) | 业务处理方法、装置、系统、可读取存储介质和电子设备 | |
WO2024000435A1 (zh) | 物联网设备的管理方法、装置、设备和存储介质 | |
WO2024032552A1 (zh) | 通信方法、装置及存储介质 | |
WO2024000445A1 (zh) | 一种QoS流的控制方法、装置及计算机存储介质 | |
WO2022227587A1 (zh) | 共享业务的建立方法及相关产品 | |
WO2023125723A1 (zh) | 协作通信方法及装置、计算机可读存储介质 | |
WO2022151252A1 (zh) | 接入网络的方法和装置 | |
WO2023160332A1 (zh) | 一种干扰规避方法及相关装置 | |
WO2023087262A1 (zh) | 通信方法及通信装置 | |
WO2023245458A1 (zh) | 一种信息上报方法、装置及计算机存储介质 | |
US20240340709A1 (en) | Communication method and apparatus |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 202280002558.6 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 22949855 Country of ref document: EP Kind code of ref document: A1 |