WO2023185728A1 - 业务处理方法、装置、终端、网络侧设备及可读存储介质 - Google Patents

业务处理方法、装置、终端、网络侧设备及可读存储介质 Download PDF

Info

Publication number
WO2023185728A1
WO2023185728A1 PCT/CN2023/084053 CN2023084053W WO2023185728A1 WO 2023185728 A1 WO2023185728 A1 WO 2023185728A1 CN 2023084053 W CN2023084053 W CN 2023084053W WO 2023185728 A1 WO2023185728 A1 WO 2023185728A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
terminal
information
emergency
type
Prior art date
Application number
PCT/CN2023/084053
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 WO2023185728A1 publication Critical patent/WO2023185728A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • This application belongs to the field of communication technology, and specifically relates to a business processing method, device, terminal, network side equipment and readable storage medium.
  • the data of the remote terminal is transparently transmitted from the relay terminal to the core network network of the remote terminal. That is to say, the relay terminal does not know that the remote terminal The data type, including whether the remote terminal is transmitting emergency service data. In this case, if the remote terminal is transmitting non-emergency services and the relay terminal only supports emergency services or can only perform relay of emergency services in a restricted state, emergency service resources will be wasted.
  • Embodiments of the present application provide a service processing method, device, terminal, network side device and readable storage medium, which can solve the problem of waste of emergency service resources caused by the existing service processing method under relay.
  • the first aspect provides a business processing method, including:
  • the first network side device acquires first information, and the first information is used to indicate at least one of the following: a relay terminal performing emergency services, or a relay terminal performing emergency services for the first remote terminal;
  • the first network side device sends second information to the second network side device according to the first information, and the second information is used to indicate at least one of the following: relay terminal performing emergency service relay, relay The terminal performs emergency service relay for the first remote terminal.
  • the second aspect provides a business processing method, including:
  • the second network side device receives second information, and the second information is used to indicate at least one of the following: the relay terminal performs emergency service relay, the relay terminal performs emergency service relay for the first remote terminal;
  • the second network side device executes the emergency service of the first remote terminal according to the second information, and/or rejects the non-emergency service of the first remote terminal.
  • the third aspect provides a business processing method, including:
  • the terminal obtains first information, and the first information is used to indicate at least one of the following: the relay terminal performs emergency service relay, the relay terminal performs emergency service relay for the first remote terminal;
  • the terminal sends the first information.
  • a service processing device applied to the first network side device, including:
  • a first acquisition module configured to acquire first information, where the first information is used to indicate at least one of the following: a relay terminal performing emergency services, a relay terminal performing emergency services for the first remote terminal. ;
  • the first sending module is configured to send second information to the second network side device according to the first information, where the second information is used to indicate at least one of the following: the relay terminal performs relay of emergency services, relay The terminal performs emergency service relay for the first remote terminal.
  • a service processing device applied to the second network side device, including:
  • the receiving module is configured to receive second information, where the second information is used to indicate at least one of the following: the relay terminal performs emergency service relay, the relay terminal performs emergency service relay for the first remote terminal;
  • An execution module configured to execute emergency services of the first remote terminal according to the second information, and/or reject non-emergency services of the first remote terminal.
  • a service processing device applied to a terminal, including:
  • the second acquisition module is configured to acquire first information, where the first information is used to indicate at least one of the following: a relay terminal performing emergency services, a relay terminal performing emergency services for the first remote terminal. ;
  • the second sending module is used to send the first information.
  • a terminal in a seventh aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor.
  • the steps of implementing the method as described in the third aspect are executed.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to obtain first information and send the first information; the first information is used to indicate at least one of the following :
  • the relay terminal is a relay that performs emergency services, and the relay terminal is a relay that the first remote terminal performs emergency services.
  • a network side device in a ninth aspect, includes a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor.
  • a network side device including a processor and a communication interface.
  • the communication interface is used to obtain first information, and the first information is Instructing at least one of the following: the relay terminal performs emergency services as a relay, the relay terminal performs emergency services as a relay for the first remote terminal; and based on the first information, sends a second message to the second network side device.
  • the second information is used to indicate at least one of the following: the relay terminal performs emergency services as a relay, the relay terminal performs emergency services as a relay for the first remote terminal; or the network side device is a second
  • the communication interface is used to receive second information
  • the second information is used to indicate at least one of the following: the relay terminal performs emergency service relay, the relay terminal performs emergency service for the first remote terminal Service relay: the processor is configured to execute emergency services of the first remote terminal according to the second information, and/or reject non-emergency services of the first remote terminal.
  • a communication system including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the service processing method as described in the third aspect.
  • the network side device can be used to perform the steps of the second aspect. The steps of the business processing method described in the third aspect, or the steps of the business processing method described in the third aspect.
  • a readable storage medium In a twelfth aspect, a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method are implemented. The steps of the method as described in the second aspect, or the steps of implementing the method as described in the third aspect.
  • a chip in a thirteenth aspect, includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the first The steps of the method described in the second aspect, or the steps of implementing the method described in the second aspect, or the steps of implementing the method described in the third aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement as described in the first aspect
  • a communication device including a processor and a memory.
  • the memory stores programs or instructions that can be run on the processor.
  • the program or instructions are executed by the processor, the following implementation is implemented: The steps of the method described in one aspect, or the steps of implementing the method described in the second aspect, or the steps of the method described in the third aspect.
  • the first network side device may send second information to the second network side device, where the first/second information is used to indicate at least one of the following: relay terminal
  • the relay and relay terminal that perform emergency services are the relays that the first remote terminal performs emergency services.
  • the second network side device can be caused to perform emergency services of the first remote terminal according to the second information, and/or reject non-emergency services of the first remote terminal, thereby ensuring that the relay terminal supports the execution of emergency services.
  • relaying only the emergency services of the corresponding remote terminal are executed, and the non-emergency services of the corresponding remote terminal are rejected, thereby avoiding the waste of emergency service resources.
  • Figure 1 is a block diagram of a wireless communication system applicable to the embodiment of the present application.
  • Figure 2 is a flow chart of a business processing method provided by an embodiment of the present application.
  • Figure 3 is a flow chart of another business processing method provided by an embodiment of the present application.
  • Figure 4 is a flow chart of another business processing method provided by an embodiment of the present application.
  • Figure 5 is a flow chart of the business processing process in application scenario 1 of the embodiment of the present application.
  • Figure 6 is a flow chart of the business processing process in application scenario 2 of the embodiment of the present application.
  • Figure 7 is a flow chart of the business processing process in application scenario 3 of the embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a service processing device provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of another service processing device provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of another service processing device provided by an embodiment of the present application.
  • Figure 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 12 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • Figure 13 is a schematic structural diagram of a network side device provided by an embodiment of the present application.
  • first, second, etc. in the description and claims of this application are used to distinguish similar objects and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first" and “second” are distinguished objects It is usually one type, and the number of objects is not limited.
  • the first object can be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the related objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced, LTE-A Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable.
  • the system includes a terminal 11 and a network side device 12.
  • the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer, TPC), a laptop computer (Laptop Computer, LC), or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a palmtop computer, a netbook, Ultra-mobile Personal Computer (UMPC), Mobile Internet Device (MID), Augmented Reality (AR)/Virtual Reality (VR) equipment, robots, wearable devices (Wearable Device), vehicle user equipment (VUE), pedestrian terminal (Pedestrian User Equipment, PUE), smart home (home equipment with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), game consoles, Terminal devices such as personal computers (PCs), teller machines or self-service machines, wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart
  • the network side device 12 may include an access network device or a core network device, where the access network device may also be called a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a wireless device.
  • Access network equipment may include a base station, a Wireless Local Area Network (WLAN) access point or a Wireless Fidelity (WiFi) node, etc.
  • the base station may be called a Node B, an Evolved Node B (eNB), or an access point.
  • BTS Base Transceiver Station
  • BSS Basic Service Set
  • ESS Extended Service Set
  • TRP Transmitting Receiving Point
  • the base station is not limited to specific technical terms. It should be noted that in this application, in the embodiment, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.
  • the core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Service Discover features (Edge Application Server Discovery Function, EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (Centralized network configuration, CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (Local NEF, or L-NEF), Binding Support Function (Binding Support Function, BSF) , application function (Application Function, AF), etc.
  • MME mobility management entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • PCF Policy Control Function
  • the scenarios to which the embodiments of this application are adapted include but are not limited to Layer-2 relay communication, N3IWF Layer-3 relay communication, etc.
  • Layer 2 relay communication the control plane data and user plane data of the remote terminal are transparently transmitted to the Layer 2 relay terminal. Therefore, the type of data or signaling transmitted by the remote terminal cannot be sensed or known by the relay terminal.
  • the Layer-2relay terminal only supports emergency services (such as announcement of relays set by the security department, fire alarm, etc.), or the Layer-2relay terminal can only perform relay of emergency services in a restricted state (such as the Layer-2relay terminal is in congestion control, is in a non-permitted area, prohibited area, etc., and cannot perform NAS connection, user plane establishment or data transmission, etc.), and the remote terminal is transmitting non-emergency services at this time. Since the data of the remote terminal is transparently transmitted to the L2relay terminal, For relay terminals, it is actually a kind of deception and a waste of emergency service resources. Therefore, in relay communications that support emergency services, for layer 2 relay communications, it is necessary to detect whether remote terminal data and/or requests are emergency services. , and only perform emergency services and reject non-urgent services.
  • emergency services such as announcement of relays set by the security department, fire alarm, etc.
  • the Layer-2relay terminal can only perform relay of emergency services in a restricted state (such as the Layer-2relay terminal is
  • Figure 2 is a flow chart of a service processing method provided by an embodiment of the present application.
  • the method is applied to a first network side device.
  • the first network side device includes but is not limited to RAN network elements, relays ( relay) AMF, relay non-3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) interworking function (Non-3GPP InterWorking Function, N3IWF), etc.
  • the relay AMF and relay N3IWF are the network functions corresponding to the relay terminal.
  • the method includes the following steps:
  • Step 21 The first network side device obtains the first information.
  • the first information is used to indicate at least one of the following: the relay terminal performs emergency service relay, and the relay terminal performs emergency service relay for the first remote terminal. That is, the first information can be understood as transmission rule information, indicating that the relay terminal supports the relay of emergency services.
  • the relay terminal may be a terminal that is performing a relay operation, or may be a terminal that is to perform a relay operation, and this is not limited.
  • the first remote terminal is a remote terminal served by the relay terminal, and the relay terminal supports providing relay services for emergency services of the first remote terminal.
  • the first information may include but is not limited to at least one of the following: the identity of the relay terminal and the identity of the first remote terminal.
  • the relay terminal corresponding to the identification can be instructed to perform the relay of the emergency service, or with the help of the identification of the relay terminal and the first remote terminal in the first information, it can be instructed to
  • the relay terminal corresponding to the identification is a relay for the first remote terminal to perform emergency services, or with the help of the identification of the first remote terminal in the first information, the corresponding relay terminal can be instructed to perform emergency services for the first remote terminal. relay.
  • the first information may indicate at least one of the following: the relay terminal is performing relay of emergency services, and the relay terminal is performing relay of emergency services for the first remote terminal. Relay for emergency services.
  • the first network side device may receive the first information from a relay AMF or a relay terminal.
  • the first network side device may receive the first information from a relay terminal or the like.
  • the first network side device can receive the first information from a relay UPF, etc., and further, the relay UPF can receive the first information from a relay terminal or RAN network element.
  • Step 22 The first network side device sends the second information to the second network side device according to the first information.
  • the second information is used to indicate at least one of the following: the relay terminal performs emergency service relay, and the relay terminal performs emergency service relay for the first remote terminal. That is, the second information can be understood as transmission rule information, indicating that the relay terminal supports the relay of emergency services. Afterwards, if the relay terminal transparently transmits the data/signaling of the first remote terminal, the second network side device can use this second information and Indicates the type of data/signaling to determine whether to accept the data/signaling, execute only emergency services, and reject non-emergency services.
  • the second network side device can be selected as remote AMF/SMF/UPF, that is, the core network network function AMF/SMF/UPF corresponding to the remote terminal, to execute or reject the emergency service of the corresponding remote terminal.
  • the second information may include but is not limited to at least one of the following: the identity of the relay terminal and the identity of the first remote terminal.
  • the relay terminal corresponding to the identifier can be instructed to perform the relay of the emergency service, or with the help of the identifiers of the relay terminal and the first remote terminal in the second information, it can be instructed to
  • the relay terminal corresponding to the identification is a relay for the first remote terminal to perform emergency services, or with the help of the identification of the first remote terminal in the second information, the corresponding relay terminal can be instructed to perform emergency services for the first remote terminal. relay.
  • the second information may indicate at least one of the following: the relay terminal is performing relay of emergency services, and the relay terminal is performing relay of emergency services for the first remote terminal. Relay for emergency services.
  • the first network side device can send the second information to the second network side device, where the first/second information is used to indicate at least one of the following:
  • the relay terminal is a relay for the first remote terminal to perform emergency services
  • the relay terminal is a relay for the first remote terminal to perform emergency services.
  • the second network side device can be caused to perform emergency services of the first remote terminal according to the second information, and/or reject non-emergency services of the first remote terminal, thereby ensuring that the relay terminal supports the execution of emergency services.
  • the non-emergency services of the corresponding remote terminal are rejected, thereby avoiding the waste of emergency service resources.
  • the first information and the second information may be the same or different. That is to say, in some cases, the first information may be the same as the second information, in which case the first network side device plays the role of forwarding the indication information; in other cases, the first information and the second information are different, The first network side device generates second information based on the acquired first information and sends it to the second network side device.
  • the first information is used to instruct the relay terminal to perform relay of emergency services
  • the second information is used to instruct the relay terminal to perform relay of emergency services for the first remote terminal.
  • the first information may include the identity of the relay terminal
  • the second information may include the identities of the relay terminal and the first remote terminal.
  • the first network side device such as a RAN network element
  • the first network side device obtains the first information instructing the relay terminal to perform relaying of emergency services and determines that the relay terminal supports providing relay services to the first remote terminal, it can generate Second information instructing the relay terminal to perform emergency service relay for the first remote terminal, and sending the second information to the second network side device.
  • the first information is used to instruct the relay terminal to perform relay of emergency services
  • the second information is used to instruct the relay terminal to perform relay of emergency services.
  • the first information and the second information indicate the same content
  • the first network side device plays the role of forwarding the indication information.
  • the first information is used to instruct the relay terminal to perform relay of emergency services for the first remote terminal
  • the second information is used to instruct the relay terminal to perform relay of emergency services for the first remote terminal.
  • the first information and the second information indicate the same content
  • the first network side device plays the role of forwarding the indication information.
  • the above-mentioned obtaining the first information may include: when at least one of the following is satisfied, the first network side device obtains the first information:
  • the relay service code of the service performed by the relay terminal is associated with the emergency type
  • the service type performed by the relay terminal is emergency type
  • the relay terminal receives the emergency service relay indication from the remote terminal
  • the relay terminal executes the emergency service relay instruction directed to the first remote terminal
  • the registration type of the relay terminal is emergency type
  • the service request type of the relay terminal is emergency type
  • the packet data unit (Packet Data Unit, PDU) session request type of the relay terminal is the emergency type.
  • the above-mentioned obtaining the first information may include: the first network side device receiving the first information from the third network side device and/or the relay terminal.
  • the third network side device is a relay AMF.
  • the third network side device is relay UPF.
  • the first information may be that the third network side device meets at least one of the following conditions: Sent by:
  • the relay service code of the service performed by the relay terminal is associated with the emergency type
  • the service type performed by the relay terminal is emergency type
  • the relay terminal receives the emergency service relay indication from the remote terminal
  • the relay terminal executes the emergency service relay instruction directed to the first remote terminal
  • the registration type of the relay terminal is emergency type
  • the service request type of the relay terminal is emergency type
  • the PDU session request type of the relay terminal is emergency type.
  • the above sending the second information to the second network side device may include: when the first network side device receives data and/or signaling from the first remote terminal, sending the second information to the second network side device. 2. Information. That is, when it is necessary to determine whether to accept data and/or signaling from the first remote terminal, the second information is sent to the second network side device.
  • This signaling can request signaling, such as Radio Resource Control Protocol (Radio Resource Control, RRC) connection establishment/modification request, etc.
  • Radio Resource Control Protocol Radio Resource Control, RRC
  • Figure 3 is a flow chart of a service processing method provided by an embodiment of the present application.
  • the method is applied to a second network side device.
  • the second network side device includes but is not limited to remote AMF, remote SMF, remote PCF, etc., this is the core network network function corresponding to the remote terminal.
  • the method includes the following steps:
  • Step 31 The second network side device receives the second information.
  • the second information is used to indicate at least one of the following: the relay terminal performs emergency service relay, and the relay terminal performs emergency service relay for the first remote terminal. That is, the second information can be understood as transmission rule information, indicating that the relay terminal supports the relay of emergency services.
  • the relay terminal may be a terminal that is performing a relay operation, or may be a terminal that is to perform a relay operation, and this is not limited.
  • the first remote terminal is a remote terminal served by the relay terminal, and the relay terminal supports providing relay services for emergency services of the first remote terminal.
  • the second information may include but is not limited to at least one of the following: the identity of the relay terminal and the identity of the first remote terminal.
  • the relay terminal corresponding to the identification can be instructed to perform the relay of the emergency service, or with the help of the relay terminal in the second information and the identifier of the first remote terminal, the relay terminal corresponding to the identifier can be instructed to perform emergency service relay for the first remote terminal, or the corresponding relay terminal can be instructed to use the identifier of the first remote terminal in the second information.
  • the relay terminal performs emergency service relay for the first remote terminal.
  • the second information may indicate at least one of the following: the relay terminal is performing relay of emergency services, and the relay terminal is performing relay of emergency services for the first remote terminal. Relay for emergency services.
  • the second network side device may receive the second information from the first network side device (such as a RAN network element, relay AMF or relay N3IWF, etc.).
  • the first network side device such as a RAN network element, relay AMF or relay N3IWF, etc.
  • Step 33 The second network side device executes the emergency service of the first remote terminal according to the second information, and/or rejects the non-emergency service of the first remote terminal.
  • the second network side device may receive the data and/or request message sent by the first remote terminal to perform the emergency service therein, or reject the non-emergency service of the first remote terminal.
  • the second network side device can execute the emergency service of the first remote terminal according to the received second information, and/or reject the non-emergency service of the first remote terminal; this second
  • the information is used to indicate at least one of the following: the relay terminal performs emergency service relay, and the relay terminal performs emergency service relay for the first remote terminal. This ensures that when the relay terminal supports relaying of emergency services, only the emergency services of the corresponding remote terminal are performed and the non-emergency services of the corresponding remote terminal are rejected, thereby avoiding waste of emergency service resources.
  • the above step 33 may include at least one of the following:
  • the second network side device determines that the type of data of the first remote terminal is an emergency type, it sends the data of the first remote terminal according to the second information; or, after determining the type of data of the first remote terminal If it is not an emergency type, refuse to send the data of the first remote terminal according to the second information;
  • the second network side device determines that the type of the request message of the first remote terminal is an emergency type, it responds to the request message of the first remote terminal according to the second information; or, after determining that the request message of the first remote terminal If the message type is not an emergency type, the request message from the first remote terminal is rejected according to the second information.
  • the request message is an RRC connection establishment/modification request, etc.
  • the second network side device may determine whether the type of the data of the first remote terminal is an emergency type or not based on the type indication in the data of the first remote terminal.
  • the type indication is used to indicate whether the type of the corresponding data is an emergency type or not.
  • the second network side device may determine whether the type of the request message of the first remote terminal is an emergency type or not based on the type indication in the request message of the first remote terminal.
  • the type indication is used to indicate whether the type of the corresponding request message is an emergency type or not.
  • Figure 4 is a flow chart of a service processing method provided by an embodiment of the present application.
  • the method is applied to a terminal.
  • the terminal can be a relay terminal, or other terminals associated with the relay terminal (such as A terminal that forwards transmission information of a relay terminal, etc.).
  • the method includes the following steps:
  • Step 41 The terminal obtains the first information.
  • the first information is used to indicate at least one of the following: the relay terminal performs emergency service relay, and the relay terminal performs emergency service relay for the first remote terminal. That is, the first information can be understood as transmission rule information, indicating that the relay terminal supports the relay of emergency services.
  • the relay terminal may be a terminal that is performing a relay operation, or may be a terminal that is to perform a relay operation, and this is not limited.
  • the first remote terminal is a remote terminal served by the relay terminal, and the relay terminal supports providing relay services for emergency services of the first remote terminal.
  • the first information may include but is not limited to at least one of the following: the identity of the relay terminal and the identity of the first remote terminal.
  • the relay terminal corresponding to the identification can be instructed to perform the relay of the emergency service, or with the help of the identification of the relay terminal and the first remote terminal in the first information, it can be instructed to
  • the relay terminal corresponding to the identification is a relay for the first remote terminal to perform emergency services, or with the help of the identification of the first remote terminal in the first information, the corresponding relay terminal can be instructed to perform emergency services for the first remote terminal. relay.
  • the first information may indicate at least one of the following: the relay terminal is performing relay of emergency services, and the relay terminal is performing relay of emergency services for the first remote terminal. Relay for emergency services.
  • Step 42 The terminal sends the first information.
  • the relay terminal may send to the RAN network element and/or relay AMF.
  • the business processing method in the embodiment of the present application can send the first information through the terminal, so that the first After obtaining the first information, the network side device sends second information to the second network side device, where the first/second information is used to indicate at least one of the following: relay terminal performing emergency services, relay terminal Performing emergency service relay for the first remote terminal.
  • the second network side device can be caused to execute the emergency service of the first remote terminal according to the received second information, and/or reject the non-emergency service of the first remote terminal, thereby ensuring that the relay terminal supports execution When relaying emergency services, only the emergency services of the corresponding remote terminal are executed, and the non-emergency services of the corresponding remote terminal are rejected, thereby avoiding waste of emergency service resources.
  • the above-mentioned obtaining the first information may include: when at least one of the following is satisfied: the terminal obtains the first information:
  • the relay service code of the service performed by the relay terminal is associated with the emergency type
  • the service type performed by the relay terminal is emergency type
  • the relay terminal receives the emergency service relay indication from the remote terminal
  • the relay terminal executes the emergency service relay instruction directed to the first remote terminal
  • the registration type of the relay terminal is emergency type
  • the service request type of the relay terminal is emergency type
  • the PDU session request type of the relay terminal is emergency type.
  • the relay terminal may forward (transparently transmit) data and/or request messages to the first remote terminal.
  • the data and/or request messages include a type indication.
  • the type indication Used to indicate whether the service type of the data and/or request message is emergency type.
  • the core network element corresponding to the first remote terminal receives the data and/or request message, only the emergency service can be executed based on the received second information and the type indication in the data and/or request message. , reject non-urgent business.
  • This embodiment 1 mainly describes that in layer 2 relay communication, the RAN network element obtains the first information and sends the second information to the remote AMF, and the remote AMF determines whether to perform remote UE operation. business. As shown in Figure 5, it includes the following steps:
  • Step 1 The relay AMF determines the relay on which the relay UE performs emergency services, obtains and sends the first information to the RAN network element.
  • the first information may be as described in the above embodiment, and will not be described again here.
  • the relay AMF may determine the relay on which the relay UE performs the emergency service after learning at least one of the following: the relay service code of the service performed by the relay UE is associated with the emergency type, and the service type performed by the relay UE is emergency.
  • Type relay UE receives the emergency service relay indication from the remote terminal, relay UE performs the relay indication of the emergency service, relay UE's registration type is emergency type, etc.
  • Step 2 After receiving the first information, the RAN network element sends the second information to the remote AMF.
  • the second information may be as described in the above embodiment, and will not be described again here.
  • the RAN network element after receiving a request message from the first remote terminal (such as an RRC connection establishment request, etc.), the RAN network element sends the second information to the remote AMF.
  • a request message from the first remote terminal such as an RRC connection establishment request, etc.
  • Step 3 Based on the received second information and combined with the data of the first remote UE and/or the type indication in the request message, the remote AMF only executes emergency services for the first remote UE and rejects non-emergency services.
  • This Embodiment 2 mainly describes that in layer 2 relay communication, the relay AMF obtains the first information and sends the second information to the remote AMF, and the remote AMF determines whether to execute the remote UE's service. As shown in Figure 6, it includes the following steps:
  • Step 1 relay AMF determines the relay on which relay UE performs emergency services, obtains the first information, and sends the second information to remote AMF.
  • the first information and the second information may be as described in the above embodiments, and will not be described again here.
  • Step 2 Step 3: Based on the received second information and combined with the data of the first remote UE and/or the type indication in the request message, the remote AMF only executes emergency services for the first remote UE and rejects non-emergency services.
  • This Embodiment 3 mainly describes that in the layer 3 relay communication of N3IWF, the relay UPF obtains and sends the first information to the relay N3IWF, and the relay N3IWF sends the second information to the remote AMF, so that the remote AMF determines whether to execute the service of the remote UE. . As shown in Figure 7, it includes the following steps:
  • Step 1 relay UPF associates the emergency type based on the relay service code of the service performed by relay UE, the service type performed by relay UE is the emergency type, the relay UE receives the emergency service relay indication from the remote terminal, and the relay UE performs the emergency service.
  • relay indication relay UE's registration type is emergency type, etc., determine the relay for relay UE to perform emergency services, obtain and send the first information to relay N3IWF.
  • the first information may be as described in the above embodiment, and will not be described again here.
  • relay UPF when relay UPF detects the data/signaling of the first remote UE, it sends the first information to relay N3IWF.
  • Step 2 After relay N3IWF receives the first information, it sends the second information to remote AMF.
  • the second information may be as described in the above embodiment, and will not be described again here.
  • Step 3 Based on the received second information and combined with the data of the first remote UE and/or the type indication in the request message, the remote AMF only executes emergency services for the first remote UE and rejects non-emergency services.
  • the execution subject may be a business processing device.
  • the business processing device executing the business processing method is taken as an example to illustrate the business processing device provided by the embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a service processing device provided by an embodiment of the present application.
  • the device is applied to a first network side device.
  • the first network side device includes but is not limited to RAN network elements, relay AMF, relay N3IWF etc.
  • the business processing device 80 includes:
  • the first acquisition module 81 is configured to acquire first information, where the first information is used to indicate at least one of the following: a relay terminal performing emergency services, a relay terminal performing emergency services for the first remote terminal. continue; continue;
  • the first sending module 82 is configured to send second information to the second network side device according to the first information, where the second information is used to indicate at least one of the following: the relay terminal performs relay of emergency services; The relay terminal performs emergency service relay for the first remote terminal.
  • the first information is used to instruct the relay terminal to perform relay of emergency services
  • the second information is used to instruct the relay terminal to perform relay of emergency services for the first remote terminal
  • the first information is used to instruct the relay terminal to perform relay of emergency services
  • the second information is used to instruct the relay terminal to perform relay of emergency services
  • the first information is used to instruct the relay terminal to perform emergency services for the first remote terminal.
  • the second information is used to instruct the relay terminal to perform relay of emergency services for the first remote terminal.
  • the first information includes at least one of the following: the identity of the relay terminal, the identity of the first remote terminal; and/or the second information includes at least one of the following: the The identity of the relay terminal and the identity of the first remote terminal.
  • the first acquisition module 81 is specifically configured to acquire the first information when at least one of the following is satisfied:
  • the relay service code of the service performed by the relay terminal is associated with the emergency type
  • the service type performed by the relay terminal is emergency type
  • the relay terminal receives the emergency service relay indication from the remote terminal
  • the relay terminal executes the emergency service relay instruction directed to the first remote terminal
  • the registration type of the relay terminal is emergency type
  • the service request type of the relay terminal is emergency type
  • the PDU session request type of the relay terminal is emergency type.
  • the first acquisition module 81 is specifically used for:
  • the first information is received from a third network side device and/or a relay terminal.
  • the first information is sent by the third network side device when at least one of the following is satisfied:
  • the relay service code of the service performed by the relay terminal is associated with the emergency type
  • the service type performed by the relay terminal is emergency type
  • the relay terminal receives the emergency service relay indication from the remote terminal
  • the relay terminal executes the emergency service relay instruction directed to the first remote terminal
  • the registration type of the relay terminal is emergency type
  • the service request type of the relay terminal is emergency type
  • the PDU session request type of the relay terminal is emergency type.
  • the first sending module 82 is specifically configured to: upon receiving data and/or signaling from the first remote terminal, send the second information to the second network side device.
  • the business processing device 80 provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 2 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • Figure 9 is a schematic structural diagram of a service processing device provided by an embodiment of the present application.
  • the device is applied to a second network side device.
  • the second network side device includes but is not limited to remote AMF, remote SMF, remote PCF etc.
  • the business processing device 90 includes:
  • the receiving module 91 is configured to receive second information, where the second information is used to indicate at least one of the following: the relay terminal performs emergency service relay, the relay terminal performs emergency service relay for the first remote terminal;
  • the execution module 92 is configured to execute the emergency service of the first remote terminal according to the second information, and/or reject the non-emergency service of the first remote terminal.
  • the second information includes at least one of the following:
  • the identity of the relay terminal and the identity of the first remote terminal are identical to the identity of the relay terminal and the identity of the first remote terminal.
  • the receiving module 91 is also configured to receive data and/or request messages sent by the first remote terminal.
  • the execution module 92 is used for at least one of the following:
  • the request message of the first remote terminal When it is determined that the type of the request message of the first remote terminal is an emergency type, respond to the request message of the first remote terminal according to the second information; or, after determining that the first remote terminal If the type of the terminal's request message is not an emergency type, the request message of the first remote terminal is rejected according to the second information.
  • the execution module 92 is also used for at least one of the following:
  • the type indication in the request message of the first remote terminal it is determined whether the type of the request message of the first remote terminal is an emergency type or not.
  • the business processing device 90 provided by the embodiment of the present application can implement the method implemented by the method embodiment in Figure 3. Each process, and achieve the same technical effect, will not be repeated here to avoid repetition.
  • Figure 10 is a schematic structural diagram of a service processing device provided by an embodiment of the present application. The device is applied to a terminal. As shown in Figure 10, the service processing device 100 includes:
  • the second acquisition module 101 is used to acquire first information, where the first information is used to indicate at least one of the following: a relay terminal performing emergency services, a relay terminal performing emergency services for the first remote terminal. continue; continue;
  • the second sending module 102 is used to send the first information.
  • the first information includes at least one of the following:
  • the identity of the relay terminal and the identity of the first remote terminal are identical to the identity of the relay terminal and the identity of the first remote terminal.
  • the second acquisition module 101 is used to acquire the first information when at least one of the following is satisfied:
  • the relay service code of the service performed by the relay terminal is associated with the emergency type
  • the service type performed by the relay terminal is emergency type
  • the relay terminal receives the emergency service relay indication from the remote terminal
  • the relay terminal executes the emergency service relay instruction directed to the first remote terminal
  • the registration type of the relay terminal is emergency type
  • the service request type of the relay terminal is emergency type
  • the PDU session request type of the relay terminal is emergency type.
  • the second sending module 102 is also configured to: after the relay path of the emergency service is established, forward data and/or request messages for the first remote terminal,
  • the data and/or request message includes a type indication, and the type indication is used to indicate whether the service type of the data and/or request message is an emergency type.
  • the business processing device 100 provided by the embodiment of the present application can implement each process implemented by the method embodiment in Figure 4 and achieve the same technical effect. To avoid duplication, the details will not be described here.
  • this embodiment of the present application also provides a communication device 110, which includes a processor 111 and a memory 112.
  • the memory 112 stores programs or instructions that can be run on the processor 111, for example.
  • the communication device 110 is the first network side device, when the program or instruction is executed by the processor 111, the steps of the business processing method embodiment shown in Figure 2 are implemented, and can The same technical effect is achieved;
  • the communication device 110 is a second network side device, when the program or instruction is executed by the processor 111, the steps of the business processing method embodiment shown in Figure 3 are implemented, and the same technology can be achieved. Effect;
  • the communication device 110 is a terminal, when the program or instruction is executed by the processor 111, each step of the business processing method embodiment shown in Figure 4 is implemented, and the same technical effect can be achieved; to avoid duplication, no description is given here. Again.
  • An embodiment of the present application also provides a terminal, including a processor and a communication interface.
  • the communication interface is used to obtain first information and send the first information; the first information is used to indicate at least one of the following: relay terminal
  • the relay and relay terminal that perform emergency services are the relays that the first remote terminal performs emergency services.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment.
  • Each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 12 is a schematic diagram of the hardware structure of a terminal that implements an embodiment of the present application.
  • the terminal 1200 includes but is not limited to: a radio frequency unit 1201, a network module 1202, an audio output unit 1203, an input unit 1204, a sensor 1205, a display unit 1206, a user input unit 1207, an interface unit 1208, a memory 1209, a processor 1210, etc. At least some parts.
  • the terminal 1200 may also include a power supply (such as a battery) that supplies power to various components.
  • the power supply may be logically connected to the processor 1210 through a power management system, thereby managing charging, discharging, and power consumption through the power management system. Management and other functions.
  • the terminal structure shown in Figure 12 does not constitute a limitation on the terminal.
  • the terminal may include more or fewer components than shown in the figure, or some components may be combined or arranged differently, which will not be described again here.
  • the input unit 1204 may include a graphics processing unit (GPU) 12041 and a microphone 12042.
  • the graphics processor 12041 is responsible for the image capture device (GPU) in the video capture mode or the image capture mode. Process the image data of still pictures or videos obtained by cameras (such as cameras).
  • the display unit 1206 may include a display panel 12061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 1207 includes at least one of a touch panel 12071 and other input devices 12072 .
  • Touch panel 12071 also known as touch screen.
  • the touch panel 12071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 12072 may include but are not limited to physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described again here.
  • the radio frequency unit 1201 after receiving downlink data from the network side device, the radio frequency unit 1201 can transmit it to the processor 1210 for processing; in addition, the radio frequency unit 1201 can send uplink data to the network side device.
  • the radio frequency unit 1201 includes, but is not limited to, an antenna, amplifier, transceiver, coupler, low noise amplifier, duplexer, etc.
  • Memory 1209 may be used to store software programs or instructions as well as various data.
  • the memory 1209 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, Image playback function, etc.) etc.
  • memory 1209 may include volatile memory or nonvolatile memory, or memory 1209 may include both volatile and nonvolatile memory.
  • non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically removable memory.
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM) , SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory Synchronous DRAM, SDRAM
  • Double data rate synchronous dynamic random access memory Double Data Rate SDRAM, DDRSDRAM
  • Enhanced SDRAM, ESDRAM synchronous link dynamic random access memory
  • Synch link DRAM synchronous link dynamic random access memory
  • SLDRAM direct memory bus random access memory
  • the processor 1210 may include one or more processing units; optionally, the processor 1210 integrates an application processor and a modem processor, where the application processor mainly handles operations related to the operating system, user interface, application programs, etc., Modem processors mainly process wireless communication signals, such as baseband processors. It can be understood that the above modem processor may not be integrated into the processor 1210.
  • the radio frequency unit 1201 is used to obtain the first information and send the first information; the first information is used to indicate at least one of the following: the relay terminal performs emergency service relay, the relay terminal is the first The remote terminal performs emergency service relay.
  • the first information includes at least one of the following: an identity of the relay terminal and an identity of the first remote terminal.
  • the radio frequency unit 1201 is also configured to obtain the first information when at least one of the following is satisfied:
  • the relay service code of the service performed by the relay terminal is associated with the emergency type
  • the service type performed by the relay terminal is emergency type
  • the relay terminal receives the emergency service relay indication from the remote terminal
  • the relay terminal executes the emergency service relay instruction directed to the first remote terminal
  • the registration type of the relay terminal is emergency type
  • the service request type of the relay terminal is emergency type
  • the PDU session request type of the relay terminal is emergency type.
  • the terminal 1200 is a relay terminal
  • the processor 1210 is configured to: after the relay path of the emergency service is established, forward data and/or request messages for the first remote terminal.
  • the message includes a type indication, and the type indication is used to indicate whether the service type of the data and/or request message is an emergency type.
  • the terminal 1200 provided by the embodiment of this application can implement each process implemented by the method embodiment in Figure 4 and achieve the same technical effect. To avoid duplication, details will not be described here.
  • An embodiment of the present application also provides a network side device, including a processor and a communication interface.
  • the communication interface is used to obtain first information, and the first information is used to indicate at least the following: One item: the relay terminal performs emergency services as a relay, and the relay terminal performs emergency services as a relay for the first remote terminal; and sends second information to the second network side device according to the first information, said The second information is used to indicate at least one of the following: the relay terminal performs emergency services as a relay, the relay terminal performs emergency services as a relay for the first remote terminal; or, when the network side device is a second network side device , the communication interface is used to receive second information, the second information is used to indicate at least one of the following: the relay terminal performs emergency service relay, the relay terminal performs emergency service relay for the first remote terminal; processing The server is configured to execute emergency services of the first remote terminal according to the second information, and/or reject non-emergency services of the first remote terminal.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment.
  • Each implementation process and implementation of the above-mentioned method embodiment are All existing methods can be applied to the network side device embodiment and can achieve the same technical effect, which will not be described again here.
  • the network side device 130 includes: a processor 131 , a network interface 132 and a memory 133 .
  • the network interface 132 is, for example, a Common Public Radio Interface (CPRI).
  • CPRI Common Public Radio Interface
  • the network side device 130 in the embodiment of the present application also includes: instructions or programs stored in the memory 133 and executable on the processor 131.
  • the processor 131 calls the instructions or programs in the memory 133 to execute Figure 8 or Figure 9
  • the execution methods of each module are shown and achieve the same technical effect. To avoid repetition, they will not be described in detail here.
  • Embodiments of the present application also provide a readable storage medium.
  • Programs or instructions are stored on the readable storage medium.
  • the program or instructions are executed by a processor, each process of the above business processing method embodiment is implemented and the same can be achieved. The technical effects will not be repeated here to avoid repetition.
  • the processor is the processor in the terminal described in the above embodiment.
  • the readable storage medium includes computer readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip.
  • the chip includes a processor and a communication interface.
  • the communication interface is coupled to the processor.
  • the processor is used to run programs or instructions to implement the above business processing method embodiment. Each process can achieve the same technical effect. To avoid duplication, it will not be described again here.
  • chips mentioned in the embodiments of this application may also be called system-on-chip, system-on-a-chip, system-on-chip or system-on-chip, etc.
  • Embodiments of the present application further provide a computer program/program product.
  • the computer program/program product is stored in a storage medium.
  • the computer program/program product is executed by at least one processor to implement the above business processing method embodiment.
  • Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.
  • Embodiments of the present application also provide a communication system, including: a terminal and a network side device.
  • the terminal can be used to perform the steps of the method shown in Figure 4 as described above.
  • the network side device can be used to perform the steps of the method shown in Figure 4 as described above. 2, or perform the steps of the method shown in Figure 3 as described above.
  • the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation.
  • the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology.
  • the computer software product is stored in a storage medium (such as ROM/RAM, disk , CD), including several instructions to cause a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in various embodiments of this application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Emergency Management (AREA)
  • Environmental & Geological Engineering (AREA)
  • Public Health (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种业务处理方法、装置、终端、网络侧设备及可读存储介质，属于通信技术领域，本申请实施例的业务处理方法包括：第一网络侧设备获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；并根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。

Description

业务处理方法、装置、终端、网络侧设备及可读存储介质
相关申请的交叉引用
本申请主张在2022年3月28日在中国提交的中国专利申请No.202210313494.3的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种业务处理方法、装置、终端、网络侧设备及可读存储介质。
背景技术
现有技术中，对于中继通信，远端(remote)终端的数据是透传中继(relay)终端到远端终端的核心网网络的，也就是说，中继终端并不知道远端终端的数据类型，包括远端终端是不是正在执行紧急业务数据的传输。这种情况下，如果远端终端在执行非紧急业务的传输，而中继终端仅支持紧急业务或者在受限状态下只能执行紧急业务的中继，将会造成紧急业务资源的浪费。
发明内容
本申请实施例提供一种业务处理方法、装置、终端、网络侧设备及可读存储介质，能够解决现有中继下的业务处理方法造成的紧急业务资源浪费的问题。
第一方面，提供了一种业务处理方法，包括：
第一网络侧设备获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
所述第一网络侧设备根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。
第二方面，提供了一种业务处理方法，包括：
第二网络侧设备接收第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
所述第二网络侧设备根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务。
第三方面，提供了一种业务处理方法，包括：
终端获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
所述终端发送所述第一信息。
第四方面，提供了一种业务处理装置，应用于第一网络侧设备，包括：
第一获取模块，用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
第一发送模块，用于根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。
第五方面，提供了一种业务处理装置，应用于第二网络侧设备，包括：
接收模块，用于接收第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
执行模块，用于根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务。
第六方面，提供了一种业务处理装置，应用于终端，包括：
第二获取模块，用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
第二发送模块，用于发送所述第一信息。
第七方面，提供了一种终端，该终端包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执 行时实现如第三方面所述的方法的步骤。
第八方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于获取第一信息，并发送所述第一信息；所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。
第九方面，提供了一种网络侧设备，该网络侧设备包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤。
第十方面，提供了一种网络侧设备，包括处理器及通信接口，其中，该网络侧设备为第一网络侧设备时，所述通信接口用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；并根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；或者，该网络侧设备为第二网络侧设备时，所述通信接口用于接收第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；所述处理器用于根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务。
第十一方面，提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如第三方面所述的业务处理方法的步骤，所述网络侧设备可用于执行如第二方面所述的业务处理法的步骤，或者如第三方面所述的业务处理法的步骤。
第十二方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十三方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一 方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十四方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十五方面，提供了一种通信设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
在本申请实施例中，第一网络侧设备在获取第一信息之后，可以向第二网络侧设备发送第二信息，所述第一/第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。由此，可以使得第二网络侧设备根据第二信息，执行第一远端终端的紧急业务，和/或，拒绝第一远端终端的非紧急业务，从而确保在中继终端支持执行紧急业务的中继时，仅执行相应远端终端的紧急业务，拒绝相应远端终端的非紧急业务，从而避免对紧急业务资源的浪费。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例提供的一种业务处理方法的流程图；
图3是本申请实施例提供的另一种业务处理方法的流程图；
图4是本申请实施例提供的另一种业务处理方法的流程图；
图5是本申请实施例的应用场景1中的业务处理过程的流程图；
图6是本申请实施例的应用场景2中的业务处理过程的流程图；
图7是本申请实施例的应用场景3中的业务处理过程的流程图；
图8是本申请实施例提供的一种业务处理装置的结构示意图；
图9是本申请实施例提供的另一种业务处理装置的结构示意图；
图10是本申请实施例提供的另一种业务处理装置的结构示意图；
图11是本申请实施例提供的一种通信设备的结构示意图；
图12是本申请实施例提供的一种终端的结构示意图；
图13是本申请实施例提供的一种网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系 统包括终端11和网络侧设备12。其中，终端11可以是手机、平板电脑(Tablet Personal Computer，TPC)、膝上型电脑(Laptop Computer，LC)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(Ultra-mobile Personal Computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(Augmented Reality，AR)/虚拟现实(Virtual Reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(Personal Computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备也可以称为无线接入网设备、无线接入网(Radio Access Network，RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点或无线保真(Wireless Fidelity，WiFi)节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能 (Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)，统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)，网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
可选的，本申请实施例适应的场景包括但不限于层二(Layer-2)中继通信、N3IWF的层三中继通信等。对于层二中继通信，remote终端的控制面数据和用户面数据都是透传层二relay终端，因此，Remote终端传输的数据或者信令的类型，relay终端无法感知或者得知的。如果Layer-2relay终端仅支持紧急业务(如公告安全部门设置的中继，火警等)，或者Layer-2relay终端在受限状态下只能执行紧急业务的中继(如Layer-2relay终端正处于拥塞控制，处于非允许区域，禁止区域等，无法执行NAS连接、用户面的建立或者数据传输等)，而remote终端此时进行非紧急业务的传输，由于remote终端的数据是透传L2relay终端，因此对于relay终端来说实际上是一种欺骗以及对紧急业务资源的浪费，因此在支持紧急业务的中继通信中，对于层二中继通信，需要检测remote终端数据和/或请求是否是紧急业务，并仅执行紧急业务，拒绝非紧急业务。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的业务处理方法、装置、终端、网络侧设备及可读存储介质进行详细地说明。
请参见图2，图2是本申请实施例提供的一种业务处理方法的流程图，该方法应用于第一网络侧设备，该第一网络侧设备包括但不限于RAN网元、中继(relay)AMF、中继非第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)互通功能(Non-3GPP InterWorking Function，N3IWF)等，该relay AMF和relay N3IWF为relay终端对应的网络功能。如图2所示，该方法包括如下步骤：
步骤21：第一网络侧设备获取第一信息。
本实施例中，第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。即第一信息可理解为传输规则信息，指示中继终端支持的是紧急业务的中继。中继终端可以为正在执行中继操作的终端，也可以为待执行中继操作的终端，对此不作限定。第一远端终端为中继终端所服务的远端终端，且中继终端支持的是为第一远端终端的紧急业务提供中继服务。
可选的，第一信息可以包括但不限于以下至少一项：中继终端的标识、第一远端终端的标识。这样借助第一信息中的中继终端的标识，可以指示该标识对应的中继终端执行紧急业务的中继，或者借助第一信息中的中继终端和第一远端终端的标识，可以指示该标识对应的中继终端为第一远端终端执行紧急业务的中继，或者借助第一信息中的第一远端终端的标识，可以指示相应中继终端为第一远端终端执行紧急业务的中继。
一些实施例中，如果中继终端正在执行紧急业务的中继，则第一信息可以指示以下至少一项：中继终端正在执行紧急业务的中继、中继终端正在为第一远端终端执行紧急业务的中继。
一些实施例中，如果第一网络侧设备为RAN网元，则第一网络侧设备可以从relay AMF或者relay终端等接收第一信息。
另一些实施例中，如果第一网络侧设备为relay AMF，则第一网络侧设备可以从relay终端等接收第一信息。
另一些实施例中，如果第一网络侧设备为relay N3IWF，则第一网络侧设备可以从relay UPF等接收第一信息，进一步的，relay UPF可以从relay终端或RAN网元接收第一信息。
步骤22：第一网络侧设备根据第一信息，向第二网络侧设备发送第二信息。
本实施例中，第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。即第二信息可理解为传输规则信息，指示中继终端支持的是紧急业务的中继。此后若中继终端透传第一远端终端的数据/信令，则第二网络侧设备可以根据此第二信息以及 数据/信令的类型指示，确定是否接受该数据/信令，并仅执行紧急业务，拒绝非紧急业务。
可选的，第二网络侧设备可选为remote AMF/SMF/UPF，即remote终端对应的核心网网络功能AMF/SMF/UPF，以执行或拒绝相应remote终端的紧急业务。
可选的，第二信息可以包括但不限于以下至少一项：中继终端的标识、第一远端终端的标识。这样借助第二信息中的中继终端的标识，可以指示该标识对应的中继终端执行紧急业务的中继，或者借助第二信息中的中继终端和第一远端终端的标识，可以指示该标识对应的中继终端为第一远端终端执行紧急业务的中继，或者借助第二信息中的第一远端终端的标识，可以指示相应中继终端为第一远端终端执行紧急业务的中继。
一些实施例中，如果中继终端正在执行紧急业务的中继，则第二信息可以指示以下至少一项：中继终端正在执行紧急业务的中继、中继终端正在为第一远端终端执行紧急业务的中继。
本申请实施例的业务处理方法，第一网络侧设备在获取第一信息之后，可以向第二网络侧设备发送第二信息，所述第一/第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。由此，可以使得第二网络侧设备根据第二信息，执行第一远端终端的紧急业务，和/或，拒绝第一远端终端的非紧急业务，从而确保在中继终端支持执行紧急业务的中继时，仅执行相应远端终端的紧急业务，拒绝相应远端终端的非紧急业务，从而避免对紧急业务资源的浪费。
需指出的，在本申请实施例中，第一信息与第二信息可以相同也可以不同。也就是说，一些情况下，第一信息可以与第二信息相同，此时第一网络侧设备起到的是转发指示信息的作用；而另一些情况下，第一信息与第二信息不同，第一网络侧设备根据获取的第一信息，生成第二信息并将其发送至第二网络侧设备。
可选的，第一信息用于指示中继终端执行紧急业务的中继，第二信息用于指示中继终端为第一远端终端执行紧急业务的中继。此情况下，第一信息可包括中继终端的标识，第二信息可包括中继终端和第一远端终端的标识。 比如，第一网络侧设备(如RAN网元)在获取指示中继终端执行紧急业务的中继的第一信息后，确定中继终端支持为第一远端终端提供中继服务，则可以生成指示中继终端为第一远端终端执行紧急业务的中继的第二信息，并将该第二信息发送给第二网络侧设备。
可选的，第一信息用于指示中继终端执行紧急业务的中继，第二信息用于指示中继终端执行紧急业务的中继。此情况下，第一信息与第二信息所指示内容相同，第一网络侧设备起到的是转发指示信息的作用。
可选的，第一信息用于指示中继终端为第一远端终端执行紧急业务的中继，第二信息用于指示中继终端为第一远端终端执行紧急业务的中继。此情况下，第一信息与第二信息所指示内容相同，第一网络侧设备起到的是转发指示信息的作用。
可选的，上述获取第一信息可以包括：在满足以下至少一项的情况下，第一网络侧设备获取第一信息：
中继终端执行的业务的中继业务码关联紧急类型；
中继终端执行的业务类型为紧急类型；
中继终端接收到远端终端的紧急业务中继指示；
中继终端执行紧急业务的中继指示；
中继终端执行针对第一远端终端的紧急业务中继指示；
中继终端的注册类型是紧急类型；
中继终端的服务请求类型是紧急类型；
中继终端的分组数据单元(Packet Data Unit，PDU)会话请求类型是紧急类型。
这样借助上述情况，可以确定中继终端执行紧急业务的中继，和/或确定中继终端为第一远端终端执行紧急业务的中继，从而准确获取第一信息。
可选的，上述获取第一信息可以包括：第一网络侧设备从第三网络侧设备和/或中继终端接收第一信息。比如，第一网络侧设备为RAN网元时，第三网络侧设备为relay AMF。又比如，第一网络侧设备为relay N3IWF时，第三网络侧设备为relay UPF。
可选的，第一信息可以是第三网络侧设备在满足以下至少一项的情况下 发送的：
中继终端执行的业务的中继业务码关联紧急类型；
中继终端执行的业务类型为紧急类型；
中继终端接收到远端终端的紧急业务中继指示；
中继终端执行紧急业务的中继指示；
中继终端执行针对第一远端终端的紧急业务中继指示；
检测到第一远端终端的数据和/或信令；
中继终端的注册类型是紧急类型；
中继终端的服务请求类型是紧急类型；
中继终端的PDU会话请求类型是紧急类型。
可选的，上述向第二网络侧设备发送第二信息可以包括：第一网络侧设备在接收到第一远端终端的数据和/或信令的情况下，向第二网络侧设备发送第二信息。即在需要判断是否接受第一远端终端的数据和/或信令情况下，向第二网络侧设备发送第二信息。此信令可以请求信令，比如无线资源控制协议(Radio Resource Control，RRC)连接建立/修改请求等。
请参见图3，图3是本申请实施例提供的一种业务处理方法的流程图，该方法应用于第二网络侧设备，该第二网络侧设备包括但不限于remote AMF、remote SMF、remote PCF等，此为remote终端对应的核心网网络功能。如图3所示，该方法包括如下步骤：
步骤31：第二网络侧设备接收第二信息。
本实施例中，第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。即第二信息可理解为传输规则信息，指示中继终端支持的是紧急业务的中继。中继终端可以为正在执行中继操作的终端，也可以为待执行中继操作的终端，对此不作限定。第一远端终端为中继终端所服务的远端终端，且中继终端支持的是为第一远端终端的紧急业务提供中继服务。
可选的，第二信息可以包括但不限于以下至少一项：中继终端的标识、第一远端终端的标识。这样借助第二信息中的中继终端的标识，可以指示该标识对应的中继终端执行紧急业务的中继，或者借助第二信息中的中继终端 和第一远端终端的标识，可以指示该标识对应的中继终端为第一远端终端执行紧急业务的中继，或者借助第二信息中的第一远端终端的标识，可以指示相应中继终端为第一远端终端执行紧急业务的中继。
一些实施例中，如果中继终端正在执行紧急业务的中继，则第二信息可以指示以下至少一项：中继终端正在执行紧急业务的中继、中继终端正在为第一远端终端执行紧急业务的中继。
一些实施例中，如果第二网络侧设备为remote AMF/SMF，则第二网络侧设备可以第一网络侧设备(如RAN网元、relay AMF或relay N3IWF等)接收第二信息。
步骤33：第二网络侧设备根据第二信息，执行第一远端终端的紧急业务，和/或，拒绝第一远端终端的非紧急业务。
可选的，在步骤33之前，第二网络侧设备可以接收第一远端终端发送的数据和/或请求消息，以执行其中的紧急业务，或者，拒绝第一远端终端的非紧急业务。
本申请实施例的业务处理方法，第二网络侧设备可以根据接收的第二信息，执行第一远端终端的紧急业务，和/或，拒绝第一远端终端的非紧急业务；此第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。由此，可以确保在中继终端支持执行紧急业务的中继时，仅执行相应远端终端的紧急业务，拒绝相应远端终端的非紧急业务，从而避免对紧急业务资源的浪费。
可选的，在本申请实施例中，上述步骤33可以包括以下至少一项：
第二网络侧设备在确定第一远端终端的数据的类型是紧急类型的情况下，根据第二信息，发送第一远端终端的数据；或者，在确定第一远端终端的数据的类型不是紧急类型的情况下，根据第二信息，拒绝发送第一远端终端的数据；
第二网络侧设备在确定第一远端终端的请求消息的类型是紧急类型的情况下，根据第二信息，响应第一远端终端的请求消息；或者，在确定第一远端终端的请求消息的类型不是紧急类型的情况下，根据第二信息，拒绝第一远端终端的请求消息。比如，该请求消息为RRC连接建立/修改请求等。
可选的，第二网络侧设备可以根据第一远端终端的数据中的类型指示，确定第一远端终端的数据的类型是或者不是紧急类型。该类型指示用于指示相应数据的类型是或者不是紧急类型。
可选的，第二网络侧设备可以根据第一远端终端的请求消息中的类型指示，确定第一远端终端的请求消息的类型是或者不是紧急类型。该类型指示用于指示相应请求消息的类型是或者不是紧急类型。
请参见图4，图4是本申请实施例提供的一种业务处理方法的流程图，该方法应用于终端，该终端可选为中继终端，或与中继终端关联的其他终端(如可转发中继终端的传输信息的终端等)。如图4所示，该方法包括如下步骤：
步骤41：终端获取第一信息。
本实施例中，第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。即第一信息可理解为传输规则信息，指示中继终端支持的是紧急业务的中继。中继终端可以为正在执行中继操作的终端，也可以为待执行中继操作的终端，对此不作限定。第一远端终端为中继终端所服务的远端终端，且中继终端支持的是为第一远端终端的紧急业务提供中继服务。
可选的，第一信息可以包括但不限于以下至少一项：中继终端的标识、第一远端终端的标识。这样借助第一信息中的中继终端的标识，可以指示该标识对应的中继终端执行紧急业务的中继，或者借助第一信息中的中继终端和第一远端终端的标识，可以指示该标识对应的中继终端为第一远端终端执行紧急业务的中继，或者借助第一信息中的第一远端终端的标识，可以指示相应中继终端为第一远端终端执行紧急业务的中继。
一些实施例中，如果中继终端正在执行紧急业务的中继，则第一信息可以指示以下至少一项：中继终端正在执行紧急业务的中继、中继终端正在为第一远端终端执行紧急业务的中继。
步骤42：终端发送第一信息。
一些实施例中，relay终端可以向RAN网元和/或relay AMF发送。
本申请实施例的业务处理方法，通过终端发送第一信息，可以使得第一 网络侧设备在获取第一信息之后，向第二网络侧设备发送第二信息，所述第一/第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。由此，可以使得第二网络侧设备根据接收的第二信息，执行第一远端终端的紧急业务，和/或，拒绝第一远端终端的非紧急业务，从而确保在中继终端支持执行紧急业务的中继时，仅执行相应远端终端的紧急业务，拒绝相应远端终端的非紧急业务，从而避免对紧急业务资源的浪费。
可选的，上述获取第一信息可以包括：在满足以下至少一项的情况下，终端获取第一信息：
中继终端执行的业务的中继业务码关联紧急类型；
中继终端执行的业务类型为紧急类型；
中继终端接收到远端终端的紧急业务中继指示；
中继终端执行紧急业务的中继指示；
中继终端执行针对第一远端终端的紧急业务中继指示；
中继终端的注册类型是紧急类型；
中继终端的服务请求类型是紧急类型；
中继终端的PDU会话请求类型是紧急类型。
这样借助上述情况，可以确定中继终端执行紧急业务的中继，和/或确定中继终端为第一远端终端执行紧急业务的中继，从而准确获取第一信息。
可选的，在紧急业务的中继路径建立后，中继终端可以为第一远端终端转发(透传)数据和/或请求消息，该数据和/或请求消息包含类型指示，该类型指示用于指示数据和/或请求消息的业务类型是否为紧急类型。之后，若第一远端终端对应的核心网网元接收到该数据和/或请求消息，则可以根据已接收的第二信息以及该数据和/或请求消息中的类型指示，仅执行紧急业务，拒绝非紧急业务。
下面结合具体实施例对本申请进行说明。
实施例1
本实施例1主要描述的是在层二中继通信中，RAN网元获取第一信息，并发送第二信息给remote AMF，由remote AMF确定是否执行remote UE的 业务。如图5所示，包括以下步骤：
步骤1：relay AMF确定relay UE执行紧急业务的中继，获取并发送第一信息给RAN网元。其中，第一信息可以如上实施例所述，在此不再赘述。
此步骤中，relay AMF可以是在获知以下至少一项的情况下，确定relay UE执行紧急业务的中继：relay UE执行的业务的中继业务码关联紧急类型、relay UE执行的业务类型为紧急类型、relay UE接收到远端终端的紧急业务中继指示、relay UE执行紧急业务的中继指示、relay UE的注册类型是紧急类型等等。
步骤2：RAN网元接收第一信息之后，发送第二信息给remote AMF。其中，第二信息可以如上实施例所述，在此不再赘述。
一种实施方式时，RAN网元在接收到第一remote终端的请求消息(如RRC连接建立请求等)后，发送第二信息给remote AMF。
步骤3：remote AMF根据接收到的第二信息，结合第一remote UE的数据和/或请求消息中的类型指示，针对第一remote UE仅执行紧急业务，拒绝非紧急业务。
实施例2
本实施例2主要描述的是在层二中继通信中，relay AMF获取第一信息，并发送第二信息给remote AMF，由remote AMF确定是否执行remote UE的业务。如图6所示，包括以下步骤：
步骤1：relay AMF确定relay UE执行紧急业务的中继，获取第一信息，并发送第二信息给remote AMF。其中，第一信息和第二信息可以如上实施例所述，在此不再赘述。
步骤2：步骤3：remote AMF根据接收到的第二信息，结合第一remote UE的数据和/或请求消息中的类型指示，针对第一remote UE仅执行紧急业务，拒绝非紧急业务。
实施例3
本实施例3主要描述的是N3IWF的层三中继通信中，relay UPF获取并发送第一信息给relay N3IWF，由relay N3IWF发送第二信息给remote AMF，使得remote AMF确定是否执行remote UE的业务。如图7所示，包括以下步骤：
步骤1：relay UPF基于relay UE执行的业务的中继业务码关联紧急类型、relay UE执行的业务类型为紧急类型、relay UE接收到远端终端的紧急业务中继指示、relay UE执行紧急业务的中继指示、relay UE的注册类型是紧急类型等情况，确定relay UE执行紧急业务的中继，获取并发送第一信息给relay N3IWF。其中，第一信息可以如上实施例所述，在此不再赘述。
一种实施方式，relay UPF在检测到第一remote UE的数据/信令时，发送第一信息给relay N3IWF。
步骤2：relay N3IWF接收第一信息之后，发送第二信息给remote AMF。其中，第二信息可以如上实施例所述，在此不再赘述。
步骤3：remote AMF根据接收到的第二信息，结合第一remote UE的数据和/或请求消息中的类型指示，针对第一remote UE仅执行紧急业务，拒绝非紧急业务。
本申请实施例提供的业务处理方法，执行主体可以为业务处理装置。本申请实施例中以业务处理装置执行业务处理方法为例，说明本申请实施例提供的业务处理装置。
请参见图8，图8是本申请实施例提供的一种业务处理装置的结构示意图，该装置应用于第一网络侧设备，该第一网络侧设备包括但不限于RAN网元、relay AMF、relay N3IWF等。如图8所示，业务处理装置80包括：
第一获取模块81，用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
第一发送模块82，用于根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。
可选的，所述第一信息用于指示中继终端执行紧急业务的中继，所述第二信息用于指示中继终端为第一远端终端执行紧急业务的中继；
或者，所述第一信息用于指示中继终端执行紧急业务的中继，所述第二信息用于指示中继终端执行紧急业务的中继；
或者，所述第一信息用于指示中继终端为第一远端终端执行紧急业务的 中继，所述第二信息用于指示中继终端为第一远端终端执行紧急业务的中继。
可选的，所述第一信息包括以下至少一项：所述中继终端的标识、所述第一远端终端的标识；和/或，所述第二信息包括以下至少一项：所述中继终端的标识、所述第一远端终端的标识。
可选的，第一获取模块81具体用于：在满足以下至少一项的情况下，获取第一信息：
中继终端执行的业务的中继业务码关联紧急类型；
中继终端执行的业务类型为紧急类型；
中继终端接收到远端终端的紧急业务中继指示；
中继终端执行紧急业务的中继指示；
中继终端执行针对第一远端终端的紧急业务中继指示；
中继终端的注册类型是紧急类型；
中继终端的服务请求类型是紧急类型；
中继终端的PDU会话请求类型是紧急类型。
可选的，第一获取模块81具体用于：
从第三网络侧设备和/或中继终端接收所述第一信息。
可选的，所述第一信息是第三网络侧设备在满足以下至少一项的情况下发送的：
中继终端执行的业务的中继业务码关联紧急类型；
中继终端执行的业务类型为紧急类型；
中继终端接收到远端终端的紧急业务中继指示；
中继终端执行紧急业务的中继指示；
中继终端执行针对第一远端终端的紧急业务中继指示；
检测到第一远端终端的数据和/或信令；
中继终端的注册类型是紧急类型；
中继终端的服务请求类型是紧急类型；
中继终端的PDU会话请求类型是紧急类型。
可选的，第一发送模块82具体用于：在接收到所述第一远端终端的数据和/或信令的情况下，向所述第二网络侧设备发送所述第二信息。
本申请实施例提供的业务处理装置80能够实现图2的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图9，图9是本申请实施例提供的一种业务处理装置的结构示意图，该装置应用于第二网络侧设备，该第二网络侧设备包括但不限于remote AMF、remote SMF、remote PCF等。如图9所示，业务处理装置90包括：
接收模块91，用于接收第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
执行模块92，用于根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务。
可选的，所述第二信息包括以下至少一项：
所述中继终端的标识、所述第一远端终端的标识。
可选的，接收模块91还用于：接收所述第一远端终端发送的数据和/或请求消息。
可选的，所述执行模块92用于以下至少一项：
在确定所述第一远端终端的数据的类型是紧急类型的情况下，根据所述第二信息，发送所述第一远端终端的数据；或者，在确定所述第一远端终端的数据的类型不是紧急类型的情况下，根据所述第二信息，拒绝发送所述第一远端终端的数据；
在确定所述第一远端终端的请求消息的类型是紧急类型的情况下，根据所述第二信息，响应所述第一远端终端的请求消息；或者，在确定所述第一远端终端的请求消息的类型不是紧急类型的情况下，根据所述第二信息，拒绝所述第一远端终端的请求消息。
可选的，所述执行模块92还用于以下至少一项：
根据所述第一远端终端的数据中的类型指示，确定所述第一远端终端的数据的类型是或者不是紧急类型；
根据所述第一远端终端的请求消息中的类型指示，确定所述第一远端终端的请求消息的类型是或者不是紧急类型。
本申请实施例提供的业务处理装置90能够实现图3的方法实施例实现的 各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
请参见图10，图10是本申请实施例提供的一种业务处理装置的结构示意图，该装置应用于终端。如图10所示，业务处理装置100包括：
第二获取模块101，用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
第二发送模块102，用于发送所述第一信息。
可选的，所述第一信息包括以下至少一项：
所述中继终端的标识、所述第一远端终端的标识。
可选的，第二获取模块101用于：在满足以下至少一项的情况下，获取第一信息：
中继终端执行的业务的中继业务码关联紧急类型；
中继终端执行的业务类型为紧急类型；
中继终端接收到远端终端的紧急业务中继指示；
中继终端执行紧急业务的中继指示；
中继终端执行针对第一远端终端的紧急业务中继指示；
中继终端的注册类型是紧急类型；
中继终端的服务请求类型是紧急类型；
中继终端的PDU会话请求类型是紧急类型。
可选的，所述终端为所述中继终端时，第二发送模块102还用于：在紧急业务的中继路径建立后，为所述第一远端终端转发数据和/或请求消息，所述数据和/或请求消息包含类型指示，所述类型指示用于指示所述数据和/或请求消息的业务类型是否为紧急类型。
本申请实施例提供的业务处理装置100能够实现图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图11所示，本申请实施例还提供一种通信设备110，包括处理器111和存储器112，存储器112上存储有可在所述处理器111上运行的程序或指令，例如，该通信设备110为第一网络侧设备时，该程序或指令被处理器111执行时实现上述图2所示的业务处理方法实施例的各个步骤，且能 达到相同的技术效果；该通信设备110为第二网络侧设备时，该程序或指令被处理器111执行时实现上述图3所示的业务处理方法实施例的各个步骤，且能达到相同的技术效果；该通信设备110为终端时，该程序或指令被处理器111执行时实现上述图4所示的业务处理方法实施例的各个步骤，且能达到相同的技术效果；为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，通信接口用于获取第一信息，并发送所述第一信息；所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。该终端实施例与上述终端侧方法实施例对应，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。
具体地，图12为实现本申请实施例的一种终端的硬件结构示意图。
该终端1200包括但不限于：射频单元1201、网络模块1202、音频输出单元1203、输入单元1204、传感器1205、显示单元1206、用户输入单元1207、接口单元1208、存储器1209以及处理器1210等中的至少部分部件。
本领域技术人员可以理解，终端1200还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1210逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图12中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1204可以包括图形处理单元(Graphics Processing Unit，GPU)12041和麦克风12042，图形处理器12041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1206可包括显示面板12061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板12061。用户输入单元1207包括触控面板12071以及其他输入设备12072中的至少一种。触控面板12071，也称为触摸屏。触控面板12071可包括触摸检测装置和触摸控制器两个部分。其他输入设备12072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1201接收来自网络侧设备的下行数据后，可以传输给处理器1210进行处理；另外，射频单元1201可以向网络侧设备发送上行数据。通常，射频单元1201包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1209可用于存储软件程序或指令以及各种数据。存储器1209可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1209可以包括易失性存储器或非易失性存储器，或者，存储器1209可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1209包括但不限于这些和任意其它适合类型的存储器。
处理器1210可包括一个或多个处理单元；可选的，处理器1210集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1210中。
其中，射频单元1201，用于获取第一信息，并发送所述第一信息；所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。
可选的，所述第一信息包括以下至少一项：所述中继终端的标识、所述第一远端终端的标识。
可选的，射频单元1201还用于：在满足以下至少一项的情况下，获取所述第一信息：
中继终端执行的业务的中继业务码关联紧急类型；
中继终端执行的业务类型为紧急类型；
中继终端接收到远端终端的紧急业务中继指示；
中继终端执行紧急业务的中继指示；
中继终端执行针对第一远端终端的紧急业务中继指示；
中继终端的注册类型是紧急类型；
中继终端的服务请求类型是紧急类型；
中继终端的PDU会话请求类型是紧急类型。
可选的，终端1200为中继终端，处理器1210用于：在紧急业务的中继路径建立后，为所述第一远端终端转发数据和/或请求消息，所述数据和/或请求消息包含类型指示，所述类型指示用于指示所述数据和/或请求消息的业务类型是否为紧急类型。
本申请实施例提供的终端1200能够实现图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，该网络侧设备为第一网络侧设备时，通信接口用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；并根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；或者，该网络侧设备为第二网络侧设备时，通信接口用于接收第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；处理器用于根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务。该网络侧设备实施例与上述网络侧设备方法实施例对应，上述方法实施例的各个实施过程和实 现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果，这里不再赘述。
本申请实施例还提供了一种网络侧设备。如图13所示，该网络侧设备130包括：处理器131、网络接口132和存储器133。其中，网络接口132例如为通用公共无线接口(Common Public Radio Interface，CPRI)。
具体地，本申请实施例的网络侧设备130还包括：存储在存储器133上并可在处理器131上运行的指令或程序，处理器131调用存储器133中的指令或程序执行图8或图9所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述业务处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，该处理器为上述实施例中所述的终端中的处理器。该可读存储介质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述业务处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述业务处理方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种通信系统，包括：终端及网络侧设备，所述终端可用于执行如上所述图4所示方法的步骤，所述网络侧设备可用于执行如上所述的图2所示方法的步骤，或者执行如上所述图3所示方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体 意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (24)

  1. 一种业务处理方法，包括：
    第一网络侧设备获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
    所述第一网络侧设备根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。
  2. 根据权利要求1所述的方法，其中，所述第一信息用于指示中继终端执行紧急业务的中继，所述第二信息用于指示中继终端为第一远端终端执行紧急业务的中继；
    或者，
    所述第一信息用于指示中继终端执行紧急业务的中继，所述第二信息用于指示中继终端执行紧急业务的中继；
    或者，
    所述第一信息用于指示中继终端为第一远端终端执行紧急业务的中继，所述第二信息用于指示中继终端为第一远端终端执行紧急业务的中继。
  3. 根据权利要求1或2所述的方法，其中，所述第一信息包括以下至少一项：
    所述中继终端的标识、所述第一远端终端的标识；
    和/或，
    所述第二信息包括以下至少一项：
    所述中继终端的标识、所述第一远端终端的标识。
  4. 根据权利要求1至3任一项所述的方法，其中，所述获取第一信息，包括：
    在满足以下至少一项的情况下，所述第一网络侧设备获取所述第一信息：
    所述中继终端执行的业务的中继业务码关联紧急类型；
    所述中继终端执行的业务类型为紧急类型；
    所述中继终端接收到远端终端的紧急业务中继指示；
    所述中继终端执行紧急业务的中继指示；
    所述中继终端执行针对第一远端终端的紧急业务中继指示；
    所述中继终端的注册类型是紧急类型；
    所述中继终端的服务请求类型是紧急类型；
    所述中继终端的PDU会话请求类型是紧急类型。
  5. 根据权利要求1至4任一项所述的方法，其中，所述获取第一信息，包括：
    所述第一网络侧设备从第三网络侧设备和/或中继终端接收所述第一信息。
  6. 根据权利要求5所述的方法，其中，所述第一信息是所述第三网络侧设备在满足以下至少一项的情况下发送的：
    所述中继终端执行的业务的中继业务码关联紧急类型；
    所述中继终端执行的业务类型为紧急类型；
    所述中继终端接收到远端终端的紧急业务中继指示；
    所述中继终端执行紧急业务的中继指示；
    所述中继终端执行针对所述第一远端终端的紧急业务中继指示；
    检测到所述第一远端终端的数据和/或信令；
    所述中继终端的注册类型是紧急类型；
    所述中继终端的服务请求类型是紧急类型；
    所述中继终端的PDU会话请求类型是紧急类型。
  7. 根据权利要求1至6任一项所述的方法，其中，所述向第二网络侧设备发送第二信息，包括：
    所述第一网络侧设备在接收到所述第一远端终端的数据和/或信令的情况下，向所述第二网络侧设备发送所述第二信息。
  8. 一种业务处理方法，包括：
    第二网络侧设备接收第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
    所述第二网络侧设备根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务。
  9. 根据权利要求8所述的方法，其中，所述第二信息包括以下至少一项：
    所述中继终端的标识、所述第一远端终端的标识。
  10. 根据权利要求8或9所述的方法，其中，所述第二网络侧设备根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务之前，所述方法还包括：
    所述第二网络侧设备接收所述第一远端终端发送的数据和/或请求消息。
  11. 根据权利要求8至10任一项所述的方法，其中，所述根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务，包括以下至少一项：
    所述第二网络侧设备在确定所述第一远端终端的数据的类型是紧急类型的情况下，根据所述第二信息，发送所述第一远端终端的数据；或者，在确定所述第一远端终端的数据的类型不是紧急类型的情况下，根据所述第二信息，拒绝发送所述第一远端终端的数据；
    所述第二网络侧设备在确定所述第一远端终端的请求消息的类型是紧急类型的情况下，根据所述第二信息，响应所述第一远端终端的请求消息；或者，在确定所述第一远端终端的请求消息的类型不是紧急类型的情况下，根据所述第二信息，拒绝所述第一远端终端的请求消息。
  12. 根据权利要求11所述的方法，所述方法还包括以下至少一项：
    所述第二网络侧设备根据所述第一远端终端的数据中的类型指示，确定所述第一远端终端的数据的类型是或者不是紧急类型；
    所述第二网络侧设备根据所述第一远端终端的请求消息中的类型指示，确定所述第一远端终端的请求消息的类型是或者不是紧急类型。
  13. 一种业务处理方法，包括：
    终端获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
    所述终端发送所述第一信息。
  14. 根据权利要求13所述的方法，其中，所述第一信息包括以下至少一 项：
    所述中继终端的标识、所述第一远端终端的标识。
  15. 根据权利要求13或14所述的方法，其中，所述获取第一信息，包括：
    在满足以下至少一项的情况下，所述终端获取所述第一信息：
    所述中继终端执行的业务的中继业务码关联紧急类型；
    所述中继终端执行的业务类型为紧急类型；
    所述中继终端接收到远端终端的紧急业务中继指示；
    所述中继终端执行紧急业务的中继指示；
    所述中继终端执行针对所述第一远端终端的紧急业务中继指示；
    所述中继终端的注册类型是紧急类型；
    所述中继终端的服务请求类型是紧急类型；
    所述中继终端的PDU会话请求类型是紧急类型。
  16. 根据权利要求13至15任一项所述的方法，其中，所述终端为所述中继终端，所述方法还包括：
    在紧急业务的中继路径建立后，所述中继终端为所述第一远端终端转发数据和/或请求消息，所述数据和/或请求消息包含类型指示，所述类型指示用于指示所述数据和/或请求消息的业务类型是否为紧急类型。
  17. 一种业务处理装置，包括：
    第一获取模块，用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
    第一发送模块，用于根据所述第一信息，向第二网络侧设备发送第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继。
  18. 根据权利要求17所述的装置，其中，所述第一信息用于指示中继终端执行紧急业务的中继，所述第二信息用于指示中继终端为第一远端终端执行紧急业务的中继；或者，
    所述第一信息用于指示中继终端执行紧急业务的中继，所述第二信息用 于指示中继终端执行紧急业务的中继；
    或者，
    所述第一信息用于指示中继终端为第一远端终端执行紧急业务的中继，所述第二信息用于指示中继终端为第一远端终端执行紧急业务的中继。
  19. 一种业务处理装置，包括：
    接收模块，用于接收第二信息，所述第二信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
    执行模块，用于根据所述第二信息，执行所述第一远端终端的紧急业务，和/或，拒绝所述第一远端终端的非紧急业务。
  20. 根据权利要求19所述的装置，其中，所述执行模块用于以下至少一项：
    在确定所述第一远端终端的数据的类型是紧急类型的情况下，根据所述第二信息，发送所述第一远端终端的数据；或者，在确定所述第一远端终端的数据的类型不是紧急类型的情况下，根据所述第二信息，拒绝发送所述第一远端终端的数据；
    在确定所述第一远端终端的请求消息的类型是紧急类型的情况下，根据所述第二信息，响应所述第一远端终端的请求消息；或者，在确定所述第一远端终端的请求消息的类型不是紧急类型的情况下，根据所述第二信息，拒绝所述第一远端终端的请求消息。
  21. 一种业务处理装置，包括：
    第二获取模块，用于获取第一信息，所述第一信息用于指示以下至少一项：中继终端执行紧急业务的中继、中继终端为第一远端终端执行紧急业务的中继；
    第二发送模块，用于发送所述第一信息。
  22. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求13至16任一项所述的业务处理方法的步骤。
  23. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述 处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至7任一项所述的业务处理方法的步骤，或者实现如权利要求8至12任一项所述的业务处理方法的步骤。
  24. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至7任一项所述的业务处理方法的步骤，或者实现如权利要求8至12任一项所述的业务处理方法的步骤，或者实现如权利要求13至16任一项所述的业务处理方法的步骤。
PCT/CN2023/084053 2022-03-28 2023-03-27 业务处理方法、装置、终端、网络侧设备及可读存储介质 WO2023185728A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210313494.3 2022-03-28
CN202210313494.3A CN116866877A (zh) 2022-03-28 2022-03-28 业务处理方法、装置、终端、网络侧设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2023185728A1 true WO2023185728A1 (zh) 2023-10-05

Family

ID=88199338

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/084053 WO2023185728A1 (zh) 2022-03-28 2023-03-27 业务处理方法、装置、终端、网络侧设备及可读存储介质

Country Status (2)

Country Link
CN (1) CN116866877A (zh)
WO (1) WO2023185728A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120100848A1 (en) * 2010-10-21 2012-04-26 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced reliability of service in mobile networks
CN110636604A (zh) * 2018-06-25 2019-12-31 华为技术有限公司 一种注册状态的管理方法及装置
WO2020199195A1 (zh) * 2019-04-04 2020-10-08 华为技术有限公司 一种数据处理方法、中继设备和网络设备
CN113711651A (zh) * 2019-04-17 2021-11-26 Lg电子株式会社 用于管理网络故障的方法
CN114071647A (zh) * 2020-07-31 2022-02-18 维沃移动通信有限公司 接入控制方法及装置
CN115314874A (zh) * 2021-05-08 2022-11-08 华为技术有限公司 一种切片选择方法、装置及相关设备

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120100848A1 (en) * 2010-10-21 2012-04-26 Telefonaktiebolaget Lm Ericsson (Publ) Enhanced reliability of service in mobile networks
CN110636604A (zh) * 2018-06-25 2019-12-31 华为技术有限公司 一种注册状态的管理方法及装置
WO2020199195A1 (zh) * 2019-04-04 2020-10-08 华为技术有限公司 一种数据处理方法、中继设备和网络设备
CN113711651A (zh) * 2019-04-17 2021-11-26 Lg电子株式会社 用于管理网络故障的方法
CN114071647A (zh) * 2020-07-31 2022-02-18 维沃移动通信有限公司 接入控制方法及装置
CN115314874A (zh) * 2021-05-08 2022-11-08 华为技术有限公司 一种切片选择方法、装置及相关设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ASUSTEK: "EPS bearer release for ProSe UE-to-Network Relay", SA WG2 MEETING #117, S2-165541, 16 October 2016 (2016-10-16), XP051155129 *
VIVO: "Deregistration due to the failed network Slice-Specific Authentication and Authorization", 3GPP TSG-CT WG1 MEETING #120, C1-196171, 30 September 2019 (2019-09-30), XP051787792 *

Also Published As

Publication number Publication date
CN116866877A (zh) 2023-10-10

Similar Documents

Publication Publication Date Title
WO2023169523A1 (zh) 数据采集方法、装置、终端及网络侧设备
WO2023093609A1 (zh) 物联网设备的会话建立方法及装置
WO2023185728A1 (zh) 业务处理方法、装置、终端、网络侧设备及可读存储介质
WO2023143436A1 (zh) 数据转发的方法、装置、终端设备和网络设备
WO2024007961A1 (zh) 中继控制方法、装置、终端及网络侧设备
WO2023185929A1 (zh) 资源控制方法、装置、终端及网络侧设备
WO2024032543A1 (zh) 信息获取方法、终端及接入网设备
WO2023131286A1 (zh) 资源控制方法、装置、终端、网络侧设备及可读存储介质
WO2024001954A1 (zh) 标识配置方法、装置、终端及存储介质
WO2023185803A1 (zh) 无线链路失败的确定方法、装置、终端及网络侧设备
WO2023165481A1 (zh) 网络故障的处理方法、终端、接入网设备及核心网设备
WO2024093712A1 (zh) 中继通信链路处理方法、中继通信链路配置方法、中继终端处理方法及相关设备
WO2023207947A1 (zh) 小区重配置方法、装置、终端及网络侧设备
WO2024032537A1 (zh) 通信方法、设备及可读存储介质
WO2023185724A1 (zh) 定位处理方法、装置、终端及网络侧设备
WO2024022440A1 (zh) 小区切换方法、装置及相关设备
WO2023185845A1 (zh) 通信方法、装置及相关设备
WO2023198071A1 (zh) 信息传输方法、装置、终端及网络侧设备
WO2024027681A1 (zh) Ue能力控制方法、装置、终端及网络侧设备
WO2024041470A1 (zh) 系统信息消息接收方法、发送方法、终端及网络侧设备
WO2023109686A1 (zh) 参数配置方法、装置、通信设备、存储介质及系统
WO2024051546A1 (zh) 选网方法及装置、终端
WO2024037512A1 (zh) 网络接入方法、装置、终端及通信设备
WO2023208048A1 (zh) 小区切换方法、装置、终端及网络侧设备
WO2023231878A1 (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: 23778095

Country of ref document: EP

Kind code of ref document: A1