CN117939409A

CN117939409A - Processing method and device for non-emergency service

Info

Publication number: CN117939409A
Application number: CN202211262428.4A
Authority: CN
Inventors: 邓强
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2022-10-14
Filing date: 2022-10-14
Publication date: 2024-04-26
Also published as: WO2024078580A1

Abstract

The application provides a method and a device for processing non-emergency services, wherein the method applied to first equipment comprises the following steps: receiving mobility restriction indication information sent by second equipment, wherein the mobility restriction indication information is used for indicating the mobility restriction state of a relay terminal; and determining whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal based on the mobility restriction state of the relay terminal. The application enables the first equipment to acquire the mobility restriction state of the relay terminal through the mobility restriction indication information, thereby determining the corresponding operation according to the mobility restriction state of the relay terminal, and solving the problem that the non-emergency service PDU session of the remote terminal cannot be processed when the remote terminal is connected to the relay terminal with mobility restriction.

Description

Processing method and device for non-emergency service

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for processing a non-emergency service.

Background

The proximity services (Proximity Service, proSe) standard project defines a Layer 2 terminal-to-Network Relay architecture in which a remote terminal (Layer-2 Remote UE) can communicate through a Relay terminal (Layer-2 Relay UE) to a Network, and further, it is specified in the related art that Relay services will not be provided for non-emergency services (non-EMERGENCY SERVICE) of the remote terminal when the Relay terminal is limited to mobility restrictions (Mobility Restriction).

A relay terminal limited by mobility restriction (Mobility Restriction) cannot provide relay services for a non-emergency service protocol data unit (Protocol Data Unit, PDU) session of a remote terminal, and how to handle non-emergency services of the remote terminal is a problem to be solved.

Disclosure of Invention

The embodiment of the application provides a non-emergency service processing method and device, which are used for solving the problem that a solution is lacking for non-emergency service processing of a remote terminal under the condition that a relay terminal limited by mobility cannot relay the non-emergency service of the remote terminal in the prior art.

In a first aspect, an embodiment of the present application provides a method for processing a non-emergency service, which is applied to a first device, including:

Receiving mobility restriction indication information sent by second equipment, wherein the mobility restriction indication information is used for indicating the mobility restriction state of a relay terminal;

and determining whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal based on the mobility restriction state of the relay terminal.

Optionally, the first device is the remote terminal, and the second device is the relay terminal;

the receiving mobility restriction indication information sent by the second device includes:

and receiving the mobility limit indication information through a direct communication message sent by the second device.

Optionally, the direct communication message includes any of the following:

Relaying the discovery message;

direct communication accept message;

Status notification message.

Optionally, the determining whether to initiate or release the non-emergency service protocol data unit PDU session of the remote terminal based on the mobility restriction status of the relay terminal includes:

in the case that the mobility restriction state of the relay terminal is a restricted state, it is determined not to initiate the non-emergency service PDU session or to release the non-emergency service PDU session.

Optionally, the determining to release the non-emergency service PDU session further comprises:

a first message is sent to a Session Management Function (SMF) entity corresponding to the remote terminal, wherein the first message is used for indicating the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session; or alternatively

Sending a second message to an AMF entity corresponding to the remote terminal, where the second message is used to instruct the AMF entity corresponding to the remote terminal to trigger the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session;

wherein the first message or the second message contains the mobility restriction indication information.

Optionally, the first device is an access and mobility management AMF entity corresponding to the remote terminal, and the second device is an access network entity or an AMF entity corresponding to the relay terminal;

the determining whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal based on the mobility restriction status of the relay terminal includes:

and determining to release the non-emergency service PDU session in the case that the mobility restriction state of the relay terminal is a restricted state.

Determining a first PDU session identifier corresponding to the non-emergency service PDU session based on the mobility restriction indication information and the PDU session information corresponding to the remote terminal;

and sending a third message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal, wherein the third message carries the first PDU session identifier.

In a second aspect, an embodiment of the present application provides a method for processing a non-emergency service, which is applied to a second device, including:

transmitting mobility restriction indication information to a first device;

Wherein the mobility restriction indication information is used for indicating a mobility restriction state of the relay terminal; the mobility restriction state of the relay terminal is used for the first device to determine whether to initiate or release a non-emergency service protocol data unit, PDU, session of the remote terminal.

Optionally, when the second device is an AMF entity corresponding to the relay terminal and the first device is an AMF entity corresponding to the remote terminal, before sending the mobility restriction indication information to the first device, the method further includes:

receiving the identification of the remote terminal sent by the relay terminal;

and determining an AMF entity corresponding to the remote terminal based on the identification of the remote terminal.

Optionally, in the case that the mobility restriction state of the relay terminal is a restricted state, and the relay terminal receives a non-emergency service establishment request message sent by the remote terminal, the second device refuses to establish the non-emergency service requested by the remote terminal.

Optionally, the mobility restriction indication information is determined based on mobility restriction information, where the mobility restriction information is determined by an AMF entity corresponding to the relay terminal.

In a third aspect, an embodiment of the present application further provides a first device, including a memory, a transceiver, and a processor, where:

A memory for storing a computer program; a transceiver for transceiving data under control of the processor; and a processor for reading the computer program in the memory and implementing the method for processing non-emergency services according to the first aspect.

In a fourth aspect, an embodiment of the present application further provides a first device, including a memory, a transceiver, and a processor, where:

A memory for storing a computer program; a transceiver for transceiving data under control of the processor; and a processor for reading the computer program in the memory and implementing the method for processing non-emergency services according to the second aspect.

In a fifth aspect, an embodiment of the present application further provides a processing apparatus for a non-emergency service, which is applied to a first device, and includes:

A first receiving unit, configured to receive mobility restriction indication information sent by a second device, where the mobility restriction indication information is used to indicate a mobility restriction state of a relay terminal;

A first determining unit, configured to determine whether to initiate or release a non-emergency service protocol data unit PDU session of a remote terminal based on a mobility restriction status of the relay terminal.

In a sixth aspect, an embodiment of the present application further provides a processing apparatus for a non-emergency service, which is applied to a second device, including:

A second transmitting unit configured to transmit mobility restriction instruction information to the first device;

In a seventh aspect, an embodiment of the present application further provides a processor-readable storage medium storing a computer program for causing the processor to execute the method for processing non-emergency services according to the first aspect or the method for processing non-emergency services according to the second aspect.

According to the method and the device for processing the non-emergency service, provided by the embodiment of the application, the mobility restriction indication information enables the first equipment to acquire the mobility restriction state of the relay terminal, so that corresponding operation is determined according to the mobility restriction state of the relay terminal, and the problem that when the remote terminal is connected to the mobility restricted relay terminal, the non-emergency service PDU session of the remote terminal cannot be processed can be solved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the present application, and other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a network architecture provided by the present application;

