WO2024078580A1 - 非紧急业务的处理方法及装置 - Google Patents

非紧急业务的处理方法及装置 Download PDF

Info

Publication number
WO2024078580A1
WO2024078580A1 PCT/CN2023/124259 CN2023124259W WO2024078580A1 WO 2024078580 A1 WO2024078580 A1 WO 2024078580A1 CN 2023124259 W CN2023124259 W CN 2023124259W WO 2024078580 A1 WO2024078580 A1 WO 2024078580A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobility restriction
remote terminal
emergency service
pdu session
message
Prior art date
Application number
PCT/CN2023/124259
Other languages
English (en)
French (fr)
Inventor
邓强
Original Assignee
大唐移动通信设备有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 大唐移动通信设备有限公司 filed Critical 大唐移动通信设备有限公司
Publication of WO2024078580A1 publication Critical patent/WO2024078580A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present application relates to the field of communication technology, and in particular to a method and device for processing non-emergency services.
  • the Proximity Service (ProSe) standard project defines a Layer-2 UE-to-Network Relay architecture, in which a remote terminal (Layer-2 Remote UE) can connect to the network for communication through a relay terminal (Layer-2 Relay UE). Furthermore, relevant technologies stipulate that when the relay terminal is subject to mobility restrictions (Mobility Restriction), it will not be able to provide relay services for the non-emergency services (non-Emergency services) of the remote terminal.
  • Mobility Restriction Mobility Restriction
  • Relay terminals restricted by mobility restrictions cannot provide relay services for non-emergency protocol data unit (PDU) sessions of remote terminals. At this time, how to handle the non-emergency services of remote terminals becomes an urgent problem that needs to be solved.
  • PDU protocol data unit
  • the embodiments of the present application provide a method and device for processing non-emergency services, so as to solve the problem in the related art that when a relay terminal is unable to relay non-emergency services for the remote terminal due to mobility restrictions, there is a lack of solutions for processing non-emergency services for the remote terminal.
  • an embodiment of the present application provides a method for processing a non-emergency service, which is applied to a first device, including:
  • PDU non-emergency service protocol data unit
  • the first device is the remote terminal, and the second device is the relay terminal;
  • the receiving the mobility restriction indication information sent by the second device includes:
  • the mobility restriction indication information is received through a direct communication message sent by the second device.
  • the direct communication message includes any one of the following:
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined not to initiate the non-emergency service PDU session or it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • the first message or the second message includes the mobility restriction indication information.
  • the first device is an access and mobility management AMF entity corresponding to the remote terminal
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • a third message for releasing the non-emergency service PDU session is sent to the SMF entity corresponding to the remote terminal, wherein the third message carries the first PDU session identifier.
  • an embodiment of the present application provides a method for processing a non-emergency service, which is applied to a second device, including:
  • the mobility restriction indication information is used to indicate the mobility restriction state of the relay terminal; the mobility restriction state of the relay terminal is used by the first device to determine whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal.
  • the method further includes:
  • the second device refuses to establish the non-emergency service requested by the remote terminal.
  • the mobility restriction indication information is determined based on mobility restriction information, and the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.
  • an embodiment of the present application further provides a first device, including a memory, a transceiver, and a processor, wherein:
  • a memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the method for processing non-emergency services as described in the first aspect above.
  • the first device is the remote terminal, and the second device is the relay terminal;
  • the receiving the mobility restriction indication information sent by the second device includes:
  • the mobility restriction indication information is received through a direct communication message sent by the second device.
  • the direct communication message includes any one of the following:
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined not to initiate the non-emergency service PDU session or it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • the first message or the second message includes the mobility restriction indication information.
  • the first device is an access and mobility management AMF entity corresponding to the remote terminal
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • a third message for releasing the non-emergency service PDU session is sent to the SMF entity corresponding to the remote terminal, wherein the third message carries the first PDU session identifier.
  • an embodiment of the present application further provides a first device, including a memory, a transceiver, and a processor, wherein:
  • a memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and implementing the method for processing non-emergency services as described in the second aspect above.
  • the method further includes:
  • the second device refuses to establish the non-emergency service requested by the remote terminal.
  • the mobility restriction indication information is determined based on mobility restriction information, and the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.
  • an embodiment of the present application further provides a non-emergency service processing device, which is applied to a first device, including:
  • a first receiving unit configured to receive mobility restriction indication information sent by a second device, wherein the mobility restriction indication information is used to indicate a mobility restriction state of the relay terminal;
  • the first determining unit is used to determine whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal.
  • PDU non-emergency service protocol data unit
  • the first device is the remote terminal, and the second device is the relay terminal;
  • the first receiving unit is configured to receive the mobility restriction indication information sent by the second device, including:
  • the first receiving unit is configured to receive the mobility restriction indication information through a direct communication message sent by the second device.
  • the direct communication message includes any one of the following:
  • the first determining unit is used to determine whether to initiate or release a non-emergency service protocol data unit (PDU) session of the remote terminal based on the mobility restriction state of the relay terminal, including:
  • the first determining unit is configured to determine not to initiate the non-emergency service PDU session or to determine to release the non-emergency service PDU session when the mobility restriction state of the relay terminal is a restricted state.
  • the device further includes a first sending unit
  • the first sending unit is used to send a first message to the session management function SMF entity corresponding to the remote terminal after determining to release the non-emergency service PDU session, wherein the first message is used to instruct the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session;
  • the first sending unit is used to send a second message to the AMF entity corresponding to the remote terminal after determining to release the non-emergency service PDU session, wherein the second message is used to instruct the AMF entity corresponding to the remote terminal to trigger the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session;
  • the first message or the second message includes the mobility restriction indication information.
  • the first device is an access and mobility management AMF entity corresponding to the remote terminal
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal
  • the first determining unit is used to determine whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal, including:
  • the first determining unit is configured to determine to release the non-emergency service PDU session when the mobility restriction state of the relay terminal is a restricted state.
  • the first determining unit is further configured to determine, after determining to release the non-emergency service PDU session, a first PDU session identifier corresponding to the non-emergency service PDU session based on the mobility restriction indication information and the PDU session information corresponding to the remote terminal;
  • the first sending unit is also used to send a third message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal, and the third message carries the first PDU session identifier.
  • an embodiment of the present application further provides a non-emergency service processing device, which is applied to a second device, including:
  • a second sending unit configured to send mobility restriction indication information to the first device
  • the mobility restriction indication information is used to indicate the mobility restriction state of the relay terminal; the mobility restriction state of the relay terminal is used by the first device to determine whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal.
  • the device further includes a second receiving unit and a second determining unit;
  • the second receiving unit is configured to receive the identifier of the remote terminal sent by the relay terminal;
  • the second determination unit is used to determine the AMF entity corresponding to the remote terminal based on the identifier of the remote terminal.
  • the device further comprises a second rejection unit
  • the second rejecting unit is used to reject the establishment of the non-emergency service requested by the remote terminal when the mobility restriction state of the relay terminal is a restricted state and the relay terminal receives a non-emergency service establishment request message sent by the remote terminal.
  • the mobility restriction indication information is determined based on mobility restriction information, and the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.
  • an embodiment of the present application also provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the non-emergency business processing method described in the first aspect or the non-emergency business processing method described in the second aspect.
  • the non-emergency service processing method and device provided in the embodiment of the present application enable the first device to obtain the mobility restriction status of the relay terminal through the mobility restriction indication information, thereby determining the corresponding operation according to the mobility restriction status of the relay terminal, and can solve the problem that the non-emergency service PDU session of the remote terminal cannot be processed when the remote terminal is connected to the relay terminal with mobility restriction.
  • FIG1 is a schematic diagram of a network architecture provided by the present application.
  • FIG2 is a flow chart of a method for processing non-emergency services provided in an embodiment of the present application
  • FIG3 is a second flow chart of a method for processing non-emergency services provided in an embodiment of the present application
  • FIG4 is a third flow chart of a method for processing non-emergency services provided in an embodiment of the present application.
  • FIG5 is a fourth flow chart of a method for processing non-emergency services provided in an embodiment of the present application.
  • FIG6 is a flowchart of a method for processing non-emergency services according to an embodiment of the present application.
  • FIG. 7 is a flowchart of a sixth method for processing non-emergency services provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of a structure of a non-emergency service processing device according to an embodiment of the present application.
  • FIG. 9 is a second structural diagram of a non-emergency service processing device provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of the structure of a first device provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of the structure of the second device provided in an embodiment of the present application.
  • the term "and/or” describes the association relationship of the associated objects, indicating that there may be three relationships.
  • a and/or B may represent: A exists alone, A and B exist at the same time, and B exists alone.
  • the character "/” generally indicates that the associated objects before and after are in an "or” relationship.
  • the term “plurality” refers to two or more than two, and other quantifiers are similar.
  • the applicable system can be the global system of mobile communication (GSM) system, the code division multiple access (CDMA) system, the broadband Wideband Code Division Multiple Access (WCDMA), general packet radio service (GPRS) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, long term evolution advanced (LTE-A) system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) system, 5G New Radio (NR) system, etc.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA broadband Wideband Code Division Multiple Access
  • GPRS general packet radio service
  • LTE long term evolution
  • FDD LTE frequency division duplex
  • TDD LTE time division duplex
  • LTE-A long term evolution advanced
  • UMTS universal mobile telecommunication system
  • WiMAX worldwide interoperability for microwave access
  • NR 5G New Radio
  • the terminal device involved in the embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem.
  • the name of the terminal device may also be different.
  • the terminal device may be called a user equipment (UE).
  • the wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN).
  • CN core networks
  • RAN radio access network
  • the wireless terminal device can be a mobile terminal device, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal device.
  • the wireless terminal device can be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited to these in the embodiments of the present application.
  • the network device involved in the embodiments of the present application may be a base station, which may include multiple cells providing services for terminals.
  • a base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface.
  • the network device may be used to convert received air frames to and from Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communications network.
  • IP Internet Protocol
  • the network device may also coordinate the management of attributes of the air interface.
  • the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (Global System for Mobile communications, GSM) or Code Division Multiple Access (Code Division Multiple Access, CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (evolutional Node B, eNB or e-NodeB) in the long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (Home evolved Node B, HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application.
  • the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographical
  • Network devices and terminal devices can each use one or more antennas for multiple input multiple output (MIMO) transmission.
  • MIMO transmission can be single user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO).
  • MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoded transmission or beamforming transmission, etc.
  • Layer-2 UE-to-Network Relay architecture defines the Layer-2 UE-to-Network Relay architecture and related processes.
  • a UE When a UE is out of network coverage or the Uu interface signal is poor, it cannot directly connect to the network. It can connect to the network through a UE with relay function.
  • the former is called Layer-2 Remote UE.
  • the Remote UE can be connected to its own NG-RAN and core network through the Relay UE.
  • FIG1 is a schematic diagram of a process of Layer-2 Remote UE communicating with a network through Layer-2 Relay UE according to an embodiment of the present application.
  • the process of Layer-2 Remote UE communicating with a network through Layer-2 Relay UE includes:
  • Relay UE can be a ProSe UE-to-Network Relay.
  • Service Authorization retrieval When connected to the network, the Remote UE and Relay UE obtain the strategy and parameters for Proximity Service (ProSe) from the network. If the Remote UE is not connected to the network, the pre-configured parameters can be used.
  • ProSe Proximity Service
  • Discovery and selection (UE-to-Network Relay discovery and selection): Remote UE and Relay UE perform a discovery process, and Remote UE selects the Relay UE with which to communicate.
  • PC5 communication and establishment PC5 connection for communication is established between Remote UE and Relay UE.
  • Access Stratum connection setup (AS connection setup): The Remote UE establishes an RRC connection with the access network, which is the same as the service access network of the Relay UE.
  • the access network can be the Next Generation Radio Access Network (NG-RAN).
  • NG-RAN Next Generation Radio Access Network
  • UE-to-Network Relay triggered Service Request If the Relay UE is in the IDLE state and receives the Radio Resource Control (RRC) connection request from the Remote UE, the Relay UE initiates the Service Request process to enter the connected state.
  • RRC Radio Resource Control
  • Non-Access Stratum connection setup (NAS connection setup): The Remote UE sends a NAS message to the Access and Mobility Management Function (AMF) entity corresponding to the Remote UE (not the Remote UE's AMF in the figure).
  • the NAS message is encapsulated in the RRC message.
  • the RRC message is transmitted through PC5
  • the interface is sent to the Relay UE, and the Relay UE forwards the RRC message to the access network.
  • the access network selects an AMF for the Remote UE and forwards the NAS message to the AMF.
  • the NAS message can be one of the Initial Registration message, Service Request message, Mobility Registration message, or Periodic Registration message.
  • PDU session establishment procedure (PDU Session Establishment procedure): Remote UE initiates the PDU session establishment procedure.
  • the data of Remote UE is transmitted between Remote UE and UPF through Relay UE and NG-RAN.
  • PCF Policy Control Function
  • SMF Session Management Function
  • UPF User Plane Function
  • Mobility Restriction restricts the mobility processing and service access of UE, including Forbidden Area, Service Area Restriction, etc. In the forbidden area, UE is not allowed to initiate any communication to the network. Service area restriction includes Allowed Area and Non-Allowed Area. In the allowed area, UE is allowed to initiate communication to the network; in the non-allowed area, UE is not allowed to initiate processes related to data transmission (such as service request Service Request). It is worth noting that when the UE performs emergency services, it will not be restricted by the above-mentioned Mobility Restriction.
  • the relevant technology defines the applicable scenarios of mobility restriction in R17 relay scenarios.
  • the Relay UE When the Relay UE is in a forbidden area or a non-allowed area, the Relay UE cannot perform relay operations (i.e., it cannot perform relay discovery and relay communication processes).
  • the Relay UE When the Relay UE is in a mobility restricted state, it can still provide relay services for the emergency services of the Remote UE, but cannot provide relay services for non-emergency services.
  • a Relay UE with mobility restrictions can provide relay services for emergency services of the Remote UE, but cannot provide relay services for non-emergency services.
  • the method for processing non-emergency services provided in the embodiment of the present application can solve the problem of how to process the non-emergency service PDU session of the remote terminal when the remote terminal is connected to the relay terminal and the relay terminal is under mobility restriction.
  • FIG. 2 is one of the flow charts of the method for processing non-emergency services provided in an embodiment of the present application. As shown in FIG. 2 , an embodiment of the present application provides a method for processing non-emergency services, which can be applied to a first device, including:
  • Step 210 receiving mobility restriction indication information sent by the second device, where the mobility restriction indication information is used to indicate a mobility restriction state of the relay terminal;
  • the first device refers to a device that can process non-emergency service protocol data unit (PDU) sessions of a remote terminal, and the processing may include initiating a session or releasing a session.
  • PDU non-emergency service protocol data unit
  • the second device refers to a device that can determine or obtain mobility restriction indication information and can send the mobility restriction indication information to the first device.
  • the mobility restriction indication information refers to information used to indicate the mobility restriction state of the relay terminal.
  • the mobility restriction indication information may indicate that the mobility restriction state of the relay terminal is in the Forbidden Area, Allowed Area, or Non-Allowed Area.
  • the mobility restriction indication information may indicate the mobility restriction state of the relay terminal in the form of a mobility restriction indicator.
  • a mobility restriction indicator For example, when the value of the mobility restriction indicator is 1, it indicates that the mobility restriction state of the relay terminal is a state in which non-emergency services can be provided to the remote terminal, such as the mobility restriction state of the relay terminal is Allowed Area; when the value of the mobility restriction indicator is 0, it indicates that the mobility restriction state of the relay terminal is a state in which non-emergency services cannot be provided to the remote terminal, such as the mobility restriction state of the relay terminal is Forbidden Area or Non-Allowed Area. Area.
  • Step 220 Determine whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal.
  • PDU non-emergency service protocol data unit
  • the first device may perform any of the following operations:
  • the non-emergency service PDU session of the remote terminal In the case where the non-emergency service PDU session of the remote terminal has been established, the non-emergency service PDU session of the remote terminal is maintained, or the non-emergency service PDU session of the remote terminal is not processed.
  • the remote terminal determines whether the remote terminal has any non-emergency services that need to be executed. If the remote terminal needs to establish a non-emergency service PDU session and the mobility restriction state of the relay terminal can support non-emergency service relaying for the remote terminal, the non-emergency service PDU session of the remote terminal is initiated, maintained, or not processed.
  • the first device may perform any of the following operations:
  • a non-emergency service PDU session that does not initiate a remote terminal may point to a network function entity, such as an SMF entity corresponding to the remote terminal, and does not send a non-emergency service PDU session establishment request, or cancels the non-emergency service PDU session establishment request that is being sent.
  • a network function entity such as an SMF entity corresponding to the remote terminal
  • the method for processing non-emergency services provided in the embodiments of the present application can be applied to relay scenarios, such as the Layer-2 UE-to-Network Relay scenario introduced above.
  • the method for processing non-emergency services uses mobility restriction indication information This enables the first device to learn the mobility restriction status of the relay terminal, thereby determining the corresponding operation according to the mobility restriction status of the relay terminal, and can solve the problem of being unable to process the non-emergency service PDU session of the remote terminal when the remote terminal is connected to the relay terminal with mobility restriction.
  • the relay terminal can support emergency services.
  • the first device is the remote terminal
  • the second device is the relay terminal
  • the first device is a remote terminal
  • the second device is a relay terminal that establishes direct communication with the remote terminal.
  • the receiving the mobility restriction indication information sent by the second device includes:
  • the mobility restriction indication information is received through a direct communication message sent by the second device.
  • the first device is a remote terminal
  • the second device is a relay terminal
  • the remote terminal and the relay terminal can communicate through direct discovery messages.
  • the direct communication message includes any one of the following:
  • a relay discovery message is a direct communication message sent during the discovery process.
  • the discovery process in direct communication may include two modes: mode A and mode B:
  • the relay terminal sends a broadcast Announcement message during the discovery process of the A mode (it should be understood that the broadcast message is a direct communication message), and the broadcast message carries the mobility restriction indication information.
  • the remote terminal sends a Solicitation message, which is used to request the relay terminal that receives the request message to return a Response message carrying mobility restriction indication information to the remote terminal; after receiving the request message, the relay terminal returns a Response message carrying mobility restriction indication information to the remote terminal.
  • the acceptance message means that a PC5 is established between the Remote UE and the Relay UE.
  • the Remote UE sends a Direct Communication Request message to the Relay UE, and the Relay UE returns a Direct Communication Accept message to the Remote UE, which includes mobility restriction indication information.
  • the mobility restriction indication information may be referred to as Mobility restriction indication. It should be understood that the embodiment of the present application does not limit the name of the mobility restriction indication information, as long as it can be used to indicate the mobility restriction status of the relay terminal.
  • the status notification message refers to a direct communication message sent by the Remote UE to the Relay UE to notify the relay terminal of the mobility restriction status after a PC5 connection is established between the Remote UE and the Relay UE.
  • the message contains mobility restriction indication information.
  • the method for processing non-emergency services provided in the embodiment of the present application sends mobility restriction indication information to the remote terminal through a direct communication message, so that the remote terminal can learn the mobility restriction status of the relay terminal, thereby solving the problem that the remote terminal cannot learn the mobility restriction status of the relay terminal and cannot process non-emergency services.
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined not to initiate the non-emergency service PDU session or it is determined to release the non-emergency service PDU session.
  • the restricted state refers to the Not Allowed Area, including the Forbidden Area and the Non-Allowed Area.
  • the relay terminal in the restricted state cannot provide non-emergency services to the remote terminal.
  • the method for processing non-emergency services enables the relay terminal to obtain the mobility restriction status of the relay terminal through mobility restriction indication information, so as to determine, based on the mobility restriction status of the relay terminal, not to initiate the non-emergency service PDU session or to determine to release the non-emergency service PDU session when the mobility restriction status of the relay terminal is in a restricted state, thereby solving the problem that the non-emergency service PDU session of the remote terminal cannot be processed when the remote terminal is connected to the relay terminal under mobility restriction.
  • the relay terminal since the relay terminal is in a mobility-restricted state, it is unable to provide relay for the non-emergency service PDU session of the remote terminal, which may cause the remote terminal to initiate a non-emergency service PDU session.
  • the remote terminal has been waiting for the relay terminal to transmit non-emergency business data.
  • the relay terminal is unable to provide non-emergency business data due to mobility restrictions.
  • the remote terminal does not initiate a non-emergency business PDU session or releases a non-emergency business PDU session. This can avoid the remote terminal waiting for data transmission for a long time and avoid non-emergency business PDU sessions occupying resources, thereby saving resources.
  • the step further includes:
  • the first device sends a first message to the session management function SMF entity corresponding to the remote terminal, where the first message is used to instruct the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session; or,
  • the first device sends a second message to the AMF entity corresponding to the remote terminal, and the second message is used to instruct the AMF entity corresponding to the remote terminal to trigger the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session.
  • a first message may be sent by the remote terminal to an SMF entity corresponding to the remote terminal
  • a second message may be sent by the remote terminal to an AMF entity corresponding to the remote terminal.
  • the first message may carry a PDU session ID corresponding to a non-emergency service PDU session, and the first message may be a PDU session release request message.
  • the session management function SMF entity corresponding to the remote terminal releases the non-emergency service PDU session according to the first message.
  • the non-emergency service PDU session corresponding to the PDU session ID is released.
  • the second message may be a non-access layer NAS message.
  • the Remote UE sends the second message to the AMF entity corresponding to the Remote UE.
  • the AMF entity corresponding to the Remote UE identifies the non-emergency service PDU session ID according to the second message, and triggers the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session.
  • the AMF entity corresponding to the remote terminal may send a PDU session release message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal.
  • the method for processing non-emergency services can solve the problem of how to release the non-emergency service PDU session of the remote terminal when the remote terminal is connected to a relay terminal with mobility restrictions, when the first device is a remote terminal and the second device is a relay terminal.
  • the first message or the second message includes the mobility restriction indication information.
  • the mobility restriction indication information can indicate the mobility restriction state of the message (first message or second message) receiver relay terminal, thereby triggering the message receiver to release the non-emergency service PDU session.
  • the first message or the second message includes mobility restriction indication information
  • the mobility restriction indication information indicates that the mobility restriction state of the relay terminal is a restricted state.
  • the message recipient can know that the relay terminal is in a restricted state, thereby triggering the message recipient to release the non-emergency service PDU session.
  • the AMF entity corresponding to the remote terminal receives the mobility restriction indication information sent by the remote terminal, and the AMF entity corresponding to the remote terminal can determine the mobility restriction status of the relay terminal based on the mobility restriction indication information, and determine that the mobility restriction status of the relay terminal does not support non-emergency services; the AMF entity corresponding to the remote terminal determines the PDU session identifier corresponding to the non-emergency service PDU session in the PDU session information corresponding to the remote terminal.
  • the PDU session information corresponding to the remote terminal may be determined based on the context of the remote terminal, where the context of the remote terminal is pre-acquired by the AMF entity corresponding to the remote terminal;
  • the AMF entity corresponding to the remote terminal can send a message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal.
  • the message may carry the PDU session identifier corresponding to the non-emergency service PDU session.
  • the SMF releases the non-emergency service PDU session corresponding to the PDU session identifier corresponding to the non-emergency service PDU session.
  • the first device is an access and mobility management AMF entity corresponding to the remote terminal
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal.
  • the AMF entity corresponding to the relay terminal is used to manage the mobility information of the relay terminal, so the mobility restriction status of the relay terminal can be obtained, so that the mobility restriction indication information can be determined and the mobility restriction indication information can be sent to the first device (the AMF entity corresponding to the remote terminal).
  • the relay terminal and the remote terminal can access the same access network, so when the access network entity can obtain the mobility restriction status of the relay terminal, determine the mobility restriction indication information, and send the mobility restriction indication information to the first device (the AMF entity corresponding to the remote terminal).
  • determining whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined to release the non-emergency service PDU session.
  • the determining to release the non-emergency service PDU session also includes:
  • a third message for releasing the non-emergency service PDU session is sent to the SMF entity corresponding to the remote terminal, wherein the third message carries the first PDU session identifier.
  • the first device is capable of determining the mobility restriction state of the relay terminal based on the mobility restriction indication information, and determines that the mobility restriction state of the relay terminal does not support non-emergency services;
  • the PDU session identifier corresponding to the non-emergency service PDU session is used as the first PDU session identifier
  • a third message for releasing the non-emergency service PDU session is sent to the SMF entity corresponding to the remote terminal, and the third message carries the first PDU session identifier. After receiving the third message, the SMF releases the non-emergency service PDU session corresponding to the first PDU session identifier.
  • the PDU session information corresponding to the remote terminal may be determined according to the context of the remote terminal.
  • the method for processing non-emergency services can solve the problem of how to release the non-emergency service session of the remote terminal when the remote terminal is connected to a relay terminal with mobility restrictions, when the first device is the access and mobility management AMF entity corresponding to the remote terminal and the second device is the access network entity or the AMF entity corresponding to the relay terminal.
  • FIG3 is a second flow chart of a method for processing non-emergency services provided in an embodiment of the present application. As shown in FIG3 , an embodiment of the present application provides a method for processing non-emergency services, which can be applied to a second device, including:
  • the mobility restriction indication information is used to indicate the mobility restriction state of the relay terminal; the mobility restriction state of the relay terminal is used by the first device to determine whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal.
  • the method for processing non-emergency services provided in the embodiment of the present application sends mobility restriction indication information to the first device, so that the first device can obtain the mobility restriction status of the relay terminal, thereby determining the corresponding operation according to the mobility restriction status of the relay terminal, and can solve the problem that the non-emergency service PDU session of the remote terminal cannot be processed when the remote terminal is connected to the relay terminal with mobility restriction.
  • the second device is the relay terminal.
  • sending the mobility restriction indication information to the first device includes: sending a direct communication message carrying the mobility restriction indication information to the first device.
  • the direct communication message includes any one of the following:
  • direct communication messages for the introduction of direct communication messages, relay discovery messages, direct communication acceptance messages and status notification messages, please refer to the above introduction and will not be repeated here.
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal.
  • the method further includes:
  • the AMF entity corresponding to the relay terminal can receive the identifier of the remote terminal, and determine the AMF entity corresponding to the remote terminal through the identifier of the remote terminal, thereby sending mobility restriction indication information to the AMF entity corresponding to the remote terminal.
  • the second device refuses to establish the non-emergency service requested by the remote terminal.
  • the relay terminal when the relay terminal is in mobility restriction, if the remote terminal indicates to the relay terminal that it is establishing a non-emergency service, the relay terminal will reject the remote terminal's request and inform the remote terminal that the relay terminal is currently in a mobility restriction state, i.e., send mobility restriction indication information to the remote terminal.
  • the second device is an access network entity or the AMF entity corresponding to the relay terminal rejects non-emergency services requested by the remote terminal, please refer to the introduction in this article and related technologies and will not be repeated here.
  • the method for processing non-emergency services can enable the relay terminal to reject the establishment of non-emergency services when the remote terminal requests to establish non-emergency services, thereby avoiding the situation where the remote terminal establishes non-emergency services but the relay terminal is unable to provide the non-emergency services to the remote terminal, thereby avoiding waste of resources.
  • the mobility restriction indication information is determined based on mobility restriction information, and the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.
  • mobility restriction information refers to information related to the mobility restriction status of the relay terminal, which may include the area where the relay terminal is currently located, the current mobility restriction status of the relay terminal, etc.
  • the mobility restriction information can be determined by the AMF entity corresponding to the relay terminal based on the location information of the relay terminal.
  • the method for processing non-emergency services provided in the embodiment of the present application is based on mobility restriction information. Determine the mobility restriction indication information, and the mobility restriction indication information indicates the mobility restriction status of the relay terminal, so that the first device can obtain the mobility restriction status of the relay terminal, and thus determine the corresponding operation according to the mobility restriction status of the relay terminal. This can solve the problem that when the remote terminal is connected to the relay terminal under mobility restriction, the non-emergency service PDU session of the remote terminal cannot be processed.
  • Embodiment 1 is a diagrammatic representation of Embodiment 1:
  • FIG. 4 is a flowchart of a third method for processing non-emergency services provided in an embodiment of the present application. As shown in FIG. 4 , an embodiment of the present application provides a method for processing non-emergency services, including:
  • the remote terminal is the first device
  • the relay terminal is the second device
  • Registration Relay UE sends a Registration Request message to the AMF entity (Relay UE AMF) corresponding to the Relay UE.
  • the AMF entity corresponding to the Relay UE returns a Registration Accept message to the Relay UE.
  • the Registration Accept message contains mobility restriction information.
  • the Relay UE can send mobility restriction indication information to the Remote UE.
  • the Relay UE If the Relay UE is currently in a mobility restriction, such as in a Forbidden Area or a Non-Allowed Area, the Relay UE indicates to the Remote UE that its mobility restriction state is restricted during the discovery process.
  • the discovery process is divided into two types: Model A and Model B.
  • the Relay UE sends a broadcast Announcement message, which contains mobility restriction indication information (Mobility restriction indication).
  • the Remote UE sends a Solicitation message to the Relay UE, and the Relay UE returns a Response message to the Remote UE, which includes mobility restriction indication information (Mobility restriction indication).
  • mobility restriction indication information Mobility restriction indication
  • the Relay UE may obtain or pre-configure an emergency service (Emergency) relay service code (RSC) from the PCF, where the Emergency RSC is used to indicate that the Relay UE can relay emergency services for the Remote UE.
  • Emergency emergency service
  • RSC relay service code
  • the broadcast Announcement message can also carry Emergency RSC.
  • the Solicitation Request message can also carry the Emergency RSC corresponding to the remote terminal.
  • the Response message may also carry the Emergency RSC corresponding to the relay terminal.
  • the Remote UE will only be able to establish an Emergency PDU session.
  • Relay selection Remote UE selects a suitable Relay UE.
  • the Remote UE selects a suitable Relay UE according to the service it needs to perform. For example, when the Remote UE needs to perform an emergency service, a UE that supports relay services for providing emergency services to the Remote UE is selected as the Relay UE.
  • the embodiments of the present application do not limit how to select the Relay UE.
  • the Relay UE may send mobility restriction indication information to the Remote UE.
  • a PC5 connection is established between the Remote UE and the Relay UE.
  • the Remote UE sends a Direct Communication Request message to the Relay UE, and the Relay UE returns a Direct Communication Accept message to the Remote UE, which includes mobility restriction indication information.
  • the Relay UE if in step 2, the Relay UE does not indicate the mobility restriction indication information to the Remote UE during the discovery process, the Relay UE sends the mobility restriction indication information to the Remote UE through a Direct Communication Accept message.
  • the Direct Communication Request message may carry the Emergency RSC corresponding to the Remote UE.
  • the Direct Communication Accept message may carry the Emergency RSC corresponding to the Relay UE.
  • the Relay UE includes only the Emergency RSC in the Direct Communication Accept message, and the Remote UE can only establish an emergency service PDU session. It can be understood that the Remote UE does not initiate a non-emergency service PDU session.
  • Registration procedure Remote UE initiates the registration procedure.
  • the Remote UE can only initiate the PDU session establishment process for emergency services.
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • FIG. 5 is a fourth flow chart of a method for processing non-emergency services provided in an embodiment of the present application. As shown in FIG. 5 , an embodiment of the present application provides a method for processing non-emergency services, including:
  • the remote terminal is the first device
  • the relay terminal is the second device
  • Relay communication The Remote UE and the Relay UE have established a connection, and the Remote UE communicates with the network through the Relay UE.
  • the Remote UE can establish an Emergency PDU session and a non-Emergency PDU session at the same time.
  • Registration process 1a. Relay UE initiates a periodic registration process or a mobility registration process; 1b. The AMF entity corresponding to the Relay UE returns mobility restriction information to the Relay UE.
  • the Relay UE finds that its mobility restriction status has been updated, for example, from Allowed Area to Non-Allowed Area, the Relay UE sends a status notification message to the Remote UE through the PC5 interface.
  • the status notification message contains mobility restriction indication information, which is used to indicate the current mobility restriction status of the Relay UE.
  • the Relay UE when the Relay UE is in a restricted state, if the Remote UE indicates to the Relay UE at the access layer (AS layer) that it is establishing a non-emergency service, the Relay UE will reject the Remote UE's request through the AS layer, and send a mobility restriction indication message to the Remote UE through the AS layer, informing the Remote UE that the Relay UE is currently in a restricted state.
  • AS layer access layer
  • Non-emergency service PDU session release If the Relay UE indicates the mobility restriction indication information to the Remote UE in step 2, and the mobility restriction indication information indicates the mobility of the relay terminal If the restricted state is a restricted state, it means that the Remote UE can only perform emergency services and needs to release the non-emergency service PDU session. There are several ways to do this:
  • the Remote UE sends a first message to the SMF (Remote UE SMF) corresponding to the Remote UE.
  • the first message may be a PDU session release request (PDU session release request) message.
  • the first message includes mobility restriction indication information for indicating the mobility restriction status of the relay terminal.
  • the mobility restriction indication information can enable the SMF corresponding to the Remote UE to know that the relay terminal does not support non-emergency services, thereby triggering the SMF corresponding to the Remote UE to release the non-emergency service PDU session.
  • the first message includes non-emergency service PDU session release indication information, which is used to instruct the SMF corresponding to the Remote UE to release the non-emergency service PDU session. It should be understood that after receiving the non-emergency service PDU session release indication information, the SMF corresponding to the Remote UE can directly release the non-emergency service PDU session without determining the mobility restriction state of the relay terminal.
  • the Remote UE sends a second message to the AMF corresponding to the Remote UE, which may be a NAS message.
  • the AMF entity corresponding to the Remote UE (Remote UE AMF) identifies the non-emergency service PDU session ID according to the second message, and sends a PDU session release request (PDU session release request) message to the SMF entity corresponding to the remote terminal, triggering the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session.
  • PDU session release request PDU session release request
  • the second message includes mobility restriction indication information
  • the AMF corresponding to the Remote UE identifies the non-emergency service PDU session identifier (identity, ID) based on the indication information, that is, the first PDU session identifier, and triggers the SMF corresponding to the Remote UE to release the non-emergency service PDU session.
  • ID non-emergency service PDU session identifier
  • Non-emergency service PDU session release process The SMF corresponding to the Remote UE initiates the non-emergency service PDU session release process.
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • FIG6 is a flowchart of a fifth method for processing non-emergency services provided in an embodiment of the present application. As shown in FIG6 , an embodiment of the present application provides a method for processing non-emergency services, including:
  • the AMF entity corresponding to the Remote UE serves as the first device, and the access network NG-RAN serves as the second device.
  • Relay communication The Remote UE and the Relay UE have established a connection, and the Remote UE communicates with the network through the Relay UE.
  • the Remote UE can establish an Emergency PDU session and a non-Emergency PDU session at the same time.
  • Registration process 1a. Relay UE initiates a periodic registration process or a mobility registration process; 1b. The AMF entity corresponding to the Relay UE returns mobility restriction information to the Relay UE.
  • the access network NG-RAN as the second device, sends mobility restriction indication information to the AMF entity corresponding to the Remote UE, which is the first device.
  • the mobility restriction indication information can be carried by the N2 message.
  • the AMF entity corresponding to the Remote UE identifies the non-emergency service PDU session ID according to the mobility restriction indication information, and sends a third message to the SMF entity corresponding to the remote terminal.
  • the third message may be a PDU session release request (PDU session release request) message.
  • the PDU session release request may carry the non-emergency service PDU session ID, triggering the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session.
  • Non-emergency service PDU session release process The SMF corresponding to the Remote UE initiates the non-emergency service PDU session release process.
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • FIG. 7 is a sixth flow chart of a method for processing non-emergency services provided in an embodiment of the present application. As shown in FIG. 7 , an embodiment of the present application provides a method for processing non-emergency services, including:
  • the AMF entity corresponding to the Remote UE is the first device, and the AMF corresponding to the Relay UE is the second device.
  • Discovery process Remote UE discovers Relay UE through the discovery process.
  • PC5 connection establishment Remote UE and Relay UE establish PC5 connection.
  • the Relay UE sends a NAS message to the AMF corresponding to the Relay UE.
  • the message includes the remote terminal identifier (Remote UE ID), such as the user permanent identifier (SUbscription Permanent Identifier, SUPI) corresponding to the Remote UE.
  • Remote UE ID such as the user permanent identifier (SUbscription Permanent Identifier, SUPI) corresponding to the Remote UE.
  • SUPI subscription Permanent Identifier
  • the AMF entity corresponding to the Relay UE finds that the Relay UE is in a restricted state
  • the AMF entity corresponding to the Relay UE finds the AMF entity corresponding to the Remote UE (Remote UE AMF) through the identifier of the remote terminal, and sends mobility restriction indication information to the Remote UE AMF.
  • the AMF corresponding to the Remote UE identifies the first PDU session identifier corresponding to the non-emergency service PDU session according to the mobility restriction indication information.
  • the AMF corresponding to the Remote UE triggers the SMF corresponding to the Remote UE to release the non-emergency service PDU session, that is, the AMF corresponding to the Remote UE sends a third message to the SMF corresponding to the Remote UE, and the third message can be a PDU session release message.
  • the third message carries the first PDU session identifier.
  • Non-emergency service PDU session release process The SMF corresponding to the Remote UE initiates the non-emergency service PDU session release process.
  • the embodiment of the present application solves the problem of how to handle the non-emergency service PDU session of the Remote UE when the Remote UE is connected to the Relay UE that supports emergency services and the Relay UE is in a restricted state.
  • FIG. 8 is a schematic diagram of a structure of a non-emergency service processing device provided in an embodiment of the present application.
  • the embodiment of the present application provides a non-emergency service processing device, which can be applied to a first device, and the device includes: a first receiving unit 810 and a first determining unit 820;
  • the first receiving unit 810 is configured to receive mobility restriction indication information sent by the second device, where the mobility restriction indication information is used to indicate a mobility restriction state of the relay terminal;
  • the first determining unit 820 is configured to determine whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal.
  • PDU non-emergency service protocol data unit
  • the first device is the remote terminal, and the second device is the relay terminal;
  • the first receiving unit 810 is configured to receive the mobility restriction indication information sent by the second device, including:
  • the first receiving unit 810 is configured to receive the mobility restriction indication information through a direct communication message sent by the second device.
  • the direct communication message includes any one of the following:
  • the first determining unit 820 is configured to determine whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal, including:
  • the first determining unit 820 is configured to determine not to initiate the non-emergency service PDU session or to determine to release the non-emergency service PDU session when the mobility restriction state of the relay terminal is a restricted state.
  • the device further includes a first sending unit
  • the first sending unit is used to send a first message to the session management function SMF entity corresponding to the remote terminal after determining to release the non-emergency service PDU session, wherein the first message is used to instruct the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session;
  • the first sending unit is used to send a second message to the AMF entity corresponding to the remote terminal after determining to release the non-emergency service PDU session, wherein the second message is used to instruct the AMF entity corresponding to the remote terminal to trigger the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session;
  • the first message or the second message includes the mobility restriction indication information.
  • the first device is an access and mobility management AMF entity corresponding to the remote terminal
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal
  • the first determining unit 820 is configured to determine whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal, including:
  • the first determining unit 820 is configured to determine to release the non-emergency service PDU session when the mobility restriction state of the relay terminal is a restricted state.
  • the first determining unit 820 is further configured to determine, after determining to release the non-emergency service PDU session, a first PDU session identifier corresponding to the non-emergency service PDU session based on the mobility restriction indication information and the PDU session information corresponding to the remote terminal;
  • the first sending unit is further used to send a third message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal, and the third message carries the first PDU Session ID.
  • FIG. 9 is a second structural diagram of a non-emergency service processing device provided in an embodiment of the present application.
  • the embodiment of the present application provides a non-emergency service processing device, which can be applied to a second device, and the device includes: a second sending unit 910;
  • the second sending unit 910 is used to send mobility restriction indication information to the first device
  • the mobility restriction indication information is used to indicate the mobility restriction state of the relay terminal; the mobility restriction state of the relay terminal is used by the first device to determine whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal.
  • the device further includes a second receiving unit and a second determining unit;
  • the second receiving unit is configured to receive the identifier of the remote terminal sent by the relay terminal;
  • the second determination unit is used to determine the AMF entity corresponding to the remote terminal based on the identifier of the remote terminal.
  • the device further comprises a second rejection unit
  • the second rejecting unit is used to reject the establishment of the non-emergency service requested by the remote terminal when the mobility restriction state of the relay terminal is a restricted state and the relay terminal receives a non-emergency service establishment request message sent by the remote terminal.
  • the mobility restriction indication information is determined based on mobility restriction information, and the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.
  • each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units are It can be implemented in the form of hardware or in the form of a software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the relevant technology or all or part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.
  • FIG10 is a schematic diagram of the structure of the first device provided in an embodiment of the present application.
  • the first device includes a memory 1020, a transceiver 1000, and a processor 1010; wherein the processor 1010 and the memory 1020 may also be arranged physically separately.
  • the memory 1020 is used to store a computer program; the transceiver 1000 is used to send and receive data under the control of the processor 1010; the processor 1010 calls the computer program stored in the memory 1020 to perform operations corresponding to any of the methods for processing non-emergency services applied to the first device provided in the embodiments of the present application according to the obtained executable instructions, for example:
  • PDU non-emergency service protocol data unit
  • the transceiver 1000 is used to receive and send data under the control of the processor 1010 .
  • the bus interface 1040 may include any number of interconnected buses and bridges, specifically connecting various circuits of one or more processors represented by the processor 1010 and the memory represented by the memory 1020.
  • the bus interface 1040 may also connect various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein.
  • the bus interface provides an interface.
  • the transceiver 1000 may be a plurality of components, namely, a transmitter and a receiver, providing a means for communicating with various other devices on a transmission medium.
  • the communication unit includes transmission media such as wireless channels, wired channels, optical cables, etc.
  • a user interface 1030 may also be included.
  • the user interface 1030 may also be an interface capable of connecting external or internal devices.
  • the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, etc.
  • the processor 1010 is responsible for managing the bus architecture and general processing, and the memory 1020 can store data used by the processor 1010 when performing operations.
  • processor 1010 can be a CPU (central processing unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array) or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the first device is the remote terminal, and the second device is the relay terminal;
  • the receiving the mobility restriction indication information sent by the second device includes:
  • the mobility restriction indication information is received through a direct communication message sent by the second device.
  • the direct communication message includes any one of the following:
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined not to initiate the non-emergency service PDU session or it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • the first message or the second message includes the mobility restriction indication information.
  • the first device is an access and mobility management AMF entity corresponding to the remote terminal
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • a third message for releasing the non-emergency service PDU session is sent to the SMF entity corresponding to the remote terminal, wherein the third message carries the first PDU session identifier.
  • the above-mentioned first device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned non-emergency business processing method embodiment, and can achieve the same technical effect.
  • the parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.
  • FIG11 is a schematic diagram of the structure of the second device provided in an embodiment of the present application.
  • the second device includes a memory 1120, a transceiver 1100, and a processor 1111; wherein the processor 1111 and the memory 1120 may also be arranged physically separately.
  • the memory 1120 is used to store a computer program; the transceiver 1100 is used to send and receive data under the control of the processor 1111; the processor 1111 calls the computer program stored in the memory 1120 to perform operations corresponding to any of the methods for processing non-emergency services applied to the second device provided in the embodiments of the present application according to the obtained executable instructions, for example:
  • the mobility restriction indication information is used to indicate the mobility restriction state of the relay terminal; the mobility restriction state of the relay terminal is used by the first device to determine whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal.
  • the transceiver 1100 is used to receive and send data under the control of the processor 1111 .
  • the bus interface 1140 may include any number of interconnected buses and bridges, specifically one or more processors represented by the processor 1111 and various circuits of the memory represented by the memory 1120 are connected together.
  • the bus interface 1140 can also connect various other circuits such as peripheral devices, voltage regulators and power management circuits, which are well known in the art and are therefore not further described herein.
  • the bus interface provides an interface.
  • the transceiver 1100 may be a plurality of components, namely, a transmitter and a receiver, and provide a unit for communicating with various other devices on a transmission medium, and these transmission media include transmission media such as wireless channels, wired channels, and optical cables.
  • a user interface 1130 may also be included, and the user interface 1130 may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 1111 is responsible for managing the bus architecture and general processing, and the memory 1120 can store data used by the processor 1111 when performing operations.
  • processor 1111 can be a CPU (central processing unit), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array) or CPLD (Complex Programmable Logic Device), and the processor can also adopt a multi-core architecture.
  • CPU central processing unit
  • ASIC Application Specific Integrated Circuit
  • FPGA Field-Programmable Gate Array
  • CPLD Complex Programmable Logic Device
  • the method further includes:
  • the second device refuses to establish the non-emergency service requested by the remote terminal.
  • the mobility restriction indication information is determined based on mobility restriction information, and the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.
  • the second device provided in the embodiment of the present application can implement all the method steps implemented in the embodiment of the method for processing non-emergency services, and can achieve the same technical
  • the parts and beneficial effects of this embodiment that are the same as those of the method embodiment will not be described in detail here.
  • an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is used to enable the processor to execute the method provided in the above embodiments and applied to the first device, including:
  • PDU non-emergency service protocol data unit
  • the first device is the remote terminal, and the second device is the relay terminal;
  • the receiving the mobility restriction indication information sent by the second device includes:
  • the mobility restriction indication information is received through a direct communication message sent by the second device.
  • the direct communication message includes any one of the following:
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined not to initiate the non-emergency service PDU session or it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • the first message or the second message includes the mobility restriction indication information.
  • the first device is an access and mobility management AMF entity corresponding to the remote terminal
  • the second device is an access network entity or an AMF entity corresponding to the relay terminal
  • the determining whether to initiate or release a non-emergency service protocol data unit (PDU) session of a remote terminal based on the mobility restriction state of the relay terminal includes:
  • the mobility restriction state of the relay terminal is a restricted state, it is determined to release the non-emergency service PDU session.
  • the step further includes:
  • a third message for releasing the non-emergency service PDU session is sent to the SMF entity corresponding to the remote terminal, wherein the third message carries the first PDU session identifier.
  • an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, wherein the computer program is used to enable the processor to execute the method provided in the above embodiments and applied to the second device, including:
  • the mobility restriction indication information is used to indicate the mobility restriction state of the relay terminal; the mobility restriction state of the relay terminal is used by the first device to determine whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal.
  • the method further includes:
  • the second device refuses to establish the non-emergency service requested by the remote terminal.
  • the mobility restriction indication information is determined based on mobility restriction information, and the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.
  • the processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.
  • magnetic storage such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.
  • optical storage such as CD, DVD, BD, HVD, etc.
  • semiconductor storage such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
  • a computer-usable storage media including but not limited to disk storage and optical storage, etc.
  • each process and/or box in the flowchart and/or block diagram, and the combination of the process and/or box in the flowchart and/or block diagram can be implemented by computer executable instructions.
  • These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the function specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.
  • processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Landscapes

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

Abstract

本申请提供一种非紧急业务的处理方法及装置，其中应用于第一设备的方法包括：接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。

Description

非紧急业务的处理方法及装置
相关申请的交叉引用
本申请要求于2022年10月14日提交的申请号为202211262428.4，发明名称为“非紧急业务的处理方法及装置”的中国专利申请的优先权，其通过引用方式全部并入本文。
技术领域
本申请涉及通信技术领域，尤其涉及一种非紧急业务的处理方法及装置。
背景技术
邻近业务(Proximity Service，ProSe)标准项目定义了一种层2终端到网络中继(Layer-2 UE-to-Network Relay)架构，在该架构中，远端终端(Layer-2 Remote UE)可通过中继终端(Layer-2 Relay UE)连接到网络进行通信，进一步的，相关技术中规定了当中继终端受限于移动性限制(Mobility Restriction)时，将无法为远端终端的非紧急业务(non-Emergency service)提供中继服务。
受限于移动性限制(Mobility Restriction)的中继终端不能为远端终端的非紧急业务协议数据单元(Protocol Data Unit，PDU)会话提供中继服务，此时，如何处理远端终端的非紧急业务成为亟需解决的问题。
发明内容
本申请实施例提供一种非紧急业务的处理方法及装置，用以解决相关技术中在受限于移动性限制的中继终端不能为远端终端的非紧急业务中继的情况下，对于远端终端的非紧急业务处理，缺乏解决方案的问题。
第一方面，本申请实施例提供一种非紧急业务的处理方法，应用于第一设备，包括：
接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用 于指示中继终端的移动性限制状态；
基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
所述接收第二设备发送的移动性限制指示信息，包括：
通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
可选地，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
可选地，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
第二方面，本申请实施例提供一种非紧急业务的处理方法，应用于第二设备，包括：
向第一设备发送移动性限制指示信息；
其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，在所述第二设备为所述中继终端对应的AMF实体，所述第一设备为所述远端终端对应的AMF实体的情况下，所述向第一设备发送移动性限制指示信息之前还包括：
接收所述中继终端发送的所述远端终端的标识；
基于所述远端终端的标识确定所述远端终端对应的AMF实体。
可选地，在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
可选地，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
第三方面，本申请实施例还提供一种第一设备，包括存储器，收发机，处理器，其中：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并实现如上所述第一方面所述的非紧急业务的处理方法。
可选地，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
所述接收第二设备发送的移动性限制指示信息，包括：
通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
可选地，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
可选地，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
第四方面，本申请实施例还提供一种第一设备，包括存储器，收发机，处理器，其中：
存储器，用于存储计算机程序；收发机，用于在所述处理器的控制下收发数据；处理器，用于读取所述存储器中的计算机程序并实现如上所述第二方面所述的非紧急业务的处理方法。
可选地，在所述第二设备为所述中继终端对应的AMF实体，所述第一设备为所述远端终端对应的AMF实体的情况下，所述向第一设备发送移动性限制指示信息之前还包括：
接收所述中继终端发送的所述远端终端的标识；
基于所述远端终端的标识确定所述远端终端对应的AMF实体。
可选地，在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
可选地，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
第五方面，本申请实施例还提供一种非紧急业务的处理装置，应用于第一设备，包括：
第一接收单元，用于接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
第一确定单元，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
所述第一接收单元，用于接收第二设备发送的移动性限制指示信息，包括：
所述第一接收单元，用于通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
可选地，所述第一确定单元，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
所述第一确定单元，用于在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
可选地，所述装置还包括第一发送单元；
所述第一发送单元，用于在确定释放所述非紧急业务PDU会话之后，向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
所述第一发送单元，用于在确定释放所述非紧急业务PDU会话之后，向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
可选地，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
所述第一确定单元，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
所述第一确定单元，用于在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
可选地，所述第一确定单元，还用于在确定释放所述非紧急业务PDU会话之后，基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
所述第一发送单元，还用于向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
第六方面，本申请实施例还提供一种非紧急业务的处理装置，应用于第二设备，包括：
第二发送单元，用于向第一设备发送移动性限制指示信息；
其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，所述装置还包括第二接收单元和第二确定单元；
所述第二接收单元，用于接收所述中继终端发送的所述远端终端的标识；
所述第二确定单元，用于基于所述远端终端的标识确定所述远端终端对应的AMF实体。
可选地，所述装置还包括第二拒绝单元；
所述第二拒绝单元，用于在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
可选地，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
第七方面，本申请实施例还提供一种处理器可读存储介质，所述处理器可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行如上所述第一方面所述的非紧急业务的处理方法或所述第二方面所述的非紧急业务的处理方法。
本申请实施例提供的非紧急业务的处理方法及装置，通过移动性限制指示信息使得第一设备能够获知中继终端的移动性限制状态，从而根据中继终端的移动性限制状态确定对应的操作，能够解决当远端终端连接到处于移动性限制的中继终端时，无法处理远端终端的非紧急业务PDU会话的问题。
附图说明
为了更清楚地说明本申请实施例或相关技术中的技术方案，下面将对实施例或相关技术描述中所需要使用的附图作一简单地介绍，显而易见地，下 面描述中的附图是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请提供的网络架构示意图；
图2是本申请实施例提供的非紧急业务的处理方法的流程示意图之一；
图3是本申请实施例提供的非紧急业务的处理方法的流程示意图之二；
图4是本申请实施例提供的非紧急业务的处理方法的流程示意图之三；
图5是本申请实施例提供的非紧急业务的处理方法的流程示意图之四；
图6是本申请实施例提供的非紧急业务的处理方法的流程示意图之五；
图7是本申请实施例提供的非紧急业务的处理方法的流程示意图之六；
图8是本申请实施例提供的非紧急业务的处理装置的结构示意图之一；
图9是本申请实施例提供的非紧急业务的处理装置的结构示意图之二；
图10为本申请实施例提供的第一设备的结构示意图；
图11为本申请实施例提供的第二设备的结构示意图。
具体实施方式
本申请实施例中术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，并不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请实施例提供的技术方案可以适用于多种系统，尤其是5G(5th Generation Mobile Communication Technology，第五代移动通信技术)系统。例如适用的系统可以是全球移动通讯(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带 码分多址(Wideband Code Division Multiple Access，WCDMA)通用分组无线业务(general packet radio service，GPRS)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统、高级长期演进(long term evolution advanced，LTE-A)系统、通用移动系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)系统、5G新空口(New Radio,NR)系统等。这多种系统中均包括终端设备和网络设备。系统中还可以包括核心网部分，例如演进的分组系统(Evloved Packet System,EPS)、5G系统(5GS)等。
本申请实施例涉及的终端设备，可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线调制解调器的其他处理设备等。在不同的系统中，终端设备的名称可能也不相同，例如在5G系统中，终端设备可以称为用户设备(User Equipment，UE)。无线终端设备可以经无线接入网(Radio Access Network,RAN)与一个或多个核心网(Core Network,CN)进行通信，无线终端设备可以是移动终端设备，如移动电话(或称为“蜂窝”电话)和具有移动终端设备的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(Personal Communication Service，PCS)电话、无绳电话、会话发起协议(Session Initiated Protocol，SIP)话机、无线本地环路(Wireless Local Loop，WLL)站、个人数字助理(Personal Digital Assistant，PDA)等设备。无线终端设备也可以称为系统、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点(access point)、远程终端设备(remote terminal)、接入终端设备(access terminal)、用户终端设备(user terminal)、用户代理(user agent)、用户装置(user device)，本申请实施例中并不限定。
本申请实施例涉及的网络设备，可以是基站，该基站可以包括多个为终端提供服务的小区。根据具体应用场合不同，基站又可以称为接入点，或者可以是接入网中在空中接口上通过一个或多个扇区与无线终端设备通信的设 备，或者其它名称。网络设备可用于将收到的空中帧与网际协议(Internet Protocol，IP)分组进行相互更换，作为无线终端设备与接入网的其余部分之间的路由器，其中接入网的其余部分可包括网际协议(IP)通信网络。网络设备还可协调对空中接口的属性管理。例如，本申请实施例涉及的网络设备可以是全球移动通信系统(Global System for Mobile communications，GSM)或码分多址接入(Code Division Multiple Access，CDMA)中的网络设备(Base Transceiver Station，BTS)，也可以是带宽码分多址接入(Wide-band Code Division Multiple Access，WCDMA)中的网络设备(NodeB)，还可以是长期演进(long term evolution，LTE)系统中的演进型网络设备(evolutional Node B，eNB或e-NodeB)、5G网络架构(next generation system)中的5G基站(gNB)，也可以是家庭演进基站(Home evolved Node B，HeNB)、中继节点(relay node)、家庭基站(femto)、微微基站(pico)等，本申请实施例中并不限定。在一些网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点和分布单元(distributed unit，DU)节点，集中单元和分布单元也可以地理上分开布置。
网络设备与终端设备之间可以各自使用一或多根天线进行多输入多输出(Multi Input Multi Output,MIMO)传输，MIMO传输可以是单用户MIMO(Single User MIMO,SU-MIMO)或多用户MIMO(Multiple User MIMO,MU-MIMO)。根据根天线组合的形态和数量，MIMO传输可以是2D-MIMO、3D-MIMO、FD-MIMO或massive-MIMO，也可以是分集传输或预编码传输或波束赋形传输等。
为了方便理解本申请实施例，下面介绍与本申请实施例相关的术语或背景：
(1)层2(Layer-2)终端到网络(UE-to-Network)的中继(Relay)架构和流程
相关技术定义了Layer-2 UE-to-Network Relay架构和相关流程。当UE处于网络覆盖范围之外或者Uu接口信号较差时，无法直接连接网络，可通过具有中继功能的UE连接网络，前者称为层2远端终端(Layer-2 Remote UE， 也可以称为远端终端)，后者称为层2中继终端(Layer-2 Relay UE，也可以称为中继终端)。Remote UE可以通过Relay UE连接到自己的NG-RAN和核心网。
(2)层2远端UE通过层2中继UE与网络进行通信的流程
图1是本申请实施例提供的Layer-2 Remote UE通过Layer-2 Relay UE与网络进行通信的流程示意图，如图1所示，Layer-2 Remote UE通过Layer-2 Relay UE与网络进行通信的流程包括：
0、初始注册：Remote UE和Relay UE在网时，可分别注册到网络。Relay UE可以是邻近业务终端至网络中继(ProSe UE-to-Network Relay)。
1、服务许可检索(Service Authorization retrieval)：在网时，Remote UE和Relay UE分别从网络中获取进行邻近业务(Proximity Service，ProSe)的策略和参数。若Remote UE不在网，可使用预配置的参数。
2、发现和选择(UE-to-Network Relay discovery and selection)：Remote UE和Relay UE执行发现过程，Remote UE选择要通信的Relay UE。
3、PC5通信和建立(PC5 connection establishment)：Remote UE和Relay UE之间建立通信的PC5连接。
4、接入层连接建立(Access Stratum connection setup，AS connection setup):Remote UE建立与接入网的RRC连接，该接入网与Relay UE的服务接入网相同。接入网可以为下一代无线接入网(Next Generation Radio Access Network，NG-RAN)。
5、中继终端触发服务请求(UE-to-Network Relay triggered Service Request)：如果Relay UE处于空闲(IDLE)态并接收到Remote UE的无线资源控制(Radio Resource Control，RRC)连接请求，Relay UE发起服务请求(Service Request)过程以进入连接态。
6、非接入层连接建立(Non-Access Stratum connection setup，NAS connection setup)：Remote UE向Remote UE对应的接入和移动性管理功能(Access and Mobility Management Function，AMF)实体(图中未Remote UE's AMF)发送NAS消息，NAS消息封装在RRC消息中，RRC消息通过PC5 接口发送到Relay UE，Relay UE将RRC消息转发到接入网。接入网为Remote UE选择AMF并将NAS消息转发到该AMF。NAS消息可以是初始注册(Initial Registration)消息、服务请求(Service Request)消息、移动性注册(mobility registration)消息或周期性注册(periodic registration)消息中的一种。
7、PDU会话建立过程(PDU Session Establishment procedure)：Remote UE发起PDU会话建立过程。
8、数据传输(data transfer)：Remote UE的数据通过Relay UE和NG-RAN在Remote UE和UPF之间传输。
对于图中的策略控制功能(Policy Control Function，PCF)、Remote UE的会话管理功能(Session Management Function，SMF)、Remote UE的用户面功能(User Plane Function，UPF)对应的步骤，参考相关技术，此处不再赘述。
(3)移动性限制(Mobility Restriction)
相关技术定义了Mobility Restriction。Mobility Restriction限制UE的移动性处理和业务接入，包括禁止区(Forbidden Area)、服务区限制(Service Area Restriction)等。在禁止区中，UE不允许发起到网络的任何通信。服务区限制包括允许区(Allowed Area)和不允许区(Non-Allowed Area)。在允许区中，UE允许发起到网络的通信；在不允许区中，UE不允许发起与数据传输相关的过程(如服务请求Service Request)。值得注意的是，当UE进行紧急业务时，将不受上述移动性限制(Mobility Restriction)的限制。
相关技术中定义了R17中继场景下移动性限制的适用场景。当Relay UE处于禁止区(Forbidden Area)或不允许区(Non-Allowed Area)中时，Relay UE不能执行中继操作(即不能执行中继发现和中继通信过程)
当Relay UE处于移动性限制时，仍然可以为Remote UE的紧急业务提供中继服务，但是不能为非紧急业务提供中继服务。
对于Layer-2 UE-to-Network Relay架构，根据相关技术规定，处于移动性限制的Relay UE可以为Remote UE的紧急业务提供中继服务，但是不能为非紧急业务提供中继服务。
当Remote UE连接到Relay UE，而Relay UE又处于移动性限制时，如何处理Remote UE的非紧急业务PDU会话是相关技术没有解决的问题。
本申请实施例提供的非紧急业务的处理方法，能够解决当远端终端连接到中继终端，而中继终端又处于移动性限制时，如何处理远端终端的非紧急业务PDU会话的问题。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，并不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图2是本申请实施例提供的非紧急业务的处理方法的流程示意图之一，如图2所示，本申请实施例提供一种非紧急业务的处理方法，可以应用于第一设备，包括：
步骤210，接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
具体的，第一设备是指能够对远端终端的非紧急业务协议数据单元(Protocol Data Unit，PDU)会话处理的设备，处理可以包括发起会话或释放会话等。
第二设备是指能够确定或者获得移动性限制指示信息、并能够向第一设备发送移动性限制指示信息的设备。
移动性限制指示信息是指用于指示中继终端的移动性限制状态的信息。
一种可能的实现中，移动性限制指示信息可以指示中继终端的移动性限制状态处于Forbidden Area、Allowed Area或Non-Allowed Area。
一种可能的实现中，移动性限制指示信息可以以移动性限制指示符的形式指示中继终端的移动性限制状态，如移动性限制指示符的值为1的情况下，指示中继终端的移动性限制状态为能够为远端终端提供非紧急业务的状态，如中继终端的移动性限制状态为Allowed Area；移动性限制指示符的值为0的情况下，指示中继终端的移动性限制状态为不能为远端终端提供非紧急业务的状态，如中继终端的移动性限制状态为Forbidden Area或Non-Allowed  Area。
应理解，以上是为便于理解本申请进行的举例，不应对本申请构成任何限定。
步骤220，基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
具体地，在中继终端的移动性限制状态为能够为远端终端提供非紧急业务的状态，如Allowed Area，第一设备可以执行以下任一操作：
在未发起远端终端的非紧急业务PDU会话的情况下，确定发起远端终端的非紧急业务PDU会话；
在已经建立远端终端的非紧急业务PDU会话的情况下，维持远端终端的非紧急业务PDU会话，或者不对远端终端的非紧急业务PDU会话进行处理。
可选地，还可以确定远端终端是否有需要执行的非紧急业务，在远端终端需要建立非紧急业务PDU会话、且中继终端的移动性限制状态能够支持为远端终端进行非紧急业务中继的情况下，发起、维持或不处理远端终端的非紧急业务PDU会话。
在中继终端的移动性限制状态为不能为远端终端提供非紧急业务的状态，如中继终端的移动性限制状态为Forbidden Area或Non-Allowed Area，第一设备可以执行以下任一操作：
在未发起远端终端的非紧急业务PDU会话的情况下，确定不发起远端终端的非紧急业务PDU会话；
在已经建立远端终端的非紧急业务PDU会话的情况下，确定释放远端终端的非紧急业务PDU会话。
不发起远端终端的非紧急业务PDU会话可以指向网络功能实体，如远端终端对应的SMF实体，不发送非紧急业务PDU会话建立请求，或者取消正在发送的非紧急业务PDU会话建立请求。
本申请实施例提供的非紧急业务的处理方法，可以应用于中继场景，如上文介绍的层2终端到网络中继(Layer-2 UE-to-Network Relay)的场景中。
本申请实施例提供的非紧急业务的处理方法，通过移动性限制指示信息 使得第一设备能够获知中继终端的移动性限制状态，从而根据中继终端的移动性限制状态确定对应的操作，能够解决当远端终端连接到处于移动性限制的中继终端时，无法处理远端终端的非紧急业务PDU会话的问题。
可选地，中继终端能够支持紧急业务。
可选地，所述第一设备为所述远端终端，所述第二设备为所述中继终端。
具体地，第一设备是远端终端，第二设备是与远端终端建立直接通信的中继终端。
可选地，所述接收第二设备发送的移动性限制指示信息，包括：
通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
具体地，第一设备为远端终端，第二设备为中继终端，远端终端和中继终端之间可以通过直接发现消息进行通信。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
具体地，对于中继发现消息，是在发现过程中发送的直接通信消息。
示例性地，直接通信中发现过程可以包括A模式和B模式两种方式：
A模式：
中继终端在A模式的发现过程中发送广播Announcement消息(应理解，广播消息是一种直接通信消息)，该广播消息携带移动性限制指示信息。
B模式：
远端终端发送请求Solicitation消息，该请求Solicitation消息用于请求接收到请求消息的中继终端向远端终端返回携带有移动性限制指示信息的响应Response消息；中继终端接收到请求消息后，向远端终端返回携带有移动性限制指示信息的响应Response消息。
应理解，以上是为便于理解本申请进行的举例，不应对本申请构成任何限定。
对于直接通信接受消息是指，在Remote UE和Relay UE之间建立PC5 连接的过程中，Remote UE向Relay UE发送直接通信请求(Direct Communication Request)消息，Relay UE向Remote UE返回直接通信接受(Direct Communication Accept)消息，该消息中包含移动性限制指示信息。
移动性限制指示信息可以称为Mobility restriction indication，应理解，本申请实施例对于移动性限制指示信息的名称不作限定，只要能够用于指示中继终端的移动性限制状态即可。
对于状态通知消息，是指Remote UE和Relay UE之间建立PC5连接后，Remote UE向Relay UE发送的、用于通知中继终端的移动性限制状态的直接通信消息，该消息中包含移动性限制指示信息。
本申请实施例提供的非紧急业务的处理方法，通过直接通信消息向远端终端发送移动性限制指示信息，使得远端终端能够获知中继终端的移动性限制状态，从而解决远端终端无法获知中继终端的移动性限制状态，进而无法处理非紧急业务的问题。
可选地，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
具体地，受限状态是指Not Allowed Area，包括Forbidden Area和Non-Allowed Area。受限状态的中继终端不能为远端终端提供非紧急业务的状态。
本申请实施例提供的非紧急业务的处理方法，通过移动性限制指示信息使得中继终端能够获知中继终端的移动性限制状态，从而根据中继终端的移动性限制状态，确定在中继终端的移动性限制状态为受限状态下，不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话，能够解决当远端终端连接到处于移动性限制的中继终端时，无法处理远端终端的非紧急业务PDU会话的问题。
应理解，由于处于移动性限制的中继终端时，无法为远端终端的非紧急业务PDU会话提供中继，可能会导致远端终端发起非紧急业务PDU会话后， 一直等待中继终端传输非紧急业务数据，但是中继终端由于处于移动性限制中，无法提供非紧急业务数据，远端终端不发起非紧急业务PDU会话或释放非紧急业务PDU会话，可以避免远端终端长时间等待数据传输，并且可以避免非紧急业务PDU会话占用资源，实现节约资源。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
第一设备向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
第一设备向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话。
具体地，可以由远端终端向远端终端对应的SMF实体发送第一消息，可以由远端终端向远端终端对应的AMF实体发送第二消息。
对于第一消息，第一消息中可以携带非紧急业务PDU会话对应的PDU会话ID，第一消息可以是PDU会话释放请求消息。远端终端对应的会话管理功能SMF实体接收到第一消息后，根据第一消息释放非紧急业务PDU会话。在第一消息中携带非紧急业务PDU会话对应的PDU会话ID的情况下，释放PDU会话ID对应的非紧急业务PDU会话。
对于第二消息，第二消息可以是非接入层NAS消息，Remote UE向Remote UE对应的AMF实体发送第二消息，Remote UE对应的AMF实体根据第二消息识别出非紧急业务PDU会话ID，并触发远端终端对应的SMF实体释放非紧急业务PDU会话。
对于远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话，可以是远端终端对应的AMF实体向远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的PDU会话释放消息。
本申请实施例提供的非紧急业务的处理方法，在第一设备为远端终端，第二设备为中继终端的情况下，能够解决当远端终端连接到处于移动性限制的中继终端时，如何实现释放远端终端的非紧急业务PDU会话的问题。
可选地，所述第一消息或所述第二消息包含所述移动性限制指示信息。
具体地，移动性限制指示信息能够指示消息(第一消息或第二消息)接收方中继终端的移动性限制状态，从而触发消息接收方释放非紧急业务PDU会话。
示例性地，第一消息或第二消息中包含移动性限制指示信息，所述移动性限制指示信息指示中继终端的移动性限制状态为受限状态，消息接收方能够获知中继终端处于受限状态，从而触发消息接收方释放非紧急业务PDU会话。
示例性地，以消息接收方为远端终端对应的AMF实体为例，远端终端对应的AMF实体接收到远端终端发送的移动性限制指示信息，远端终端对应的AMF实体基于所述移动性限制指示信息能够确定中继终端的移动性限制状态，并确定中继终端的移动性限制状态不支持非紧急业务；远端终端对应的AMF实体在所述远端终端对应的PDU会话信息中，确定所述非紧急业务PDU会话对应的PDU会话标识。
可选地，远端终端对应的PDU会话信息可以根据远端终端的上下文确定，远端终端的上下文是远端终端对应的AMF实体预先获得的；
远端终端对应的AMF实体可以向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的消息，所述消息中可以携带有所述非紧急业务PDU会话对应的PDU会话标识，SMF接收到消息后释放非紧急业务PDU会话对应的PDU会话标识对应的非紧急业务PDU会话。
可选地，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体。
应理解，中继终端对应的AMF实体用于管理中继终端的移动性信息，因此可以获得中继终端的移动性限制状态，从而可以确定移动性限制指示信息，并向第一设备(远端终端对应的AMF实体)发送移动性限制指示信息。
中继终端和远端终端可以接入同一个接入网，因此当接入网实体可以获得中继终端的移动性限制状态，确定移动性限制指示信息，并向第一设备(远端终端对应的AMF实体)发送移动性限制指示信息。
可选地，在所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体的情况下，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
可选地，在所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体的情况下，所述确定释放所述非紧急业务PDU会话之后还包括：
基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
具体地，第一设备基于所述移动性限制指示信息能够确定中继终端的移动性限制状态，并确定中继终端的移动性限制状态不支持非紧急业务；
在所述远端终端对应的PDU会话信息中，将所述非紧急业务PDU会话对应的PDU会话标识作为第一PDU会话标识；
向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识，SMF接收到第三消息后释放第一PDU会话标识对应的非紧急业务PDU会话。
可选地，远端终端对应的PDU会话信息可以根据远端终端的上下文确定。
本申请实施例提供的非紧急业务的处理方法，在所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体的情况下，能够解决当远端终端连接到处于移动性限制的中继终端时，如何实现释放远端终端的非紧急业务会话的问题。
图3是本申请实施例提供的非紧急业务的处理方法的流程示意图之二，如图3所示，本申请实施例提供一种非紧急业务的处理方法，可以应用于第二设备，包括：
向第一设备发送移动性限制指示信息；
其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
具体地，第二设备是指能够确定或者获得移动性限制指示信息、并能够向第一设备发送移动性限制指示信息的设备。确定移动性限制指示信息可以是指第二设备根据与中继终端的移动性限制状态相关的信息确定移动性限制指示信息，获取移动性限制指示信息可以是指能够接收到其他设备发送的移动性限制指示信息。
对于第一设备和移动性限制指示信息的介绍，参考上文的介绍，此处不再赘述。
本申请实施例提供的非紧急业务的处理方法，通过向第一设备发送移动性限制指示信息，使得第一设备能够获知中继终端的移动性限制状态，从而根据中继终端的移动性限制状态确定对应的操作，能够解决当远端终端连接到处于移动性限制的中继终端时，无法处理远端终端的非紧急业务PDU会话的问题。
可选地，在所述第一设备为所述远端终端的情况下，所述第二设备为所述中继终端。
可选地，所述向第一设备发送移动性限制指示信息包括：向所述第一设备发送携带有所述移动性限制指示信息的直接通信消息。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
具体地，对于直接通信消息、中继发现消息、直接通信接受消息和状态通知消息的介绍，参考上文的介绍，此处不再赘述。
可选地，在所述第一设备为所述远端终端对应的AMF实体的情况下，所述第二设备为接入网实体或所述中继终端对应的AMF实体。
可选地，在所述第二设备为所述中继终端对应的AMF实体，所述第一设备为所述远端终端对应的AMF实体的情况下，所述向第一设备发送移动性限制指示信息之前还包括：
接收所述中继终端发送的所述远端终端的标识；
基于所述远端终端的标识确定所述远端终端对应的AMF实体。
具体地，中继终端对应的AMF实体可以接收远端终端的标识，通过远端终端的标识确定所述远端终端对应的AMF实体，从而实现向远端终端对应的AMF实体发送移动性限制指示信息。
可选地，在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
具体地，以第二设备为中继终端为例，当中继终端处于移动性限制时，如果远端终端向中继终端指示其建立的是非紧急业务，那么中继终端将拒绝远端终端的请求，并告知远端终端目前中继终端处于移动性限制状态，即向远端终端发送移动性限制指示信息。
对于所述第二设备为接入网实体或所述中继终端对应的AMF实体拒绝远端终端请求的非紧急业务的流程，参考本文介绍以及相关技术，此处不再赘述。
本申请实施例提供的非紧急业务的处理方法，能够在远端终端请求建立非紧急业务时，由中继终端拒绝非紧急业务的建立，从而避免远端终端建立非紧急业务但中继终端无法为远端终端提供非紧急业务的情况，避免了资源浪费。
可选地，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
具体地，移动性限制信息是指与中继终端的移动性限制状态相关的信息，可以包括中继终端当前所在的区域，中继终端当前的移动性限制状态等，移动性限制信息可以由中继终端对应AMF实体根据中继终端的位置信息确定。
本申请实施例提供的非紧急业务的处理方法，通过基于移动性限制信息 确定移动性限制指示信息，由移动性限制指示信息指示中继终端的移动性限制状态，使得第一设备能够获知中继终端的移动性限制状态，从而根据中继终端的移动性限制状态确定对应的操作，能够解决当远端终端连接到处于移动性限制的中继终端时，无法处理远端终端的非紧急业务PDU会话的问题。
下面结合多个实施例对本申请实施例提供的非紧急业务的处理方法进行介绍。
实施例1：
图4是本申请实施例提供的非紧急业务的处理方法的流程示意图之三，如图4所示，本申请实施例提供一种非紧急业务的处理方法，包括：
本申请实施例中，远端终端为第一设备，中继终端为第二设备，
1、注册：Relay UE向Relay UE对应的AMF实体(Relay UE AMF)发送注册请求(Registration Request)消息，Relay UE对应的AMF实体向Relay UE返回注册接受(Registration Accept)消息，注册接受消息中包含移动性限制信息。
2、状态通知：可选地，可以在状态通知过程中，由Relay UE向Remote UE发送移动性限制指示信息。
如果Relay UE当前处于移动性限制(Mobility restriction)，例如处于Forbidden Area或者Non-Allowed Area中，Relay UE在发现过程中向Remote UE指示其移动性限制状态处于受限状态。发现过程分为A模式(Model A)和B模式(Model B)两种类型。
在A模式发现过程中，Relay UE发送广播Announcement消息，该消息中包含移动性限制指示信息(Mobility restriction indication)。
在B模式发现过程中，Remote UE向Relay UE发送请求Solicitation消息，Relay UE向Remote UE返回响应Response消息，该消息中包含移动性限制指示信息(Mobility restriction indication)。
可选地，Relay UE可以从PCF获取或者预配置紧急业务(Emergency)中继服务代码(Relay Service Code，RSC)，Emergency RSC用于指示Relay UE能够为Remote UE中继紧急业务。
可选地，广播Announcement消息中还可以携带Emergency RSC。
可选地，请求Solicitation消息中还可以携带远端终端对应的Emergency RSC。
可选地，响应Response消息中还可以携带中继终端对应的Emergency RSC，
可选地，Relay UE在广播Announcement消息或响应Response消息中只包含中继终端对应的Emergency RSC的情况下，那么Remote UE将只能建立Emergency PDU会话。
3、中继选择：Remote UE选择合适的Relay UE。
具体地，Remote UE根据自身需要执行的业务选择合适的Relay UE，示例性地，在Remote UE需要执行紧急业务的情况下，选择支持为Remote UE提供紧急业务的中继服务的UE作为Relay UE。本申请实施例对如何选择Relay UE不做限定。
4、PC5连接建立过程：可选地，可以在PC5连接建立过程中，由Relay UE向Remote UE发送移动性限制指示信息。
Remote UE和Relay UE之间建立PC5连接。Remote UE向Relay UE发送直接通信请求(Direct Communication Request)消息，Relay UE向Remote UE返回直接通信接受(Direct Communication Accept)消息，直接通信接受(Direct Communication Accept)消息中包含移动性限制指示信息。
可选地，如果在步骤2中，Relay UE在发现过程中没有向Remote UE指示移动性限制指示信息，Relay UE通过直接通信接受(Direct Communication Accept)消息向Remote UE发送移动性限制指示信息。
可选地，直接通信请求(Direct Communication Request)消息中可以携带有Remote UE对应的Emergency RSC。
可选地，直接通信接受(Direct Communication Accept)消息中可以携带有Relay UE对应的Emergency RSC。
可选地，Relay UE在直接通信接受(Direct Communication Accept)消息中只包含Emergency RSC，那么Remote UE将只能建立紧急业务PDU会话， 可以理解为Remote UE不发起非紧急业务PDU会话。
5、注册过程(Registration procedure)：Remote UE发起注册过程。
6、PDU会话建立过程(PDU session establishment procedure)：
如果Relay UE向Remote UE指示了Relay UE处于受限状态，Remote UE仅能发起针对紧急业务的PDU会话建立过程。
对于Remote UE对应的AMF实体和Remote UE对应的SMF实体的功能，参考相关技术，此处不再赘述。
实施例2：
图5是本申请实施例提供的非紧急业务的处理方法的流程示意图之四，如图5所示，本申请实施例提供一种非紧急业务的处理方法，包括：
本申请实施例中，远端终端为第一设备，中继终端为第二设备，
0、中继通信：Remote UE与Relay UE已建立连接，Remote UE通过Relay UE与网络进行通信。
可选地，Remote UE可以同时建立Emergency PDU会话和non-Emergency PDU会话。
1、注册过程：1a.Relay UE发起周期性注册(periodic registration)过程或移动性注册(mobility registration过程)；1b.Relay UE对应的AMF实体向Relay UE返回移动性限制信息。
2、状态通知：如果Relay UE发现自身的移动性限制状态有了更新，例如从Allowed Area变成Non-Allowed Area，Relay UE通过PC5接口向Remote UE发送状态通知消息，状态通知消息中包含移动性限制指示信息，用于指示Relay UE当前的移动性限制状态。
可选地，当Relay UE处于受限状态时，如果Remote UE在接入层(AS layer)向Relay UE指示其建立的是非紧急业务，那么Relay UE将通过AS layer拒绝Remote UE的请求，并通过AS layer向Remote UE发送移动性限制指示信息，告知Remote UE目前Relay UE处于受限状态。
3、非紧急业务PDU会话释放：如果Relay UE在步骤2中向Remote UE指示了移动性限制指示信息，且移动性限制指示信息指示中继终端的移动性 限制状态为受限状态，则表示Remote UE仅能进行紧急业务，需要释放非紧急业务PDU会话。有以下几种方法：
3a、Remote UE向Remote UE对应的SMF(Remote UE SMF)发送第一消息，第一消息可以是PDU会话释放请求(PDU session release request)消息。
可选地，第一消息中包含移动性限制指示信息，用于指示中继终端的移动性限制状态，在中继终端的移动性限制状态为受限状态下，移动性限制指示信息可以使Remote UE对应的SMF获知中继终端不支持非紧急业务，从而触发Remote UE对应的SMF释放非紧急业务PDU会话。
可选地，第一消息中包含释放非紧急业务PDU会话指示信息，用于指示Remote UE对应的SMF释放非紧急业务PDU会话。应理解，Remote UE对应的SMF接收到释放非紧急业务PDU会话指示信息后，可以直接释放非紧急业务PDU会话，无需确定中继终端的移动性限制状态。
3b、Remote UE向Remote UE对应的AMF发送第二消息，第二消息可以是NAS消息，Remote UE对应的AMF实体(Remote UE AMF)根据第二消息识别出非紧急业务PDU session ID，并向远端终端对应的SMF实体发送PDU会话释放请求(PDU session release request)消息，触发远端终端对应的SMF实体释放非紧急业务PDU会话。
可选地，第二消息中包含移动性限制指示信息，Remote UE对应的AMF根据该指示信息识别出非紧急业务PDU会话标识(identity，ID)，即第一PDU会话标识，并触发Remote UE对应的SMF释放非紧急业务PDU会话。
4、非紧急业务PDU会话释放过程：Remote UE对应的SMF发起非紧急业务PDU会话释放过程。
实施例3：
图6是本申请实施例提供的非紧急业务的处理方法的流程示意图之五，如图6所示，本申请实施例提供一种非紧急业务的处理方法，包括：
本申请实施例中，Remote UE对应的AMF实体作为第一设备，接入网NG-RAN作为第二设备。
0、中继通信：Remote UE与Relay UE已近建立连接，Remote UE通过Relay UE与网络进行通信。
可选地，Remote UE可以同时建立Emergency PDU会话和non-Emergency PDU会话。
1、注册过程：1a.Relay UE发起周期性注册(periodic registration)过程或移动性注册(mobility registration过程)；1b.Relay UE对应的AMF实体向Relay UE返回移动性限制信息。
2、状态通知：接入网NG-RAN作为第二设备，向作为第一设备的Remote UE对应的AMF实体发送移动性限制指示信息，移动性限制指示信息可以由N2消息携带。
3、非紧急业务PDU会话释放：Remote UE对应的AMF实体(Remote UE AMF)根据移动性限制指示信息识别出非紧急业务PDU会话ID，并向远端终端对应的SMF实体发送第三消息，所述第三消息可以是PDU会话释放请求(PDU session release request)消息，所述PDU会话释放请求中可以携带有非紧急业务PDU会话ID，触发远端终端对应的SMF实体释放非紧急业务PDU会话。
4、非紧急业务PDU会话释放过程：Remote UE对应的SMF发起非紧急业务PDU会话释放过程。
实施例4：
图7是本申请实施例提供的非紧急业务的处理方法的流程示意图之六，如图7所示，本申请实施例提供一种非紧急业务的处理方法，包括：
本申请实施例中，Remote UE对应的AMF实体为第一设备，Relay UE对应的AMF为第二设备。
1、发现过程：Remote UE通过发现过程发现Relay UE。
2、PC5连接建立：Remote UE和Relay UE建立PC5连接。
3、Relay UE向Relay UE对应的AMF发送NAS消息，该消息中包含远端终端的标识(Remote UE ID)，例如Remote UE对应的用户永久标识符(SUbscription Permanent Identifier，SUPI)。
4、状态通知：Relay UE对应的AMF实体(Relay UE AMF)发现Relay UE处于受限状态时，Relay UE对应的AMF实体通过远端终端的标识找到Remote UE对应的AMF实体(Remote UE AMF)，并向Remote UE AMF发送移动性限制指示信息，Remote UE对应的AMF根据移动性限制指示信息识别出非紧急业务PDU会话对应的第一PDU会话标识。
5、Remote UE对应的AMF触发Remote UE对应的SMF释放非紧急业务PDU会话，即，Remote UE对应的AMF向Remote UE对应的SMF发送第三消息，第三消息可以为PDU会话释放消息。
可选地，所述第三消息携带有所述第一PDU会话标识。
6、非紧急业务PDU会话释放过程：Remote UE对应的SMF发起非紧急业务PDU会话释放过程。
本申请实施例解决了当Remote UE连接到支持紧急业务的Relay UE，而Relay UE又处于受限状态时，如何处理Remote UE的非紧急业务PDU会话的问题。
参考图8，图8是本申请实施例提供的非紧急业务的处理装置的结构示意图之一，本申请实施例提供一种非紧急业务的处理装置，可以应用于第一设备，所述装置包括：第一接收单元810和第一确定单元820；
所述第一接收单元810，用于接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
所述第一确定单元820，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
所述第一接收单元810，用于接收第二设备发送的移动性限制指示信息，包括：
所述第一接收单元810，用于通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
可选地，所述第一确定单元820，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
所述第一确定单元820，用于在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
可选地，所述装置还包括第一发送单元；
所述第一发送单元，用于在确定释放所述非紧急业务PDU会话之后，向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
所述第一发送单元，用于在确定释放所述非紧急业务PDU会话之后，向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
可选地，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
所述第一确定单元820，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
所述第一确定单元820，用于在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
可选地，所述第一确定单元820，还用于在确定释放所述非紧急业务PDU会话之后，基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
所述第一发送单元，还用于向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU 会话标识。
本申请各实施例提供的方法和装置是基于同一申请构思的，由于非紧急业务的处理方法和非紧急业务的处理装置解决问题的原理相似，且能够达到相同的技术效果，因此装置和方法的实施可以相互参见，重复之处不再赘述。
参考图9，图9是本申请实施例提供的非紧急业务的处理装置的结构示意图之二，本申请实施例提供一种非紧急业务的处理装置，可以应用于第二设备，所述装置包括：第二发送单元910；
所述第二发送单元910，用于向第一设备发送移动性限制指示信息；
其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，所述装置还包括第二接收单元和第二确定单元；
所述第二接收单元，用于接收所述中继终端发送的所述远端终端的标识；
所述第二确定单元，用于基于所述远端终端的标识确定所述远端终端对应的AMF实体。
可选地，所述装置还包括第二拒绝单元；
所述第二拒绝单元，用于在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
可选地，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
本申请各实施例提供的方法和装置是基于同一申请构思的，由于非紧急业务的处理方法和非紧急业务的处理装置解决问题的原理相似，且能够达到相同的技术效果，因此装置和方法的实施可以相互参见，重复之处不再赘述。
需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既 可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个处理器可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对相关技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
图10为本申请实施例提供的第一设备的结构示意图，如图10所示，该第一设备包括存储器1020，收发机1000和处理器1010；其中，处理器1010与存储器1020也可以物理上分开布置。
存储器1020，用于存储计算机程序；收发机1000，用于在处理器1010的控制下收发数据；处理器1010通过调用存储器1020存储的计算机程序，用于按照获得的可执行指令执行本申请实施例提供的任一所述应用于第一设备的非紧急业务的处理方法对应的操作，例如：
接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
具体地，收发机1000用于在处理器1010的控制下接收和发送数据。
其中，在图10中，总线接口1040可以包括任意数量的互联的总线和桥，具体由处理器1010代表的一个或多个处理器和存储器1020代表的存储器的各种电路连接在一起。总线接口1040还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1000可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置 通信的单元，这些传输介质包括，这些传输介质包括无线信道、有线信道、光缆等传输介质。针对不同的第一设备，还可以包括用户接口1030，用户接口1030还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1010负责管理总线架构和通常的处理，存储器1020可以存储处理器1010在执行操作时所使用的数据。
可选的，处理器1010可以是CPU(中央处理器)、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)，处理器也可以采用多核架构。
可选地，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
所述接收第二设备发送的移动性限制指示信息，包括：
通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
可选地，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
可选地，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
在此需要说明的是，本申请实施例提供的上述第一设备，能够实现上述非紧急业务的处理方法实施例所实现的所有方法步骤，且能够达到相同的技术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
图11为本申请实施例提供的第二设备的结构示意图，如图11所示，该第二设备包括存储器1120，收发机1100和处理器1111；其中，处理器1111与存储器1120也可以物理上分开布置。
存储器1120，用于存储计算机程序；收发机1100，用于在处理器1111的控制下收发数据；处理器1111通过调用存储器1120存储的计算机程序，用于按照获得的可执行指令执行本申请实施例提供的任一所述应用于第二设备的非紧急业务的处理方法对应的操作，例如：
向第一设备发送移动性限制指示信息；
其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
具体地，收发机1100用于在处理器1111的控制下接收和发送数据。
其中，在图11中，总线接口1140可以包括任意数量的互联的总线和桥，具体由处理器1111代表的一个或多个处理器和存储器1120代表的存储器的各种电路连接在一起。总线接口1140还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口提供接口。收发机1100可以是多个元件，即包括发送机和接收机，提供用于在传输介质上与各种其他装置通信的单元，这些传输介质包括，这些传输介质包括无线信道、有线信道、光缆等传输介质。针对不同的第二设备，还可以包括用户接口1130，用户接口1130还可以是能够外接内接需要设备的接口，连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器1111负责管理总线架构和通常的处理，存储器1120可以存储处理器1111在执行操作时所使用的数据。
可选的，处理器1111可以是CPU(中央处理器)、ASIC(Application Specific Integrated Circuit，专用集成电路)、FPGA(Field－Programmable Gate Array，现场可编程门阵列)或CPLD(Complex Programmable Logic Device，复杂可编程逻辑器件)，处理器也可以采用多核架构。
可选地，在所述第二设备为所述中继终端对应的AMF实体，所述第一设备为所述远端终端对应的AMF实体的情况下，所述向第一设备发送移动性限制指示信息之前还包括：
接收所述中继终端发送的所述远端终端的标识；
基于所述远端终端的标识确定所述远端终端对应的AMF实体。
可选地，在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
可选地，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
在此需要说明的是，本申请实施例提供的上述第二设备，能够实现上述非紧急业务的处理方法实施例所实现的所有方法步骤，且能够达到相同的技 术效果，在此不再对本实施例中与方法实施例相同的部分及有益效果进行具体赘述。
另一方面，本申请实施例还提供一种处理器可读存储介质，所述处理器可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行上述各实施例提供的、应用于第一设备的方法，包括：
接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
所述接收第二设备发送的移动性限制指示信息，包括：
通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
可选地，所述直接通信消息包括以下任一：
中继发现消息；
直接通信接受消息；
状态通知消息。
可选地，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
可选地，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
可选地，所述确定释放所述非紧急业务PDU会话之后还包括：
基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
另一方面，本申请实施例还提供一种处理器可读存储介质，所述处理器可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行上述各实施例提供的、应用于第二设备的方法，包括：
向第一设备发送移动性限制指示信息；
其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
可选地，在所述第二设备为所述中继终端对应的AMF实体，所述第一设备为所述远端终端对应的AMF实体的情况下，所述向第一设备发送移动性限制指示信息之前还包括：
接收所述中继终端发送的所述远端终端的标识；
基于所述远端终端的标识确定所述远端终端对应的AMF实体。
可选地，在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
可选地，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
所述处理器可读存储介质可以是处理器能够存取的任何可用介质或数据存储设备，包括但不限于磁性存储器(例如软盘、硬盘、磁带、磁光盘(MO)等)、光学存储器(例如CD、DVD、BD、HVD等)、以及半导体存储器(例如ROM、EPROM、EEPROM、非易失性存储器(NAND FLASH)、固态硬盘(SSD))等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机可执行指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机可执行指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些处理器可执行指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的处理器可读存储器中，使得存储在该处理器可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些处理器可执行指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要 求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (34)

  1. 一种非紧急业务的处理方法，应用于第一设备，包括：
    接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
    基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
  2. 根据权利要求1所述的非紧急业务的处理方法，其中，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
    所述接收第二设备发送的移动性限制指示信息，包括：
    通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
  3. 根据权利要求2所述的非紧急业务的处理方法，其中，所述直接通信消息包括以下任一：
    中继发现消息；
    直接通信接受消息；
    状态通知消息。
  4. 根据权利要求2或3所述的非紧急业务的处理方法，其中，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
    在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
  5. 根据权利要求4所述的非紧急业务的处理方法，其中，所述确定释放所述非紧急业务PDU会话之后还包括：
    向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
    向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
    其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
  6. 根据权利要求1所述的非紧急业务的处理方法，其中，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
    所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
    在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
  7. 根据权利要求6所述的非紧急业务的处理方法，其中，所述确定释放所述非紧急业务PDU会话之后还包括：
    基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
    向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
  8. 一种非紧急业务的处理方法，应用于第二设备，包括：
    向第一设备发送移动性限制指示信息；
    其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
  9. 根据权利要求8所述的非紧急业务的处理方法，其中，在所述第二设备为所述中继终端对应的AMF实体，所述第一设备为所述远端终端对应的AMF实体的情况下，所述向第一设备发送移动性限制指示信息之前还包括：
    接收所述中继终端发送的所述远端终端的标识；
    基于所述远端终端的标识确定所述远端终端对应的AMF实体。
  10. 根据权利要求8或9所述的非紧急业务的处理方法，其中，在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
  11. 根据权利要求8或9所述的非紧急业务的处理方法，其中，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
  12. 一种第一设备，包括存储器、收发机和处理器：
    所述存储器，用于存储计算机程序；所述收发机，用于在所述处理器的控制下收发数据；所述处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
    基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
  13. 根据权利要求12所述的第一设备，其中，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
    所述接收第二设备发送的移动性限制指示信息，包括：
    通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
  14. 根据权利要求13所述的第一设备，其中，所述直接通信消息包括以下任一：
    中继发现消息；
    直接通信接受消息；
    状态通知消息。
  15. 根据权利要求13或14所述的第一设备，其中，所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
    在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
  16. 根据权利要求15所述的第一设备，其中，所述确定释放所述非紧急业务PDU会话之后还包括：
    向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一 消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
    向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
    其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
  17. 根据权利要求12所述的第一设备，其中，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
    所述基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
    在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
  18. 根据权利要求17所述的第一设备，其中，所述确定释放所述非紧急业务PDU会话之后还包括：
    基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
    向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU会话标识。
  19. 一种第二设备，包括存储器、收发机和处理器：
    所述存储器，用于存储计算机程序；所述收发机，用于在所述处理器的控制下收发数据；所述处理器，用于读取所述存储器中的计算机程序并执行以下操作：
    向第一设备发送移动性限制指示信息；
    其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
  20. 根据权利要求19所述的第二设备，其中，在所述第二设备为所述中 继终端对应的AMF实体，所述第一设备为所述远端终端对应的AMF实体的情况下，所述向第一设备发送移动性限制指示信息之前还包括：
    接收所述中继终端发送的所述远端终端的标识；
    基于所述远端终端的标识确定所述远端终端对应的AMF实体。
  21. 根据权利要求19或20所述的第二设备，其中，在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
  22. 根据权利要求19或20所述的第二设备，其中，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
  23. 一种非紧急业务的处理装置，应用于第一设备，包括：
    第一接收单元，用于接收第二设备发送的移动性限制指示信息，所述移动性限制指示信息用于指示中继终端的移动性限制状态；
    第一确定单元，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
  24. 根据权利要求23所述的非紧急业务的处理装置，其中，所述第一设备为所述远端终端，所述第二设备为所述中继终端；
    所述第一接收单元，用于接收第二设备发送的移动性限制指示信息，包括：
    所述第一接收单元，用于通过所述第二设备发送的直接通信消息，接收所述移动性限制指示信息。
  25. 根据权利要求24所述的非紧急业务的处理装置，其中，所述直接通信消息包括以下任一：
    中继发现消息；
    直接通信接受消息；
    状态通知消息。
  26. 根据权利要求24或25所述的非紧急业务的处理装置，其中，所述 第一确定单元，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
    所述第一确定单元，用于在所述中继终端的移动性限制状态为受限状态的情况下，确定不发起所述非紧急业务PDU会话或确定释放所述非紧急业务PDU会话。
  27. 根据权利要求26所述的非紧急业务的处理装置，其中，所述装置还包括第一发送单元；
    所述第一发送单元，用于在确定释放所述非紧急业务PDU会话之后，向所述远端终端对应的会话管理功能SMF实体发送第一消息，所述第一消息用于指示所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；或者，
    所述第一发送单元，用于在确定释放所述非紧急业务PDU会话之后，向所述远端终端对应的AMF实体发送第二消息，所述第二消息用于指示所述远端终端对应的AMF实体触发所述远端终端对应的SMF实体释放所述非紧急业务PDU会话；
    其中，所述第一消息或所述第二消息包含所述移动性限制指示信息。
  28. 根据权利要求23所述的非紧急业务的处理装置，其中，所述第一设备为所述远端终端对应的接入和移动性管理AMF实体，所述第二设备为接入网实体或所述中继终端对应的AMF实体；
    所述第一确定单元，用于基于所述中继终端的移动性限制状态，确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话，包括：
    所述第一确定单元，用于在所述中继终端的移动性限制状态为受限状态的情况下，确定释放所述非紧急业务PDU会话。
  29. 根据权利要求28所述的非紧急业务的处理装置，其中，所述第一确定单元，还用于在确定释放所述非紧急业务PDU会话之后，基于所述移动性限制指示信息和所述远端终端对应的PDU会话信息，确定所述非紧急业务PDU会话对应的第一PDU会话标识；
    所述第一发送单元，还用于向所述远端终端对应的SMF实体发送用于释放所述非紧急业务PDU会话的第三消息，所述第三消息携带有所述第一PDU 会话标识。
  30. 一种非紧急业务的处理装置，应用于第二设备，包括：
    第二发送单元，用于向第一设备发送移动性限制指示信息；
    其中，所述移动性限制指示信息用于指示中继终端的移动性限制状态；所述中继终端的移动性限制状态用于第一设备确定是否发起或释放远端终端的非紧急业务协议数据单元PDU会话。
  31. 根据权利要求30所述的非紧急业务的处理装置，其中，所述装置还包括第二接收单元和第二确定单元；
    所述第二接收单元，用于接收所述中继终端发送的所述远端终端的标识；
    所述第二确定单元，用于基于所述远端终端的标识确定所述远端终端对应的AMF实体。
  32. 根据权利要求30或31所述的非紧急业务的处理装置，其中，所述装置还包括第二拒绝单元；
    所述第二拒绝单元，用于在所述中继终端的移动性限制状态为受限状态，且所述中继终端接收到所述远端终端发送的非紧急业务建立请求消息的情况下，所述第二设备拒绝建立所述远端终端请求的非紧急业务。
  33. 根据权利要求30或31所述的非紧急业务的处理装置，其中，所述移动性限制指示信息是基于移动性限制信息确定的，所述移动性限制信息由所述中继终端对应的AMF实体确定。
  34. 一种处理器可读存储介质，所述处理器可读存储介质存储有计算机程序，所述计算机程序用于使所述处理器执行权利要求1至7任一项所述的非紧急业务的处理方法或权利要求8至11任一项所述的非紧急业务的处理方法。
PCT/CN2023/124259 2022-10-14 2023-10-12 非紧急业务的处理方法及装置 WO2024078580A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211262428.4 2022-10-14
CN202211262428.4A CN117939409A (zh) 2022-10-14 2022-10-14 非紧急业务的处理方法及装置

Publications (1)

Publication Number Publication Date
WO2024078580A1 true WO2024078580A1 (zh) 2024-04-18

Family

ID=90668869

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/124259 WO2024078580A1 (zh) 2022-10-14 2023-10-12 非紧急业务的处理方法及装置

Country Status (2)

Country Link
CN (1) CN117939409A (zh)
WO (1) WO2024078580A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110021234A1 (en) * 2009-07-21 2011-01-27 Scott Ferrill Tibbitts Method and system for controlling a mobile communication device in a moving vehicle
WO2021146685A1 (en) * 2020-01-19 2021-07-22 Talebi Fard Peyman Relay node selection
CN114424612A (zh) * 2020-08-18 2022-04-29 Oppo广东移动通信有限公司 中继传输的方法、中继终端和远端终端
CN114650619A (zh) * 2020-12-18 2022-06-21 华硕电脑股份有限公司 无线通信系统中支持用户设备到网络中继通信的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110021234A1 (en) * 2009-07-21 2011-01-27 Scott Ferrill Tibbitts Method and system for controlling a mobile communication device in a moving vehicle
WO2021146685A1 (en) * 2020-01-19 2021-07-22 Talebi Fard Peyman Relay node selection
CN114424612A (zh) * 2020-08-18 2022-04-29 Oppo广东移动通信有限公司 中继传输的方法、中继终端和远端终端
CN114650619A (zh) * 2020-12-18 2022-06-21 华硕电脑股份有限公司 无线通信系统中支持用户设备到网络中继通信的方法和设备

Also Published As

Publication number Publication date
CN117939409A (zh) 2024-04-26

Similar Documents

Publication Publication Date Title
WO2022036555A1 (zh) 中继传输的方法、中继终端和远端终端
WO2022028041A1 (zh) 用户终端与网络进行通信的方法、终端、网络设备及装置
US20230397020A1 (en) Method and apparatus for controlling data transmission, and storage medium
WO2022028276A1 (zh) 业务处理方法、信息指示方法、终端和网络设备
WO2023000884A1 (zh) 多播会话处理方法、网络功能实体、装置及存储介质
WO2022156439A1 (zh) 信息传输方法、装置、基站及介质
WO2022206678A1 (zh) 数据传输方法、装置及存储介质
WO2022116820A1 (zh) 终端rrc连接恢复的方法和装置
WO2024078580A1 (zh) 非紧急业务的处理方法及装置
WO2022022684A1 (zh) 中继链路连接控制方法及装置
WO2021147672A1 (zh) 会话处理方法及通信装置
WO2024067398A1 (zh) 紧急业务的处理方法及装置
WO2023020276A1 (zh) 组播广播业务数据传输方法、装置、设备以及存储介质
WO2024067322A1 (zh) 候选小区配置的变更方法、装置、终端和网络设备
WO2024082839A1 (zh) 一种信息传输方法、装置及设备
WO2024027584A1 (zh) 多播业务的业务数据接收方法、设备、装置及存储介质
WO2024017069A1 (zh) 定位方法、装置及存储介质
WO2023072014A1 (zh) 相对定位方法、电子设备、装置及存储介质
WO2023125107A1 (zh) 一种信息处理方法、装置及可读存储介质
WO2023284474A1 (zh) Amf选择方法、设备、装置及存储介质
WO2023061081A1 (zh) 一种信息处理方法、装置及可读存储介质
WO2023202343A1 (zh) 信息传输方法、终端、网络设备、装置及存储介质
WO2023116627A1 (zh) 信息处理方法、装置及可读存储介质
WO2024066399A1 (zh) 进入连接态的方法、装置、终端和网络设备
WO2023202391A1 (zh) 组播业务传输方法、设备、装置及存储介质

Legal Events

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

Ref document number: 23876780

Country of ref document: EP

Kind code of ref document: A1