Fig. 2 is a schematic flow chart of a method for processing a non-emergency service according to an embodiment of the present application;

FIG. 3 is a second flow chart of a non-emergency service processing method according to an embodiment of the present application;

FIG. 4 is a third flow chart of a method for processing non-emergency services according to an embodiment of the present application;

FIG. 5 is a flowchart illustrating a method for processing a non-emergency service according to an embodiment of the present application;

FIG. 6 is a flowchart of a method for processing a non-emergency service according to an embodiment of the present application;

fig. 7 is a flowchart illustrating a method for processing a non-emergency service according to an embodiment of the present application;

Fig. 8 is a schematic structural diagram of a non-emergency service processing device according to an embodiment of the present application;

FIG. 9 is a second schematic diagram of a non-emergency service processing apparatus according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a first device according to an embodiment of the present application;

Fig. 11 is a schematic structural diagram of a second device according to an embodiment of the present application.

Detailed Description

In the embodiment of the application, the term "and/or" describes the association relation of the association objects, which means that three relations can exist, for example, a and/or B can be expressed as follows: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

The term "plurality" in embodiments of the present application means two or more, and other adjectives are similar.

The following description of the embodiments of the present application will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.

The technical scheme provided by the embodiment of the application can be suitable for various systems, in particular to a 5G (5 th Generation Mobile Communication Technology, fifth generation mobile communication technology) system. For example, applicable systems may be global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet Radio service (GENERAL PACKET Radio service, GPRS), long term evolution (long term evolution, LTE), LTE frequency division duplex (frequency division duplex, FDD), LTE time division duplex (time division duplex, TDD), long term evolution-advanced (long term evolution advanced, LTE-a), universal mobile system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX), 5G New air interface (New Radio, NR) systems, and the like. Terminal devices and network devices are included in these various systems. Core network parts such as evolved packet system (Evloved PACKET SYSTEM, EPS), 5G system (5 GS), etc. may also be included in the system.

The terminal device according to the embodiment of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem, etc. The names of the terminal devices may also be different in different systems, for example in a 5G system, the terminal devices may be referred to as User Equipment (UE). The wireless terminal device may communicate with one or more Core Networks (CNs) via a radio access Network (Radio Access Network, RAN), which may be mobile terminal devices such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, e.g., portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile devices that exchange voice and/or data with the radio access Network. Such as Personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal DIGITAL ASSISTANT, PDA) and the like. The wireless terminal device may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station), remote station (remote station), access point (access point), remote terminal device (remote terminal), access terminal device (ACCESS TERMINAL), user terminal device (user terminal), user agent (user agent), user equipment (user device), and embodiments of the present application are not limited.

The network device according to the embodiment of the present application may be a base station, where the base station may include a plurality of cells for providing services for the terminal. A base station may also be called an access point or may be a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or other names, depending on the particular application. The network device may be configured to exchange received air frames with internet protocol (Internet Protocol, IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management for the air interface. For example, the network device according to the embodiment of the present application may be a network device (Base Transceiver Station, BTS) in a global system for mobile communications (Global System for Mobile communications, GSM) or code division multiple access (Code Division Multiple Access, CDMA), a network device (NodeB) in a wideband code division multiple access (Wide-band Code Division Multiple Access, WCDMA), an evolved network device (evolutional Node B, eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), a home evolved base station (Home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), etc., which are not limited in the embodiment of the present application. In some network structures, the network devices may include centralized unit (centralized unit, CU) nodes and Distributed Unit (DU) nodes, which may also be geographically separated.

Multiple-input Multiple-output (Multi Input Multi Output, MIMO) transmissions may be made between the network device and the terminal device, each using one or more antennas, and the MIMO transmissions may be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of the root antenna combinations.

To facilitate an understanding of embodiments of the present application, the following terms or contexts associated with embodiments of the present application are presented:

(1) Layer 2 (Layer-2) terminal-to-Network (UE-to-Network) Relay architecture and flow

The related art defines a Layer-2 UE-to-Network Relay architecture and related flows. When the UE is out of network coverage or Uu interface signals are poor, the UE cannot directly connect to the network, and can connect to the network through the UE having a relay function, the former is called Layer 2 far-end terminal (Layer-2 Remote UE, which may also be called far-end terminal), and the latter is called Layer 2 relay terminal (Layer-2 Relay UE, which may also be called relay terminal). The Remote UE may connect to its own NG-RAN and core network through the Relay UE.

(2) Flow for layer 2 remote UE to communicate with network through layer 2 relay UE

Fig. 1 is a schematic flow chart of communication between Layer-2 Remote UE and a network through Layer-2Relay UE according to an embodiment of the present application, as shown in fig. 1, the flow chart of communication between Layer-2 Remote UE and a network through Layer-2Relay UE includes:

0. Initial registration: the Remote UE and the Relay UE may register with the network respectively while in the network. The Relay UE may be a proximity services terminal-to-Network Relay (ProSe UE-to-Network Relay).

1. Service license retrieval (Service Authorization retrieval): in the network, the Remote UE and the Relay UE acquire policies and parameters for proximity services (Proximity Service, proSe) from the network, respectively. If the Remote UE is not on the network, pre-configured parameters may be used.

2. Discovery and selection (UE-to-Network Relay discovery and selection): the Remote UE and the Relay UE perform a discovery procedure, and the Remote UE selects the Relay UE to be communicated.

3. PC5 communication and setup (PC 5 connection establishment): a PC5 connection for communication is established between the Remote UE and the Relay UE.

4. Access layer connection establishment (Access Stratum connection setup, AS connection setup) the Remote UE establishes an RRC connection with an access network that is the same as the serving access network of the Relay UE. The access network may be a next generation radio access network (Next Generation Radio Access Network, NG-RAN).

5. Relay terminal triggers a service Request (UE-to-Network RELAY TRIGGERED SERVICE Request): if the Relay UE is in an IDLE (IDLE) state and receives a radio resource control (Radio Resource Control, RRC) connection Request of the Remote UE, the Relay UE initiates a Service Request (Service Request) procedure to enter the connected state.

6. Non-access stratum connection establishment (Non-Access Stratum connection setup, NAS connection setup): the Remote UE sends NAS messages to access and mobility management function (ACCESS AND Mobility Management Function, AMF) entities (not Remote UE's AMFs in the figure) corresponding to the Remote UE, the NAS messages are encapsulated in RRC messages, the RRC messages are sent to Relay UE through PC5 interface, and the Relay UE forwards the RRC messages to the access network. The access network selects an AMF for the Remote UE and forwards the NAS message to the AMF. The NAS message may be one of an initial registration (Initial Registration) message, a Service Request (Service Request) message, a mobility registration (mobility registration) message, or a periodic registration (periodic registration) message.

7. PDU session establishment procedure (PDU Session Establishment procedure): the Remote UE initiates a PDU session establishment procedure.

8. Data transmission (DATA TRANSFER): data of the Remote UE is transferred between the Remote UE and the UPF through the Relay UE and the NG-RAN.

For the steps corresponding to the policy control function (Policy Control Function, PCF), the session management function (Session Management Function, SMF) of the Remote UE, and the user plane function (User Plane Function, UPF) of the Remote UE in the figure, reference is made to the related art, and details are not repeated here.

(3) Mobility restriction (Mobility Restriction)

The related art defines Mobility Restriction. Mobility Restriction limit mobility handling and traffic access for the UE, including Forbidden areas (Forbidden Area), service Area restrictions (SERVICE AREA restrictions), etc. In the forbidden region, the UE is not allowed to initiate any communication to the network. Service Area restrictions include Allowed areas (Allowed areas) and disallowed areas (Non-Allowed areas). In the allowed zone, the UE allows initiation of communication to the network; in the disallowed area, the UE is not allowed to initiate a procedure related to data transmission (e.g. a Service Request). It is noted that the UE will not be limited by the mobility restriction (Mobility Restriction) described above when performing emergency services.

An applicable scenario for mobility restriction in the R17 relay scenario is defined in the related art. When the Relay UE is in a Forbidden Area (Forbidden Area) or a disallowed Area (Non-Allowed Area), the Relay UE cannot perform a Relay operation (i.e., cannot perform Relay discovery and Relay communication procedures)

When the Relay UE is in mobility restriction, relay service can still be provided for emergency services of the Remote UE, but Relay service cannot be provided for non-emergency services.

For the Layer-2 UE-to-Network Relay architecture, a Relay UE under mobility restriction may provide Relay service for emergency services of a Remote UE, but may not provide Relay service for non-emergency services according to related art specifications.

How to handle non-emergency service PDU sessions for Remote UEs is an unsolved problem with the related art when the Remote UEs are connected to the Relay UEs, which are in turn under mobility restrictions.

The method for processing the non-emergency service provided by the embodiment of the application can solve the problem of how to process the non-emergency service PDU session of the remote terminal when the remote terminal is connected to the relay terminal and the relay terminal is in mobility limitation.

Fig. 2 is one of flow diagrams of a non-emergency service processing method provided by an embodiment of the present application, and as shown in fig. 2, an embodiment of the present application provides a non-emergency service processing method, which may be applied to a first device, and includes:

step 210, receiving mobility restriction indication information sent by a second device, where the mobility restriction indication information is used to indicate a mobility restriction state of a relay terminal;

Specifically, the first device refers to a device capable of session processing of a non-emergency service protocol data unit (Protocol Data Unit, PDU) of the remote terminal, where the processing may include initiating a session or releasing a session, etc.

The second device refers to a device capable of determining or obtaining mobility restriction indication information and capable of transmitting the mobility restriction indication information to the first device.

The mobility restriction instruction information refers to information for indicating a mobility restriction state of the relay terminal.

In one possible implementation, the mobility restriction indication information may indicate that the mobility restriction state of the relay terminal is in Forbidden Area, allowed Area, or Non-Allowed Area.

In one possible implementation, the mobility restriction indication information may indicate a mobility restriction state of the relay terminal in the form of a mobility restriction indicator, for example, in the case that the value of the mobility restriction indicator is 1, the mobility restriction state of the relay terminal is a state capable of providing non-emergency services to the remote terminal, for example, the mobility restriction state of the relay terminal is Allowed Area; in the case where the value of the mobility restriction indicator is 0, the mobility restriction state of the relay terminal is indicated as a state in which Non-emergency services cannot be provided to the remote terminal, for example, the mobility restriction state of the relay terminal is Forbidden Area or Non-Allowed Area.

It should be understood that the foregoing is illustrative of the present application and is not to be construed as limiting thereof.

Step 220, determining whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal based on the mobility restriction status of the relay terminal.

Specifically, in a state where the mobility restriction state of the relay terminal is a state where a non-emergency service can be provided to the remote terminal, such as Allowed Area, the first device may perform any of the following operations:

Under the condition that the non-emergency service PDU session of the remote terminal is not initiated, determining to initiate the non-emergency service PDU session of the remote terminal;

in the case that the non-emergency service PDU session of the remote terminal has been established, the non-emergency service PDU session of the remote terminal is maintained or is not processed.

Optionally, it may also be determined whether the remote terminal has a non-emergency service to be executed, where the non-emergency service PDU session of the remote terminal is initiated, maintained or not processed in the case where the remote terminal needs to establish the non-emergency service PDU session and the mobility limited state of the relay terminal is capable of supporting non-emergency service relay for the remote terminal.

In the case where the mobility restriction state of the relay terminal is a state in which Non-emergency services cannot be provided to the remote terminal, for example, the mobility restriction state of the relay terminal is Forbidden Area or Non-Allowed Area, the first device may perform any of the following operations:

Under the condition that the non-emergency service PDU session of the remote terminal is not initiated, determining that the non-emergency service PDU session of the remote terminal is not initiated;

In the case that the non-emergency service PDU session of the remote terminal has been established, it is determined to release the non-emergency service PDU session of the remote terminal.

The non-emergency service PDU session not originating the remote terminal may refer to not sending a non-emergency service PDU session establishment request to a network function entity, such as an SMF entity corresponding to the remote terminal, or canceling the non-emergency service PDU session establishment request being sent.

The processing method of the non-emergency service provided by the embodiment of the application can be applied to a Relay scene, such as a Layer 2 terminal-to-Network Relay (Layer-2 UE-to-Network Relay) scene introduced above.

According to the method for processing the non-emergency service, provided by the embodiment of the application, the mobility limit state of the relay terminal can be acquired by the first equipment through the mobility limit indication information, so that corresponding operation is determined according to the mobility limit state of the relay terminal, and the problem that when the remote terminal is connected to the relay terminal with mobility limit, the non-emergency service PDU session of the remote terminal cannot be processed can be solved.

Alternatively, the relay terminal can support emergency services.

Optionally, the first device is the remote terminal, and the second device is the relay terminal.

Specifically, the first device is a remote terminal, and the second device is a relay terminal that establishes direct communication with the remote terminal.

Optionally, the receiving mobility restriction indication information sent by the second device includes:

Specifically, the first device is a remote terminal, the second device is a relay terminal, and communication between the remote terminal and the relay terminal can be performed through a direct discovery message.

Optionally, the direct communication message includes any of the following:

Relaying the discovery message;

direct communication accept message;

Status notification message.

Specifically, for the relay discovery message, it is a direct communication message transmitted in the discovery process.

Illustratively, the discovery process in direct communication may include two modes, a mode and B mode:

A mode:

the relay terminal transmits a broadcast advertisement message (it is understood that the broadcast message is a direct communication message) in the discovery process of the a mode, the broadcast message carrying mobility restriction indication information.

B mode:

The remote terminal sends a request Solicitation message, wherein the request Solicitation message is used for requesting the relay terminal which receives the request message to return a Response message carrying mobility restriction indication information to the remote terminal; and after receiving the request message, the relay terminal returns a Response message carrying mobility restriction indication information to the remote terminal.

The direct communication acceptance message refers to that in the process of establishing the PC5 connection between the Remote UE and the Relay UE, the Remote UE sends a direct communication request (Direct Communication Request) message to the Relay UE, and the Relay UE returns a direct communication acceptance (Direct Communication Accept) message to the Remote UE, where the message includes mobility restriction indication information.

The mobility restriction indication information may be referred to as Mobility restriction indication, and it should be understood that the name of the mobility restriction indication information is not limited in the embodiment of the present application, so long as the mobility restriction indication information can be used to indicate the mobility restriction state of the relay terminal.

The status notification message refers to a direct communication message sent by the Remote UE to the Relay UE after establishing the PC5 connection between the Remote UE and the Relay UE, where the message includes mobility restriction indication information, and is used for notifying the mobility restriction status of the Relay terminal.

According to the method for processing the non-emergency service, the mobility restriction indication information is sent to the remote terminal through the direct communication message, so that the remote terminal can know the mobility restriction state of the relay terminal, and the problem that the remote terminal cannot know the mobility restriction state of the relay terminal and cannot process the non-emergency service is solved.

Specifically, the restricted state refers to Not Allowed Area, including Forbidden Area and Non-Allowed Area. A relay terminal in a restricted state cannot provide a state of non-emergency services to a remote terminal.

According to the method for processing the non-emergency service, the relay terminal can acquire the mobility restriction state of the relay terminal through the mobility restriction indication information, so that the non-emergency service PDU session is not initiated or released under the condition that the mobility restriction state of the relay terminal is restricted according to the mobility restriction state of the relay terminal, and the problem that the non-emergency service PDU session of the remote terminal cannot be processed when the remote terminal is connected to the relay terminal in the mobility restriction can be solved.

It should be understood that, when the relay terminal is in mobility limitation, the relay cannot be provided for the non-emergency service PDU session of the remote terminal, which may cause that the remote terminal waits for the relay terminal to transmit the non-emergency service data all the time after initiating the non-emergency service PDU session, but the relay terminal cannot provide the non-emergency service data when being in mobility limitation, the remote terminal does not initiate the non-emergency service PDU session or release the non-emergency service PDU session, which may avoid the remote terminal waiting for data transmission for a long time, and may avoid the non-emergency service PDU session occupying resources, thereby realizing resource saving.

the first equipment sends a first message to a Session Management Function (SMF) entity corresponding to the remote terminal, wherein the first message is used for indicating the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session; or alternatively

The first device sends a second message to an AMF entity corresponding to the remote terminal, where the second message is used to instruct the AMF entity corresponding to the remote terminal to trigger the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session.

Specifically, the remote terminal may send the first message to the SMF entity corresponding to the remote terminal, and the remote terminal may send the second message to the AMF entity corresponding to the remote terminal.

For the first message, the first message may carry a PDU session ID corresponding to the non-emergency service PDU session, and the first message may be a PDU session release request message. And after receiving the first message, the session management function SMF entity corresponding to the remote terminal releases the non-emergency service PDU session according to the first message. And under the condition that the first message carries the PDU session ID corresponding to the non-emergency service PDU session, releasing the non-emergency service PDU session corresponding to the PDU session ID.

For the second message, the second message may be a non-access stratum NAS message, where the Remote UE sends the second message to an AMF entity corresponding to the Remote UE, and the AMF entity corresponding to the Remote UE identifies a non-emergency service PDU session ID according to the second message, and triggers the SMF entity corresponding to the Remote terminal to release the non-emergency service PDU session.

For the AMF entity corresponding to the remote terminal to trigger the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session, the AMF entity corresponding to the remote terminal may send a PDU session release message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal.

The processing method of the non-emergency service provided by the embodiment of the application can solve the problem of how to release the non-emergency service PDU session of the remote terminal when the remote terminal is connected to the relay terminal with mobility limitation under the condition that the first equipment is the remote terminal and the second equipment is the relay terminal.

Optionally, the first message or the second message contains the mobility restriction indication information.

In particular, the mobility restriction indication information can indicate a mobility restriction state of a relay terminal of a message (first message or second message) receiving side, thereby triggering the message receiving side to release the non-emergency service PDU session.

Illustratively, the first message or the second message includes mobility restriction indication information, where the mobility restriction indication information indicates that a mobility restriction state of the relay terminal is a restricted state, and the message receiver can learn that the relay terminal is in the restricted state, so as to trigger the message receiver to release the non-emergency service PDU session.

Taking an example of an AMF entity corresponding to a remote terminal as a message receiver, the AMF entity corresponding to the remote terminal receives mobility restriction indication information sent by the remote terminal, and the AMF entity corresponding to the remote terminal can determine a mobility restriction state of the relay terminal based on the mobility restriction indication information, and determine that the mobility restriction state of the relay terminal does not support non-emergency services; and the AMF entity corresponding to the remote terminal determines the PDU session identifier corresponding to the non-emergency service PDU session in the PDU session information corresponding to the remote terminal.

Optionally, the PDU session information corresponding to the remote terminal may be determined according to a context of the remote terminal, where the context of the remote terminal is obtained in advance by an AMF entity corresponding to the remote terminal;

the AMF entity corresponding to the remote terminal can send a message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal, the message can carry the PDU session identifier corresponding to the non-emergency service PDU session, and the SMF can release the non-emergency service PDU session corresponding to the PDU session identifier corresponding to the non-emergency service PDU session after receiving the message.

Optionally, the first device is an access and mobility management AMF entity corresponding to the remote terminal, and the second device is an access network entity or an AMF entity corresponding to the relay terminal.

It should be understood that the AMF entity corresponding to the relay terminal is used to manage mobility information of the relay terminal, and thus a mobility restriction state of the relay terminal can be obtained, so that mobility restriction indication information can be determined and sent to the first device (the AMF entity corresponding to the remote terminal).

The relay terminal and the remote terminal can access the same access network, so when the access network entity can obtain the mobility restriction state of the relay terminal, the mobility restriction indication information is determined, and the mobility restriction indication information is sent to the first device (the AMF entity corresponding to the remote terminal).

Optionally, in the case that the first device is an access and mobility management AMF entity corresponding to the remote terminal, and the second device is an access network entity or an AMF entity corresponding to the relay terminal, the determining whether to initiate or release a non-emergency service protocol data unit PDU session of the remote terminal based on the mobility restriction status of the relay terminal includes:

Optionally, in the case that the first device is an access and mobility management AMF entity corresponding to the remote terminal and the second device is an access network entity or an AMF entity corresponding to the relay terminal, the determining to release the non-emergency service PDU session further includes:

Specifically, the first device can determine a mobility restriction state of the relay terminal based on the mobility restriction indication information, and determine that the mobility restriction state of the relay terminal does not support non-emergency services;

in the PDU conversation information corresponding to the remote terminal, the PDU conversation identification corresponding to the non-emergency service PDU conversation is used as a first PDU conversation identification;

And sending a third message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal, wherein the third message carries the first PDU session identifier, and the SMF releases the non-emergency service PDU session corresponding to the first PDU session identifier after receiving the third message.

Alternatively, the PDU session information corresponding to the remote terminal may be determined according to the context of the remote terminal.

According to the method for processing the non-emergency service, provided by the embodiment of the application, when the first equipment is the access and mobility management AMF entity corresponding to the remote terminal and the second equipment is the access network entity or the AMF entity corresponding to the relay terminal, the problem of how to realize releasing the non-emergency service session of the remote terminal when the remote terminal is connected to the relay terminal with mobility limitation can be solved.

Fig. 3 is a second flowchart of a non-emergency service processing method provided in an embodiment of the present application, as shown in fig. 3, where the non-emergency service processing method provided in the embodiment of the present application may be applied to a second device, and includes:

transmitting mobility restriction indication information to a first device;

Specifically, the second device refers to a device capable of determining or obtaining mobility restriction indication information and capable of transmitting the mobility restriction indication information to the first device. Determining the mobility restriction indication information may mean that the second device determines the mobility restriction indication information according to information related to a mobility restriction state of the relay terminal, and acquiring the mobility restriction indication information may mean that the mobility restriction indication information transmitted by the other device can be received.

The description of the first device and the mobility restriction indication information is referred to the above description, and will not be repeated here.

According to the method for processing the non-emergency service, the mobility limit indication information is sent to the first device, so that the first device can acquire the mobility limit state of the relay terminal, corresponding operation is determined according to the mobility limit state of the relay terminal, and the problem that when the remote terminal is connected to the relay terminal with mobility limit, the non-emergency service PDU session of the remote terminal cannot be processed can be solved.

Optionally, in a case where the first device is the remote terminal, the second device is the relay terminal.

Optionally, the sending mobility restriction indication information to the first device includes: and sending a direct communication message carrying the mobility limit indication information to the first device.

Optionally, the direct communication message includes any of the following:

Relaying the discovery message;

direct communication accept message;

Status notification message.

Specifically, the description of the direct communication message, the relay discovery message, the direct communication acceptance message, and the status notification message is referred to the above description, and will not be repeated here.

Optionally, in the case that the first device is an AMF entity corresponding to the remote terminal, the second device is an access network entity or an AMF entity corresponding to the relay terminal.

receiving the identification of the remote terminal sent by the relay terminal;

Specifically, the AMF entity corresponding to the relay terminal may receive the identifier of the remote terminal, and determine the AMF entity corresponding to the remote terminal according to the identifier of the remote terminal, so as to send mobility restriction indication information to the AMF entity corresponding to the remote terminal.

Specifically, taking the second device as an example of the relay terminal, when the relay terminal is in mobility restriction, if the remote terminal indicates to the relay terminal that the relay terminal is established as a non-emergency service, the relay terminal will reject the request of the remote terminal and inform the remote terminal that the relay terminal is in a mobility restriction state at present, that is, send mobility restriction indication information to the remote terminal.

For the process that the second device rejects the non-emergency service requested by the remote terminal for the access network entity or the AMF entity corresponding to the relay terminal, refer to the description and related technologies, and are not repeated herein.

The method for processing the non-emergency service provided by the embodiment of the application can refuse the establishment of the non-emergency service by the relay terminal when the remote terminal requests to establish the non-emergency service, thereby avoiding the situation that the remote terminal establishes the non-emergency service but the relay terminal cannot provide the non-emergency service for the remote terminal and avoiding resource waste.

Specifically, the mobility restriction information refers to information related to a mobility restriction state of the relay terminal, and may include an area where the relay terminal is currently located, a current mobility restriction state of the relay terminal, and the like, where the mobility restriction information may be determined by a corresponding AMF entity of the relay terminal according to location information of the relay terminal.

According to the method for processing the non-emergency service, the mobility limit indication information is determined based on the mobility limit information, and the mobility limit state of the relay terminal is indicated by the mobility limit indication information, so that the first device can acquire the mobility limit state of the relay terminal, corresponding operation is determined according to the mobility limit state of the relay terminal, and the problem that when the remote terminal is connected to the relay terminal with mobility limit, the non-emergency service PDU session of the remote terminal cannot be processed can be solved.

The following describes a method for processing non-emergency services provided by the embodiment of the present application in connection with a plurality of embodiments.

Example 1:

Fig. 4 is a third flow chart of a non-emergency service processing method provided by an embodiment of the present application, as shown in fig. 4, where the embodiment of the present application provides a non-emergency service processing method, including:

in the embodiment of the application, the remote terminal is a first device, the relay terminal is a second device,

1. Registering: the Relay UE sends a registration request (Registration Request) message to an AMF entity (Relay UE AMF) corresponding to the Relay UE, and the AMF entity corresponding to the Relay UE returns a registration acceptance (Registration Accept) message to the Relay UE, wherein the registration acceptance message contains mobility restriction information.

2. State notification: alternatively, the mobility restriction indication information may be sent by the Relay UE to the Remote UE during the status notification procedure.

If the Relay UE is currently in mobility restriction (Mobility restriction), e.g., in Forbidden Area or Non-Allowed Area, the Relay UE indicates to the Remote UE that its mobility restriction state is in a restricted state during discovery. The discovery process is divided into two types, a mode (Model a) and B mode (Model B).

In the a-mode discovery process, the Relay UE transmits a broadcast advertisement message containing mobility restriction indication information (Mobility restriction indication).

In the B-mode discovery process, the Remote UE sends a request Solicitation message to the Relay UE, which returns a Response message to the Remote UE, where the message includes mobility restriction indication information (Mobility restriction indication).

Optionally, the Relay UE may obtain or pre-configure an Emergency service (RSC) Relay service Code (RELAY SERVICE Code) from the PCF, EMERGENCY RSC for indicating that the Relay UE is capable of relaying Emergency service for the Remote UE.

Optionally, EMERGENCY RSC may also be carried in the broadcast advertisement message.

Optionally, the request Solicitation message may also carry EMERGENCY RSC corresponding to the remote terminal.

Optionally, the Response message may also carry EMERGENCY RSC corresponding to the relay terminal,

Alternatively, in the case where the Relay UE only includes EMERGENCY RSC corresponding to the Relay terminal in the broadcast handover message or the Response message, then the Remote UE will only be able to establish EMERGENCY PDU session.

3. Relay selection: the Remote UE selects an appropriate Relay UE.

Specifically, the Remote UE selects an appropriate Relay UE according to the service that needs to be executed by itself, and, for example, in the case where the Remote UE needs to execute the emergency service, selects a UE supporting the Relay service that provides the emergency service for the Remote UE as the Relay UE. The embodiment of the application does not limit how to select the Relay UE.

4. PC5 connection establishment procedure: alternatively, the mobility restriction indication information may be sent by the Relay UE to the Remote UE during the PC5 connection establishment procedure.

A PC5 connection is established between the Remote UE and the Relay UE. The Remote UE sends a direct communication request (Direct Communication Request) message to the Relay UE, and the Relay UE returns a direct communication accept (Direct Communication Accept) message to the Remote UE, wherein the direct communication accept (Direct Communication Accept) message contains mobility restriction indication information.

Alternatively, if in step 2 the Relay UE does not indicate mobility restriction indication information to the Remote UE during discovery, the Relay UE sends the mobility restriction indication information to the Remote UE through a direct communication accept (Direct Communication Accept) message.

Optionally, the direct communication request (Direct Communication Request) message may carry EMERGENCY RSC corresponding to the Remote UE.

Optionally, the direct communication accept (Direct Communication Accept) message may carry EMERGENCY RSC corresponding to the Relay UE.

Alternatively, the Relay UE only includes EMERGENCY RSC in the direct communication accept (Direct Communication Accept) message, then the Remote UE will only be able to establish the emergency services PDU session, with the understanding that the Remote UE does not initiate the non-emergency services PDU session.

5. Registration procedure (Registration procedure): the Remote UE initiates a registration procedure.

6. PDU session establishment procedure (PDU session establishment procedure):

if the Relay UE indicates to the Remote UE that the Relay UE is in a restricted state, the Remote UE can only initiate a PDU session establishment procedure for emergency services.

For the functions of the AMF entity corresponding to the Remote UE and the SMF entity corresponding to the Remote UE, reference is made to related technologies, which are not described herein.

Example 2:

Fig. 5 is a flow chart of a non-emergency service processing method provided by an embodiment of the present application, as shown in fig. 5, where the embodiment of the present application provides a non-emergency service processing method, including:

0. Relay communication: the Remote UE has established a connection with the Relay UE, and communicates with the network through the Relay UE.

Alternatively, the Remote UE may establish EMERGENCY PDU session and non-EMERGENCY PDU session simultaneously.

1. Registration process: the relay UE initiates a periodic registration (periodic registration) procedure or a mobility registration (mobility registration procedure); and 1b, the AMF entity corresponding to the Relay UE returns mobility restriction information to the Relay UE.

2. State notification: if the Relay UE finds that the mobility restriction status of the Relay UE is updated, for example, from an Allowed Area to a Non-Allowed Area, the Relay UE sends a status notification message to the Remote UE through the PC5 interface, where the status notification message includes mobility restriction indication information, and is used to indicate the current mobility restriction status of the Relay UE.

Optionally, when the Relay UE is in the restricted state, if the Relay UE indicates to the Relay UE at an access layer (AS layer) that the Relay UE establishes a non-emergency service, the Relay UE will reject the request of the Relay UE through the AS layer, and send mobility restriction indication information to the Relay UE through the AS layer, informing the Relay UE that the Relay UE is currently in the restricted state.

3. Non-emergency service PDU session release: if the Relay UE indicates mobility restriction indication information to the Remote UE in step 2 and the mobility restriction indication information indicates that the mobility restriction state of the Relay terminal is a restricted state, it indicates that the Remote UE can only perform emergency services and needs to release the non-emergency service PDU session. There are several methods:

3a, the Remote UE sends a first message to SMF (Remote UE SMF) corresponding to the Remote UE, where the first message may be a PDU session release request (PDU session release request) message.

Optionally, the first message includes mobility restriction indication information, which is used to indicate a mobility restriction state of the relay terminal, where when the mobility restriction state of the relay terminal is a restricted state, the mobility restriction indication information may enable the SMF corresponding to the Remote UE to learn that the relay terminal does not support the non-emergency service, so as to trigger the SMF corresponding to the Remote UE to release the non-emergency service PDU session.

Optionally, the first message includes release non-emergency service PDU session indication information, which is used to indicate the SMF corresponding to the Remote UE to release the non-emergency service PDU session. It should be understood that after the SMF corresponding to the Remote UE receives the release non-emergency service PDU session indication information, the non-emergency service PDU session may be directly released, without determining the mobility restriction state of the relay terminal.

3B, the Remote UE sends a second message to the AMF corresponding to the Remote UE, where the second message may be a NAS message, and the AMF entity corresponding to the Remote UE (Remote UE AMF) identifies the non-emergency service PDU session ID according to the second message, and sends a PDU session release request (PDU session release request) message to the SMF entity corresponding to the Remote terminal, to trigger the SMF entity corresponding to the Remote terminal to release the non-emergency service PDU session.

Optionally, the second message includes mobility restriction indication information, and the AMF corresponding to the Remote UE identifies a non-emergency service PDU session identifier (identity, ID), that is, the first PDU session identifier, according to the indication information, and triggers the SMF corresponding to the Remote UE to release the non-emergency service PDU session.

4. Non-emergency service PDU session release procedure: and the SMF corresponding to the Remote UE initiates a non-emergency service PDU session release process.

Example 3:

fig. 6 is a fifth flow chart of a non-emergency service processing method provided by an embodiment of the present application, as shown in fig. 6, where the embodiment of the present application provides a non-emergency service processing method, including:

In the embodiment of the application, an AMF entity corresponding to Remote UE is used as a first device, and an access network NG-RAN is used as a second device.

0. Relay communication: the Remote UE has established a connection with the Relay UE, and the Remote UE communicates with the network through the Relay UE.

2. State notification: the access network NG-RAN serves as a second device, and sends mobility restriction indication information to an AMF entity corresponding to the Remote UE serving as a first device, where the mobility restriction indication information may be carried by an N2 message.

3. Non-emergency service PDU session release: an AMF entity corresponding to the Remote UE (Remote UE AMF) identifies a non-emergency service PDU session ID according to the mobility restriction indication information, and sends a third message to an SMF entity corresponding to the Remote terminal, where the third message may be a PDU session release request (PDU session release request) message, and the PDU session release request may carry the non-emergency service PDU session ID, so as to trigger the SMF entity corresponding to the Remote terminal to release the non-emergency service PDU session.

Example 4:

Fig. 7 is a sixth flow chart of a non-emergency service processing method provided by an embodiment of the present application, as shown in fig. 7, where the embodiment of the present application provides a non-emergency service processing method, including:

In the embodiment of the application, the AMF entity corresponding to the Remote UE is the first equipment, and the AMF corresponding to the Relay UE is the second equipment.

1. The discovery process comprises the following steps: the Remote UE discovers the Relay UE through a discovery procedure.

2. PC5 connection establishment: the Remote UE and the Relay UE establish a PC5 connection.

3. The Relay UE sends a NAS message to the AMF corresponding to the Relay UE, where the NAS message includes an identifier of the Remote terminal (Remote UE ID), for example, a user permanent identifier corresponding to the Remote UE (SUbscription PERMANENT IDENTIFIER, SUPI).

4. State notification: when an AMF entity (Relay UE AMF) corresponding to the Relay UE finds that the Relay UE is in a limited state, the AMF entity (Remote UE AMF) corresponding to the Relay UE finds an AMF entity (Remote UE AMF) corresponding to the Remote terminal through an identification of the Remote terminal, and sends mobility restriction indication information to the Remote UE AMF, and the AMF corresponding to the Remote UE identifies a first PDU session identification corresponding to the non-emergency service PDU session according to the mobility restriction indication information.

5. AMF corresponding to the Remote UE triggers SMF corresponding to the Remote UE to release the non-emergency service PDU session, namely, AMF corresponding to the Remote UE sends a third message to SMF corresponding to the Remote UE, and the third message can be PDU session release message.

Optionally, the third message carries the first PDU session identifier.

6. Non-emergency service PDU session release procedure: and the SMF corresponding to the Remote UE initiates a non-emergency service PDU session release process.

The embodiment of the application solves the problem of how to process the non-emergency service PDU session of the Remote UE when the Remote UE is connected to the Relay UE supporting the emergency service and the Relay UE is in a limited state.

Referring to fig. 8, fig. 8 is a schematic structural diagram of a non-emergency service processing apparatus according to an embodiment of the present application, where the non-emergency service processing apparatus may be applied to a first device, and the apparatus includes: a first receiving unit 810 and a first determining unit 820;

The first receiving unit 810 is configured to receive mobility restriction indication information sent by the second device, where the mobility restriction indication information is used to indicate a mobility restriction state of the relay terminal;

The first determining unit 820 is configured to determine whether to initiate or release a non-emergency service protocol data unit PDU session of a remote terminal based on a mobility restriction status of the relay terminal.

the first receiving unit 810 is configured to receive mobility restriction indication information sent by the second device, and includes:

The first receiving unit 810 is configured to receive the mobility restriction indication information through a direct communication message sent by the second device.

Optionally, the direct communication message includes any of the following:

Relaying the discovery message;

direct communication accept message;

Status notification message.

Optionally, the first determining unit 820 is configured to determine whether to initiate or release a non-emergency service protocol data unit PDU session of a remote terminal based on a mobility restriction status of the relay terminal, including:

the first determining unit 820 is configured to determine not to initiate the non-emergency service PDU session or determine to release the non-emergency service PDU session in the case where the mobility restriction state of the relay terminal is a restricted state.

Optionally, the apparatus further comprises a first transmitting unit;

The first sending unit is configured to send a first message to a session management function SMF entity corresponding to the remote terminal after determining to release the non-emergency service PDU session, where the first message is used to instruct the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session; or alternatively

The first sending unit is configured to send a second message to an AMF entity corresponding to the remote terminal after determining to release the non-emergency service PDU session, where the second message is used to instruct the AMF entity corresponding to the remote terminal to trigger the SMF entity corresponding to the remote terminal to release the non-emergency service PDU session;

The first determining unit 820 is configured to determine whether to initiate or release a non-emergency service protocol data unit PDU session of a remote terminal based on a mobility restriction status of the relay terminal, and includes:

the first determining unit 820 is configured to determine to release the non-emergency service PDU session when the mobility restriction status of the relay terminal is a restricted status.

Optionally, the first determining unit 820 is further configured to determine, after determining to release the non-emergency service PDU session, a first PDU session identifier corresponding to the non-emergency service PDU session based on the mobility limit indication information and PDU session information corresponding to the remote terminal;

The first sending unit is further configured to send a third message for releasing the non-emergency service PDU session to the SMF entity corresponding to the remote terminal, where the third message carries the first PDU session identifier.

The method and the device provided by the embodiments of the present application are based on the same application conception, and because the principle of solving the problem is similar for the non-emergency service processing method and the non-emergency service processing device, and the same technical effect can be achieved, the implementation of the device and the method can be referred to each other, and the repetition is omitted.

Referring to fig. 9, fig. 9 is a second schematic structural diagram of a non-emergency service processing apparatus according to an embodiment of the present application, where the non-emergency service processing apparatus according to the embodiment of the present application may be applied to a second device, and the apparatus includes: a second transmitting unit 910;

The second sending unit 910 is configured to send mobility restriction indication information to the first device;

Optionally, the apparatus further comprises a second receiving unit and a second determining unit;

the second receiving unit is configured to receive the identifier of the remote terminal sent by the relay terminal;

The second determining unit is configured to determine an AMF entity corresponding to the remote terminal based on the identifier of the remote terminal.

Optionally, the apparatus further comprises a second reject unit;

The second rejecting unit is configured to reject, when the mobility restriction state of the relay terminal is a restricted state and the relay terminal receives a non-emergency service establishment request message sent by the remote terminal, the second device to establish the non-emergency service requested by the remote terminal.

It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice. In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a processor-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Fig. 10 is a schematic structural diagram of a first device according to an embodiment of the present application, and as shown in fig. 10, the first device includes a memory 1020, a transceiver 1000 and a processor 1010; wherein the processor 1010 and the memory 1020 may also be physically separate.

A memory 1020 for storing a computer program; a transceiver 1000 for transceiving data under the control of the processor 1010; the processor 1010 is configured to execute any operation corresponding to the processing method of the non-emergency service applied to the first device according to the obtained executable instruction by calling a computer program stored in the memory 1020, where the operation corresponds to the processing method of the non-emergency service provided by the embodiment of the present application, for example:

In particular, the transceiver 1000 is operative to receive and transmit data under the control of the processor 1010.

Wherein in fig. 10, bus interface 1040 may comprise any number of interconnected buses and bridges, and in particular, one or more processors represented by processor 1010 and various circuits of memory represented by memory 1020, coupled together. The bus interface 1040 may also connect various other circuits together, such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. Transceiver 1000 may be a number of elements, i.e., including a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including wireless channels, wired channels, optical cables, etc. For different first devices, a user interface 1030 may also be included, the user interface 1030 may also be an interface capable of interfacing with an internal connection requiring device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 1010 is responsible for managing the bus architecture and general processing, and the memory 1020 may store data used by the processor 1010 in performing operations.

Alternatively, the processor 1010 may be a CPU (central processing unit), an ASIC (Application SPECIFIC INTEGRATED Circuit), an FPGA (Field-Programmable gate array) or a CPLD (Complex Programmable Logic Device ), and the processor may also employ a multi-core architecture.

Optionally, the direct communication message includes any of the following:

Relaying the discovery message;

direct communication accept message;

Status notification message.

It should be noted that, the first device provided in this embodiment of the present application can implement all the method steps implemented in the non-emergency service processing method embodiment, and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.

Fig. 11 is a schematic structural diagram of a second device according to an embodiment of the present application, and as shown in fig. 11, the second device includes a memory 1120, a transceiver 1100, and a processor 1111; the processor 1111 and the memory 1120 may also be physically separated.

A memory 1120 for storing a computer program; a transceiver 1100 for transceiving data under the control of the processor 1111; the processor 1111 is configured to execute any of the operations corresponding to the processing method of the non-emergency service applied to the second device provided in the embodiment of the present application according to the obtained executable instructions by calling a computer program stored in the memory 1120, for example:

transmitting mobility restriction indication information to a first device;

In particular, the transceiver 1100 is configured to receive and transmit data under the control of the processor 1111.

Wherein in fig. 11, bus interface 1140 may comprise any number of interconnected buses and bridges, and in particular, one or more processors represented by processor 1111 and various circuits of memory represented by memory 1120, coupled together. The bus interface 1140 may also connect various other circuits together, such as peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. Transceiver 1100 may be a number of elements, including a transmitter and a receiver, providing a means for communicating with various other apparatus over transmission media, including wireless channels, wired channels, optical cables, etc. For a second, different device, user interface 1130 may also be included, user interface 1130 may also be an interface capable of interfacing with an inscribed desired device, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 1111 is responsible for managing the bus architecture and general processing, and the memory 1120 may store data used by the processor 1111 in performing the operations.

Alternatively, the processor 1111 may be a CPU (central processing unit), an ASIC (Application SPECIFIC INTEGRATED Circuit), an FPGA (Field-Programmable gate array) or a CPLD (Complex Programmable Logic Device ), and the processor may also employ a multi-core architecture.

receiving the identification of the remote terminal sent by the relay terminal;

It should be noted that, the second device provided in this embodiment of the present application can implement all the method steps implemented in the non-emergency service processing method embodiment, and achieve the same technical effects, and detailed descriptions of the same parts and beneficial effects as those in the method embodiment in this embodiment are omitted.

In another aspect, an embodiment of the present application further provides a processor readable storage medium, where a computer program is stored, where the computer program is configured to cause the processor to execute the method provided in the foregoing embodiments and applied to the first device, where the method includes:

Optionally, the direct communication message includes any of the following:

Relaying the discovery message;

direct communication accept message;

Status notification message.

In another aspect, an embodiment of the present application further provides a processor readable storage medium, where a computer program is stored, where the computer program is configured to cause the processor to execute the method provided in the foregoing embodiments and applied to the second device, where the method includes:

transmitting mobility restriction indication information to a first device;

receiving the identification of the remote terminal sent by the relay terminal;

The processor-readable storage medium may be any available medium or data storage device that can be accessed by a processor, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, non-volatile storage (NAND FLASH), solid State Disk (SSD)), etc.

It will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, magnetic disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These processor-executable instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims

1. A method for processing non-emergency services, applied to a first device, comprising:

2. The method for processing non-emergency services according to claim 1, wherein said first device is said remote terminal and said second device is said relay terminal;

3. The method for processing non-emergency services according to claim 2, wherein said direct communication message includes any one of:

Relaying the discovery message;

direct communication accept message;

Status notification message.

4. A method for processing non-emergency services according to claim 2 or 3, wherein said determining whether to initiate or release a non-emergency services protocol data unit PDU session of a remote terminal based on a mobility restriction status of said relay terminal comprises:

5. The method for processing the non-emergency service according to claim 4, wherein the determining to release the non-emergency service PDU session further comprises:

6. The method for processing non-emergency services according to claim 1, wherein the first device is an access and mobility management AMF entity corresponding to the remote terminal, and the second device is an access network entity or an AMF entity corresponding to the relay terminal;

7. The method for processing the non-emergency service according to claim 6, wherein the determining to release the non-emergency service PDU session further comprises:

8. A method for processing non-emergency services, applied to a second device, comprising:

transmitting mobility restriction indication information to a first device;

9. The method for processing a non-emergency service according to claim 8, wherein, when the second device is an AMF entity corresponding to the relay terminal and the first device is an AMF entity corresponding to the remote terminal, before sending the mobility restriction indication information to the first device, the method further comprises:

receiving the identification of the remote terminal sent by the relay terminal;

10. The method according to claim 8 or 9, wherein the second device refuses to establish the non-emergency service requested by the remote terminal in a case where the mobility restriction state of the relay terminal is a restricted state and the relay terminal receives the non-emergency service establishment request message transmitted by the remote terminal.

11. The method according to claim 8 or 9, wherein the mobility restriction indication information is determined based on mobility restriction information determined by an AMF entity corresponding to the relay terminal.

12. A first device comprising a memory, a transceiver, and a processor:

the memory is used for storing a computer program; the transceiver is used for receiving and transmitting data under the control of the processor; the processor is configured to read the computer program in the memory and perform the following operations:

13. A second device comprising a memory, a transceiver, and a processor:

transmitting mobility restriction indication information to a first device;

14. A non-emergency service processing apparatus, applied to a first device, comprising:

15. A non-emergency service processing apparatus, applied to a second device, comprising:

16. A processor-readable storage medium, characterized in that the processor-readable storage medium stores a computer program for causing the processor to execute the method of processing non-emergency services according to any one of claims 1 to 7 or the method of processing non-emergency services according to any one of claims 8 to 11.